Related
From what I have seen it can be rather difficult to take the 4.4.2 update. I am rooted using the methods from jcase and am currently on 4.4 with the correct bootloaders for the update. I have been using xposed and I know I need to flash the xposed disable zip file, but how do I do that without having TWRP or CWM? I think I have done everything else needed to get take the update (removed superuser app and turned off all root permissions.)is there anything else that needs to be done besides disable xposed?
I have a VZW DE on 4.4.2, unlocked bootloader, rooted, no custom ROM.
Was wondering if there is any way to hide the system update prompts/notifications as I'd rather wait for a more substantial upgrade (Android L).
Using root explorer I did go to etc/security/ and renamed otacerts.zip to otacerts.zip.bak to no avail. Also, there didn't seem to be anything for me to freeze in TiBu.
Not only is this a marginal upgrade imo, I just don't want to mess with going back to stock recovery, upgrading to 4.4.4, flashing TWRP, re-root, do system tweaks (e.g. replace ugly vzw 4G Icon and bars, but first check to see if someone made one compatible to 4.4.4), research whether wifi tether from xposed module still works on 4.4.4, etc. Just plain don't have the time to do all that at the moment.
Thanks in advance!
I thought I had replied to this exact question yesterday...
use a root capable file explorer, got to /system/priv-apps and rename 3C_OTA.APK
Of course, if your phone has already downloaded the file, navigate to /cache and remove it.
Reboot after making the changes.
that has prevented getting prompted in the past.
I did what Mark said.. renamed the 3c ota apk and also 3c ota odex file and confirm it will stop download and notices. if you just rename the 3c ota apk file alone and not the odex file to, you may get the download and reboot problems.. someone will have to confirm that, I gave a Moto X to my little brother running 4.4 and only renamed the 3c ota apk file and four weeks later he gave it back to me with a cracked screen and said it kept rebooting trying to update but failed because it was rooted. that's when I opened up root file explorer and noticed I did not change the odex file, I only changed the apk file. I'm running a 4.4 rooted and change both files and I never get the updates.
on my brother's new replacement phone running 4.4.2 I have it rooted with towelPie and renamed both files and seems to not be bothering me about the update now. I did let it download the new update at first attempt I went in and deleted the two files and it interrupted the download so I can confirm it will stop the download deleting those two files even when the download has already began
Out of curiosity, why wouldn't you take the update?
Sent from my Dev Edition Moto X
Schaweet said:
Out of curiosity, why wouldn't you take the update?
Click to expand...
Click to collapse
I can say for my two Non-DE Verizon Moto X phones running 4.4.2 and TowelPieRoot that I'm not taking the update for root reasons first and foremost. Until the time when a 4.4.4 root method is developed, if ever, I'll remain on 4.4.2.
I appreciate the suggestions in this thread however because I'm looking to hide these notices myself.
doitinthedirt said:
I did what Mark said.. renamed the 3c ota apk and also 3c ota odex file and confirm it will stop download and notices. if you just rename the 3c ota apk file alone and not the odex file to, you may get the download and reboot problems.. someone will have to confirm that, I gave a Moto X to my little brother running 4.4 and only renamed the 3c ota apk file and four weeks later he gave it back to me with a cracked screen and said it kept rebooting trying to update but failed because it was rooted. that's when I opened up root file explorer and noticed I did not change the odex file, I only changed the apk file. I'm running a 4.4 rooted and change both files and I never get the updates.
on my brother's new replacement phone running 4.4.2 I have it rooted with towelPie and renamed both files and seems to not be bothering me about the update now. I did let it download the new update at first attempt I went in and deleted the two files and it interrupted the download so I can confirm it will stop the download deleting those two files even when the download has already began
Click to expand...
Click to collapse
Thanks, all! I went ahead and renamed the odex as well. Rebooted and good to go!
Schaweet said:
Out of curiosity, why wouldn't you take the update?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Would have to do a whole mess of stuff, like:
disable xposed frameworks and gravity box, defrost certain system apps and vzw bloat from TiBu probably, re-install android sdk (since I had formatted PC since 4.4.2), flash stock recovery, take the OTA, reflash custom recovery, re-enable xposed and gravity box (only gravity box has since split from one module to an ICS and KK version and I still have the old version), then upgrade and tweak gravity box settings, get rid of ugly VZW 4GLTE icon with stock/nexus version (but first see if someone made one that works on 4.4.4), research whether the xposed wifi-tether module works on 4.4.4, and maybe one or two other things...
all that takes TIME which I don't have a whole lot of at the moment... and all that for the ability to pause video recording and a get a dialer that has a white background instead of black? and supposed tweaks under the hood like battery and performance, all unconfirmed? yeah, personally, I'd rather wait.
Fair enough. So you know if you flash system.img once you reinstall xposed all your gravity box settings are still there.
Sent from my Dev Edition Moto X
jamespark said:
Would have to do a whole mess of stuff, like:
disable xposed frameworks and gravity box, defrost certain system apps and vzw bloat from TiBu probably, re-install android sdk (since I had formatted PC since 4.4.2), flash stock recovery, take the OTA, reflash custom recovery, re-enable xposed and gravity box (only gravity box has since split from one module to an ICS and KK version and I still have the old version), then upgrade and tweak gravity box settings, get rid of ugly VZW 4GLTE icon with stock/nexus version (but first see if someone made one that works on 4.4.4), research whether the xposed wifi-tether module works on 4.4.4, and maybe one or two other things...
all that takes TIME which I don't have a whole lot of at the moment... and all that for the ability to pause video recording and a get a dialer that has a white background instead of black? and supposed tweaks under the hood like battery and performance, all unconfirmed? yeah, personally, I'd rather wait.
Click to expand...
Click to collapse
Schaweet said:
Fair enough. So you know if you flash system.img once you reinstall xposed all your gravity box settings are still there.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Why not just use the FULL FXZ? http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you flash the FXZ, (since it is a "Keep Data" FXZ), you don't need to take the OTA. You don't need to disable Xposed. You don't need to disable any modules - or subsequently set them back up. You don't need to flash stock recovery. You don't need to worry about any modifications you have made to /system.... And you DON'T NEED THE OTA!
And just like @Schaweet has advised -- once you re-flash TWRP, re-root, and re-install Xposed Framework, all of your Xposed modules and their respective settings are already set the way you had them....
It turns this in to about a 10-15 minute process from start to finish. WAYYYY Easier. I don't get it...
EDIT: I do see that you have the "Old" gravitybox installed, so this might require setting up the new version. But everything else stated is completely relevant.
I froze MotorolaOTA 1.0
samwathegreat said:
Why not just use the FULL FXZ? http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you flash the FXZ, (since it is a "Keep Data" FXZ), you don't need to take the OTA. You don't need to disable Xposed. You don't need to disable any modules - or subsequently set them back up. You don't need to flash stock recovery. You don't need to worry about any modifications you have made to /system.... And you DON'T NEED THE OTA!
And just like @Schaweet has advised -- once you re-flash TWRP, re-root, and re-install Xposed Framework, all of your Xposed modules and their respective settings are already set the way you had them....
It turns this in to about a 10-15 minute process from start to finish. WAYYYY Easier. I don't get it...
Click to expand...
Click to collapse
HUGE. I haven't been following any forums for several months and was not aware of this FXZ. Great to know, thanks!
Mayze23 said:
I froze MotorolaOTA 1.0
Click to expand...
Click to collapse
same
A thread already exists for this exact thing here. Please post question in Q&A in future and search before creating new threads.
Thread closed
Hi,
I seem to have managed to bootloop my Nexus 5. Yesterday I updated my Nexus to Android Lollipop (through the system update), I rooted it with CF-Root. All working well after.
However, I noticed that xposed was not activated. So I pressed on uninstall with the intention to install again. As soon as it rebooted, the device got a bootloop.
What should I do?
I tried the xposed-disabler fix but to no avail.
Thanks,
Immortali
Flash stock firmware again. I'm sure stock images are available in the N5 section.
Also, Xposed is not compatible with Lollipop so don't try to install it again unless you want to recover from another bootloop.
Sent from my C6603
Dies that mean that I will lose all data and need to reinstall all apps again?
immortali said:
Dies that mean that I will lose all data and need to reinstall all apps again?
Click to expand...
Click to collapse
I don't have an N5, but you should be able to just flash /system leaving your data intact.
If you ask in the N5 section I'm sure someone there will help you.
Sent from my C6603
You can save your data!
If you know how to flash the stock image (If not, let me know), you can just look at the "flash-all" file and search for: "fastboot -w update image-hammerhead-<VersionCode>.zip".
Then, just delete the "-w" (W stands for Wipe).
After that you can just flash with no fear, all of your data will be kept.
If you don't know how to flash a stock image or you know another way to do so that is not giving you the option to not wipe everything form your device, let me know and I'll send you a guide (well, actually, I will translate you a guide from another language ).
Hope I helped and sorry for my English
OmerElbaz said:
If you know how to flash the stock image (If not, let me know), you can just look at the "flash-all" file and search for: "fastboot -w update image-hammerhead-<VersionCode>.zip".
Then, just delete the "-w" (W stands for Wipe).
After that you can just flash with no fear, all of your data will be kept.
If you don't know how to flash a stock image or you know another way to do so that is not giving you the option to not wipe everything form your device, let me know and I'll send you a guide (well, actually, I will translate you a guide from another language ).
Hope I helped and sorry for my English
Click to expand...
Click to collapse
I'll try that
I did something else:
I did a Nandroid backup, Flash Stocked and then restored the data part only. It is still in the bootloop, therefore I am presuming that the data is actually corrupted.
Can I edit a nandroid backup that is saved on my pc and remove xposed from it?
I think teh lesson here is when moving from one version of Android to another you should do a clean install, either that or just dirty flash over the after a system wipe. Either way I struggle to see how this is an Xposed issue..
OmerElbaz said:
If you know how to flash the stock image (If not, let me know), you can just look at the "flash-all" file and search for: "fastboot -w update image-hammerhead-<VersionCode>.zip".
Then, just delete the "-w" (W stands for Wipe).
After that you can just flash with no fear, all of your data will be kept.
If you don't know how to flash a stock image or you know another way to do so that is not giving you the option to not wipe everything form your device, let me know and I'll send you a guide (well, actually, I will translate you a guide from another language ).
Hope I helped and sorry for my English
Click to expand...
Click to collapse
Please note that even without the -w flag, if it flashes over userdata.img then that's a wipe.
cmstlist said:
Please note that even without the -w flag, if it flashes over userdata.img then that's a wipe.
Click to expand...
Click to collapse
I didn't knew that actually, what exactly does it wipes?
And still it's pretty much the best you can do... I think
Argh, did exactly the same with the same result. So it's an XPosed issue.
Installed Lollipop OTA on my Nexus 7 WiFi 2013 with XPosed installed. Everything fine and running for a few days.
A few hours ago I decided to remove the XPosed framework from inside the XPosed installer and rebooted -> bootloop.
Strange that this happens after removing XPosed.
OmerElbaz said:
I didn't knew that actually, what exactly does it wipes?
And still it's pretty much the best you can do... I think
Click to expand...
Click to collapse
Userdata.img covers the entire data partition including internal SD, installed apps and app data. Flashing Userdata.img is equivalent to a full data and storage wipe.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:11 AM ---------- Previous post was at 08:07 AM ----------
Inferi0r said:
Argh, did exactly the same with the same result. So it's an XPosed issue.
Installed Lollipop OTA on my Nexus 7 WiFi 2013 with XPosed installed. Everything fine and running for a few days.
A few hours ago I decided to remove the XPosed framework from inside the XPosed installer and rebooted -> bootloop.
Strange that this happens after removing XPosed.
Click to expand...
Click to collapse
All the modifications that Xposed originally made to your system were reverted by the OTA. I'm sure what happened was the Xposed installer held onto backups of the system files it had modified. When you "uninstalled" Xposed it replaced some proper Lollipop system files with backups that came from KitKat. No wonder it bootlooped.
Since it corrupted system files, what you really need to do is reflash the system.img of Lollipop in fastboot. Then it should boot fine without data loss. Then reroot if you want to.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
Userdata.img covers the entire data partition including internal SD, installed apps and app data. Flashing Userdata.img is equivalent to a full data and storage wipe.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:11 AM ---------- Previous post was at 08:07 AM ----------
All the modifications that Xposed originally made to your system were reverted by the OTA. I'm sure what happened was the Xposed installer held onto backups of the system files it had modified. When you "uninstalled" Xposed it replaced some proper Lollipop system files with backups that came from KitKat. No wonder it bootlooped.
Since it corrupted system files, what you really need to do is reflash the system.img of Lollipop in fastboot. Then it should boot fine without data loss. Then reroot if you want to.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Are you sure about the wipe?
Cuz I think I already used this method once "without wiping" (For sure used it WITH wiping b4 but I'm not sure I also used without..) and if I really used it this way then I'm pretty sure it didn't wiped any of my data (I may be wrong, though, let me know if it's 100% wipes).
Thanks for all the suggestions, I managed to reboot my Nexus 7 without any loss of userdata.
With help of the Nexus Root Toolkit v1.9.8 I flashed the system.img from the razor-lrx21p-factory-ba55c6ab.zip onto my device in bootloader mode. Within 3 minutes I was up and running again.
That's all it takes to fix the bootloop.
Ok, but the question is "What to do to uninstall Xposed after Lollipop Update ?"
db77 said:
Ok, but the question is "What to do to uninstall Xposed after Lollipop Update ?"
Click to expand...
Click to collapse
You don't do anything. If the update succeeded and your device boots successfully, then the update already removed Xposed.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
You don't do anything. If the update succeeded and your device boots successfully, then the update already removed Xposed.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Some people who try to uninstal Xposed, have bootloop.
I haven't uninstall Xposed and I wait for an update for Lollipop... because my Nexus 5 works fine without uninstall Xposed. But it don't work...
db77 said:
Some people who try to uninstal Xposed, have bootloop.
I haven't uninstall Xposed and I wait for an update for Lollipop... because my Nexus 5 works fine without uninstall Xposed. But it don't work...
Click to expand...
Click to collapse
What doesn't work? The OTA? Lollipop? Xposed?
If you did the OTA and the OS works, then just remove the Xposed Installer app and your Xposed modules. Xposed itself is no longer installed so don't take any further steps.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
What doesn't work? The OTA? Lollipop? Xposed?
If you did the OTA and the OS works, then just remove the Xposed Installer app and your Xposed modules. Xposed itself is no longer installed so don't take any further steps.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Xposed don't work under Lollipop.
On my Nexus 5, Xposed is always present but don't work, because ART et not Dalvik.
It has not been uninstalled...
db77 said:
Xposed don't work under Lollipop.
On my Nexus 5, Xposed is always present but don't work, because ART et not Dalvik.
It has not been uninstalled...
Click to expand...
Click to collapse
What makes you say Xposed is still there? The files that were patched when you installed Xposed under KitKat have been replaced by the Lollipop upgrade. Hence it's gone.
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?
When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
idbl_fanatic said:
When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
Click to expand...
Click to collapse
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
WOW thank you, I didn't know that TWRP did this.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
Ok, I am a little confused, I am trying to apply the MRA58K from LMY48T OTA found here: http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 in the ZIP file, I am not finding system.img, or boot.img
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
idbl_fanatic said:
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
Click to expand...
Click to collapse
yup
simms22 said:
yup
Click to expand...
Click to collapse
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
idbl_fanatic said:
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
Click to expand...
Click to collapse
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
zelendel said:
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
Click to expand...
Click to collapse
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
idbl_fanatic said:
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
Click to expand...
Click to collapse
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
zelendel said:
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
Click to expand...
Click to collapse
That makes sense, maybe I'll go to MMB29K instead.
Systemless root or systemless exposed?
Sent from my Nexus 6 using XDA-Developers mobile app
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
putridfoetus said:
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
Click to expand...
Click to collapse
Thank you, I just reinstalled 6.0.1 MOB30M and it works!
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
cL0uD` said:
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
Click to expand...
Click to collapse
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
idbl_fanatic said:
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
Click to expand...
Click to collapse
Yes, used, Great job, Mr Chainfire