Database Develop

[Q] Issues with the LG Esteem Exploit

I've been viewing these forums for quite sometime just never posted before. I was one of the people with the LG Revolution that lost the Super One Click Root when the OOA Update hit over the summer.
I have SU still installed and its been updated even though I can not gain root access and since I do not have root access I am unable to uninstall it. I have tried the One Click Root Tool for the LG Esteem after upgrading to GB. It say's that its completed but Root Check denies the fact it is rooted.
I tried Super One Click and it states the device is in fact rooted but when I try to use any root access apps it states "Unable to write". Any ideas on why it still wont allow the root to edit the read/write access for my device?
Thank you,
Mike

hey :9 I'm having the same issue. Heres to hoping someone figures it out

Ronin_EMT said:
I've been viewing these forums for quite sometime just never posted before. I was one of the people with the LG Revolution that lost the Super One Click Root when the OOA Update hit over the summer.
I have SU still installed and its been updated even though I can not gain root access and since I do not have root access I am unable to uninstall it. I have tried the One Click Root Tool for the LG Esteem after upgrading to GB. It say's that its completed but Root Check denies the fact it is rooted.
I tried Super One Click and it states the device is in fact rooted but when I try to use any root access apps it states "Unable to write". Any ideas on why it still wont allow the root to edit the read/write access for my device?
Thank you,
Mike
Click to expand...
Click to collapse
Do you know how to use adb?
Sent from my VS910 4G using xda premium

I'm from the Esteem side and some people were having the same problem after the superuser unroot fiasco and people couldn't re-root with the original one click because it did not clear the old su. Check over on Android forums/Esteem/All things root section. It was fixed by adding a few command lines to the script to clear the old su and give you the new su and binaries. HTH
Sent from my LG-MS910 using Tapatalk

aplusgfx said:
I'm from the Esteem side and some people were having the same problem after the superuser unroot fiasco and people couldn't re-root with the original one click because it did not clear the old su. Check over on Android forums/Esteem/All things root section. It was fixed by adding a few command lines to the script to clear the old su and give you the new su and binaries. HTH
Sent from my LG-MS910 using Tapatalk
Click to expand...
Click to collapse
Ty this worked wonders! I found it rather fast. Only problem with this guys batch is the fact you have to manually reboot your device for it to work. After I rebooted my apps were asking for SU access!
Here is a link for anyone else suffering from the unable to root because of SU already locked on your device.
androidforums.com/esteem-all-things-root/435750-one-click-root-updated-final-w-superuser-3-0-6-binary-3-0-3-download.html
Just remember after you've run the batch file to unplug your device and reboot.

Lost root after flashing SmoothROM 4.4

