Need Help - Xposed not activating after reboot/Sense 6 Toolbox crash error - AT&T HTC One (M7)

Hi guys.
I don't usually post looking for help because I'm usually successful with Google and searching here on xda...but I can't seem to figure out what's wrong with my case.
Just graded from Android Rev HD 63.0 to 70.0
Everything was working great in 63...once I upgraded to 70, Xposed stopped activating on boot and so did Sense 6 Toolbox.
Here's the run down:
HTC One M7 AT&T, Rooted (Super SU 1.94), S-ON, TWRP 2.7, been successfully running 63.0 since release with no problems. As soon I upgraded to 70, Xposed doesn't want to activate after a reboot (but it says it will Update/Install just fine).
This as a result has caused Sense 6 Toolbox to stop working with this error:
(Can't post picture, but this is the statement):
Unfortunately, the process com.android.systemui has stopped.
This only comes up when I attempt a SOFT REBOOT from Xposed to try and activate the Framework...though if I keep the Framework inactive (by just rebooting), this will NOT show up.
Even tried a clean wipe and reinstall from the ground up.
Can anyone else confirm these issues so I can confirm to myself that this is still a software issue and not something I'm doing wrong?
Thanks for the help! :good:
Best regards.

I also have this same issue.

I had this issue as well. What seems to have worked for me uninstalling Xposed 2.6 and Sense 6 Toolbox, then installing an older version of Xposed (2.5)

Related

[Q]Disable Receivers -> No Boot!

Hey guys here at xda!!
I've got a little problem and i'd like to know if someone can help me fix it
So, yesterday i used Rom Toolbox to disable some receivers for some apps....nothing too special, i just disabled the ones i though weren't really needed for those apps....also some notification ones or at boot time ones i think (also i don't remember touching any startup apps because i already had handled those with startup manager free)....anyway: now reboot is stuck...at, well, reboot (bootanimation)...
Does anyone know how i can restore Rom Toolbox changes, or reenable all receivers from recovery?
Or something else which might help?
Unfortunately, i don't have either a recent nandroid nor a recent titanium backup. So switching roms would be a pain...
MY ROM: Foxhound 0.1 for Galaxy S3 based on stock 4.2.2 (kernel is stock) and i have xposed framework, just in case that might help:good:
I really appreciate your help guys! PEACE!
Reflash your rom, without a wipe, first. If you've broken the framework that will enable it to boot.
If you still can't boot due to a broken app then start in safe mode, uninstall the apps you changed then reboot.
boomboomer said:
Reflash your rom, without a wipe, first. If you've broken the framework that will enable it to boot.
If you still can't boot due to a broken app then start in safe mode, uninstall the apps you changed then reboot.
Click to expand...
Click to collapse
thanks for the reply!
safe mode (which i had never even known existen on android) appears to not be working....i mean it keeps getting stuck at boot so who knows why,
i flashed the rom, rebooted, it booted (yay) and then the usual message popped up with "updating applications x out of x", and after having finished it appears to be stuck at the same message with "opening applications under way" (translation from italian). the title of the message is "updating/upgrading android os"...
i think i might be force to flash a new rom

[Q] Xposed Framework Not Updated After Reboot

