Related
So i was Rooted on NB4 and after being unable to do the KK update OTA I manually installed it through recovery and it worked. After rebooting after the KK update was installed I still have the "Custom" padlock on the boot-animation and to my surprise the SuperUser app is still on my phone. I have tried to go into Application Manager to attempt to uninstall it but there is no uninstall option: Only the option to "force stop" and "turn off." If i try and open the SU app it just says "there's no SU binary installed. I've checked in Odin Mode and Knox is still 0x0, Binary say "Offiial" and Status is "Custom."
Anyone have any idea how to remove the "Custom" status and SU App?
Try doing a factory reset in recovery, and wiping the cache in recovery.
Tried that 2 times already. Also just went to set up ISIS wallet and I get an error message saying that "This phone has been rooted, ISIS is not supported"
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I am same situation and also want to know.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
It's almost acting as if the phone is rooted but there is no Root access or binary. I'm gonna attempt to install the update again and see what happens.
Reinstalled update and still SU is installed. I just want to get this thing back to stock
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Well when you root it installs certain files. When you update without unrooting, those files never get erased completely. Traces are left behind. Now that you've updated and don't have root access to remove them, you're stuck with them. You can try reverting back to mj5 (if it's possible because I don't know anyone tried yet) and updating again. Or you can patiently wait for root access to come along for the latest release.
2 routes that I see.
The XDA method of reverting back to MJ5 with Odin (but stop before rooting it)
or
megalomaniac's MJ5 for Safestrap. Install SS, install MJ5 to the stock slot. Reboot and you'll have to set the whole phone up again (AT&T Ready2Go will run), then you'll get the NB4 update almost immediately. If that won't load 4.4.2, at least it'll look like a stock NB4 (no "Custom" padlock) and Samsung (at BB) or AT&T will reflash it with their tool - which will let it accept the update to 4.4.2.
Here's what I did...
I went from the 4.4.2 leak back to MJ5 - no root - then accepted NB4 OTA. Then used Kingo 1.18 to root NB4. Explicitly copied all of the files from fix.zip and updated permissions.
Before accepting 4.4.2 OTA - go into SuperSu and go to options - fully uninstall root - then reboot.
Root will be gone - now proceed with 4.4.2 OTA (may need to set clock ahead or factory reset to trigger OTA download) and it installed w/o any issues.
Leak -> MJ5 stock/no root -> NB4 OTA -> root -> apply fix.zip -> Unroot -> 4.4.2 OTA
HTH - good luck!
Rukbat said:
2 routes that I see.
The XDA method of reverting back to MJ5 with Odin (but stop before rooting it)
or
megalomaniac's MJ5 for Safestrap. Install SS, install MJ5 to the stock slot. Reboot and you'll have to set the whole phone up again (AT&T Ready2Go will run), then you'll get the NB4 update almost immediately. If that won't load 4.4.2, at least it'll look like a stock NB4 (no "Custom" padlock) and Samsung (at BB) or AT&T will reflash it with their tool - which will let it accept the update to 4.4.2.
Click to expand...
Click to collapse
lehighkid said:
Here's what I did...
I went from the 4.4.2 leak back to MJ5 - no root - then accepted NB4 OTA. Then used Kingo 1.18 to root NB4. Explicitly copied all of the files from fix.zip and updated permissions.
Before accepting 4.4.2 OTA - go into SuperSu and go to options - fully uninstall root - then reboot.
Root will be gone - now proceed with 4.4.2 OTA (may need to set clock ahead or factory reset to trigger OTA download) and it installed w/o any issues.
Leak -> MJ5 stock/no root -> NB4 OTA -> root -> apply fix.zip -> Unroot -> 4.4.2 OTA
HTH - good luck!
Click to expand...
Click to collapse
What fix are you referring to? I'm on stock rooted NB4 with safe strap but I am thinking about going back to stock rom slot. Un installing safestrap. Then using SU to remove root. Then use king to u root after SU is gone. What do you think about that?
Sent from my SAMSUNG-SM-N900A using Tapatalk
If you un-root with superuser, you can't un-root with kingo too. Because you already un-rooted.
why are you giving up root?
I see so many people trying to go to stock KK but they will lose root forever - no? Why not use Knoxraid and have both (unless you are selling / taking it back)? Sorry - I'm a bit confused by this mass exodus from root ...
I am referring to the fix posted here: http://forum.xda-developers.com/showthread.php?t=2699321
It contains some system files to replace and a script.
I did not use SafeStrap at all.
rawb123456 said:
What fix are you referring to? I'm on stock rooted NB4 with safe strap but I am thinking about going back to stock rom slot. Un installing safestrap. Then using SU to remove root. Then use king to u root after SU is gone. What do you think about that?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Dont use the mj5 restore if you're on official 4.4.2 im pretty sure it wont work ( you may brick)
Sent from my GT-I9300 using xda app-developers app
Hey guys. I've been holding off on KK until the root came out so it sounds like I can finally make the swap. My questions are more concerned with going from 4.3 MJ5 to 4.4.2. Currently I have my MJ5 rooted, along with apps like TB, Greenify, Xposed, etc.
If I do the OTA (currently disabled in TB) I assume it will upgrade to KK, keep all my apps, and also take away root. However, what about the fact xposed is installed without root? Or say the frozen apps I have in TB? What happens to them? Will I need to first uninstall Xposed and TB before installing the OTA or can I safely move to an unrooted KK before applying the new towelroot?
Thanks
First of all if your on 4.3 mj5 you have to update to 4.3 nb4. Then again you will have to update to 4.4.2 nc2.
The first scenario is updating to nb4. If your rooted you will lose it, but you'll update. The problem starts when you want to update to nb4. If you have deleted any system apps in mj5 your update will probably fail. If it works superuser will remain installed but useless. Same with xposed etc... so then you can re-root with towellroot. You'll need to uninstall superuser and reinstall superuser version 1.99 because the previous version won't work. Then your xposed and whatnot will need to be updated but still work.
If your update to nc2 fails you need to find the thread in the general section that restores mj5. Then again update to nb4, and again to nc2. Then root and reinstall xposed etc.....
If I were you I'd restore any frozen or uninstalled apps with titanium. Uninstall any apps requiring root like xposed etc... Then un-root mj5 and pray you update all the way thru.
440bro said:
First of all if your on 4.3 mj5 you have to update to 4.3 nb4. Then again you will have to update to 4.4.2 nc2.
The first scenario is updating to nb4. If your rooted you will lose it, but you'll update. The problem starts when you want to update to nb4. If you have deleted any system apps in mj5 your update will probably fail. If it works superuser will remain installed but useless. Same with xposed etc... so then you can re-root with towellroot. You'll need to uninstall superuser and reinstall superuser version 1.99 because the previous version won't work. Then your xposed and whatnot will need to be updated but still work.
If your update to nc2 fails you need to find the thread in the general section that restores mj5. Then again update to nb4, and again to nc2. Then root and reinstall xposed etc.....
If I were you I'd restore any frozen or uninstalled apps with titanium. Uninstall any apps requiring root like xposed etc... Then un-root mj5 and pray you update all the way thru.
Click to expand...
Click to collapse
I was afraid you were going to say that. I guess it wont be the end of the world but will definitely be time consuming. So if I restore all hidden apps (didnt delete any), unroot, etc, once I turn the OTA services back on, which should it download? Or can I manually flash a version from somewhere on the net?
Also there is no way to avoid the nb4 route and go right to nb2? Thanks
http://forum.xda-developers.com/showthread.php?t=2786043
Sent from my SM-N900A using Tapatalk
thanks. is there a file for nb4 though or will the OTA bring me there? I believe I have to do MJ5 to NB4 to NC2?
Kingo has an unroot option might try unfreezing all your apps and removing all your root apps and settings then running unroot I'm really curious if this will work.
My wife's phone is rooted mj5 and I'd like to update but my wife won't let me so I've been wondering the best way to not lose all my settings
Sent from my XT907 using XDA Free mobile app
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
I've decided to get my phone ready to accept the (hopefully soon) OTA update for my 2013 X. Right now it's on 4.4.4, bootloader unlocked (thanks Sunshine!), and rooted. I had it rooted to take advantage of Xposed and Secure Settings with Tasker integration. I also used TitaniumBackup to freeze the Verizon and some Moto apps I never used.
Currently, I have uninstalled every Xposed module I downloaded, then unistalled Xposed itself and finally the Xposed installer app. After that I went into Titanium and defrosted everything that was frozen. Now I have a fair amount of updates coming in from the Play store for all those apps that were frozen. Should I go ahead and update them?
From what I've read, there's been talk on whether or not I have to un-root my phone. I thought I just had to use the toolkit to flash back the stock recovery? That should be the only thing left to do? What about some apps that are device administrators like Cerberus? Do I need to remove them from that list?
Thank you for any advice. I plan on flashing stock recovery when I get home this evening.
Generally speaking an OTA will probably fail if apps it expects to be present are missing or modified in the /system partition. I don't know if having additional items (like Cerberus) will halt the OTA or not. Custom recovery may also interfere with the OTA.
It sounds like you already did all the work, but I personally wouldn't have done any of that until the OTA was actually rolling out. I know they said it will be soon, but it could still be weeks away. I wouldn't give up my phone that was setup how I like it, but that's just my preference.
When the OTA drops, if you try and install it will do all of the validation before it installs anything. If the validation fails, it will tell you it has an error and it won't work. Then you'll have to fix whatever was modified, or reflash the stock firmware to be compatible with the OTA.
I don't believe updating the apps is necessary. I don't even think they need to be active (you can use the Disable function in the App Info screen to hide them), they just need to be present in your /system folder with the correct signature, is how I understand it.
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?