[Q] Rogers S5 Active UNLOCKED - AT&T Samsung Galaxy S 5

Ok I've got my Rogers Samsung S5 Active unlocked, and confirmed by Root Checker and I've installed SuperSU Pro.
I rooted it via this particular method I read at
theunlockr
It reboots and functions as normal, however when I attempt to utilize SuperSU it says that KNOX is installed, it then allows me to dissable which I do and it remarks successful.
What I want to know is what do I do to remove ROGERS craptastic apps, and keep them off, what do I use to get in and modify some of the parameters of the phone, like CPU speed and so forth?
If there are any decent fully working ROM's for a newbie like myself, I'd be happy to throw a go at using one.
Any help with getting the absolute MOST from my device would be appreciated.
Thanks for reading
RW

Go to the play store and search for root. You'll find a lot of apps for tweaking the S5. You have many choices for a ROM because you have an unlocked bootloader. I think you can use the latest AOSP or Cyanogen mod, or if you want to set up safestrap your can run the Dynamic Kat ROM found here. That ROM has an assistant app that lets you tweak a whole lot of things all from the app.

Related

[Q] z4root?

Just noticed the app z4root in the Market. It claims one-click rooting and unrooting of various devices, among them the Galaxy S. Search of the Galaxy Tab boards didn't turn up anything. Is this safe and recommended for the Tab?
Used it myself and it went smoothly. Far smoother than previous rooting methods I had to use on other devices.
Thanks, I was too timid to try it without someone confirming it first.
I can now also confirm that it works fine. Went very smoothly, took about 1 minute and a reboot.
It seems like such an odd way to root for me. My first experience of rooting was a HTC Legend. I had to downgrade the software (one complete wipe and flashing of firmware) and then flash a rooted update. And I still don't have proper write access to the /system partition. It took about half an hour to root the Legend, this took 2 minutes, and I didn't loose any data. Awesome!
Noob Question (first adroid device I've had) : So, what are the benefits of rooting the tab? Removing pre-installed samsung apps?
Ah...I found a nice article..so that's the only way I can remove the stupid Vodafone booting / shutting down image?
Can confirm, rooted the tab yesterday with this and after that run the OCLF, now the Tab works like a Charm.
Garret said:
Noob Question (first adroid device I've had) : So, what are the benefits of rooting the tab? Removing pre-installed samsung apps?
Ah...I found a nice article..so that's the only way I can remove the stupid Vodafone booting / shutting down image?
Click to expand...
Click to collapse
My favorite advantage: Running AdFree, which very effectively blocks most ads, in the browser and also inside other apps.
Rapax said:
My favorite advantage: Running AdFree, which very effectively blocks most ads, in the browser and also inside other apps.
Click to expand...
Click to collapse
It's the only reason I rooted this thing.
Garret said:
Noob Question (first adroid device I've had) : So, what are the benefits of rooting the tab? Removing pre-installed samsung apps?
Ah...I found a nice article..so that's the only way I can remove the stupid Vodafone booting / shutting down image?
Click to expand...
Click to collapse
from noob to noob - to be able do things that manufacturer doesnt think of - adfree, clock synch, interface mods, changing the way memory works (get rid of stacking lags).. all in all improve things that in retail are sold to you and a "new" model))
And i know for sure
- 1)dont do anything before reading stuff here
- 2)if you dont know that you need it - dont do it
- 3)dont do things until you know exactly how to undo them unless you are looking for pretexts to buy yourself a new device.
sorry for this lecture)
Router thanks. Good informations.
I would like to root my SGT because I need CIFS access to my network share directories, in my Windows network. I found some prgs in the Market, but they need 'root rights'. So here I am. I will use this root app.
A question for you (you seem experienced) about the correct procedure to reinstall apps already installed after a root procedure:
1. Do an AppBrain Syncronize
2. Launch Root (Z4root)
3. Install the AppBrain app again and then connect to my AppBrain account to 'restore' apps?
Is it correct my idea?
that is correct, its not like the root we do when rooting and android phone like my evo, you can actuall run the z4root the run and install that program
Rapax said:
My favorite advantage: Running AdFree, which very effectively blocks most ads, in the browser and also inside other apps.
Click to expand...
Click to collapse
...and Droid Wall, to prevent applications from accessing the web "unnecessarily"
that was easy and painless. nice, full root
I've found that I loose root occasionally, any idea why?
Sent from my GT-P1000 using XDA App
Seems to work.
Sent from my GT-P1000 using Tapatalk
Router said:
from noob to noob - to be able do things that manufacturer doesnt think of - adfree, clock synch, interface mods, changing the way memory works (get rid of stacking lags).. all in all improve things that in retail are sold to you and a "new" model))
And i know for sure
- 1)dont do anything before reading stuff here
- 2)if you dont know that you need it - dont do it
- 3)dont do things until you know exactly how to undo them unless you are looking for pretexts to buy yourself a new device.
sorry for this lecture)
Click to expand...
Click to collapse
Well, for starters I'd like to get rid of the very annoying vodafone booting / shutting down images.
If I could also remove some pre-installed apps, that'd be nice too ^^
recovery
Does this root give a recovery image?
kevinniven said:
Does this root give a recovery image?
Click to expand...
Click to collapse
No. As far as I'm aware we don't have a recovery image.
Swyped from my Galaxy Tab
sts_fin said:
Can confirm, rooted the tab yesterday with this and after that run the OCLF, now the Tab works like a Charm.
Click to expand...
Click to collapse
When you ran OCLF, what was the amount of RAM you selected, I think by default it shows somewhere around 846 odd..
Used it myself and it went smoothly. Far smoother than previous rooting methods I had to use on other devices.

