LMAO!I know that a lot of people use the Twrp on their S7 Edge. Do you have a particular reason? Never mind its off topic here.
Sent from my SM-N910T3 using Tapatalk
LMAO!I know that a lot of people use the Twrp on their S7 Edge. Do you have a particular reason? Never mind its off topic here.
Are you running a stock rom? I only ask becsuse installing Xposed on a stock Samsung rom will bootloop it. If you are stock, flashing the uninstaller should fix it.
Sent from my SM-N910T3 using Tapatalk
I don't have that luxury,I have an S7 edge so i can't have TWRP
---------- Post added at 04:56 PM ---------- Previous post was at 04:55 PM ----------
When i flashed with flashfire, i had a systemui force close
This is only True when it comes to devices that are not rooted.
If the device is properly rooted, then this statement is false.
If your S7 Edge is properly rooted, i would recommend installing BusyBox (if you haven't already done so).
In addition, have you looked at the following thread that applies to the rooting and XPosed installation (amongst other things) of the S7 Edge while keeping the Stock ROM?
GUIDE: ROOT, install XPOSED, and UNROOT/returning to stock a Galaxy S7 or S7 Edge by psouza4
Good Luck and Happy New Year!
Sent using the d2vzw Communicator from the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
Are you running a stock rom? I only ask becsuse installing Xposed on a stock Samsung rom will bootloop it. If you are stock, flashing the uninstaller should fix it.
Sent from my SM-N910T3 using Tapatalk
I don't have that luxury,I have an S7 edge so i can't have TWRP
---------- Post added at 04:56 PM ---------- Previous post was at 04:55 PM ----------
When i flashed with flashfire, i had a systemui force close
You know you are in the thread of Xposed for Samsung devices, this version is not intended to bootloop on stock Samsung rom (TouchWiz), it is just optimized for it.
Therefore your claim is not true.
---------- Post added at 06:36 PM ---------- Previous post was at 06:29 PM ----------
Can you be a little more specific does the systemui force close happen before, during or after flashing ?
Have you also tried clearing dalvik/cache ?
Is it only systemui that force closes or are there more processes or apps that force closes ?
Can you provide some log file of force close in the form of logcat ?
Don't know how to do it, the logcat,once I unlock the phone,the system fc. I'm gonna try to wipe Dalvik and cache this time
Don't know how to do it, the logcat,once I unlock the phone,the system fc. I'm gonna try to wipe Dalvik and cache this time
---------- Post added at 08:47 PM ---------- Previous post was at 08:09 PM ----------
It worked after I wiped Dalvik & Cache... Is there a way to have the nav bar from Gravity box without having a systemui fc?
Don't know about that but I know Gravitybox is an app that can cause problems with custom roms and/or Xposed as they are already heavily modified.
Good to know. Thank you very muchAre you running a stock rom? I only ask becsuse installing Xposed on a stock Samsung rom will bootloop it. If you are stock, flashing the uninstaller should fix it.
This is only True when it comes to devices that are not rooted.
If the device is properly rooted, then this statement is false.
My apologies. I thought I was in the Official rovo89 thread and was only repeating what I read:You know you are in the thread of Xposed for Samsung devices, this version is not intended to bootloop on stock Samsung rom (TouchWiz), it is just optimized for it.
Therefore your claim is not true.
---------- Post added at 06:36 PM ---------- Previous post was at 06:29 PM ----------
Can you be a little more specific does the systemui force close happen before, during or after flashing ?
Have you also tried clearing dalvik/cache ?
Is it only systemui that force closes or are there more processes or apps that force closes ?
Can you provide some log file of force close in the form of logcat ?
So, am I right to assume that this thread is one of the "work arounds" rovo89 was referring to?rovo89 said:Known issues:
- Bootloops on Samsung stock ROMs.That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
It's OK and yes as I already mentioned and as stated in the OP this version is optimized for Samsung devices.:good:Good to know. Thank you very much
Sent from my SM-N910T3 using Tapatalk
---------- Post added at 04:17 PM ---------- Previous post was at 03:59 PM ----------
My apologies. I thought I was in the Official rovo89 thread and was only repeating what I read:
So, am I right to assume that this thread is one of the "work arounds" rovo89 was referring to?
Again, my apologies
Sent from my SM-N910T3 using Tapatalk
This article is the newest, which I have found:
Download the module you want... go to modules on the app and activate it. Then reboot and it should workG900M running stock Android 6.0.1.... Started without bootloop, but no module works.
Any suggestions on how the modules work?
I did a new test and it worked, actually it's a module that I wanted to install that did not work well.Download the module you want... go to modules on the app and activate it. Then reboot and it should work
dalvik.vm.dex2oat-filter=everything
dalvik.vm.image-dex2oat-filter=everything
Excellent response. I am honored to be in the presence of a Lineage team member (truly). I've had many problems with Xposed and quit trying to use them in one of my basic ROMs some time ago.
I am impressed so far with the performance of 14.1. And the space it freed up from all the Sammy stuff on the stock
I'm looking for good things from your team and have yet to be disappointed. Now I need to break it so I can really get under the hood.
Great work team,