Related
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.
Coming from the simplicity of a Nexus 7 and a Moto G, I am a little confused by how the Z3TC handles recovery and flashing. After a two hour session last night I finally got CM12 20150217 running but not matter what I try, I can't seem to get Xposed 2.7 alpha1 to run (it works just fine on Cm12 on my Nexus so it ought to work, somehow).
In the god awful CM12 recovery, flashing xposed fails with an error message I remain unable to read. Flashing it with the twrp that someone integrated into the stock kernel succeeds according to the twrp status but then the xposed installer still does not see the app_process (it sees the bridge however, which I find weird and have not seen like this before).
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
In principle, I am open to going to AOSP if someone can point me to a scorpion_windy image (all I can find on FXP is scorpion for AOSP, which is another weirdness that confuses me) and feels I have better chances of getting it to work there....
Hi,
what you need to do is to install twrp recovery to the FOTA partition.
(This will also allow you update cm12 through cyanDelta, which is not possibe with the crappy cm12 recovery)
It's all decribed here: http://forum.xda-developers.com/z3-tablet-compact/development/daily-cm12-unofficial-builds-t2983400
The twrp img is actually a modified Z2 twrp, but it seems to work.
(i am writing "it seems" because i have a SGP621 myself, for this one I can say "it works").
Please note:
- It is no problem if app_process displays only ---, that is a known bug of the alpha
- not all xposed modules are working. XGELS is working for sure, if you want to test.
- You need to invoke soft reboot from within the xposed app after each flashing of the xposed zip (which you need to flash after each ROM update). Otherwise xposed will not work currently.
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Edit: Or not, a 10 s power & vol + action followed by power on lets me boot both TWRP and CM12, very strange.
Now lets see if I can get Xprivacy to do its job (for starters, the boot.img contents are different than on the GOogle/Moto devices so we shall see)
nupi said:
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Click to expand...
Click to collapse
wow, I'm really sorry to hear that ... I have no idea what might have gone wrong.
You can turn off the device by holding the power button for 7-10 seconds.
If ou want to remove twrp from the FOTA partition, simply reinstall (ONLY) FOTA from the current ftf (SGP621_23.0.1.A.0.167_CE.ftf) through flashtools.
Never mind, I got it back and TWRP flashed xposed cleanly but I can't get it to work - soft reboot does not help, either
However, the kernel seems to have the wrong WiFi drivers for the SGP611 (at the very least, I don't get WiFi anymore). Back to flashing the CM12 kernel for now... I am thinking I should go back to KitKat until someone with a little more clue figures this one out
nupi said:
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
Click to expand...
Click to collapse
Cyanogen has made the worst mistake every with CM12 and CM Recovery Testing at the same Time.
As long as Cyanogen does not develop a real Recoveryfunction to CM Recovery this crap will block much more then Xposed.
I asked a few questions in the official thread and did not resolve my issue. From replies to others in the thread I should probably try asking in the 'Discussion' thread(?) but I thought I would ask other HAM2 users here first.
Short version:
On my Ascend Mate 2 and I cannot boot after using romracer's version of xposed for sdk22 (http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979). I flash the latest version, wipe the cache, and press "reboot". It shows the boot logo, then the boot animation, then stays on the slightly animated Huawei logo indefinitely. I left it for an hour once just to see if it would change/finish.
Longer version:
(Started by making everything factory reset/stock.)
1. Got the B321 update
2. Got TWRP 2.8.7
3. Rooted with the latest SuperSU
4. Installed Viper4Android FX
5. Restored all my apps and settings with the stock backup tool
6. Flashed xposed-v71-sdk22-arm-by-romracer-20150816.zip
7. Would no longer boot. (First logo screen stays on for much longer than normal, then the Huawei animation plays, but without sound, and finally the animated Huawei logo just sits there.)
Nothing else was changed or added or modded before trying to flask xposed.
• The APK is not yet installed (not sure if that matters)
• I’ve tried the current version, as well as 70, 69, 68, and 67 for good measure
• I attempted to flash the 64 and 86 versions just in case
• I even tried a version for sdk22 posted by C3C076. This version did not even get to the animation screen and could not be removed with romracer's uninstaller (just thought I would try)
• I’ve tried waiting 10, 20 and even 60+ minutes for the boot to complete… it just sits there
• I’ve checked and rechecked and redownloaded the zip from the official (“unofficial”) first page
• I wipe the dalvik cache each and every time I flash
• After a few minutes, if connected to my computer, the initial Huawei folder window will appear (the one with Docs, drivers, and “autorun”), and my phone will show up in adb devices list in command prompt. I can even use adb commands at this point. I really believe this means something.
• To get back into my phone, each time, I have to restore the system backup or flash the uninstaller zip.
I really want a number of xposed modules! My phone works 'fine' without them, but who roots their phone for merely 'fine'. Any suggestions are appreciated.
Haven't heard of xposed working on stock lollipop EMUI . It does work on CM tho .
neocortex08 said:
I asked a few questions in the official thread and did not resolve my issue. From replies to others in the thread I should probably try asking in the 'Discussion' thread(?) but I thought I would ask other HAM2 users here first.
Short version:
On my Ascend Mate 2 and I cannot boot after using romracer's version of xposed for sdk22 (http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979). I flash the latest version, wipe the cache, and press "reboot". It shows the boot logo, then the boot animation, then stays on the slightly animated Huawei logo indefinitely. I left it for an hour once just to see if it would change/finish.
Longer version:
(Started by making everything factory reset/stock.)
1. Got the B321 update
2. Got TWRP 2.8.7
3. Rooted with the latest SuperSU
4. Installed Viper4Android FX
5. Restored all my apps and settings with the stock backup tool
6. Flashed xposed-v71-sdk22-arm-by-romracer-20150816.zip
7. Would no longer boot. (First logo screen stays on for much longer than normal, then the Huawei animation plays, but without sound, and finally the animated Huawei logo just sits there.)
Nothing else was changed or added or modded before trying to flask xposed.
• The APK is not yet installed (not sure if that matters)
• I’ve tried the current version, as well as 70, 69, 68, and 67 for good measure
• I attempted to flash the 64 and 86 versions just in case
• I even tried a version for sdk22 posted by C3C076. This version did not even get to the animation screen and could not be removed with romracer's uninstaller (just thought I would try)
• I’ve tried waiting 10, 20 and even 60+ minutes for the boot to complete… it just sits there
• I’ve checked and rechecked and redownloaded the zip from the official (“unofficial”) first page
• I wipe the dalvik cache each and every time I flash
• After a few minutes, if connected to my computer, the initial Huawei folder window will appear (the one with Docs, drivers, and “autorun”), and my phone will show up in adb devices list in command prompt. I can even use adb commands at this point. I really believe this means something.
• To get back into my phone, each time, I have to restore the system backup or flash the uninstaller zip.
I really want a number of xposed modules! My phone works 'fine' without them, but who roots their phone for merely 'fine'. Any suggestions are appreciated.
Click to expand...
Click to collapse
He is correct. You have to be on CM. EMUI will NOT allow closed to work. Flash the uninstaller zip.
icyboyice said:
Haven't heard of xposed working on stock lollipop EMUI . It does work on CM tho .
Click to expand...
Click to collapse
Thanks. I was worried that might be the case, a few days into my efforts, when I saw the "Xposed for CyanogenMod" guide posted a few days ago.
If that is the case, I suppose I have two additional questions:
1. Will installing CM mean another wipe and restore? (I'm certain I know the answer, which is of course "yes", but I thought I would ask all the same.)
I only ask because I hate having to re-do all my settings (3 email accounts in the google app, general device settings, etc), which neither the stock restore app or non-pro Titanium backup ever seems to put back.
Read through the "preview-cyanogenmod-mate-2 thread". Guess I'd have to bite the bullet.
2. Is CM worth it on its own? (And by worth it, I mean worth it for the HAM2... I can see CM's features with a quick search.)
I know I'll like being able to finally get Xposed, but I wonder if this will be an issue for getting updates like the recent B322. Or perhaps CM fixes that concern? I don't know much about it. My experience is limited to learning to root my phone for slightly more functionality on a few root apps.
Read through the "preview-cyanogenmod-mate-2 thread". Still not sure after reading about random restarts and battery issues (possibly from wake locks and/or google apps?).
Guess I'll just have to decide whether to try it after reading more comments in other threads about it.
Thanks for the help both of you!
neocortex08 said:
Thanks. I was worried that might be the case, a few days into my efforts, when I saw the "Xposed for CyanogenMod" guide posted a few days ago.
If that is the case, I suppose I have two additional questions:
1. Will installing CM mean another wipe and restore? (I'm certain I know the answer, which is of course "yes", but I thought I would ask all the same.)
I only ask because I hate having to re-do all my settings (3 email accounts in the google app, general device settings, etc), which neither the stock restore app or non-pro Titanium backup ever seems to put back.
Read through the "preview-cyanogenmod-mate-2 thread". Guess I'd have to bite the bullet.
2. Is CM worth it on its own? (And by worth it, I mean worth it for the HAM2... I can see CM's features with a quick search.)
I know I'll like being able to finally get Xposed, but I wonder if this will be an issue for getting updates like the recent B322. Or perhaps CM fixes that concern? I don't know much about it. My experience is limited to learning to root my phone for slightly more functionality on a few root apps.
Read through the "preview-cyanogenmod-mate-2 thread". Still not sure after reading about random restarts and battery issues (possibly from wake locks and/or google apps?).
Guess I'll just have to decide whether to try it after reading more comments in other threads about it.
Thanks for the help both of you!
Click to expand...
Click to collapse
For someone like you that doesn't have a lot of experience with custom Roms I would say wait till things are better.
Moody66 said:
For someone like you that doesn't have a lot of experience with custom Roms I would say wait till things are better.
Click to expand...
Click to collapse
Thanks! As excited as I am to have Xposed, I really like my EMUI (and don't want to pay for the play store one you suggested to others), I like B321s stability, and I like not changing settings often. So for now I'll wait and deal with not having trivialities like AdAway or playing Youtube in the background.
@neocortex08
You only need root on your phone to be able to install adaway. You don't need xposed.
For background playback of YouTube videos you may want to check this out
http://forum.xda-developers.com/showthread.php?t=2213945
They have a install method for those who are rooted and have xposed and those who don't .
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.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2