[Q] Good for Enterprise on custom Android ROMs

Has anyone had a problem with the intial setup for Good for Enterprise on custom Android ROMs? I installed it (using an issued PIN) on stock eclair on my Captivate and it worked fine. I then rooted, backed it up via TIBU and restored on Froyo and it still worked fine. The same process worked recently on Gingerbread. However, I have tried multiple custom Froyo ROMs and 1 GB recently and if I try the initial setup (with a new PIN) on anything other than stock eclair (even rooted), it will stop at "retrieving policies" and never complete. I then have to ask for a new PIN from my IT support and revert to eclair and finish the setup, backup, and restore on the later custom ROMs. Has anyone seen this and have any idea why? My IT support has no idea. I am not in a policy checking for root access and it does continue to work with root.
EDIT: I wonder if it is that the device name used in build properties is referenced during that step and it fails due to an unknown device...
Also, I have found that after I have it working after a certain PIN used, if I ever restore to an ealier point (due to a theme gone wrong, etc) then it stops syncing even if the restore point is AFTER I had it working with that PIN. It seems like the local software either is exchanging a dynamic password with the server or there is a message index, etc that has to be in sync. Any thoughts?
When in the Good setup screen, go to Menu>Device Info. Does the Phone number appear? I've been using CM7 just fine with Good but after the last few nightlies, Good no longer works. The phone number doesn't appear in the device info. Good thinks there is no phone network present.
I am a heavy Good user, unfortunately also addicted to changing ROMs on a frequent basis. I have never had an issue with Good running on any ROM, just on restoring from TiBu. I can flash new kernels, themes, etc, and Good works just fine. If I re-flash the same ROM, it resides and works just fine. It is only when flashing a new ROM I have problems. Good appears to restore OK, but won't pull new emails to the inbox. I ave to get a new PIN and re-install.
Same here.. i am addicted to flashing as well.
I tried Titanium backup to backup and restore to new ROM, but somehow Good just keep crashing after i put in my password.
I am sure I can ask for new pin, reinstall and what not.. but how often can we ask IT people (for my company at least) for new pins, until one day they may say, bugger off you ROM addict!
Finally figured it out, I think. The trick is to NOT have Good running in persistent mode when you do the backup with TiBu. IOW, reboot and backup with TiBu before you start Good and log in. I did that the last couple of new ROMs and it restored and worked just fine.
Sent from my SGH-I897 using XDA App
GOOD for Enterprise on Imito AM801 Tablet
I am also getting the Phone network is off. This is a tablet and does not have any phone piece or sim card installed. No hardware is even inside the tablet. Has anyone ran accross this issue on tablets?
This works for me.
http://forum.xda-developers.com/showthread.php?p=35263313#post35263313
Good with custom roms
Just to share a recent experience on that topic:
I wanted to have a custom rom but need GFE for my work which of course has a policy of no root with GFE.
So after a little research and useful info from this forum I figured a very simple way to do it, as long as you don't consider root as critical for your day-to-day stuff
1. Install your custom rom which most likely requires rooting
2. Install SuperSU from the Play Store and use it to remove root completely
3. Install and activate GFE
That's it!
Hoope this helps someone else how got a little scared to have to go through scripts and stuff to do this
Using a Galaxy S4 with Carbon Rom
Anteus20 said:
Just to share a recent experience on that topic:
I wanted to have a custom rom but need GFE for my work which of course has a policy of no root with GFE.
So after a little research and useful info from this forum I figured a very simple way to do it, as long as you don't consider root as critical for your day-to-day stuff
1. Install your custom rom which most likely requires rooting
2. Install SuperSU from the Play Store and use it to remove root completely
3. Install and activate GFE
That's it!
Hoope this helps someone else how got a little scared to have to go through scripts and stuff to do this
Using a Galaxy S4 with Carbon Rom
Click to expand...
Click to collapse
Does this still work?
I too need GFE on my Galaxy S4 but am sick of the poor battery life. I tried SlimKat and Google Play Edition roms, and removed root using Super SU in both cases. But GFE gives a message "Not supported for this type of Handheld". . Not sure if GFE is looking for a TW based ROM.
I will give it another go using Carbon ROM. Still, any other advice / experience on getting GFE working on a custom ROM would be much appreciated.
Thanks.
joshic75 said:
Does this still work?
I too need GFE on my Galaxy S4 but am sick of the poor battery life. I tried SlimKat and Google Play Edition roms, and removed root using Super SU in both cases. But GFE gives a message "Not supported for this type of Handheld". . Not sure if GFE is looking for a TW based ROM.
I will give it another go using Carbon ROM. Still, any other advice / experience on getting GFE working on a custom ROM would be much appreciated.
Thanks.
Click to expand...
Click to collapse
You quoted a 1 year old post, might be hard to get a reply. Also this is for the S1, while the app (GFE) might be the same, the ROMs definitely aren't.
That being said, chances are that the app was updated to prevent that workaround. You could flash a TW based ROM and test it though.
Thanks for the reply. I will try posting a fresh question in the Q&A thread in case anyone has more recent experience with GFE. Cheers.
joshic75 said:
Thanks for the reply. I will try posting a fresh question in the Q&A thread in case anyone has more recent experience with GFE. Cheers.
Click to expand...
Click to collapse
There is an xposed module for this.
Hi, are you referring to Wanam Xposed which has a "fake official system status" functionality?
As I understand, Xposed needs root, but Good for enterprise doesn't work on a rooted handset. Can Xposed work without root?
Also Wanam Xposed is meant to work with TW based ROMs whereas I don't want to go back to TW based ROM unless it is extremely light.
joshic75 said:
Hi, are you referring to Wanam Xposed which has a "fake official system status" functionality?
As I understand, Xposed needs root, but Good for enterprise doesn't work on a rooted handset. Can Xposed work without root?
Also Wanam Xposed is meant to work with TW based ROMs whereas I don't want to go back to TW based ROM unless it is extremely light.
Click to expand...
Click to collapse
I'm a bit confused here, Custom ROMs are pre-rooted. Therefor, if you're not on TW, you're rooted.
And yes, Xposed does require root. As for Wanam, I duno if it works on AOSP but best way to know is you try
Thanks for replying.
Supersu has a Full Unroot functionality which removes root.
Yes I will try, but every failed attempt sends an email to office admin so I have to be prudent.
http://www.gogadgetx.com/xposed-framework-install-use-best-modules-list/
The link above mentions that root is required while installing XPosed, but later it can perform without root. Is this correct or not?
joshic75 said:
Thanks for replying.
Supersu has a Full Unroot functionality which removes root.
Yes I will try, but every failed attempt sends an email to office admin so I have to be prudent.
http://www.gogadgetx.com/xposed-framework-install-use-best-modules-list/
The link above mentions that root is required while installing XPosed, but later it can perform without root. Is this correct or not?
Click to expand...
Click to collapse
I have never personally tried it without root but you can test that fairly easily. I expect it would depend on the module you're using, some require more permissions than others.
I tried it out but it didn't work.
I have to go back to stock ROM

