Develop Bugs

Zenprise requiring Unroot

I was having issue finding a way to unroot. I did not want to use ODIN since I did not want the bloated software. I finally found the info.
http://forum.xda-developers.com/showthread.php?p=21568681#post21568681
I hope that someone will put this in the notes for Unrooting. This was the only way I found to remove Superuser 3.0.7 after removing the bloat ware.
I put this info on a Text file and copied it to Terminal Emulator.
I hope this helps someone out there.

Hi,
i was using Zenprise Connect on my cyanogen and with SuperSu it was possible de desactivate root. Connect was seeing my device as not rooted.
Since the new version of Zenprise Worx it doesn't work anymore. I have tested a lot of things and Zenprise always see my device as rooted, even if i suppress all su busybox and other rooted stuff.
Is there a way to use Zenprise on a cyanogen device ? even on unrooting totaly ?
Thanks in advance
Cédric

c-dric said:
Hi,
i was using Zenprise Connect on my cyanogen and with SuperSu it was possible de desactivate root. Connect was seeing my device as not rooted.
Since the new version of Zenprise Worx it doesn't work anymore. I have tested a lot of things and Zenprise always see my device as rooted, even if i suppress all su busybox and other rooted stuff.
Is there a way to use Zenprise on a cyanogen device ? even on unrooting totaly ?
Thanks in advance
Cédric
Click to expand...
Click to collapse
try installing xposed framework 2.4.1 from here http://repo.xposed.info/module/de.robv.android.xposed.installer, and install this module http://forum.xda-developers.com/showthread.php?t=2574647 it hasn't been tested with all apps that require no root but it is worth a shot.

Hello,
thanks for this information, it works !!!!!

Cannot root LG G3 (After Update)

Hi,
I got LG G3 (02, D855) and recently I updated as it required a software update. This removed root (it had root before, I installed root via the one click installer created by avicohh.). After this update I can no longer root, when I install SuperSU I get this dreadful error: there is no su binary installed and supersu cannot install it
I have tried one click installer + the GUI version as well, all seems to go well, but according to both scripts, but once I run SuperSU, it gives that error.
I've seen some posts which says I need to flash it or whatever, but I have no idea how to do this, prefer one click scripts!!
PS the software suite upgraded to latest version 5.0 Android.
Cheers
Asim

Sorry I can't help you but you have helped me... I too am rooted and last night the ota update downloaded and is now sitting on top of screen wanting me to install it.
I don't think I will now as would like to keep root.
Do you know how to get rid of the tick at top incase I accidentally install the update?
Regards diddle ?

diddledude said:
Sorry I can't help you but you have helped me... I too am rooted and last night the ota update downloaded and is now sitting on top of screen wanting me to install it.
I don't think I will now as would like to keep root.
Do you know how to get rid of the tick at top incase I accidentally install the update?
Regards diddle ��
Click to expand...
Click to collapse
Hi, in update center, you should be able to turn of automatic updates, also I think if you click the notification > click install later, it will ask you when to remind you, I think from this popup you should be able to abort installation.
Can't duplicate it since I already updated.

Worked asimr
Thanks for the help
Will wait till a working one click appears before I do any updates ����

Same problem as yours, after i unrooted my phone via supersu, i cant root anymore
I have tried to root the phone again in recovery mode or via adb... None of them success
Hope somebody can help :crying:

FireTV 1 unrooted?

Hi all,
I'd previously rooted, installed recovery, etc on my FireTV version 1. Everything was working great, and I thought I'd disabled updates. I turned it on recently and It somehow lost root. Everything is still installed, but can't open SuperSU, towelroot says the device isn't supported. Still says that Xposed is installed with the framework though.
The system says I'm now on 51.1.4.1_user_514013920 for some reason. Checking for system update still gives an error. What went wrong, and is there any way to fix it?
@AFTVNews, I'm mainly looking at you

Does anyone know?

If you disabled updates its probably the fact that the fire tv has updated its self, im afraid thats why su (root) isnt working & your device isn't supported because your firmware has upgraded. You have no way to root at the moment in time unless a os5 root for AFTV gen1 is created sometime in the near future? It is possible because Rbox is making a Os5 root for Gen 1.... But i think you need root already for that? My advice would be if you still want root, get a AFTV 2 while root is still possible & root/block updates & wait for the new recovery & rom being developed by Rbox which fingers crossed should be very near to be released. I still cant get over why you would want to unblock updates for when you had root & exposed framework? oh well whats done is done now.
If this helps press that thanks button

If he install clockword mod and if he can still get into it, couldn't he flash the latest rom and get root back?

That's very confusing?
Disabling updates should've been the first thing you did after rooting (presumably a long time ago if you have gen 1.)
Disabling updates, successfully or not, shouldn't've caused you to lose root. If you have CWM, your aftv should not be able to receive a stock update. Of course towel root won't work because your firmware is based on stock software that is not rootable. Are you certain you did nothing else other than disable updates?
I'm basing all of this off the assumption you have CWM. If so then just push the same firmware you currently have installed to /sdcard and flash it again. Install busybox and I'd think you'd be ok. You probably already know this but aftvnews has all rbox's prerooted roms.

