I got root, My kernel date is Apr 16th
Sent from my SAMSUNG-SM-G900A with 128gb SD.
S5 active has root now
Sent from my SAMSUNG-SM-G870A using Tapatalk
Anyone change DPI yet?
One of my main reason for wanting root was to change DPI. Anyone have success in changing dpi after root?
Does this root method trip Knox counter
Sent from my VS980 4G using XDA Premium 4 mobile app
E28 Bimmer said:
S5 active has root now
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
.
I have Active. Just install the apk and it reboots? Does SuperSU show up?
Superuser doesn't show up but root apps work. You can download rootchecker from play store to verify once it reboots
Sent from my SAMSUNG-SM-G870A using Tapatalk
artjrv said:
Does this root method trip Knox counter
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine says Knox warranty is void
Device is now Custom status
Sent from my SAMSUNG-SM-G900A with 128gb SD.
artjrv said:
Does this root method trip Knox counter
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine didn't get tripped. You're safe
from my frothy.... froth... frosty... frost
Rooted and yes, I was able to change per-app DPI using an Xposed module. So far, no issues. Haven't done much but install Xposed and a bunch of long-awaited modules!
Rooted SM-G900A. Knox is NOT tripped, double checked. SuperSU manually installed using the .apk available from their website. The SuperSU app in the app store is not updated to the latest version yet. Froze LocalFOTA and AT&T Software Update using Titanium Backup so hopefully no OTA in the future. Also froze the security policy update app in Titanium Backup.
How do you check if Knox tripped
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
shemantis said:
Rooted and yes, I was able to change per-app DPI using an Xposed module. So far, no issues. Haven't done much but install Xposed and a bunch of long-awaited modules!
Click to expand...
Click to collapse
What DPI did you go with? I couldn't find the DPI in the build.prop
Install Xposed
runnernsd said:
One of my main reason for wanting root was to change DPI. Anyone have success in changing dpi after root?
Click to expand...
Click to collapse
skatin707 said:
What DPI did you go with? I couldn't find the DPI in the build.prop
Click to expand...
Click to collapse
@skatin707 do not use build.prop to change the DPI. That makes a global change, you can use Xposed and then get the module called "App Settings" in the Xposed Download repo and change the DPI to something different for each app. Forums/browsers maybe you want 400dpi or smaller but games system etc you'll want to stay at a higher DPI to not have spacing issues. @runnernsd this also applies to you.
byte9 said:
@skatin707 do not use build.prop to change the DPI. That makes a global change, you can use Xposed and then get the module called "App Settings" in the Xposed Download repo and change the DPI to something different for each app. Forums/browsers maybe you want 400dpi or smaller but games system etc you'll want to stay at a higher DPI to not have spacing issues. @runnernsd this also applies to you.
Click to expand...
Click to collapse
I wasn't going to use the build.prop to change it, I just wanted to know what the stock DPI was. I use textdroider and xposed modules to modify specific apps.
skatin707 said:
I wasn't going to use the build.prop to change it, I just wanted to know what the stock DPI was. I use textdroider and xposed modules to modify specific apps.
Click to expand...
Click to collapse
432 ppi is the stock. Little lower than the GS4 because screen size.
ryfermadness said:
How do you check if Knox tripped
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Turn off the phone, then, press power, home, and volume down button together and hold them until you reach a prompt that says press volume up to continue. Press volume up and you should see a Knox Counter in one of the lines listed. If it's 0x0 its not void, if it's 0x1 its tripped and therefore warranty is void.
I can't find the dpi in build.prop either but I actually want to do a global
byte9 said:
@skatin707 do not use build.prop to change the DPI. That makes a global change, you can use Xposed and then get the module called "App Settings" in the Xposed Download repo and change the DPI to something different for each app. Forums/browsers maybe you want 400dpi or smaller but games system etc you'll want to stay at a higher DPI to not have spacing issues. @runnernsd this also applies to you.
Click to expand...
Click to collapse
runnernsd said:
I can't find the dpi in build.prop either but I actually want to do a global
Click to expand...
Click to collapse
432 is stock, I can't really decide what a good change would be.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I prefer the smaller icons... my M8 is at 320 It's the perfect size.
skatin707 said:
432 is stock, I can't really decide what a good change would be.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
runnernsd said:
I prefer the smaller icons... my M8 is at 320 It's the perfect size.
Click to expand...
Click to collapse
I prefer smaller as well. I used 380 on my G2 and it worked really well.
Related
Google wallet supported.
Thread can be closed.............
...
so eventually Google wallet will be updated to allow install on the one I would assume, right?
DomSim said:
so eventually Google wallet will be updated to allow install on the one I would assume, right?
Click to expand...
Click to collapse
It should just give it time
Sent from my EVO using xda premium
DomSim said:
so eventually Google wallet will be updated to allow install on the one I would assume, right?
Click to expand...
Click to collapse
Yes eventually..
Sent from my HTCONE using xda premium
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
18th.abn said:
Google Wallet for the HTC ONE.
-Easy fix for viper Rom
-Should work on stock rooted w/ wp . -removed Kernal
-Always save your original build.prop before modifying
Using Rom Toolbox
1. Open up build.prop editor
2. Change the following values
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
3. Save changes
4. Reboot device, install wallet and open
-wallet takes a couple minutes to initialize so be patient, it works great!
5. Restore your original build.prop
This method should work fine on stock rooted also as long as you have a kernal with /system wp removed.
Also, if you don't want Rom toolbox you can navigate to /system/build.prop and open the file in any text editor to make the changes.
Click to expand...
Click to collapse
Hey does this affect the camera in any kind of way? Like the face cam. I know there was an issue with the tint of the cam. It had a red tint on the evo lte when we started doing this in the beginning.
Sent from my HTCONE using xda premium
No.....once you get Google wallet initialized and working your gonna put your original build.prop back
Sent from my HTCONE using Tapatalk 2
Guys there is an update on the market as of today and Google wallet is now working following the edited build prop
Sent from my Galaxy Nexus using xda premium
I got it work on my ATT GN2, Thanks!
Sent from my 64gb internal Jedi XP12 I317 GN2 using xda premium
Google wallet works without modification now.
Sent from my HTCONE using xda premium
tridogg97 said:
Google wallet works without modification now.
Click to expand...
Click to collapse
Glad that I'm not the only one seeing that. It still shows as unsupported, but it works.
Sent from my HTCONE using Tapatalk 2
Harfainx said:
Glad that I'm not the only one seeing that. It still shows as unsupported, but it works.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
i cant find a way to download it. did u download the apk from a 3rd party? or through the play store?
drsfinest72 said:
i cant find a way to download it. did u download the apk from a 3rd party? or through the play store?
Click to expand...
Click to collapse
Honestly I'm not sure where I got it. I believe that it came from Viperrom. Duce says that it wasn't added in d3rpONE (I noticed mine working while I was on d3rpONE, but I think something restored it from viperrom), and the only other ROM that I've run is Viper's.
Sent from my HTCONE using Tapatalk 2
Harfainx said:
Honestly I'm not sure where I got it. I believe that it came from Viperrom. Duce says that it wasn't added in d3rpONE (I noticed mine working while I was on d3rpONE, but I think something restored it from viperrom), and the only other ROM that I've run is Viper's.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
ah i see. think you could send me the apk? seems like you probably restored your apps+system data from d3rp rom to viper, as im running viperrom too and not seeing any wallet app.
Here's the link for the working (non-modified) Wallet apk that I use, with screenshot showing it on my One.
https://www.4shared.com/download/NJgEOM_0/Wallet_16-R96-v16.apk
Just install the apk normally through a file explorer, no need to push with ADB, or do anything in recovery. I uninstalled mine and tested just to be sure.
Harfainx said:
Here's the link for the working (non-modified) Wallet apk that I use, with screenshot showing it on my One.
https://www.4shared.com/download/NJgEOM_0/Wallet_16-R96-v16.apk
Just install the apk normally through a file explorer, no need to push with ADB, or do anything in recovery. I uninstalled mine and tested just to be sure.
Click to expand...
Click to collapse
kudos to you thanks bro =D
Wallet is one of my favorite android apps. Glad it is finally working
Sent from my HTCONE using xda app-developers app
Harfainx said:
Here's the link for the working (non-modified) Wallet apk that I use, with screenshot showing it on my One.
Just install the apk normally through a file explorer, no need to push with ADB, or do anything in recovery. I uninstalled mine and tested just to be sure.
Click to expand...
Click to collapse
Ok - so just to confirm (I'm a bit of a newbie) Google Wallet works on the HTC One, but you still have to root the device, yeah? Will using the DevUnlock tool from HTC work, or...?
agreen123 said:
Ok - so just to confirm (I'm a bit of a newbie) Google Wallet works on the HTC One, but you still have to root the device, yeah? Will using the DevUnlock tool from HTC work, or...?
Click to expand...
Click to collapse
No need to root. Use the download link above a few posts and install as normal.
Sent from my HTCONE using xda app-developers app
gk1984 said:
No need to root. Use the download link above a few posts and install as normal.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I tried that, but when it starts up, it says that "Google Wallet is not yet available for your device or mobile network."
I'm on AT&T.
(I guess I'm in the wrong group? I had it running on my AT&T Nexus S just fine, but I really wanted to upgrade
Think rooting would help overcome the problem of being on AT&T? Not sure why it worked on my Nexus S, since it was on AT&T too... I may have bought it as an unlocked phone, originally...
Not sure if there's any difference in support between carriers. Sorry
Sent from my HTCONE using xda app-developers app
will it root .257 firmware??
Who knows..
Sent from my C6903 using Tapatalk
I want to know I cant stand those big softkeys anymore I need to make them auto hide and small!! such a nice screen wasted with ugly soft keys.
teamHTC said:
I want to know I cant stand those big softkeys anymore I need to make them auto hide and small!! such a nice screen wasted with ugly soft keys.
Click to expand...
Click to collapse
You can always flash a prerooted .257
Look in the dev section for them. There are a couple with instructions on how flash them
Have you tried reading the update changelog on kingo website? It's very visible. Nothing about Z1 there. Simple deduction, it will most likely not root 257
Sent from my C6903 using Tapatalk
gregbradley said:
You can always flash a prerooted .257
Look in the dev section for them. There are a couple with instructions on how flash them
Click to expand...
Click to collapse
Daelyn said:
Have you tried reading the update changelog on kingo website? It's very visible. Nothing about Z1 there. Simple deduction, it will most likely not root 257
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I just don't want to take too long and any risks with flashing the prerooted 257 , I rather wait. and I contacted kingo to see if it will work.
teamHTC said:
I just don't want to take too long and any risks with flashing the prerooted 257 , I rather wait. and I contacted kingo to see if it will work.
Click to expand...
Click to collapse
It doesn't take long, and there is no risk. I am running my version now...its fine.
Kingo Android Root V1.1.1 is coming up! Many thanks to Ryan, with his help and testing work the Development Team fixed the SuperSU bug.
In this new version:
1. SuperSU updated to the latest version of v1.65
2. Fixed bugs concerning the conflict issue with certain apps after employing root script on Samsung Galaxy Note2，Note3 and S Series.
3. Removed several root scripts due to license issue, which would effect few SONY models.
This is from official kingoapp FB. Yet there are nothing specific about rooting Z1.
teamHTC said:
I want to know I cant stand those big softkeys anymore I need to make them auto hide and small!! such a nice screen wasted with ugly soft keys.
Click to expand...
Click to collapse
Hmm your right the softkeys are really huge and ugly....could you tell me how to hide them?
Sent from my C6903 using XDA Premium 4 mobile app
Thanks teamhtc I just removed my softkeys thanks to some hide softkeys app and made it that they would only show when I touch the bottom right of my screen.
It looks so much better now
Also it's really easy to go back to the old unbranded firmware and update pre rooted.
So I suggest doing that instead of waiting for kingo......
Sent from my C6903 using XDA Premium 4 mobile app
Just noticed that Private mode won't work. When I scan my fingerprint to enable it it says "Failed to enable Private mode. Please try again." Anyone else have this problem or know a solution? Much appreciated.
Sent from my Rooted AT&T Galaxy S5 using Tapatalk Pro.
Did you install xposed? If you uninstall xposed, it should work again. It's being looked into. Check out http://forum.xda-developers.com/xposed/xposed-s5-t2725405
Sent from my SAMSUNG-SM-G900A using Tapatalk
fsupartyboy850 said:
Just noticed that Private mode won't work. When I scan my fingerprint to enable it it says "Failed to enable Private mode. Please try again." Anyone else have this problem or know a solution? Much appreciated.
Sent from my Rooted AT&T Galaxy S5 using Tapatalk Pro.
Click to expand...
Click to collapse
Same error here
Well, it's fixable, but how depends on what you did. What did you do? Did you use xposed? Did you try the download booster fix? You have tell us more here than just "oh my Private mode won't work", and "same here".
I will assume you both used Xposed, since the only information is "oh my Private mode won't work". In which case you can just uninstall the framework, and that will fix private mode. If you tried the download booster, or something else, then you may have to flash the AP_G900A file from my tutorial in the general section, which will break your root until reroot and any changes you made to the system.
Rooted with xposed, few modules, few notification bar tile tweaks with sqlite, change the true to false to have UPS mode work, backed up and uninstalled and froze most bloat with tibu.
Sent from my Rooted AT&T Galaxy S5 using Tapatalk Pro.
shortydoggg said:
Well, it's fixable, but how depends on what you did. What did you do? Did you use xposed? Did you try the download booster fix? You have tell us more here than just "oh my Private mode won't work", and "same here".
I will assume you both used Xposed, since the only information is "oh my Private mode won't work". In which case you can just uninstall the framework, and that will fix private mode. If you tried the download booster, or something else, then you may have to flash the AP_G900A file from my tutorial in the general section, which will break your root until reroot and any changes you made to the system.
Click to expand...
Click to collapse
What is the file named? Is this something we can root cloak I have exposed with busybox and Wanam
galaxy s4 nutjob said:
What is the file named? Is this something we can root cloak I have exposed with busybox and Wanam
Click to expand...
Click to collapse
There are several ways that can be fixed.
It's in the Xposed Installer, if you have it click on framework and uninstall.
You can also follow this post, as it has worked for some.
http://forum.xda-developers.com/showpost.php?p=52833401&postcount=28
or you can do a downgrade from the soft bricked guide in the general section.
shortydoggg said:
There are several ways that can be fixed.
It's in the Xposed Installer, if you have it click on framework and uninstall.
You can also follow this post, as it has worked for some.
http://forum.xda-developers.com/showpost.php?p=52833401&postcount=28
or you can do a downgrade from the soft bricked guide in the general section.
Click to expand...
Click to collapse
Mine was already set to false to fix s health if I unis tall xposed will i lose all the mods as well?
galaxy s4 nutjob said:
Mine was already set to false to fix s health if I unis tall xposed will i lose all the mods as well?
Click to expand...
Click to collapse
Your mods should still be there, but just not working until you reinstall xposed. I'm not going to say that all of them will be, however. Right now I'm just uninstalling, then reinstalling xposed framework from the xposed installer, depending on whether I need the mods or private mode at that moment, until there is a working fix.
Other than that, you have to decide whether you want mods, or private mode. That's the disadvantage right now.
shortydoggg said:
Your mods should still be there, but just not working until you reinstall xposed. I'm not going to say that all of them will be, however. Right now I'm just uninstalling, then reinstalling xposed framework from the xposed installer, depending on whether I need the mods or private mode at that moment, until there is a working fix.
Other than that, you have to decide whether you want mods, or private mode. That's the disadvantage right now.
Click to expand...
Click to collapse
Ok cool thanks for the info
shortydoggg said:
Right now I'm just uninstalling, then reinstalling xposed framework from the xposed installer, depending on whether I need the mods or private mode
Click to expand...
Click to collapse
Just tried this method and no luck. Still get the same error message.
Sent from my Rooted AT&T Galaxy S5 using Tapatalk Pro.
fsupartyboy850 said:
Just tried this method and no luck. Still get the same error message.
Sent from my Rooted AT&T Galaxy S5 using Tapatalk Pro.
Click to expand...
Click to collapse
You may have to try the downgrade from the general section.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
fsupartyboy850 said:
Just tried this method and no luck. Still get the same error message.
Sent from my Rooted AT&T Galaxy S5 using Tapatalk Pro.
Click to expand...
Click to collapse
If runtime was changed from dalvik to Art private mode will not enable.... if you've switched try switching back to dalvik and it will run perfectly!
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
wynnemelvin said:
If runtime was changed from dalvik to Art private mode will not enable.... if you've switched try switching back to dalvik and it will run perfectly!
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm in dalvik.
Sent from my Rooted AT&T Galaxy S5 using Tapatalk Pro.
I would like to know if it's possible to temporary unroot my phone to use the TomTom app.
I saw that the superuser pro app has per app settings, could I use this to temporary unroot my phone?
Sorry to respond so late
You can temporarily unroot your phone safly with the checkbox in super SU (i tried it myself) I am unsure if rebooting while unrooting is okay.
If you get xposed you can use rootcloak, better than uprooting.
Sent from my Tw5ted SM-G900A using Tapatalk
Rakuu said:
If you get xposed you can use rootcloak, better than uprooting.
Sent from my Tw5ted SM-G900A using Tapatalk
Click to expand...
Click to collapse
Thanks, I'll look into this.
Any good replacements? I am rooted and can't use it
Sent from my SM-N950U using Tapatalk
jerrycoffman45 said:
Any good replacements? I am rooted and can't use it
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Also I have a gear s2 it would need to sync with
Sent from my SM-N950U using Tapatalk
S Health works. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306 do that
me2151 said:
S Health works. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306 do that
Click to expand...
Click to collapse
Thanks that worked
Sent from my SM-N950U using Tapatalk
jerrycoffman45 said:
Thanks that worked
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Hi. I too want to make s health app work on my rooted yet stock running as of now, note8. I went on the above link but the download link for app seems to be down. Could you please attach your method and the APK file you used. It would be a great help. Thanks!
Ruuu said:
Hi. I too want to make s health app work on my rooted yet stock running as of now, note8. I went on the above link but the download link for app seems to be down. Could you please attach your method and the APK file you used. It would be a great help. Thanks!
Click to expand...
Click to collapse
. Open the root file explorer and go to the /system folder.
3. Open the file named build.prop in text editor
4. In the build.prop file look for ro.config.tima=1 change the 1 to 0 and save changes
The regular shealth app will work after that
Sent from my SM-N960U using Tapatalk
jerrycoffman45 said:
Thanks that worked
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
jerrycoffman45 said:
. Open the root file explorer and go to the /system folder.
3. Open the file named build.prop in text editor
4. In the build.prop file look for ro.config.tima=1 change the 1 to 0 and save changes
The regular shealth app will work after that
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
After doing this, how can I again unroot my phone as I want OTA updates to come?
Ruuu said:
After doing this, how can I again unroot my phone as I want OTA updates to come?
Click to expand...
Click to collapse
If it is the snapdragon version you can't it is root with no updates or stock with updates. To uproot just flash stock firmware with oden warning that will wipe your phone and it will be like when you got the phone
Sent from my SM-N960U using Tapatalk
jerrycoffman45 said:
If it is the snapdragon version you can't it is root with no updates or stock with updates. To uproot just flash stock firmware with oden warning that will wipe your phone and it will be like when you got the phone
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
No sir. I've exynos version. I just want my s health app to work and then have a stock firmware on my phone for OTA updates to come!
Ruuu said:
No sir. I've exynos version. I just want my s health app to work and then have a stock firmware on my phone for OTA updates to come!
Click to expand...
Click to collapse
Ok I can't answer your question I have never had that model mine was a snapdragon hopefully someone else can help you
Sent from my SM-N960U using Tapatalk
Ruuu said:
No sir. I've exynos version. I just want my s health app to work and then have a stock firmware on my phone for OTA updates to come!
Click to expand...
Click to collapse
If you have Exynos and want stock firmware/updates, then just flash the latest stock firmware using Odin.
If on the other hand you are rooted and want to stay that way, then just make the build.prop change for s-health and enjoy. You can't get ota updates while rooted, but you could flash new updates through Odin and then re-root, etc. (but make backups first).
sefrcoko said:
If you have Exynos and want stock firmware/updates, then just flash the latest stock firmware using Odin.
If on the other hand you are rooted and want to stay that way, then just make the build.prop change for s-health and enjoy. You can't get ota updates while rooted, but you could flash new updates through Odin and then re-root, etc. (but make backups first).
Click to expand...
Click to collapse
Can I not root and then make build.prop change for s-health and then unroot via the unroot option in SuperSU app ?
Ruuu said:
No sir. I've exynos version. I just want my s health app to work and then have a stock firmware on my phone for OTA updates to come!
Click to expand...
Click to collapse
Well until some one finds a way to reset knox , i believe no other way to update OTA on rooted device. Flashing Stockrom will solved OTA problem but S Health will remain unable to Opens.
If you wants to unroot, just choose full unroot from superuser manager app after editing the build.prop (still No OTA update though)
I Hopes it helps
jerrycoffman45 said:
Thanks that worked
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
For you working also synchronisation? (Like in my screen?)
I want to root soon my N950F Pie but I want to keep sHealth usable with all my data
You are on Pie? All working?
Wave3.3 said:
For you working also synchronisation? (Like in my screen?)
I want to root soon my N950F Pie but I want to keep sHealth usable with all my data
You are on Pie? All working?
Click to expand...
Click to collapse
There is a line in build.prop that if you change, it allows you to use shealth on a rooted phone.
SnowFuhrer said:
There is a line in build.prop that if you change, it allows you to use shealth on a rooted phone.
Click to expand...
Click to collapse
Yes sir. All people say this.
"It works, it open, it work"
But I want to know if synchronisation with Samsung Account work after this.
No one use this functionality?
Wave3.3 said:
Yes sir. All people say this.
"It works, it open, it work"
But I want to know if synchronisation with Samsung Account work after this.
No one use this functionality?
Click to expand...
Click to collapse
I don't know why it wouldn't.