Database Develop

Using TWRP recovery with non-rooted phone?

Hi Guys,
My company uses Good For Enterprise for email, which requires a phone to not be rooted. Well I was using Xposed and Rootcloak to hide root, but it appears an update patched that exploit. So I flashed the SBF for 4.4.2 and have Good running. Well I wanted to be able to use TWRP to go back to my rooted backups, but once I push TWRP to my device, my STOCK unrooted fresh SBF'ed received a "SuperSU Installer" in my apps and also a persistent notification wanting me to install SuperSU through Google Play or TWRP. Good then failed the Root check and locked me out. So I thought I could push the stock recovery back and it would go away, but nope, no dice. Any ideas? FWIW I'm running a DE Moto X from Verizon, unlocked bootloader on 4.4.2 system and bootloader.

dkoon1987 said:
Hi Guys,
My company uses Good For Enterprise for email, which requires a phone to not be rooted. Well I was using Xposed and Rootcloak to hide root, but it appears an update patched that exploit. So I flashed the SBF for 4.4.2 and have Good running. Well I wanted to be able to use TWRP to go back to my rooted backups, but once I push TWRP to my device, my STOCK unrooted fresh SBF'ed received a "SuperSU Installer" in my apps and also a persistent notification wanting me to install SuperSU through Google Play or TWRP. Good then failed the Root check and locked me out. So I thought I could push the stock recovery back and it would go away, but nope, no dice. Any ideas? FWIW I'm running a DE Moto X from Verizon, unlocked bootloader on 4.4.2 system and bootloader.
Click to expand...
Click to collapse
Seems you did everything right BUT when TWRP ask if you wanna install root or superuser.. forget which it says. Just say no. Then you should be root free. Hope that helps!

drago10029 said:
Seems you did everything right BUT when TWRP ask if you wanna install root or superuser.. forget which it says. Just say no. Then you should be root free. Hope that helps!
Click to expand...
Click to collapse
Thanks, but when I was in TWRP recovery it did ask me to root, and I said no; but it still had the "SuperSU Installer" in the app drawer, and couldn't be removed.

dkoon1987 said:
Thanks, but when I was in TWRP recovery it did ask me to root, and I said no; but it still had the "SuperSU Installer" in the app drawer, and couldn't be removed.
Click to expand...
Click to collapse
hmm, well if you say you came from stock, flashed TWRP and SU installed itself. than maybe just removing root would work. There's a guide for that, probably in the general thread. also, I read that there is a way to load multiple ROMs that's stickied in one of the threads. That could be exactly what you need!!
Don't remember which thread so you have to find it.

Sent a new phone with 4.3....what would you do?

So I was having issue with my note 3 ( bluetooth issues ) I upgraded to 4.4.2
AT&T sent me a new / refurb phone and it has 4.3 on it.
So Im curious on what you guys would do?
Upgrade to 4.4.2 and stick with all this stupid bloatware
or
Root, and rom it?
If that latter, does anyone have any links to do that ( I used to do it with my S2, S3 and S4 )
thank s

Root it. It's not worth the grief to upgrade it to 4.4.2.
You can root it and use safestrap to install custom ROMs, or just enjoy the stock setup with root.
Sent from my locked down Note 3 via the tapatalk app

ROOT AND ROM it!
I was ROOTED and ROM'd, but I got bit by the OTA Upgrade bug... I went through all the hassle of downgrading, unrooting, resetting, then upgrading.
Now I've got the fresh new bloated OTA official 4.4.2 and NO ROOT.

Should I use Kingo? is that still safe for the Note 3 on 4.3?

well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal

Root it!
I rooted with Kingo, no problems, the first day I got the Note 3 and took the Nb4 update. I was so lucky to catch the KK update and froze it mid-download with ttb. I am so glad!! I wouldn't be able to use this thing without root. I have installed safestrap and roms without issue. (staying on 4.3 roms mind you)

scojosmac said:
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Click to expand...
Click to collapse
try uninstalling ss then install it again, make sure it is 3.71 not 3.72. 3.71 doesnt need busybox if im not mistaken.

scojosmac said:
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Click to expand...
Click to collapse
I am going to use Kingo tomorrow as well I think. How does get root? Will it have superuser on it after it roots or do you have to put it on the phone yourself?
Thanks.

Krunk83 said:
I am going to use Kingo tomorrow as well I think. How does get root? Will it have superuser on it after it roots or do you have to put it on the phone yourself?
Thanks.
Click to expand...
Click to collapse
kingo installs supersu. when supersu installs, click on it and choose disable knox, presto!

i upgraded to nc2 and want to downgrade to mj5 now.. any method ?

anuragsodhi1 said:
i upgraded to nc2 and want to downgrade to mj5 now.. any method ?
Click to expand...
Click to collapse
no downgrades from official ota nc2 sir, no root method and no unlocked bootloader.

scojosmac said:
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Click to expand...
Click to collapse
Did you try rebooting into recovery via a power menu? That is what the tutorial says it should do. Hold power to bring up the menu and it should then have an option to reboot into recovery. I am going to try safestrap too I think.

Lost root after latest supersu update

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

Hide 4.4.4 System Update?

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

Flashable OTA?

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