Maybe you only disabled ota on your router? Have you taken it anywhere else? Or got a new router?
Sent from my SM-G900F using Tapatalk

Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...

ldeveraux said:
Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...
Click to expand...
Click to collapse
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk

deanr1977 said:
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.

ldeveraux said:
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.
Click to expand...
Click to collapse
You're not understanding. First, the firmware you have MUST have boot menu installed. Therefore you can choose to boot recovery from there. OR connect adb and reboot recovery. Adbfire simplifies this...
You should be fine to flash a prerooted rom and it should fix whatever got messed up.
Again, theres NO way youre running stock because im fairly certain rbox's recovery wont allow the installation. Theres an issue with you su no doubt but im thinking youre still rooted.

Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.

AFTVnews.com said:
Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.
Click to expand...
Click to collapse
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?

ldeveraux said:
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?
Click to expand...
Click to collapse
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3

AFTVnews.com said:
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3
Click to expand...
Click to collapse
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?

ldeveraux said:
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?
Click to expand...
Click to collapse
I haven't looked into the Google Play Store in a while. I plan to update my guide once Fire OS 5 is released to older devices, since any changes I make now likely won't work after the update.

Android Pay broken, was working.

Hey all, I am running stock US unlocked Rom 1.80.617, rooted, s-off, Verizon radio, and Android pay was working fine. Just went to use it and said it couldn't work on this system,... Yada yada.. The only thing that has changed between the last time and this time I used Android pay was that I updated to SuperSU 2.76 through Android play store and I updated AdAway through xda labs. Can someone explain to me why either of those updates would have broken AP or could it be something else? Also, is there any easy way to check if I still have systemless root? Assuming I would do that with an ADB command. Can I run the command in a terminal emulator on the phone? Don't really want to boot up the computer of I don't have to. Thanks in advance.

changed permissions of /su/bin to 751 and safetynet checker passes.. . Assume that means AP will work. Will purchase something and report back. Still unsure why AP worked before then randomly quit.
Edit: OK, safetynet checker didn't pass when i reran it, seems random when it passes or not. Anyone have any ideas?

Light1984 said:
Hey all, I am running stock US unlocked Rom 1.80.617, rooted, s-off, Verizon radio, and Android pay was working fine. Just went to use it and said it couldn't work on this system,... Yada yada.. The only thing that has changed between the last time and this time I used Android pay was that I updated to SuperSU 2.76 through Android play store and I updated AdAway through xda labs. Can someone explain to me why either of those updates would have broken AP or could it be something else? Also, is there any easy way to check if I still have systemless root? Assuming I would do that with an ADB command. Can I run the command in a terminal emulator on the phone? Don't really want to boot up the computer of I don't have to. Thanks in advance.
Click to expand...
Click to collapse
Well you screwed yourself. Adaway modified system, Android pay will not work on a modified system. That's why it require systemless root to work

Behold_this said:
Well you screwed yourself. Adaway modified system, Android pay will not work on a modified system. That's why it require systemless root to work
Click to expand...
Click to collapse
But I used Android pay fine with AdAway for a while right after you posted the 1.80.617 RUU. Installed AdAway from XDA labs and updated if through labs as well. Honestly just seemed to randomly stop working.
So if AdAway is the culprit, is there an app with similar functionality that doesn't break AP (xposed is obviously out cause it breaks AP)?

Light1984 said:
But I used Android pay fine with AdAway for a while right after you posted the 1.80.617 RUU. Installed AdAway from XDA labs and updated if through labs as well. Honestly just seemed to randomly stop working.
So if AdAway is the culprit, is there an app with similar functionality that doesn't break AP (xposed is obviously out cause it breaks AP)?
Click to expand...
Click to collapse
Installing adaway isn't the problem. using ad away is the problem. As soon as you apply ad blocking adway modifies your host file. At that point system has been modified and Android pay will fail.

Behold_this said:
Installing adaway isn't the problem. using ad away is the problem. As soon as you apply ad blocking adway modifies your host file. At that point system has been modified and Android pay will fail.
Click to expand...
Click to collapse
But I updated host files as soon as I installed AdAway when I clean flashed the 1.80.617 RUU you provided. It worked after that on two occasions, would it fix it if I change where the host file is saved (after a clean install before applying updated host files of course)? I think that's an option in AdAway, you can move it into \data.

Light1984 said:
But I updated host files as soon as I installed AdAway when I clean flashed the 1.80.617 RUU you provided. It worked after that on two occasions, would it fix it if I change where the host file is saved (after a clean install before applying updated host files of course)? I think that's an option in AdAway, you can move it into \data.
Click to expand...
Click to collapse
Yeah, i would think that should.

If anyone else is following this I believe google has changed something to kill AP with root again. I've been following another thread (for a different phone) and it seems others have experienced the same thing.
http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659/page43

System update notice

Greetings. I am already running mm on my d851 and just received an ota this morning. I have saved it and can post it too my mega off anyone wants to look at it. My question is if anyone else has gotten it yet and if it breaks our bootload/twrp?

