Database Info

Xsposed warning

I thought I'd just stick this up here as a little warning to others. I have a N9005, stock rom but rooted with cf autoroot. Had phone a month with no issues what so ever, 3 days ago I decided to put xsposed on there and find some some modules. Before I found any I got a warning saying sd card umounted so decided to try sort that out. I then quickly found out the power button had gained a 5 second delay from press to any responses. Next the dialer keeps freezing and when I'm on a call the proximity sensor won't turn the screen back on for 10 seconds after I move phone away from my head. Most annoying of all is the clock app has just totally derpt. Got no alarm clock at all and clock widget keeps saying I'm in Israel!! The sd card seams to be totally dead as neither my sensation, G nexus or pc will read it now and my backups are on it so I guess today's job is finding stock rom and starting from scratch again.
All this may just only happen to me but I thought I'd put it out there as a little warning

shottle said:
I thought I'd just stick this up here as a little warning to others. I have a N9005, stock rom but rooted with cf autoroot. Had phone a month with no issues what so ever, 3 days ago I decided to put xsposed on there and find some some modules. Before I found any I got a warning saying sd card umounted so decided to try sort that out. I then quickly found out the power button had gained a 5 second delay from press to any responses. Next the dialer keeps freezing and when I'm on a call the proximity sensor won't turn the screen back on for 10 seconds after I move phone away from my head. Most annoying of all is the clock app has just totally derpt. Got no alarm clock at all and clock widget keeps saying I'm in Israel!! The sd card seams to be totally dead as neither my sensation, G nexus or pc will read it now and my backups are on it so I guess today's job is finding stock rom and starting from scratch again.
All this may just only happen to me but I thought I'd put it out there as a little warning
Click to expand...
Click to collapse
I have been using xposed for about a month since i got my Note 3. Never had any issues. So this happened even before you installed any modules?
Well xposed had been known to be tricky. Most times it works, sometimes it messes up and sometimes it gets you into a boot loop.

Yeah, was scrolling through the modules to download when the sd warning came on and all the other problems have since followed. Just want to note that I haven't installed anything else since Xposed and had no issues before installing

You installed the latest xposed version right? The previous ones are not compatible with 4.3. I've been using it with no problems.
Sent from my SM-N9005 using Tapatalk

Yeah, the latest version. What is really confusing me is why it's getting my location as Israel constantly. Doesn't matter if I'm on wifi or 4G

shottle said:
Yeah, the latest version. What is really confusing me is why it's getting my location as Israel constantly. Doesn't matter if I'm on wifi or 4G
Click to expand...
Click to collapse
The next logical question would be - Have you tried uninstalling it to see if the issues go away? If they do go away, try reinstalling it and see if you experience the same thing.
I've been using Xposed with the Wanam module and don't have any issues.

Have uninsulated. Made no difference. Factory reset made no difference either. Just had a full wipe and flashed clean stock rom. Will see how that does then will know if all is fixed

Ive had similar issues with xposed myself
~hy from germany~

Not all Xposed module is working in every phone.
You should name which Xposed framework module give you problem.
So far I using Xposed framework till now fine and not much issue.
I only use few module:
App Settings - 100% working.
Wanam Xposed - theming is working, hide smart stay, blocking mode and etc is working but not all example center clock not working since MJ6 firmware as it will give you FC after end call.
Instagram Downloader - 100% working.

Andrewtst said:
Not all Xposed module is working in every phone.
You should name which Xposed framework module give you problem.
So far I using Xposed framework till now fine and not much issue.
I only use few module:
App Settings - 100% working.
Wanam Xposed - theming is working, hide smart stay, blocking mode and etc is working but not all example center clock not working since MJ6 firmware as it will give you FC after end call.
Instagram Downloader - 100% working.
Click to expand...
Click to collapse
I never installed any modules

victorlht88 said:
Sounds more like a hardware issue.
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
It's simple. Your device is hacked by mossad.

Just to say, after a full wipe and clean flash back to stock rom all is normal again. I'm guessing just got unlucky with xposed this time. Not sure if I'll be in any rush to try again for a little while

I have xposed with a lot of modules, but xblast and 3 dot menu modules cause troubles, screen freezes and ui stops working

