My wife's phone was rooted and a couple of xposed mods, but I uninstalled xposed (I think), and re-enabled all the bloatware, but the OTA keeps failing. Any ideas?
slide83 said:
My wife's phone was rooted and a couple of xposed mods, but I uninstalled xposed (I think), and re-enabled all the bloatware, but the OTA keeps failing. Any ideas?
Click to expand...
Click to collapse
Btw, I don't care about keeping root on the phone. Just looking to get KK stock.
You sure you didn't delete any system apps that came with the original Rom? What's the error message?
xdabbeb's 24 a rom
slide83 said:
My wife's phone was rooted and a couple of xposed mods, but I uninstalled xposed (I think), and re-enabled all the bloatware, but the OTA keeps failing. Any ideas?
Click to expand...
Click to collapse
Did you happen to install a custom recovery?
mjones73 said:
Did you happen to install a custom recovery?
Click to expand...
Click to collapse
Nope, just rooted
slide83 said:
Nope, just rooted
Click to expand...
Click to collapse
What error are you getting when trying to run the OTA.
slide83 said:
My wife's phone was rooted and a couple of xposed mods, but I uninstalled xposed (I think), and re-enabled all the bloatware, but the OTA keeps failing. Any ideas?
Click to expand...
Click to collapse
I had the same problem and solved it by running the Verizon updater that is on the phone:
http://forum.xda-developers.com/showpost.php?p=52013202&postcount=29
Related
I am on 4.4.2 stock. I am unlocked and rooted. When I go to install xposed the app hangs and eventually force closes. I can install xposed on custom roms but not stock. Any suggestions?
Do you have ART on?
Gus194 said:
Do you have ART on?
Click to expand...
Click to collapse
No I do not have art on.
robwege said:
I am on 4.4.2 stock. I am unlocked and rooted. When I go to install xposed the app hangs and eventually force closes. I can install xposed on custom roms but not stock. Any suggestions?
Click to expand...
Click to collapse
Install busybox installer and use the advanced install. Then try to install xposed again
waiflih said:
Install busybox installer and use the advanced install. Then try to install xposed again
Click to expand...
Click to collapse
i appreciated the help. I figured it out. Apparently when I re rooted after the upgrade to 4.4.2 it didnt actually install the supersu app. I cant beleive I missed that.
Hi all!
I wonder if anyone managed to install Xposed & Xprivacy on Lollipop? I tried to install xposed, flashed it through the recovery, restarted the phone which was apparently working fine. I installed then the xposed module manager, it was saying that xposed was installed. I restarted the phone and this time I had a bootloop.
So my question is, has anyone succeeded?
Thanks
Bootlooping
difto said:
Hi all!
I wonder if anyone managed to install Xposed & Xprivacy on Lollipop? I tried to install xposed, flashed it through the recovery, restarted the phone which was apparently working fine. I installed then the xposed module manager, it was saying that xposed was installed. I restarted the phone and this time I had a bootloop.
So my question is, has anyone succeeded?
Thanks
Click to expand...
Click to collapse
No luck... even with unlocked BL, Root, and the new Xposed 3.0 alpha3 (xposed-sdk21-arm-20150426.zip)...
Exact same symptoms. Everything else works, but only xprivacy causes the loop...
Anyone else have luck?
Well the développer of xprivacy said that it triggers a bug in xposed and that it cannot do anything before xposed gets updated (which can take time as the xposed developer only works on it as a leisure)
difto said:
Well the développer of xprivacy said that it triggers a bug in xposed and that it cannot do anything before xposed gets updated (which can take time as the xposed developer only works on it as a leisure)
Click to expand...
Click to collapse
Hey thanks for the update. Anything we can do to help expedite the bugfix?
you can do this with App Ops , it's on google play.
briarbiz said:
Hey thanks for the update. Anything we can do to help expedite the bugfix?
Click to expand...
Click to collapse
I think he suspended the development until Xposed gets updated so no unfortunately.
difto said:
I think he suspended the development until Xposed gets updated so no unfortunately.
Click to expand...
Click to collapse
Yeah, I guess it's understandable...
Thanks for the info...
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
I've tried installing Xposed several times now with no luck. I install in TWRP, reboot, and then my phone sits on a black screen with the blue light for forever until it goes to the Sprint LTE logo and then just stops there. I end up having to shut my phone down (which won't happen unless it's plugged in to charge), go back into TWRP, and then use the Xposed uninstaller. Then when I reboot, everything loads back up perfectly. I don't really know what's causing this? I apologize as I'm kind of a noob to rooting & such.
I have a Galaxy Note 5 SM-N920P on Android 6.0.1. Any advice?
(The only reason I really wanted to get Xposed is so I could install a module to bypass the root status for Snapchat...lol)
kdisn said:
I've tried installing Xposed several times now with no luck. I install in TWRP, reboot, and then my phone sits on a black screen with the blue light for forever until it goes to the Sprint LTE logo and then just stops there. I end up having to shut my phone down (which won't happen unless it's plugged in to charge), go back into TWRP, and then use the Xposed uninstaller. Then when I reboot, everything loads back up perfectly. I don't really know what's causing this? I apologize as I'm kind of a noob to rooting & such.
I have a Galaxy Note 5 SM-N920P on Android 6.0.1. Any advice?
(The only reason I really wanted to get Xposed is so I could install a module to bypass the root status for Snapchat...lol)
Click to expand...
Click to collapse
Which Xposed file did you flash?
Sent from my SCH-R220
mattzeller said:
Which Xposed file did you flash?
Sent from my SCH-R220
Click to expand...
Click to collapse
I think I downloaded from here. Xda website wasn't working last night while I was doing it.
http://android.wonderhowto.com/how-...work-android-6-0-marshmallow-devices-0166278/
kdisn said:
I think I downloaded from here. Xda website wasn't working last night while I was doing it.
http://android.wonderhowto.com/how-...work-android-6-0-marshmallow-devices-0166278/
Click to expand...
Click to collapse
If you running stock 6.0.1 and not a CM ROM you need the specialized one for Samsung. Check this thread:
http://forum.xda-developers.com/showthread.php?p=62377731
Don't forget after flashing it you should wipe caches, and it will take a little while to boot the first time after flashing Xposed
Sent from my SCH-R220
mattzeller said:
If you running stock 6.0.1 and not a CM ROM you need the specialized one for Samsung. Check this thread:
http://forum.xda-developers.com/showthread.php?p=62377731
Don't forget after flashing it you should wipe caches, and it will take a little while to boot the first time after flashing Xposed
Sent from my SCH-R220
Click to expand...
Click to collapse
I'm running stock, yes. Thank you for the link. I'll try it and then let you know!!
mattzeller said:
If you running stock 6.0.1 and not a CM ROM you need the specialized one for Samsung. Check this thread:
http://forum.xda-developers.com/showthread.php?p=62377731
Don't forget after flashing it you should wipe caches, and it will take a little while to boot the first time after flashing Xposed
Sent from my SCH-R220
Click to expand...
Click to collapse
The file you sent worked great still can't get into Snapchat though, but that's another issue. RootCloak doesn't do anything for it.
kdisn said:
The file you sent worked great still can't get into Snapchat though, but that's another issue. RootCloak doesn't do anything for it.
Click to expand...
Click to collapse
Suhide hides root from snapchat, but Snapchat doesn't want you to have Xposed. There is a work around involving backing up app data on an unrooted, no Xposed phone and restoring that app data on rooted and Xposed phone
Sent from my SCH-R220
mattzeller said:
Suhide hides root from snapchat, but Snapchat doesn't want you to have Xposed. There is a work around involving backing up app data on an unrooted, no Xposed phone and restoring that app data on rooted and Xposed phone
Sent from my SCH-R220
Click to expand...
Click to collapse
I have tried several things and have been unable to get Snapchat to login. I have a backup of a logged in Snapchat from an unrooted device and when I install it onto my rooted phone, the app just logs me out.
kdisn said:
I have tried several things and have been unable to get Snapchat to login. I have a backup of a logged in Snapchat from an unrooted device and when I install it onto my rooted phone, the app just logs me out.
Click to expand...
Click to collapse
Maybe remove Xposed, then unroot, root systemless(at least SR2), root switch, then turn off root and login. Once logged in turn root back on and install Xposed. Should work
Sent from my SCH-R220
mattzeller said:
Maybe remove Xposed, then unroot, root systemless(at least SR2), root switch, then turn off root and login. Once logged in turn root back on and install Xposed. Should work
Sent from my SCH-R220
Click to expand...
Click to collapse
I'll try that. I flashed from Odin to wipe everything off and Snapchat works, but I don't have TWRP anymore. Even without Xposed and root, even when I JUST had TWRP, Snapchat wouldn't let me log in. But I'll try what you told me and hope it works
mattzeller said:
Maybe remove Xposed, then unroot, root systemless(at least SR2), root switch, then turn off root and login. Once logged in turn root back on and install Xposed. Should work
Sent from my SCH-R220
Click to expand...
Click to collapse
So after a bunch of trouble with my phone, I'm left with what I can only assume are leftover files of Xposed that I didn't get off my phone when I flashed the uninstall file. I'm not rooted and only have TWRP, but Snapchat still refuses to let me login.
kdisn said:
So after a bunch of trouble with my phone, I'm left with what I can only assume are leftover files of Xposed that I didn't get off my phone when I flashed the uninstall file. I'm not rooted and only have TWRP, but Snapchat still refuses to let me login.
Click to expand...
Click to collapse
Maybe do a factory reset to clear those out and see if snapchat will work
Sent from my SCH-R220
mattzeller said:
Maybe do a factory reset to clear those out and see if snapchat will work
Sent from my SCH-R220
Click to expand...
Click to collapse
I ran the uninstaller for Xposed again and it seems to have wiped the rest of the files because snapchat now lets me login. Now time to follow the instructions you gave me before w/ systemless rooting my NAND is backed up too just in case I screw up again.