Hey all,
I tried searching for this issue, but couldn't find anything--apologies if it's been answered already. I just got my first smartphone and rooted it yesterday, so I'm new to this stuff (but in general am good w/ tech). It's a Moto X non-dev verizon, and running 4.4.
Xposed Framework (installed 2.4.1) won't stay up to date after a hard reboot (app_process is a red dash) and thus my modules don't work at bootup. There actually was an issue when I first installed Xposed: after installing and then updating and rebooting, it wouldn't say it was up to date until I did a soft reboot. Now after a hard reboot, I have to reupdate xposed and then soft reboot for modules to work. Apparently there are at least a few others with the same issue. Is this a known bug?
Any ideas? I've tried reinstalling Xposed, no go. SuperSU seems to work fine with my other apps too. Any help would be appreciated!
Thanks!
P.S. Gravitybox is hella crazy what the wizardry?
I am having the exact same problem. When I click reboot or soft boot I get a blank dialog box and then click ok but nothing ever happens and when I reboot manually from the power menu it gives me the red dashes like you said. It worked fine on my nexus 5 a while back but I'm trying it now on my galaxy tab 2 and getting this issue
ricesteamer said:
Hey all,
I tried searching for this issue, but couldn't find anything--apologies if it's been answered already. I just got my first smartphone and rooted it yesterday, so I'm new to this stuff (but in general am good w/ tech). It's a Moto X non-dev verizon, and running 4.4.
Xposed Framework (installed 2.4.1) won't stay up to date after a hard reboot (app_process is a red dash) and thus my modules don't work at bootup. There actually was an issue when I first installed Xposed: after installing and then updating and rebooting, it wouldn't say it was up to date until I did a soft reboot. Now after a hard reboot, I have to reupdate xposed and then soft reboot for modules to work. Apparently there are at least a few others with the same issue. Is this a known bug?
Any ideas? I've tried reinstalling Xposed, no go. SuperSU seems to work fine with my other apps too. Any help would be appreciated!
Thanks!
P.S. Gravitybox is hella crazy what the wizardry?
Click to expand...
Click to collapse
The newest version of Xposed (2.5) solved this, but not directly:
Without TWRP or CWM or anything, I tried to install/update the framework via recovery (flash zip automatically) -- this was a new option in the update. It didn't exactly work, but then I tried install/update normally (writing to /system) and it finally worked. No idea why, but I'm happy. I googlefu'd the crap out of this too, sigh.

Android Revolution HD 70.0 - Wrong Battery percentage reported at reboot

Hello,
I am totally new to android hacking, so thanks in advance for replying with as much details as possible.
I have an HTC One and wanted to root and install ARHD 70.0.
I rooted unlocked the bootloader, then rooted the phone. All went well.
Default install of ARHD 70.0 (with all checkboxes by default: sense6 tool box, google packages). I also checked the first 2 checkboxes for performances: ext4 setting and nosql setting. Before installing i did a wipe as recommended.
Then i installed ARHD 70.0. Installation went well too.
Upon reboot im in Sense 6 and i'm loving it.
As soon as I reboot, after about 1min, my battery level jumps to a fixed value (77% on that case) and goes down really slowly. Im 100% sure there is not tat much left because the indicator was at 50% just before i rebooted and also right after the phone restarted. After about 1min, it gets to 77% and sticks there.
I reinstalled multiple times (always with wiping first). I tried without Xposed framework and Sense 6 tool box... The issue reappeared after the first restart (from Sense, not from installation of ARHD).
I am pretty sure it's not hardware related because when i was on my unmodified HTC Once with Sense 5.5, it never happened.
I have not (afaik) modified/installed a kernel.
Do you guys know what could be the problem ?
Is there a way to see whats happening once i reboot into a log file so i can see which process affects this ? It always happens after reboot when i'm about 1min in.
Thanks for your help. Tried searching the forums, but i couldnt find anything helpful
EDIT1: AFAIK i must be S-ON since i havent changed anything regarding that
EDIT2: I also tried to update Xposed framework (because it was reporting that it was runnign an old version) through recovery (because im S-On) and then i updated Sense 6 toolbox (cause it needed an update) and it didnt fix my issue.
I

Crashes (red LED, black screen, reboot) with running Xposed