Mine, if this helps anyone (I've never had any problems):
App Settings
Boot Manager (Amazing)
Disable Clear Defaults Dialog
GravityBox (I disabled for messing something up - tread carefully)
GreenYoutube
NotificationMod
NotifyClean (Amazing)
Per App Hacking
Play Store Fixes
ReceiverStop (Amazing)
Tinted Status Bar (Great)
Wanam Exposed
XBatteryThemer
XBlast Tools (Great, but tread carefully)
XHaloFloatingWindow (I've not managed to get working)
Xposed Recent Tasks

What is the make of the SD card that failed? Was it SanDisk?

shottle said:
Just to say, after a full wipe and clean flash back to stock rom all is normal again. I'm guessing just got unlucky with xposed this time. Not sure if I'll be in any rush to try again for a little while
Click to expand...
Click to collapse
How do you do your full wipe?

columbo said:
What is the make of the SD card that failed? Was it SanDisk?
Click to expand...
Click to collapse
No, was a Samsung

sofes said:
How do you do your full wipe?
Click to expand...
Click to collapse
Through TWRP

Rooted Nexus not starting

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:.

Reboots all the time since the latest OTA update

I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?

You can try a factory reset.

ShadowLea said:
You can try a factory reset.
Click to expand...
Click to collapse
I know I probably should after an update anyway, but I'd hate to have to set up the tablet all over again, so I'll give it a few more days. I was wondering if anyone came accross this problem and found a different solution. Some people mentioned their ATT version crashing and how un-disabling an app has fixed it. I don't have an app called My Magazines though, so that's no good. I have a bunch of apps disabled though. Could any of them cause such funny behaviour?

I think it is a problem on several firmwares, and the devices are rooted.
I fixed it using the Xposed Framework and the Wanam addon.
Or you can try the http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 add-on.

Thanks, this seems to be it. It looks like I'll be rooting my tablet when I get home today I should have done it ages ago anyway, if only to set the desktop user agent in the browser and get rid of adds.

Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!

Tintinnuntius said:
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Click to expand...
Click to collapse
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.

Makoto1 said:
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Click to expand...
Click to collapse
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!

Tintinnuntius said:
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Click to expand...
Click to collapse
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.

Makoto1 said:
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Click to expand...
Click to collapse
I tried googling, but like I said, the official TWRP site did not have a file for p900, only p905. Here's the list of all the supported devices on their site, I only see p905 and 3g variants.
Then there's this site. I didn't realize that "v1awifi" is the part that refers to p900. I'm going to use the latest version from here today and try to get root again. If I succeed, I'll then try the Xposed package. I only had three reboots in the last 24 hours though (which is much less than before my first root attempt), so it might be a while before I can be certain the reboots are gone.
EDIT: I rooted in a few minutes without a single problem. Xposed and module installed, starting the clock for reboot-watch now I'll report back immediately if I get a reboot, or in 24h if I don't.
EDIT2: It looks like Xposed with the Samsung SystemServer Crash Fix works. The app posts notifications when a crash is prevented, and I've just had three in the last hour, with no crashes.

Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).

Makoto1 said:
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Click to expand...
Click to collapse
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.

Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
I also installed the System Server Crash Fix, but it didn't prevent the reboot. Hopefully it works for you!
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.

Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...

Makoto1 said:
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Click to expand...
Click to collapse
I went halfway between your approaches. I chose to disable Knox when asked, but I did not freeze any of the apps with Knox in the name in TB. First, I reset the default apps settings and then used TB to freeze a bunch of bloatware, but nothing with Knox in the name. The only such app currently frozen is Knox Notification Manager 1.0. Also, I never installed Wanam module, just SSCF.

Tintinnuntius said:
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem, since I upgrade my T900, I have the same behavior you described.
Read a lot and tried everything, even Xposed Installer. Nothing corrected it.
I didn't test this firmware version it without root (can't live without it!).
If what you said that you have the random reboot without root, I really think that this firmware release is buggy.
I will now return to the previous firmware.

fdu123 said:
If what you said that you have the random reboot without root, I really think that this firmware release is buggy. I will now return to the previous firmware.
Click to expand...
Click to collapse
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago

arcadia2uk said:
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Click to expand...
Click to collapse
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
---------- Post added at 10:40 AM ---------- Previous post was at 10:32 AM ----------
Tintinnuntius said:
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
Click to expand...
Click to collapse
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...

Makoto1 said:
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Click to expand...
Click to collapse
Adblock Plus version 1.2.1.325 works fine for me. It allows some unobtrusive ads through by default. If you want to block all you can, but you have to manually enable it in app settings.
If a particular app is still showing ads it sometimes helps to clear the cache.

Makoto1 said:
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
Click to expand...
Click to collapse
You could always try installing them the right way round to see if it will make a difference. I think I installed both apps at the same time, but then I opened Xposed, activated it, rebooted the tablet, then activated the module (which showed up in Xposed automatically, IIRC).
First, you should double-check that the SSCF is activated in Xposed, if it is not, it won't stop the crashes.

Systemless Instructions - How to - 09/11/2016

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!!!!!

Rerooting my s7

I'm rerooting my s7 but I need every advice I can get to make sure my phone does not bootloop I was told it was becuase if you mess with the phone to much it'll go into a bootloop but I really haven't done anything to the phone when it was rooted im not saying it's wrong I'm just saying maybe it's somthing else so if someone out there has a s7 rooted and haven't run into the loop pls leave what you did in the post pls

I've rooted countless times because of the boot loops as well until I found out that the xposed module was causing it. Every since I've rooted without xposed, I haven't had a bootloop since.

officialbambam said:
I've rooted countless times because of the boot loops as well until I found out that the xposed module was causing it. Every since I've rooted without xposed, I haven't had a bootloop since.
Click to expand...
Click to collapse
I didn't find out about xposed like 3 weeks after rooting so that coudnt be the issue

TH3B0SS said:
I didn't find out about xposed like 3 weeks after rooting so that coudnt be the issue
Click to expand...
Click to collapse
I'm almost 100% sure it's the xposed module you've installed that's causing the boot loops. If I were you, I'd uninstall the xposed module and return to stock and reroot without xposed and I'm certain that's the solution to your problem.

officialbambam said:
I'm almost 100% sure it's the xposed module you've installed that's causing the boot loops. If I were you, I'd uninstall the xposed module and return to stock and reroot without xposed and I'm certain that's the solution to your problem.
Click to expand...
Click to collapse
Well like I said during the time I was rooted I didn't install xposed but I'll give it run today when I get home

officialbambam said:
I'm almost 100% sure it's the xposed module you've installed that's causing the boot loops. If I were you, I'd uninstall the xposed module and return to stock and reroot without xposed and I'm certain that's the solution to your problem.
Click to expand...
Click to collapse
I can now confirm that it was not the xposed module I'm rooted now for like 2 to 1 mouth with xposed installed