Guys i have a moto g, running 4.4.4 stock android and i cant find the way to install the xposed framework.
When i click on install/update it installs correctly but when y reboot it just goes to boot loop, i tried all the installs methods, via recovery, manually and all xposed versions and nothing changes. after flashing the xposed disabler zip i get the green 54 on XposedBridge.jar and the red -- on app_process.
at first i was running 4.4.3 but i updated to 4.4.4 via OTA to see if i was able to solve it but nothing.
I have the boorloader unlockd, i run the root cheker i dont know whats going wrong
thanks
Dalvik?
NotLutzik said:
Dalvik?
Click to expand...
Click to collapse
you mean wipe dalvik cache?? i wipe them many times and nothing
petervil said:
you mean wipe dalvik cache?? i wipe them many times and nothing
Click to expand...
Click to collapse
No, he means if you are using Dalvik or ART? Xposed framework doesn't work with ART runtime.
Im using dalvik!
Sent from my XT1032 using XDA Free mobile app
Root
Have you verified Root access since you installed the OTA update?
Yes it still works
Sent from my XT1032 using XDA Free mobile app
petervil said:
Yes it still works
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
lokoxlrock said:
Have you verified Root access since you installed the OTA update?
Click to expand...
Click to collapse
4.4.4 fixes the root exploit. Are you sure you still have root access?
If you can't install Xposed after running the tool, you don't have temporary write access and Xposed won't work.
However if you still can root, this is an issue with the root and not Xposed. Check the TowelPieRoot forum post.
P.S.
AFAIK the dev doesn't have a Moto G to test the exploit on, so it's not officially working on that device.
Related
Curious to see if anyone else has lost root after the latest supersu update? Rebooting did not change anything. I'm unable to use any root apps (xposed, root explorer, etc).
Any ideas?
Thx!
Sent from my XT1060 using Tapatalk
jco23 said:
Curious to see if anyone else has lost root after the latest supersu update? Rebooting did not change anything. I'm unable to use any root apps (xposed, root explorer, etc).
Any ideas?
Thx!
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
You should tell is if you are using a root exploit (and which one), what android version you are on, and whether or not you are BL-Unlocked.
I can tell you that my unlocked devices had no issues updating SuperSU, and root apps still work fine.
(I'm guessing you are locked since your signature says "Status 0")....but please confirm.
samwathegreat said:
You should tell is if you are using a root exploit (and which one), what android version you are on, and whether or not you are BL-Unlocked.
I can tell you that my unlocked devices had no issues updating SuperSU, and root apps still work fine.
(I'm guessing you are locked since your signature says "Status 0")....but please confirm.
Click to expand...
Click to collapse
sorry. correct locked. on 4.4.2 with root exploits.
but I got it back after installing other superuser apps.
Sent from my XT1060 using Tapatalk
jco23 said:
sorry. correct locked. on 4.4.2 with root exploits.
but I got it back after installing other superuser apps.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Oh, great! So problem solved, or are you seeking a solution to work with the most recent SuperSU?
I would rather use supersu, but so long as super user from click clockworkmod works, its all the sane for me.
Thx for the reply though.
I had to uninstall supersu, install super user, attempt to install it, reboot, make sure have root access via root explorer, install xposed, install adaway, soft reboot.
Sent from my XT1060 using Tapatalk
I factory reset my Nexus 5 on stock Lollipop. Put TWRP recovery on it, rooted it. Flashed the xposed zip. Phone won't go past the boot screen. What am I doing wrong??
scottharris4 said:
I factory reset my Nexus 5 on stock Lollipop. Put TWRP recovery on it, rooted it. Flashed the xposed zip. Phone won't go past the boot screen. What am I doing wrong??
Click to expand...
Click to collapse
I guess a module is incompatible with your phone but I may be wrong (just my opinion). You are going through a bootloop. I had one of these last week and had to disable xposed to uninstall it. I think you can find it in /storage/emulated/0/Android/data/de.robv.android.xposed.installer/files/Xposed-Disabler-Recovery.zip I got the info from this link: https://seo-michael.co.uk/how-to-disable-xposed-installer/ flashed the uninstaller with my twrp recovery, rebooted, uninstalled incompatible module, installed xposed again via xposed installer app and your done (if what I said is the case). Hope this helps. Good luck.
No, it's not an incompatible module. My phone won't boot as soon as I flash xposed. It has nothing to do with modules.
scottharris4 said:
No, it's not an incompatible module. My phone won't boot as soon as I flash xposed. It has nothing to do with modules.
Click to expand...
Click to collapse
Sorry I don't know anything else. I would try it anyway.
Sent from Boost Mobile Moto G (xt1031) using XDA Mobile App
dirty_smurf45 said:
Sorry I don't know anything else. I would try it anyway.
Sent from Boost Mobile Moto G (xt1031) using XDA Mobile App
Click to expand...
Click to collapse
There are no modules installed after a factory reset! I can't try that method when it's impossible.
scottharris4 said:
There are no modules installed after a factory reset! I can't try that method when it's impossible.
Click to expand...
Click to collapse
I'm just trying to help you get past the bootloop since idk what the problem is (it was just an opinion). If you installed Xposed, you get the uninstall zip file. That disables Xposed for you to fix it.
Sent from Boost Mobile Moto G (xt1031) using XDA Mobile App
I installed Xposed, and a module that thought (knock on) I think it was not compatible, to restart the device, it gives boot loop, clean the dalvik and it starts, if I reboot again, boot loop return. Any solution? :crying: my phone is a xperia z2
Starxd said:
I installed Xposed, and a module that thought (knock on) I think it was not compatible, to restart the device, it gives boot loop, clean the dalvik and it starts, if I reboot again, boot loop return. Any solution? :crying: my phone is a xperia z2
Click to expand...
Click to collapse
You have to uninstall the module to fix it. If you're on Kitkat then I think there should be a zip in Android/data/com.somexposedstuff and somewhere in there. Idk about lollipop
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
Its a Lollipop
Starxd said:
Its a Lollipop
Click to expand...
Click to collapse
I don't know how to disable in on lollipop (even though i'm using it). According to this thread: http://forum.xda-developers.com/xpo...-framework-t3039371/post59082375#post59082375 you can uninstall iy withouth wiping data.
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
dirty_smurf45 said:
I don't know how to disable in on lollipop (even though i'm using it). According to this thread: http://forum.xda-developers.com/xpo...-framework-t3039371/post59082375#post59082375 you can uninstall iy withouth wiping data.
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
Click to expand...
Click to collapse
I did the following: with Root Explorer googled the word "Xposed" appeared some files, deleted all, restarted, same thing
Starxd said:
I did the following: with Root Explorer googled the word "Xposed" appeared some files, deleted all, restarted, same thing
Click to expand...
Click to collapse
You're on your bootlooped phone? If so, just disable and uninstall the module that caused the bootloop. I really don't know how to do this on lolliop. Maybe posting in Xposed General? I t would be the appropriate location for this thread.
Starxd said:
I did the following: with Root Explorer googled the word "Xposed" appeared some files, deleted all, restarted, same thing
Click to expand...
Click to collapse
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
dirty_smurf45 said:
You're on your bootlooped phone? If so, just disable and uninstall the module that caused the bootloop. I really don't know how to do this on lolliop. Maybe posting in Xposed General? I t would be the appropriate location for this thread.
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
Click to expand...
Click to collapse
I had only excluded files containing "Xposed" in the name with Root Explorer, but remained the files described in this post: http://forum.xda-developers.com/showpost.php?p=58964632&postcount=2258
Made as described, restarted, he updated one last time and went back to normal. Thanks for your help. : D
No problem. Remember to uninstall the incompatible application.
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
So this morning I got this maintenance update and now I'm being told that an update is available and that this install is differed. When I click on "select to continue update" I'm told my system is up to date. I've already wiped cache, which did not help. Anyone else experiencing this?
KWKSLVR said:
So this morning I got this maintenance update and now I'm being told that an update is available and that this install is differed. When I click on "select to continue update" I'm told my system is up to date. I've already wiped cache, which did not help. Anyone else experiencing this?
Click to expand...
Click to collapse
Are you unlocked and rooted?
Nope, totally stock Verizon 4.4.4. I'm so far out of the loop, I didn't even know I could unlock and root in the first place.
Anyone have a fxz for this update? I have it too, but I am rooted with twrp.
Sent from my XT1060 using Tapatalk
T-Keith said:
Anyone have a fxz for this update? I have it too, but I am rooted with twrp.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
There does not appear to be an FXZ for this.
You can try flashing stock Recovery.img onto your phone and take it. Unlike other OTA's that failed due to Xposed, this one did not give me any issues installing with Xposed still enabled.
NOTE: I'm unlocked bootloader, rooted, running TWRP, with Xposed instaled (MotoXNetActivity module installed). I haven't made any other modifications. I only run apps that require root like AdFree, wifi tether for root, Root Explorer, etc.
KidJoe said:
There does not appear to be an FXZ for this.
You can try flashing stock Recovery.img onto your phone and take it. Unlike other OTA's that failed due to Xposed, this one did not give me any issues installing with Xposed still enabled.
NOTE: I'm unlocked bootloader, rooted, running TWRP, with Xposed instaled (MotoXNetActivity module installed). I haven't made any other modifications. I only run apps that require root like AdFree, wifi tether for root, Root Explorer, etc.
Click to expand...
Click to collapse
Thanks, I think this answered my questions in the other thread.
Is there a risk to try running the update with stock recovery and other Xposed modules like Gravity Box? Would they fail similarly to a failed system check like I've had in the past for removing/renaming system apps and such?
Here's the download link for the factory image at the usual place: https://dl.google.com/dl/android/aosp/hammerhead-mmb29s-factory-6bfcdfa4.tgz
Amazed to see that no one created a thread for this (I guess). I know that this is only a month security bug fixing, but still, sometimes they fix other things beyond that.
If anyone notice more bug fixes (or more bugs!!!) beside the security ones, glad to report.
does anyone manage to root it with superSU 2.66?
onesolo said:
Amazed to see that no one created a thread for this
Click to expand...
Click to collapse
Probably because other threads have the link already...
aslam_ said:
does anyone manage to root it with superSU 2.66?
Click to expand...
Click to collapse
Yes. It works without problems.
Sent from my Nexus 5 using XDA Free mobile app
damijanp said:
Yes. It works without problems.
Click to expand...
Click to collapse
So, one only needs to have TWRP and flash latest systemless SuperSu, right?!
EddyOS said:
Probably because other threads have the link already...
Click to expand...
Click to collapse
It's not about the link!!! It's about a thread to discuss this new factory image!!
onesolo said:
So, one only needs to have TWRP and flash latest systemless SuperSu, right?!
Click to expand...
Click to collapse
Yes.
aslam_ said:
does anyone manage to root it with superSU 2.66?
Click to expand...
Click to collapse
Yes. I now have Android 6.0.1 (MMB29S), SuperSU 2.66 and ElementalX 6.0.7.
What the difference with mmb29k?
faighter said:
What the difference with mmb29k?
Click to expand...
Click to collapse
Monthly security update.
tuncan said:
Yes. I now have Android 6.0.1 (MMB29S), SuperSU 2.66 and ElementalX 6.0.7.
Click to expand...
Click to collapse
I'm now on 6.0.1 MMB29K, SuperSU 2.65, and ElementalX 6.07 and intend to update to MMB29S, SuperSU 2.66, same ElementalX. Were/are you running Xposed? I'm wondering if I should uninstall it first and then reinstall afterwards. Thanks
Yes, it worked for me. After update, I flashed elementsX 6.07, then SuperSU 2.66.
PhilipTD said:
I'm now on 6.0.1 MMB29K, SuperSU 2.65, and ElementalX 6.07 and intend to update to MMB29S, SuperSU 2.66, same ElementalX. Were/are you running Xposed? I'm wondering if I should uninstall it first and then reinstall afterwards. Thanks
Click to expand...
Click to collapse
I tried today with xposed and the new factory, NFC service started crashing (i flashed the new system img without deleting data).
So i rebooted again in twrp, flashed the xposed uninstaller zip, then wiped dalvik/cache, flashed xposed installer, wiped dalvik/cache again. Now it's working fine.
ezio84 said:
I tried today with xposed and the new factory, NFC service started crashing (i flashed the new system img without deleting data).
So i rebooted again in twrp, flashed the xposed uninstaller zip, then wiped dalvik/cache, flashed xposed installer, wiped dalvik/cache again. Now it's working fine.
Click to expand...
Click to collapse
Did you wipe cache and dalvik the first time?
I have problems with the update :crying:
Before updating, I had the phone in "alarms only" mode; I flashed the new factory image, and now I can't disable it anymore! I tried both using the notification pane, and the volume rocker, but the setting doesn't switch off...
Any ideas?
PhilipTD said:
Did you wipe cache and dalvik the first time?
Click to expand...
Click to collapse
Yes i did (i also did a fastboot erase for cache, system and boot partitions).
pgptheoriginal said:
I have problems with the update :crying:
Before updating, I had the phone in "alarms only" mode; I flashed the new factory image, and now I can't disable it anymore! I tried both using the notification pane, and the volume rocker, but the setting doesn't switch off...
Any ideas?
Click to expand...
Click to collapse
Weird issue. I'd try a factory reset.
I figured out how to disable it: I added a rule to enable Do Not Disturb for calendar events, then created an event lasting one minute. At the end of the event, the phone was back to "All notifications"; the toggle works fine now.
Sent from my Nexus 5 using Tapatalk
Does it fix the syncing/notification issues ?
PhilipTD said:
I'm now on 6.0.1 MMB29K, SuperSU 2.65, and ElementalX 6.07 and intend to update to MMB29S, SuperSU 2.66, same ElementalX. Were/are you running Xposed? I'm wondering if I should uninstall it first and then reinstall afterwards. Thanks
Click to expand...
Click to collapse
No, I don't have Xposed at the moment.
Another minor issue is that WiFi seems to be always on, looking at the battery usage graph, even when it's set to be off (WiFi scanning is disabled), and even when the phone is in airplane mode!
I don't know how to check if it's actually always on, but I noticed this both before and after the latest security update.
Sent from my Nexus 5 using Tapatalk