Yesterday I couldn't hold it any longer and unlocked my bootloader. Then, I rooted, flashed Xposed and run some root apps.
Every now and then, my Z4T freezes and fully reboots (Sony Xperia logo). In between, the screen turns blank and the LED flashes red 4 times. Does this have any special meaning on Xperia devices? Overheating? Or just a generic crash?
/edit: I have the feeling it is a System UI crash in my case, which then causes a total system reboot. I think so because when I try to do a Soft Reboot, which is a System UI reinitialization (or a zygote reinit?), it will also fully reboot. Tried that with the Xposed Installer and (Material) Power Menu.
/edit2: It's probably not a System UI crash, but if it is, it's definitely Xposed related. Also, soft rebooting is broken on the Z4 Tablet, it'll result in a crash and a full reboot. Right now, there is a scenario in which Xposed causes either random reboots or reboots right after booting into Android after the 'optimizing apps' stage (after wiping Cacvhe/Dalvik after flashing Xposed). Uninstalling Xposed fixes these issues. Research is ongoing, if you have any experiences yourself, please share your findings.
Hi,
I don't have the answer to this unfortunately, but I have had exactly the same issue with the blinking red light and it happened after I installed Xposed too, a few funny things have happened since I rooted and flashed Xposed....
I also get the red light if I use soft reboot but its fine with a proper full reboot. I would be interested too if anyone knows the answer to this.
D_STROY said:
Hi,
I don't have the answer to this unfortunately, but I have had exactly the same issue with the blinking red light and it happened after I installed Xposed too, a few funny things have happened since I rooted and flashed Xposed....
Click to expand...
Click to collapse
Is this with just Xposed and no active modules or apps that use root? Have you applied the Camera crash fix mentioned in the Xperia z4 tablet[root] and xposed thread?
I also get the red light if I use soft reboot but its fine with a proper full reboot. I would be interested too if anyone knows the answer to this.
Click to expand...
Click to collapse
Same here. So it looks like soft rebooting is definitely broken on the Z4T, so I think it could be the ROM or kernel. What are you running? I'm on latest stock ROM (CDA 1295-4711, Germany, Customized DE, 28.0.A.8.260 / R6A) and kernel is AndroPlus v10. Xposed is v79, SDK21, ARM64 (xposed-v79-sdk21-arm64.zip).
Right now my suspicion is on the app GMD Auto Hide Soft Keys root that casues a System UI crash...
Hey!
Had same issue, started about 3 weeks after unlocking, rooting and xposed out of nowhere ... reflashed Stock, rooted again and problem solved!
No more reboots even i set up my system ecxactly like before ...
Don´t know what was really causing the issue but reflashing helped me
Cheers
Mr. Schnabel said:
Hey!
Had same issue, started about 3 weeks after unlocking, rooting and xposed out of nowhere ... reflashed Stock, rooted again and problem solved!
No more reboots even i set up my system ecxactly like before ...
Don´t know what was really causing the issue but reflashing helped me
Cheers
Click to expand...
Click to collapse
Thanks for the feedback. This seems like a common fix so I'll try that (after I have completed my Titanium backups). I should use Flashtool, right?
jelbo said:
Yesterday I couldn't hold it any longer and unlocked my bootloader.
Click to expand...
Click to collapse
Now why did you have to go and do that jelbo that just means less people to try the root method when marshmellow is released!
Oh well...
jelbo said:
Thanks for the feedback. This seems like a common fix so I'll try that (after I have completed my Titanium backups). I should use Flashtool, right?
Click to expand...
Click to collapse
Yes, restored via Flashtool did the trick!
Downloaded the FW directly there and flashed it then rooted again with AndroPlus Kernel ....
Reboots startet after updating from V7 to V8 if i remember correctly ... when rooting then again i needet to start with V5 and updated then to V10 ... every higher Version than V5 gave me an error in ADB ....
Mr. Schnabel said:
Yes, restored via Flashtool did the trick!
Downloaded the FW directly there and flashed it then rooted again with AndroPlus Kernel ....
Reboots startet after updating from V7 to V8 if i remember correctly ... when rooting then again i needet to start with V5 and updated then to V10 ... every higher Version than V5 gave me an error in ADB ....
Click to expand...
Click to collapse
That could have worked back then maybe, but the .260 firmware apparently needs v10. I just flashed v5 and my tablet didn't boot anymore. That got fixed though, phew.
I re-flashed .260 with Flashtool, reflashed the kernel, SuperSU and Xposed. I somehow had my apps still there, so I hope that's OK for this fix.
Let's see if it's stable now...
scoobydu said:
Now why did you have to go and do that jelbo that just means less people to try the root method when marshmellow is released!
Oh well...
Click to expand...
Click to collapse
Haha, yeah... the software keys were making me mad. I could hide them with GMD Full Screen Immersive Mode, but when immersed, you can't type
/edit2: Oh noo.... first thing that happened when Android finished booting: the crash I described.
Sorry wasn't really clear i only flashed V5 to get into TWRP and then flashed V10 on latest FW. English is not my first Language but everything ok from what i read now?
Mr. Schnabel said:
Sorry wasn't really clear i only flashed V5 to get into TWRP and then flashed V10 on latest FW. English is not my first Language but everything ok from what i read now?
Click to expand...
Click to collapse
I was just a bit too hasty, no worries. English isn't my first language either.
Everything ok so far now, yeah. I re-flashed with wiping everything and this time just rooted, no Xposed. So far, so good.
jelbo said:
Is this with just Xposed and no active modules or apps that use root? Have you applied the Camera crash fix mentioned in the Xperia z4 tablet[root] and xposed thread?
Same here. So it looks like soft rebooting is definitely broken on the Z4T, so I think it could be the ROM or kernel. What are you running? I'm on latest stock ROM (.260) and kernel is AndroPlus v10. Xposed is v79, SDK21, ARM64.
Right now my suspicion is on the app GMD Auto Hide Soft Keys root that casues a System UI crash...
Click to expand...
Click to collapse
Hi Jelbo
Sorry I haven't replied sooner, haven't been on XDA for a few days! I wasn't aware of the camera fix, i'll check that out, thankyou. Aside from the camera not working, Audio settings and MusicFX have gone right up the wall, I had to freeze them because of all the FC messages popping up.....was driving me crazy in the end!
Yes I am also running the same ROM, Kernel and Xposed version that you have, and I also think that something with Xposed and the soft rebooting causes a System UI crash too, I don't know why I didn't mention it in my first reply to you as that was one of my suspicions, a soft reboot is a an unclean shutdown (I think?...) and the Z4 doesn't seem to like it!
I had some problems with Xposed modules too, I haven't got the GMD one installed but Gravitybox was the first one I installed straight away, I was really missing it without having root and aswell as numerous other modules I have installed I had the newest version of xStana running and everytime I went into the Recent apps either via softkey or BKB50 , I was getting a full system UI crash so I disabled gravitybox as I have navbar tweaks enabled....rebooted and still same issue, disabled xStana and all was fine again. So to my relief it wasn't Gravitybox and to fix the problem I installed the oldest version of Xstana and it has been working fine.
Also.....do you have or want viper4android FX installed? I just thought I'd ask because I cannot get it to work either Apk or ZiP install. I flashed the ZiP after no success with Apk and I was convinced I had bricked my beloved tablet after that, I couldn't get it to boot then it turned to bootloop and after nearly 2 days of trying alI I could think of I managed to rescue it by removing the ZiP via TWRP......I dont know if its SONY or Lollipop that causes problems but I have had things that won't play nicely it seems.....
EDIT: Sorry I just realised you asked if I had a problem with Xposed itself or wether it was with modules/apps that were active that were causing problems, I'm afraid I don't have the answer as I have had active modules as soon as I rooted and flashed Xposed.
My guess is that it is Xposed framework that is causing issues, I don't know if you have this too....but the system logs on my device have wall after wall of error code displayed in red and they nearly all mention Xposed, honestly I have never seen such a vast list that repeats over and again of errors, it made me think about uninstalling Xposed but I just can't live without it!!!
Mr. Schnabel said:
Hey!
Had same issue, started about 3 weeks after unlocking, rooting and xposed out of nowhere ... reflashed Stock, rooted again and problem solved!
No more reboots even i set up my system ecxactly like before ...
Don´t know what was really causing the issue but reflashing helped me
Cheers
Click to expand...
Click to collapse
But are you running Xposed again or not?
D_STROY said:
Hi Jelbo
Yes I am also running the same ROM, Kernel and Xposed version that you have, and I also think that something with Xposed and the soft rebooting causes a System UI crash too, I don't know why I didn't mention it in my first reply to you as that was one of my suspicions, a soft reboot is a an unclean shutdown (I think?...) and the Z4 doesn't seem to like it!
Click to expand...
Click to collapse
I don't think it's an 'unclean shutdown', as it reboots. I think a SystemUI crash has more or less the same effect as a soft (or hot) reboot. These should immediately show the boot animation, but on the Z4T they cause a full (or cold) reboot, beginning at the splash screens, showing the Sony and Android logo's.
Also.....do you have or want viper4android FX installed? I just thought I'd ask because I cannot get it to work either Apk or ZiP install. I flashed the ZiP after no success with Apk and I was convinced I had bricked my beloved tablet after that, I couldn't get it to boot then it turned to bootloop and after nearly 2 days of trying alI I could think of I managed to rescue it by removing the ZiP via TWRP......I dont know if its SONY or Lollipop that causes problems but I have had things that won't play nicely it seems.....
Click to expand...
Click to collapse
No, I don't use or intend to use that.
EDIT: Sorry I just realised you asked if I had a problem with Xposed itself or wether it was with modules/apps that were active that were causing problems, I'm afraid I don't have the answer as I have had active modules as soon as I rooted and flashed Xposed.
My guess is that it is Xposed framework that is causing issues, I don't know if you have this too....but the system logs on my device have wall after wall of error code displayed in red and they nearly all mention Xposed, honestly I have never seen such a vast list that repeats over and again of errors, it made me think about uninstalling Xposed but I just can't live without it!!!
Click to expand...
Click to collapse
I haven't installed Xposed yet on my fresh install. It's been running great so far with all kinds of root apps and tweaks. When I had the reboot problems I also had it with no Xposed modules active.
I'm very hesistant now to install Xposed, because of stories that the uninstall.zip didn't fix problems and that's the only rollback option since TWRP restore is broken.
jelbo said:
But are you running Xposed again or not?
Click to expand...
Click to collapse
Yes, like said running same setup as before the re-boots occurred. Root/Xposed/Same modules/ same apps, etc.
System was running w/o problems for about 3 weeks and out of nowhere came those re-boots. Didn´t update any app/module/etc. in this time only thing was the BK50 but i had it for about 10 days before it started acting weird so don´t know what was really causing the problems ....
Sometimes after seconds, sometimes after minutes, sometimes after hours ... out of nowhere black screen/Red light and reboot ...
Mr. Schnabel said:
Yes, like said running same setup as before the re-boots occurred. Root/Xposed/Same modules/ same apps, etc.
System was running w/o problems for about 3 weeks and out of nowhere came those re-boots. Didn´t update any app/module/etc. in this time only thing was the BK50 but i had it for about 10 days before it started acting weird so don´t know what was really causing the problems ....
Sometimes after seconds, sometimes after minutes, sometimes after hours ... out of nowhere black screen/Red light and reboot ...
Click to expand...
Click to collapse
I just flashed xposed-v79-sdk21-arm64.zip, after I was running great for a few days, rooted. Guess what? After the boot and when all the apps were 'optimized': black screen, red LED and a reboot. So, this issue is definitely caused by Xposed.. What I still don't understand is why it's working for @Mr. Schnabel. Guess something is different and the cause of my issue.
I just flashed xposed-uninstaller-20150831-arm64.zip, hopefully things will be stable again.
Anyone else running Xposed, but without issues?
/edit: seems like we're not alone in this. I'm currently searching older Xposed framework .zip's, these are somehow hard to find as the old versions are replaced with the new in the Xposed thread :S I want to try xposed-v78-sdk21-arm64.zip.
/edit2: Just tried it with xposed-v78-sdk21-arm64.zip (found on a flaky Chinese Baidu mirror) and this also resulted in a crash, very quickly after booting. I'll have to delve into how to get some logging on this so people can look into this.
/edit3: @dl12345 once compiled an unofficial v74 build that worked great on a Z3+, but a Sony ROM update killed compatibility. At least on the Z3+, according to @DHGE, who ran the unofficial v74 on his Z4 Tablet. I just read now last week he was running v78 on his Z4 Tablet, so I guess he is also running it without the rebooting issue on the latest .260 firmware...
@jelbo
typing this on my tablet:
all fine here with xposed v78, now on v79 - no random reboots
only Sony camera app is crashing, deodexing according to AndroPlus did not help. That could be a tablet issue.
DHGE said:
@jelbo
typing this on my tablet:
all fine here with xposed v78, now on v79 - no random reboots
only Sony camera app is crashing, deodexing according to AndroPlus did not help. That could be a tablet issue.
Click to expand...
Click to collapse
All right. Just to be clear, this is with:
firmware 28.0.A.8.260 (mine is CDA 1295-4711, Germany, Customized DE, R6A)
AndroPlus Kernel v10
AndroPlus' TWRP 2.8.7.0
xposed-v79-sdk21-arm64.zip
No other, special things like disabling SELinux?
I really wonder what causes the difference here. I completely re-flashed the stock firmware a few days ago, including the kernel, recovery and Xposed. First thing that happened was the crash. So it couldn't have been any other 3rd party apps or Android settings.
I then redid everything, but did not install Xposed and things run fine. As soon as I flash Xposed (have tried v78 and v79) I get the crash. I do wipe cache and Dalvik cache after I have flashed Xposed. When I uninstall Xposed, the problem is gone.
I did not do the deodex trick for the camera app this time, but that would not bother me anyway, I don't use the camera.
Do you have any idea? Life without Xposed is hard.
Here are some logs, one from a normal boot without Xposed, two with Xposed v79 flashed; an initial boot and a second boot, both of where the device crashed and rebooted.
I also filed a report on rovo89's Xposed GitHub.
From similar Sony Xposed issues I have the feeling that some of my odex files are corrupted (which ship on several Sony ROMs) and that people who are running Xposed on a Z4T just fine are running a slightly different build than me (e.g. a non German one), in which these files are OK.
jelbo said:
All right. Just to be clear, this is with:
firmware 28.0.A.8.260 (mine is CDA 1295-4711, Germany, Customized DE, R6A)
AndroPlus Kernel v10
AndroPlus' TWRP 2.8.7.0
xposed-v79-sdk21-arm64.zip
No other, special things like disabling SELinux?
Do you have any idea? Life without Xposed is hard.
Click to expand...
Click to collapse
I do not know the exact numbers of the german ROM but since I got it via XperiFirm we should have the same version.
SELinux is enforcing.
I have deactivated lots of bloatware like VideoEditor, Google apps, myxperia...
I have disabled all autostarts of apps via Xprivacy (or Titanium Backup?) that I deemed unnecessary/nosy.
DHGE said:
I do not know the exact numbers of the german ROM but since I got it via XperiFirm we should have the same version.
SELinux is enforcing.
I have deactivated lots of bloatware like VideoEditor, Google apps, myxperia...
I have disabled all autostarts of apps via Xprivacy (or Titanium Backup?) that I deemed unnecessary/nosy.
Click to expand...
Click to collapse
Thanks. More or less the same here. I disabled or froze a lot of system apps using Titanium Backup and My Android Tools Pro, based on this Xperia LP 5.x debloat script. I did miss a few, because they were not listed and I don't know what they do, so maybe one of those that is still running is the culprit here. Rather difficult to compare between you and me.
Here's the Xperifirm list as of now, by the way. Maybe I'll try the US variant.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jelbo said:
Thanks. More or less the same here. I disabled or froze a lot of system apps using Titanium Backup and My Android Tools Pro, based on this Xperia LP 5.x debloat script. I did miss a few, because they were not listed and I don't know what they do, so maybe one of those that is still running is the culprit here. Rather difficult to compare between you and me.
Here's the Xperifirm list as of now, by the way. Maybe I'll try the US variant.
Click to expand...
Click to collapse
Hi,
I just can confirm that soft reboot doesn't work. (Without Xposed installed)
Sony Xperia Z4 SGP771
Androplus Kernel V10
Twrp 2.8.7.0
SuperSu 2.46
28.0.A.8.260/R10A Customized FR
I tried xposed-v79-sdk21-arm64.zip (three modules loaded: greenify,3c toolbox pro,Ownorientation) two weeks ago and my only problem (I think) was the Sony camera app stop working, so reflash stock rom, androplus,twrp,SuperSu and restore UserData via twrp did the job.
I try to install xposed and the deodexed trick for the sony camera app next weekend if i'm not busy.