[Q] Question about compiling

If I compile a kernel using these instructions
showthread.php?t=2246833&highlight=cdma
Will it include root? I tried some rooting instructions, but they were apparently only for the gsm version of this phone, and I have the CDMA version with Cricket :/
I tried my google-fu but didn't find how to include SU and superuser in the kernel. I downloaded golfc-ics-3.0.16-3d39477.zip from htcdev, which I think is the one I need, but I want to make sure I can achieve what I'm hoping. I want root so I can remove bloatware like google+ and facebook, set a few things to system apps that aren't really, protecting them from removal, make use of titanium backup, and make use of a few other things I had on my old [email protected], like root call blocking, and silencing startup sounds without turning the sound off before powering down the phone.
I'm sure it's been answered, but I didn't find it
If anyone could help out a noob who seems to be a slow learner, it'd be really appreciated.

Losing root after 2 or 3 reboots

Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.

Help using baking app finding non-existing root

banking app, not baking app, f**ks sake
Hello there. I have been using stock android 7.1.1 for a while and decided to try using roms again (Pure Nexus). One of the apps that i need is "Vipps" its a Norwegian banking app used to transfer money to friends and stuff, but its notorious for finding root. I used to use xposed and root cloak on android 6, but i know well it dosent work with 7. Magisk dosent hide it, suhide dosent hide it.
After installing Vipps it rejects opening promting me with "Vipps does not support rooted devices". Only thing is its running a ROM that comes with no root.
- Cheers, Kristiansja
edit: root checker doesn't find annything either
kristiansja said:
banking app, not baking app, f**ks sake
Hello there. I have been using stock android 7.1.1 for a while and decided to try using roms again (Pure Nexus). One of the apps that i need is "Vipps" its a Norwegian banking app used to transfer money to friends and stuff, but its notorious for finding root. I used to use xposed and root cloak on android 6, but i know well it dosent work with 7. Magisk dosent hide it, suhide dosent hide it.
After installing Vipps it rejects opening promting me with "Vipps does not support rooted devices". Only thing is its running a ROM that comes with no root.
- Cheers, Kristiansja
edit: root checker doesn't find annything either
Click to expand...
Click to collapse
Go into the root settings and remove root. Mind you this cause some of the features of the rom to stop working. Apps like that are not only looking for root but also for unlocked bootloaders. So if those apps are important to you then might want to stick to a fully stock set up and relock your bootloader.
zelendel said:
Go into the root settings and remove root. Mind you this cause some of the features of the rom to stop working. Apps like that are not only looking for root but also for unlocked bootloaders. So if those apps are important to you then might want to stick to a fully stock set up and relock your bootloader.
Click to expand...
Click to collapse
Pure Nexus comes without root
kristiansja said:
Pure Nexus comes without root
Click to expand...
Click to collapse
Go into developer option and turn off USB debugging. After that, reboot the phone and see if Vipps is working. If that doesn't work, I have one more suggestion.
It's probably checking ro.build.tags and/or ro.build.type. These are set to test-keys and userdebug on PN (if I remember correctly) and some apps need them to be set to release-keys and user. It could also be looking for other prop values and possibly also busybox (also included in PN, I believe).
Or BusyBox...
Sent from my Nexus 6 using Tapatalk

Categories

Resources