i have rooted my lg g3 with stump root, i would like to remove the root to update my lg to the lollipop software i have used supersu to full unroot and remove all root apps, i use root checker and it states i'm unrooted but when i go and install new software a message appears advising me unable to update a rooted device, can anyone help me i am unable to access a computer to unroot, i'm using my android !
Unfortunately you will have to find a way to get access to a pc to do this properly. There's rarely a way to revert to full stock without a pc.
good luck
So I rooted my device with Towelroot. I checked that it was rooted and I used my device for sometime and then I thought I really didnt need root so I unrooted my device through superuser. I used an app called root checker and it said that my device didnt have root permissions. So now I need OTA updates and it says that my device had been modified in an authorized way? Did I unroot it properly or is there another way to fix this or unroot my device. I am looking forward to your replies.
Thanks!
I am new here, I have just root my asus zenfone 5 . And accidentally opened king root and phone rooted again. And when i opened super su it was showing error ”binary not updated" and then i cross checked on root checker app it is showing ”phone not rooted properly "(before it had been shown ”phone rooted properly) plz help...
rpn123 said:
I am new here, I have just root my asus zenfone 5 . And accidentally opened king root and phone rooted again. And when i opened super su it was showing error ”binary not updated" and then i cross checked on root checker app it is showing ”phone not rooted properly "(before it had been shown ”phone rooted properly) plz help...
Click to expand...
Click to collapse
find your phones stock firmware and flash it back to stock, then you can try rooting again.
once you mess up root, on most devices, it usually cant be fixed without starting over.
Since there is still no root method above 5.1.1, perhaps I should make a thread for ideas on rooting the Samsung Galaxy S6 6.0.2 and higher
I was thinking of editing default.prop in the ramdisk so I can gain root access since this is what I am hearing.
ro.secure is like root without the need of ADB
ro.debugging is root but you need ADB.
And then attempt to install su and superuser
I've seen someone on 6.0.2 on root checker saying they have root their S6 but it was hard to get root. So I am guessing he edited default.prop in the ramdisk.
That's all I am thinking, might think wrong or stuck in the past, but what do you guys think on what might get root access? I actually need ideas on what can get root access to the S6
AndroidFan16 said:
Since there is still no root method above 5.1.1, perhaps I should make a thread for ideas on rooting the Samsung Galaxy S6 6.0.2 and higher
I was thinking of editing default.prop in the ramdisk so I can gain root access since this is what I am hearing.
ro.secure is like root without the need of ADB
ro.debugging is root but you need ADB.
And then attempt to install su and superuser
I've seen someone on 6.0.2 on root checker saying they have root their S6 but it was hard to get root. So I am guessing he edited default.prop in the ramdisk.
That's all I am thinking, might think wrong or stuck in the past, but what do you guys think on what might get root access? I actually need ideas on what can get root access to the S6
Click to expand...
Click to collapse
This guy you've heard has root on 6.0.2 is on the G920V right, also seems interesting, do you think you could link this image, or original posting or whatever?
If Root Checker has an option to contact the person that rooted 6.0.2, I would do it, but I can't. That's why I made the "Rooting Ideas"
Also, I have the feeling that since PC2 can be downgraded to OK7, it might have the same bootloader. So technically were not far from root for marshmallow.
You can check in root checker. Cause that's were I found someone that rooted the verizon S6
AndroidFan16 said:
If Root Checker has an option to contact the person that rooted 6.0.2, I would do it, but I can't. That's why I made the "Rooting Ideas"
Also, I have the feeling that since PC2 can be downgraded to OK7, it might have the same bootloader. So technically were not far from root for marshmallow.
You can check in root checker. Cause that's were I found someone that rooted the verizon S6
Click to expand...
Click to collapse
Ok, after I flash again (FLASHFIRE WORKS!, too bad it is pretty much useless now..., may have soft bricked it again XD) Working with Rooted 5.1.1, and it is quite crap... the battery life is maybe 3 hours max, and everything is SLOW!
THINGS I'VE TRIED:
Flashing 5.0.2 via Flashfire - FAIL
Flashing 5.0.2 via Flashfire, then flashing custom sboot - FAIL
SuperSU-MEing Kingroot in 5.1.1 - Kind of....*
Flashing PC2 Firmware (MM), With Everroot Enabled FAIL**
THINGS I NEED TO TRY:
Flashing Custom SU (or Custom VZW S7 SU) via FlashFire
Waiting For ROMS for the Eng-Kernal....
That Is All The Info I Have
*SuperSU works, but bootloops on reboot...
**Stuck at Screen BEFORE BOOT LOGO
(Where is says Powered By Android at the bottom)
---------- Post added at 03:04 AM ---------- Previous post was at 02:46 AM ----------
AndroidFan16 said:
If Root Checker has an option to contact the person that rooted 6.0.2, I would do it, but I can't. That's why I made the "Rooting Ideas"
Also, I have the feeling that since PC2 can be downgraded to OK7, it might have the same bootloader. So technically were not far from root for marshmallow.
You can check in root checker. Cause that's were I found someone that rooted the verizon S6
Click to expand...
Click to collapse
HOLD UP! The S7 SuperSU binary!
What About In FlashFire
WIPE, FLASH PC2 (MM FIRMWARE), FLASH VZW-S7 SU BINARY, REBOOT
Maybe, Just Maybe...
Mnky313 said:
This guy you've heard has root on 6.0.2 is on the G920V right, also seems interesting, do you think you could link this image, or original posting or whatever?
Click to expand...
Click to collapse
Mnky313 said:
Ok, after I flash again (FLASHFIRE WORKS!, too bad it is pretty much useless now..., may have soft bricked it again XD) Working with Rooted 5.1.1, and it is quite crap... the battery life is maybe 3 hours max, and everything is SLOW!
THINGS I'VE TRIED:
Flashing 5.0.2 via Flashfire - FAIL
Flashing 5.0.2 via Flashfire, then flashing custom sboot - FAIL
SuperSU-MEing Kingroot in 5.1.1 - Kind of....*
Flashing PC2 Firmware (MM), With Everroot Enabled FAIL**
THINGS I NEED TO TRY:
Flashing Custom SU (or Custom VZW S7 SU) via FlashFire
Waiting For ROMS for the Eng-Kernal....
That Is All The Info I Have
*SuperSU works, but bootloops on reboot...
**Stuck at Screen BEFORE BOOT LOGO
(Where is says Powered By Android at the bottom)
---------- Post added at 03:04 AM ---------- Previous post was at 02:46 AM ----------
HOLD UP! The S7 SuperSU binary!
What About In FlashFire
WIPE, FLASH PC2 (MM FIRMWARE), FLASH VZW-S7 SU BINARY, REBOOT
Maybe, Just Maybe...
Click to expand...
Click to collapse
It could work though
Since the verizon S7 users are in the same boat as us
I really hate lollipop. Its soooooooooo slooooooooowwwwww. So I want to see if we can try to get the S7 SU binary asap before my phone gets more slower :crying:
Tried to root 6.0.2 with Easy One-Click tool on the forum for tests and giggles. Gave me a bootloop.
I have given up on customizing Android and flashed stock firmware from sammobile, now I can't open the S health app. A pop up shows "Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices. (0x110020521) I downloaded and ran root checker and it shows the phone is not rooted. Is there any way I can get rid of this without rooting again?
Nightcatfisher said:
I have given up on customizing Android and flashed stock firmware from sammobile, now I can't open the S health app. A pop up shows "Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices. (0x110020521) I downloaded and ran root checker and it shows the phone is not rooted. Is there any way I can get rid of this without rooting again?
Click to expand...
Click to collapse
You need to edit the build.prop
Look for ro.config.tima and change the "1" to a "0".
You can either use a app like root explorer or BuildProp Editor.
You will have to root to fix this as it is using Knox to detect the past root/recovery flash.
Once you trip knox with twrp / root you can undo that.
Rooting alone shouldnt be giving you any trouble?
What problems were you having that made you want to go stock with no root?
DeeXii said:
You need to edit the build.prop
Look for ro.config.tima and change the "1" to a "0".
You can either use a app like root explorer or BuildProp Editor.
Click to expand...
Click to collapse
I wonder where you got this little tidbit of advice from...
https://forum.xda-developers.com/showthread.php?p=71995091
Nightcatfisher said:
I have given up on customizing Android and flashed stock firmware from sammobile, now I can't open the S health app. A pop up shows "Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices. (0x110020521) I downloaded and ran root checker and it shows the phone is not rooted. Is there any way I can get rid of this without rooting again?
Click to expand...
Click to collapse
just downgrade to 6.0.1 with odin, start s health and let the phone upgrade it`s self to 7. Worked for me