When I use Yoti I only get the white logo screen, then the app closes. After googling the issue, it appears that the app does not allow rooted devices. I've since tried RootCloak to no avail.
My phone is an s6 edge plus, rooted but still has the stock ROM. I believe Knox is tripped as well, not sure if Yoti checks that though?
jftechdrones said:
When I use Yoti I only get the white logo screen, then the app closes. After googling the issue, it appears that the app does not allow rooted devices. I've since tried RootCloak to no avail.
My phone is an s6 edge plus, rooted but still has the stock ROM. I believe Knox is tripped as well, not sure if Yoti checks that though?
Click to expand...
Click to collapse
Even with magisk hide it doesn't work?
([emoji813]9/[emoji725]/9[emoji813])
Just removed supersu and installed magisk. Yoti no longer crashes but I get an error about rooted devices, so still no luck...
Related
Hey Guys,
I own a Samsung Galaxy S4 from Verizon and have followed the guide on how to root it posted on the forums. For a while things were good. My phone booted up with the correct loading screen and my device detected that I was on an official kernel. Now for reasons I'm not sure of, my phone is saying that the kernel is custom and the lock icon has returned when I restart or cold boot my phone. I'm not running custom firm ware, I'm running a stock Verizion kernel. I tried to delete SuperUser, but it isn't installed. My binaries for SuperSU are up-to-date. I'm still rooted, but I would like to get rid of the unlock icon when I boot up and I would like to get the system to recognize that this is an official kernel.
Also ES File Explorer is unable to mount r/w privilages on my phone in order to delete busybox and su so that I could try to re-root the phone again. Any help would be appreciated, thanks!!
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
sneekerpimpz said:
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
Click to expand...
Click to collapse
Most of the time mine is gone. Maybe once a week I might see it.
sneekerpimpz said:
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
Click to expand...
Click to collapse
So I managed to get rid of it. I'm not sure if it's permanent, but here's what I did. I couldn't delete the stuff in the root directory (and this was before I found solid explorer which has better root access programming than es does). So I did a factory reset and found that that worked for a while, but then I noticed that downloading Triangle Away seemed to be causing the problem because the lock icon returned after I installed it and gave it root access. So I deleted it and chose the 'unroot' option from the list of options in supersu. Then I re-rooted the phone using the guide. Now the lock icon hasn't returned, and the device status under the about phone menu says that my firmware is the official one. Another thing I noticed is that I'm running an older version of busybox (version 1.17.1 I think, as installed by motochopper).
Again I'm not sure what I did differently, or changed as a result of my method, but it seems to have worked. Perhaps someone with more development knowledge can let me know what's happened for my own personal information.
Has anyone tried Towelroot on the S4 NC5 build?
Is this going to unlock the bootloader?
Sent from my SCH-I545 using Tapatalk
This is root method....no it will NOT unlock boot loader
And yes I have used it on my wife's phone it works great..
There is a thepread on it in general section...
sambrooke said:
Has anyone tried Towelroot on the S4 NC5 build?
Is this going to unlock the bootloader?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Works perfectly.
sambrooke said:
Has anyone tried Towelroot on the S4 NC5 build?
Is this going to unlock the bootloader?
Click to expand...
Click to collapse
We really seem to have failed in helping people to understand this, as Towelroot users are now bricking phones right and left by people who root bootloader locked phones then use Goo Manager and the like to try to flash custom recovery and fail.
If your bootloader is locked, you can't flash custom recovery or custom kernel. It doesn't matter if you're rooted or not.
"CUSTOM" Software
Does anyone know if the triggers the "Custom" and the unlocked padlock when rebooting?
seadooman said:
Does anyone know if the triggers the "Custom" and the unlocked padlock when rebooting?
Click to expand...
Click to collapse
It DOES trigger the Custom padlock. With root access you can install Xposed Framework and one of modules allows you to reset that back to Original boot screen.
I think triangle away will work also. I haven't tried yet, but removed the custom screen with the mk2 build after that was rooted with saferoot.
http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Sent from my IdeaPad U410 using Tapatalk
Lost "HI Galaxy Funtion"
Not sure if its related but I lost the handsfree "HI Galaxy" , Get the cannot connect to servers error. Anyone experience this?
seadooman said:
Not sure if its related but I lost the handsfree "HI Galaxy" , Get the cannot connect to servers error. Anyone experience this?
Click to expand...
Click to collapse
If it really happened out of the blue, without installing or reconfiguring anything, your issue will probably be fixed with a power cycle. I would try a battery pull, holding down the power button for a couple seconds without the battery in place (to drain remnants of electricity), replace the battery, boot, reboot, soft/hotboot. If that doesn't fix it, you must have done something to stop it from functioning in the first place.
Yes that also happened to me.. Not sure if it was related to towel root or something I froze. I unfroze everything and uninstalled towel root still had issue..ended up reinstalling oem firmware and everything works normal now. Wondering if the samsung servers know the phone is rooted and refuse connection?
seadooman said:
Yes that also happened to me.. Not sure if it was related to towel root or something I froze. I unfroze everything and uninstalled towel root still had issue..ended up reinstalling oem firmware and everything works normal now. Wondering if the samsung servers know the phone is rooted and refuse connection?
Click to expand...
Click to collapse
Doubtful; people saying "Hi Galaxy" is free advertising for them. If it occured after freezing tasks I'm sure that was the source of the problem. Must be SELinux related. Next time, just redo your root; you probably didn't need to forfeit data.
I unfroze everything and it was hit and miss if it connected or not. Reinstalled android problem was gone. Just thought I would offer my experience on this..
On NC5 it was the fastest and easiest root ever.
One of my phone's is a Galaxy S3 using NE1 and since i couldn't unlock the bootloader but, i had successfully rooted it using towelroot.
It has been about 6 months and i never had issues.
Not everyone with a matching phone has the same issues when it comes to Rooting as well as Bootloader Unlocking.
One's bad experience doesn't always mean another will have the same. This all depends on the expertise and know-how of the user as well as the reliability of an individual who provides the information and/or files accomplishing a Root and/or Bootloader Unlocking.
Just my opinion :fingers-crossed:
I have Verizon Samsung Galaxy S4 with 4.4.2. It has been rooted since I bought it at the end of May 2013. I re rooted many times to keep up with software updates. I used Kies 3 to flash back to default 4.4.2. I mean a complete nuke. I then flashed with towelroot and rebooted to see if the custom broken padlock was present at boot. The padlock was not present and no padlock icon present yay!!!. I installed SuperSu by chainfire and disabled knox as per SuperSu suggestion. I rebooted to check if custom flag had been tripped. The broken padlock was there god dammit.
SuperSu seems to have triggered knox or tripped the counter.
How do I maintain root and have the boot screen display everything is normal.
AND how do I get settings to display official instead of custom.
Please help as XDA and Google searches are not providing ansers.
You won't find a lot of info because most people would tell you if you don't want the custom padlock don't use custom software. You can use "Triangle Away" or the option in the Security Hacks section of the Wanam Xposed module.
Thanks
joshm.1219 said:
You won't find a lot of info because most people would tell you if you don't want the custom padlock don't use custom software. You can use "Triangle Away" or the option in the Security Hacks section of the Wanam Xposed module.
Click to expand...
Click to collapse
Well. I looked at triangle away. It messes with the hardware startup code and I don't want to do that. So ill be fine for now. My phone is out of warranty so it's not a big deal and I have insurance on my pbone. I was only bothered because I like pretty visuals.
purplenate26 said:
I have Verizon Samsung Galaxy S4 with 4.4.2. It has been rooted since I bought it at the end of May 2013. I re rooted many times to keep up with software updates. I used Kies 3 to flash back to default 4.4.2. I mean a complete nuke. I then flashed with towelroot and rebooted to see if the custom broken padlock was present at boot. The padlock was not present and no padlock icon present yay!!!. I installed SuperSu by chainfire and disabled knox as per SuperSu suggestion. I rebooted to check if custom flag had been tripped. The broken padlock was there god dammit.
SuperSu seems to have triggered knox or tripped the counter.
How do I maintain root and have the boot screen display everything is normal.
AND how do I get settings to display official instead of custom.
Please help as XDA and Google searches are not providing ansers.
Click to expand...
Click to collapse
Well, perhaps you could start with the sticky threads here?
One: Assuming that "triped" is just a typo for "tripped": No, that's wrong. First, the phrase "tripped Knox" is usually how people refer to something that sets the "Knox Warranty Void" flag. Installing SuperSU will not set the Warranty Void flag.
You're apparently seeing the "Custom" flag show up at boot, and claiming that's evidence that something "tripped Knox". That's wrong. That's been discussed in the sticky threads here and in the General forum. The "Custom" status means that your phone is no longer running stock.
If you care about the "Custom" flag, flash stock. It'll get cleared after a while. Or, run one of the several techniques to clear it (Triangle Away, Xposed framework, etc.)
The easy way to clear that flag is to flash a stock ROM. If you want to run non-stock, you'll need to live with it, or use one of the work-arounds. I use TA to clear Custom.
something i kinda want to add to this, SuperSU will actively disable knox upon installing it. There is absolutely no way you can trip Knox just with SuperSU. From what i can tell, Knox only gets tripped when you modify the kernel or boot stuff (recovery, etc.) and by that point you'd end up bricking a phone if you didnt have the MDK bootloader
Clear syscope with titanium backup
Sent from my GT-I9505G using XDA Free mobile app
Hey Guys, I have 2 SM-G925F phones, an older one with a cracked screen and new one I got today. I had originally updated to 5.1.1 on the older phone, installed Samsung pay on it and worked fine. I rooted the phone and tripped knox due to the new kernel. When I got my new phone, I updated it to the stock 5.1.1 and tried to download Samsung pay on it but it says the app isn't supported on my device, even though it had work previously. Any recommendations on how to fix this? Is there someway I can reset my google/play account as to showing my new Edge that doesn't have Knox tripped? Thanks!
Where did you install from?
The pay app? I downloaded it originally from the Google play store.
I have to search because I didn't find on playstore
You won't be able to find it in the playstore if your phone is rooted, it shows as "unable to install on your device"
Also, you won't find it if the phone isn't from a supported carrier. I have the international G925F and I had to sideload the framework and the app though I can't get it to work.
So I have a Verizon SCH i545 S4 running Android 5.0.1 with VRUGOF1. I've learned that is version has a locked bootloader so custom roms like Cyanogen are completely off the table for me. I'm not so much worried about that but I really want to be able to basically do 2 things: remove bloatware and use xposed with the Notifyclean module to get rid of those freaking "Wifi is available" and "Location set by GPS" notifications. I was able to do this before I foolishly upgraded to 5.0.1., but now I can't.
So far I've been able to root my device by doing the OC1 Odin flash, then Wondershare. Got Supersu, got busybox, and was able to use Flashfire to install stang5litre (thinking that xposed would work on it. It doesn't). So after all that preamble, my question is how can I install a different rom like Hyperactive? I've read that you can install other roms, as long as they're Touchwiz compatible, and according to the Hyperactive release notes, it comes with xposed. But all the instructions I have read talk about installing it with a custom recovery, which I can't use since I have a locked bootloader. I tried flashing it with Flashfire just to see if it worked, and softbricked my phone, forcing me to reinstall the stock rom over Odin, and go through all the rooting stuff all over again.
Also, I have tried installing and using SafeStrap but it won't work on my phone. It boots into the Safestrap: Disabled screen with the two buttons on the bottom to start normally or go into recovery, but no matter what I press, the screen goes blank, the phone vibrates, and it just boots normally. I cannot get into the recovery function.
Is what I want possible? Is there any way at all to just get a Verizon Galazy S4 with the VRUGOF1 locked bootloader to accept xposed? Everything I've tried so far has failed and/or forced me to totally reset everything and start over. I just want to get rid of those damn persistent Google notifications.
Check out albe95's s6 rom
I've been running his s6 rom for about a month, and it's great. After turning all of the s6 edge functions off, it runs like a dream. I was able to install xposed and change all the stuff I wanted. Good luck.
DRMMR144 said:
...was able to use Flashfire to install stang5litre (thinking that xposed would work on it. It doesn't). .
Click to expand...
Click to collapse
I have the same base unit as you and was running xposed on Stang5litre v2 just fine. There are several versions of xposed out there and only one of them worked for me. I'm pretty sure this was the one... https://www.androidfilehost.com/?fid=23991606952607509
I'm not running xposed now - only because I just like to keep things simple and would rather live with a few limitations than loading up mods that may give problems
I am running @stang5litre 's v3 with Xposed working perfectly fine. In your subject of the thread... you mention "hyperactive"
.....do you mean Hyperdrive ROM?
hooks024 said:
I've been running his s6 rom for about a month, and it's great. After turning all of the s6 edge functions off, it runs like a dream. I was able to install xposed and change all the stuff I wanted. Good luck.
Click to expand...
Click to collapse
I agree, you should check out the galaxy s6 rom. I've been able to get xposed working well also. But are you sure you're flashing the right version of xposed? Try searching in the comments to see if anyone else had that problem and which exact version to use. (Despite this being a reply to hooks024;64804157's comment it is obviously directed at the maker of the thread).