I guess is this? - http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FWB9HI4652POATWA28CB0D6/D85130e_00_0711.kdz
Maybe July or June security patches

Probably is it. My dump its only 78mb

just received mine today .... whats this update is for ? have you updated

I have not yet, I keep telling it to remind me later since I dont want to break root/twrp

BoredKender said:
I have not yet, I keep telling it to remind me later since I dont want to break root/twrp
Click to expand...
Click to collapse
same here...

is it somekind of sec patch because i did not see any changes / improvements in it can i find details about this patch ???
---------- Post added at 07:48 PM ---------- Previous post was at 07:28 PM ----------
This update was released for the LG G3 to bring the device to android 6.0.1 with build number D85130e. This update included Google Security Enhancements, and a software stability update.

Android version is still 6.0 in this update:
Android version: 6.0
Android security patch level: 2016-07-01
Kernel version: 3.4.0
Build number: MRA58K
Software version: D85130e
Security software version: MDF v1.1 Release 2
Click to expand...
Click to collapse

Maybe this is for the quad rooter Qualcomm bugs? PS, just got mine too, waiting to see if it breaks root. If it is just updated Qualcomm drivers, maybe not.
Sent from my LG-D851 using XDA-Developers mobile app

It doesn't change the android version, kernel version, build, or security software version. I don't think that it will remove root or TWRP but I'm not trying it until someone can confirm.
Here's the issues that the update should address: https://source.android.com/security/bulletin/2016-07-01.html#security_vulnerability_summary

has anyone got any fix for that low wifi signals in MM

The update does break root and without root I can not access TWRP manager. Until a root method is found, stay away from this update.
jdmst77 said:
It doesn't change the android version, kernel version, build, or security software version. I don't think that it will remove root or TWRP but I'm not trying it until someone can confirm.
Here's the issues that the update should address: https://source.android.com/security/bulletin/2016-07-01.html#security_vulnerability_summary
Click to expand...
Click to collapse

Strange. It did not remove root for me (SU) but did blow away TWRP. I was able to re-install TWRP using the app and I was able to reboot into TWRP. So, I guess proceed at your own risk.....

I had installed "Twilight" before the update to D85130e. No problems at all but since I updated the "Screen overlay detected" don't let me use any (ANY) app that requires access to SD or SMS, so I am unable to use whatsapp, LINE, even the gallery....
I go to the permissions page and turn off and on everything but it still show up the error.
I did a hardreset and didn't work. Same error "Screen overlay detected". I cant watch videos, listen to music, etc. is just a feature phone now (unless I downgrade).
Any ideas what is going on with this problem?

mrashoo said:
has anyone got any fix for that low wifi signals in MM
Click to expand...
Click to collapse
I'm glad that I'm not the only one noticing that. I thought I had a hardware issue
jmacguire said:
The update does break root and without root I can not access TWRP manager. Until a root method is found, stay away from this update.
Click to expand...
Click to collapse
out of curiosity, what method did you use to root and are you using Chainfire's SuperSu?
boulos said:
Strange. It did not remove root for me (SU) but did blow away TWRP. I was able to re-install TWRP using the app and I was able to reboot into TWRP. So, I guess proceed at your own risk.....
Click to expand...
Click to collapse
SuperUser by the CM team or SuperSu by Chainfire or something else?

jdmst77 said:
I'm glad that I'm not the only one noticing that. I thought I had a hardware issue
out of curiosity, what method did you use to root and are you using Chainfire's SuperSu?
SuperUser by the CM team or SuperSu by Chainfire or something else?
Click to expand...
Click to collapse
SuperSU (v2.76) by ChainfireXDA

Under D, I rooted with King Root. Rebooted into TWRP and installed Chainfire's SuperSU regular. Once my phone booted, I uninstalled SuperSu and installed my pro version from the play store. So I am back to D now. Some of the cosmetic changes in E are poor so I made sure to turn off LG Update and now I do not get the nag messages about T-Mobile has an update available.
jdmst77 said:
I'm glad that I'm not the only one noticing that. I thought I had a hardware issue
out of curiosity, what method did you use to root and are you using Chainfire's SuperSu?
SuperUser by the CM team or SuperSu by Chainfire or something else?
Click to expand...
Click to collapse

jmacguire said:
Under D, I rooted with King Root. Rebooted into TWRP and installed Chainfire's SuperSU regular. Once my phone booted, I uninstalled SuperSu and installed my pro version from the play store. So I am back to D now. Some of the cosmetic changes in E are poor so I made sure to turn off LG Update and now I do not get the nag messages about T-Mobile has an update available.
Click to expand...
Click to collapse
good to hear that you still have root. losing TWRP was unexpected but since there are no kernel changes, I would have been surprised if E would unroot a device. I have the same setup as you but I haven't tried E yet. Wwith root, TWRP isn't hard to get back, just mildly annoying to have to do it again on E

I could not update the latest patch!! I have stock rooted MM Rom and custom TWRP recovery. Whenever a window pop up install update i click install and restart the phone restarts and goes to TWRP and it does not start the update process !! any body help me out from this problem how can i update ?

Should be able to force it using the LG Update tool on PC I would think