Is it worth installing Xposed Framework on Z4 Tablet?

As the topic title states..
Is is worth flashing and installing Xposed Framework on our loved Z4 Tablet(s) - or does it result in a soft brick / infinity bootloop?
Did read here somewhere that it was some trouble with getting Xposed to work properly on Z4 Tablet (?) so I rather ask you guys before taking the shot and biting the bullet..
Any suggestions / experiences om this matter, guys?
@all
Yes it's worth, actually random reboots almost went away with the latest androplus kernel. But permanent reboots are still here with after optimization apps(wipe dalvik cash) and xmod for coc no matter with xposed it or not. If you nevertheless catch a bootloop or brutal hang which are unlikely to happen, shut down your tablet(volume up and power button) boot in twrp(volume up when it boot with yellow led) and wipe cash/dalvick cash with twrp and should run fine again.
It's totally worth it as it really enhances Android. GravityBox works too, so that alone is great.
As alex009988 says, there are still random crash+reboot problems, but people seem to get these without Xposed installed as well. After flashing Xposed you'll need to wipe cache/dalvik, which causes Android to 'optimize' all of the apps when booting into Android for the 1st time after. When that's done, you'll most likely get a crash and reoboot, but after that it'll just let you enter Android.
Make sure to put the Xposed uninstall .zip file on the tablet too - in cas eof issues you can uninstall Xposed. As for Xposed itself, you'll need the official SDK21 ARM64 build.

Categories

Resources