Hey guys. I got my grouper yesterday, I'm hoping for a warm welcome
The first thing I did when I took it out of the box was fire it up, unlocked and rooted. When I rooted, I flashed SuperSU flashable. I also flashed CWM touch. After that I flashed SmoothROM 4.4, and I was solid. I installed all of my usual apps, then went to do what I call debloating, (Looking for apps I don't use such as voicedialer.apk, and deleting them) using root browser (/system/app). I noticed it wouldn't delete, then tried another app that requires root permissions. Nothing. I got suspicious, then re-downloaded root checker. "Sorry! You're device does not have proper root access!" What happened? Is this just me, or is this a widespread problem with this ROM? I'd like to keep this ROM if possible. Is there a way to re-root my device (more or less)? Thanks, a response or any help would be very much appreciated.
Sent from my Nexus 7 using xda premium

Rom specific questions need to be posted in that rom's thread. Do not start new threads about custom rom issues.

LiquidPlatinum said:
Hey guys. I got my grouper yesterday, I'm hoping for a warm welcome
The first thing I did when I took it out of the box was fire it up, unlocked and rooted. When I rooted, I flashed SuperSU flashable. I also flashed CWM touch. After that I flashed SmoothROM 4.4, and I was solid. I installed all of my usual apps, then went to do what I call debloating, (Looking for apps I don't use such as voicedialer.apk, and deleting them) using root browser (/system/app). I noticed it wouldn't delete, then tried another app that requires root permissions. Nothing. I got suspicious, then re-downloaded root checker. "Sorry! You're device does not have proper root access!" What happened? Is this just me, or is this a widespread problem with this ROM? I'd like to keep this ROM if possible. Is there a way to re-root my device (more or less)? Thanks, a response or any help would be very much appreciated.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I am having same issue

This issue has been addressed; do a Verizon Nexus Forum search.

Uninstall supersu, reboot, then install the market version, not the flash able zip
Sent from my Nexus 7 using xda premium

That fixed my issue
Sent from my HTC Raider X710e using xda app-developers app

[Q] ResetNotify asking for SU permission?

Hi all,
today i was playing with my New One and suddenly this "ResetNotify" popped out asking for SU permission, anyone knows what this process/app is and what does it do?
My phone is on stock rom, rooted with SuperUser, clockwork recovery, and Xposed mod only.
Thanks!!

I tried searching "ResetNotify" but i couldnt find any information, has anyone seen/encounter this? i didnt had the chance to copy down the process but i believe its com.htc.resetnotify?
just wondering if anyone has seen this and what does this process do that requires root permission? if i never rooted my phone it would still work?

I see (or at least saw) it on a regular basis. I also did a search to try and find out what it was about. Eventually decided to ignore it unless virus apps started to scream about it.
Sent from my Tricked out 2.4.0 HTC One via xda-developers application

i decided to grant it permission permanently since it pops up everyday, although i still have no idea what it does...

mingtaoh said:
Hi all,
today i was playing with my New One and suddenly this "ResetNotify" popped out asking for SU permission, anyone knows what this process/app is and what does it do?
My phone is on stock rom, rooted with SuperUser, clockwork recovery, and Xposed mod only.
Thanks!!
Click to expand...
Click to collapse
Same problems, any idea ?

Install SuperSU (update the su binary too) and wait for it to happen again. Then go into Logs and see what app called it

Well??? What called it?

I'm also facing this issue.
I'm rooted, unlocked bootloader, custom recovery (TWRP), STOCK rom.
I did not grant permission figuring this is some ploy by htc to check if their devices are rooted and perhaps unroot it? Is that even possible?
Has this happened with any other prior HTC devices? anyone have answer to this?

Ghoymakh said:
Well??? What called it?
Click to expand...
Click to collapse
SuperUser Pro is required to use this feature
com.htc.resetnotify is a common one across multiple htc devices, based upon what I can glean from the forums. I just went ahead and blocked it though. If I didn't have the device rooted, it wouldn't ask me for root privileges, so I just denied it and it shouldn't make a difference vs a stock setup.

mingtaoh said:
i decided to grant it permission permanently since it pops up everyday, although i still have no idea what it does...
Click to expand...
Click to collapse
If you don't know what it is, the best approach/security is to deny permanently. Think of it like the key to your house. Are you going to give a stranger a key so he can come in and do whatever, whenever?

Had this issue today, too. After granting temporary su permissions to the process I could see a toast that it was setting Filesystem rights. Unfortunately I couldn't see what permissions were ser on what file.
After that I permanently denied su permissions for resetnotify but probably changing fs rights is permanent.
Sent from my HTC One using xda app-developers app

I just got this too. I've had the phone since Tuesday. Unlocked, recovery and rooted... but still on stock. I denied it too. Just wish I could find an answer as to what it actually is.

Would love to know what it is. I used to get regular requests from it but I might have granted it permanent su
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 5.3.0
teaMSeven(stable) kernel 3.9.2

I just had the same request and I have the same concerns as others on this thread.
Is it a 3rd party app that initiated it?
If it is an HTC call, then why?
This happened first on my HTC one that I've had for a week.
Tmobile M7, unlocked,, TWRP recovery, rooted, and stock Sense 5 for five days.

It is a HTC app letting you know that your device has had an reset/data wipe and I think it wants to help you restore your data or settings.
You saw this after you unlocked your bootloader which wiped your data right?

Same problem here as well. Didnt give it rights though.

Same problem here, and I denied. It popped every day.

My guess..
mingtaoh said:
Hi all,
today i was playing with my New One and suddenly this "ResetNotify" popped out asking for SU permission, anyone knows what this process/app is and what does it do?
My phone is on stock rom, rooted with SuperUser, clockwork recovery, and Xposed mod only.
Thanks!!
Click to expand...
Click to collapse
The first time I got this i assumed it was part of the "your phone has recovered from an abnormal reset send report to HTC" message that you get after rebooting from CWM. I imagine, if we didnt have root access it would just send the info to HTC with out asking for permission. I could be wrong, but it just seemed to make sense to me.

Happened to me a moment ago, denied it but now asking to "Setup the phone"...

This also happened to me just now, just after midnight local phone time. HTC One SV, newly (over 24hrs ago) rooted, stock HTC Sense.
I've looked in all apps and ResetNotify reports:
ResetNotify
version 2.10
Can be Force Closed
Cannot be Disabled
Show Notifications is ticked on and cannot be changed
Total 4.00KB
App 0.00B
USB Storage 0.00B
Data 4.00KB
Phone Storage 0.00B
Permissions:
System tools:
Prevent phone from sleeping
Run at startup
When it requested SU I hadn't rebooted my phone recently but I do recall having the "HTC phone home" messages after unlocking with CWM bootloader, but before rooting.
Obviously, I refused ResetNotify from having SU as it wasn't an app that I had manually started. No adverse affects as yet.

[Q] Lost root after installing safestrap

I installed 3.75 B03 safestrap on my S5A from AT&T. After I backed up my stock rom, I noticed that Safestrap was disabled and I lost my root on my phone. Does anyone know what might of happened? I have no custom roms or that sort of thing on my device. Please keep in mind that I just switched from IOS to Android a few weeks ago and am trying to learn everything via google. Thanks for any input on this matter.

When you say sfaestrap is disabled do you mean while your phone is booting it shoss the safestrap splashscreen with a red [Safestrap: disabled] because in that case safestrap is working that just means you aren't currently booted in to a rom slot which is fine. As for loosing root, what all have you done to verify this? Have you considered just rerooting?
Sent from my SM-G900A using Tapatalk

Rakuu said:
When you say sfaestrap is disabled do you mean while your phone is booting it shoss the safestrap splashscreen with a red [Safestrap: disabled] because in that case safestrap is working that just means you aren't currently booted in to a rom slot which is fine. As for loosing root, what all have you done to verify this? Have you considered just rerooting?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yes, you are correct. It shows red [Safestrap: disabled]. I used root checker from the play store to check if I was still rooted. It determined that I was not. The weird thing is, I rebooted my device and got root access again. So I rebooted it yet once again and I lost root access. It seems to be an intermittent problem. If I keep rebooting, it will eventually give me root access again. I was also able to successfully backup my stock rom and restore the device to give me root access again as well. I've just been playing around with it to try and figure out what is causing it to lose root access. Any ideas? I do have a 64gb evo samsung class 10 card if that makes any difference.

citron2k1 said:
Yes, you are correct. It shows red [Safestrap: disabled]. I used root checker from the play store to check if I was still rooted. It determined that I was not. The weird thing is, I rebooted my device and got root access again. So I rebooted it yet once again and I lost root access. It seems to be an intermittent problem. If I keep rebooting, it will eventually give me root access again. I was also able to successfully backup my stock rom and restore the device to give me root access again as well. I've just been playing around with it to try and figure out what is causing it to lose root access. Any ideas? I do have a 64gb evo samsung class 10 card if that makes any difference.
Click to expand...
Click to collapse
Do you have supersu or superuser or any root manager app like that? If not install one and ser it up(install binaries, etc) and give it another go. If yiu do what exactly happens when you check, does any popup come up asking if you want to grant or disallow access?
Sent from my SM-G900A using Tapatalk

Rakuu said:
Do you have supersu or superuser or any root manager app like that? If not install one and ser it up(install binaries, etc) and give it another go. If yiu do what exactly happens when you check, does any popup come up asking if you want to grant or disallow access?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I already had supersu installed. I don't recall ever having to set anything up. So I think everything is set at default. Should I "install SuperSu into /system"?

citron2k1 said:
I already had supersu installed. I don't recall ever having to set anything up. So I think everything is set at default. Should I "install SuperSu into /system"?
Click to expand...
Click to collapse
That shouldnt be necesaary. So i assume everything ran smooth with installing busybox(required for safestrap) and any other root applications? The dialogs came up and such? You never answered my question last time, have you already allowed root checker root access, or has it ever asked for it at all?
Sent from my SM-G900A using Tapatalk

Rakuu said:
That shouldnt be necesaary. So i assume everything ran smooth with installing busybox(required for safestrap) and any other root applications? The dialogs came up and such? You never answered my question last time, have you already allowed root checker root access, or has it ever asked for it at all?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yes, I did allow root checker root access. Sorry I missed that question. Further, everything ran smoothly with busybox. I'll just keep an eye on it. I hardly ever have to reboot my phone. Its just a minor hiccup that I have to deal with for now. Thanks for your help in this matter.

N910T acting crazy after root

So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.

I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...

Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk

Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.

noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?

I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip

https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it

Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk

Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?

Did you flash over 2.71. And do you have a su app icon on your scrren.

noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.

Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot

MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!

Welcome bud.

Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother

Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk

Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha

My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk

I think it's normal...maybe...ha Im pretty sure it's the warranty bit

are there root for N910A 5.1.1