Database Users

Removing ads on 5.1.1

I have found a way to remove ads on 5.1.1, it is exactly the same way as 5.0.1 except you NEED root for it to work.
Type in the following commands in a command prompt. Be sure USB debugging is on and it is securely connected to your computer. Although you do type reboot as the last command, the tablet turns off, just press the power button . This was successful on two of my tablets.
Code:
adb shell
su
At this point grant superuser access from the tablet
Code:
pm hide com.amazon.kindle.kso
exit
reboot
In theory this should work from a terminal emulator straight on your tablet but I have not tried it out
EDIT:
I should have explained the process better as some people are getting confused.
1. Make sure you have the correct drivers and USB debugging turned on your tablet.
2. Download this one click tool to gain root access if you have not done so already. Make sure to disable OTA updates from the tool as well (not necessary for removing ads but will be useful in the future).
3. Open a command window on your computer and type the commands above. If you have root you should get a
Code:
#
symbol after typing the su command.

Hello, it's my first post here so I apologize if the question is basic - I went thru all of the steps in other fourms last night and got Google Play to install just fine and even temporarily I appear to get the lock ads to remove but at best that doesn't seem to last past a reboot. After some further reading I found that unfortunately the kindle did a OTA update to 5.1.1 and that explains the reason I've been unable to permanently get rid of those lock ads.
I read your post, but I'm unclear on what I need to do to get root access (I mean without completely rooting the thing) I ran ADB from a windows command line, but I get a "not found" command when i type in SU..here's what it looks like (I'm putting my typing in bold, and the auto generated command line stuf in regular):
========================================
c:\amazon>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127:[email protected]:/ $
=====================================
Since I've only done the automated scrip that is supposed to allow google play and remove ads, I didn't really expect to have root access, but I'm hoping there's some way I can get this to work without trying to fully root the kindle. If I have to go that route I might as well get rid of the entire Kindle OS... I don't actually want to do that, as I use amazon prime so a lot of the default junk that comes with this kindle is useful.

Big-T said:
Hello, it's my first post here so I apologize if the question is basic - I went thru all of the steps in other fourms last night and got Google Play to install just fine and even temporarily I appear to get the lock ads to remove but at best that doesn't seem to last past a reboot. After some further reading I found that unfortunately the kindle did a OTA update to 5.1.1 and that explains the reason I've been unable to permanently get rid of those lock ads.
I read your post, but I'm unclear on what I need to do to get root access (I mean without completely rooting the thing) I ran ADB from a windows command line, but I get a "not found" command when i type in SU..here's what it looks like (I'm putting my typing in bold, and the auto generated command line stuf in regular):
========================================
c:\amazon>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127:[email protected]:/ $
=====================================
Since I've only done the automated scrip that is supposed to allow google play and remove ads, I didn't really expect to have root access, but I'm hoping there's some way I can get this to work without trying to fully root the kindle. If I have to go that route I might as well get rid of the entire Kindle OS... I don't actually want to do that, as I use amazon prime so a lot of the
default junk that comes with this kindle is useful.
Click to expand...
Click to collapse
Yeah it could have been better explained, they meant that process works if your tablet is rooted.
You won't get root commands to work in shell like that if it isn't rooted. Like it says the su file isn't there.
A lot changed yesterday with respect to 5.1.1 and root.
So you could use the temporary root found yesterday to gain access. Should be able to disable it from there. (First two code boxes there show the temp root access and the resulting prompt, the third lets you make it permanent). Though not sure why rooting it is tantamount to removing the entire OS tbh anyway.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362

Pond-life said:
Yeah it could have been better explained, they meant that process works if your tablet is rooted.
You won't get root commands to work in shell like that if it isn't rooted. Like it says the su file isn't there.
A lot changed yesterday with respect to 5.1.1 and root.
So you could use the temporary root found yesterday to gain access. Should be able to disable it from there. (First two code boxes there show the temp root access and the resulting prompt, the third lets you make it permanent). Though not sure why rooting it is tantamount to removing the entire OS tbh anyway.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Click to expand...
Click to collapse
Thank you! It appears I finally got the ads cleared permanently although I had a few hiccups along the way. I'm going to try to step-by-step this for anyone else that may have problem like I did (First andriod device, first time messing with one)
1) Got my kindle yesterday and it did an automatic over the air update to 5.1.1 - Found instructions for installing the google play store and removing ads in this excellent thread http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
2) Downloaded "Amazon-Fire-5th-Gen-Install-Play-Store.zip" file from rootjunkysdl.com but had some problems getting my device to recognize correctly. I found the only drivers to work on two seperate computers were from the amazon website https://developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing#Introduction
3) After I got the drivers to install I ran the "1-Install-Play-Store.bat" file from step #1. The batch file guided me thru everything and the Google Playstore worked just fine. At first I thought I got rid of the lock screen ads as well, but after my first reboot the ads came back.
4) This thread pointed out that with the new 5.1.1 updated you had to have root access enabled. I tried to do so, but the commands weren't working. The problem was, I was missing a critical step that wasn't explicitly stated in the other threads YOU MUST INSTALL THE ROOT_FIRE.ZIP and point your command prompt window to this extracted folder...even though the zip file in step#1 has an adb.exe it's missing other files to get you root acees
http://rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen
5) After unpacking and running the commands as provided, the ads are gone. I'm attaching a link to a screenshot of my command window so folks can see what they should be typing in:
https://www.dropbox.com/s/icyyzr14limkosu/Capture.JPG?dl=0

Big-T said:
Thank you! It appears I finally got the ads cleared permanently although I had a few hiccups along the way. I'm going to try to step-by-step this for anyone else that may have problem like I did (First andriod device, first time messing with one)
1) Got my kindle yesterday and it did an automatic over the air update to 5.1.1 - Found instructions for installing the google play store and removing ads in this excellent thread http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
2) Downloaded "Amazon-Fire-5th-Gen-Install-Play-Store.zip" file from rootjunkysdl.com but had some problems getting my device to recognize correctly. I found the only drivers to work on two seperate computers were from the amazon website https://developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing#Introduction
3) After I got the drivers to install I ran the "1-Install-Play-Store.bat" file from step #1. The batch file guided me thru everything and the Google Playstore worked just fine. At first I thought I got rid of the lock screen ads as well, but after my first reboot the ads came back.
4) This thread pointed out that with the new 5.1.1 updated you had to have root access enabled. I tried to do so, but the commands weren't working. The problem was, I was missing a critical step that wasn't explicitly stated in the other threads YOU MUST INSTALL THE ROOT_FIRE.ZIP and point your command prompt window to this extracted folder...even though the zip file in step#1 has an adb.exe it's missing other files to get you root acees
http://rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen
5) After unpacking and running the commands as provided, the ads are gone. I'm attaching a link to a screenshot of my command window so folks can see what they should be typing in:
https://www.dropbox.com/s/icyyzr14limkosu/Capture.JPG?dl=0
Click to expand...
Click to collapse
Think it might depend when you downloaded the Amazon-Fire-5th-Gen-Install-Play-Store.zip, the zip has been around for some time and he updated it several times last night and somewhat confusingly kept the same name for it and the batch file inside.
The current zip and a few other versions last night has the root riles in the "files" directory that the batch uses them from there. Even then the order of the commands isn't ideal I don't think as the block the ads one comes in the install google play one before the root install which it relies on it.
I think if adb shell pm hide com.amazon.kindle.kso was moved to the blocking 5.1.1 OTA section and updated the same way those OTA hides were to
adb shell su -c "pm disable com.amazon.kindle.kso"
so that section would be
adb shell su -c "pm disable com.amazon.otaverifier"
adb shell su -c "pm disable com.amazon.device.software.ota"
adb shell su -c "pm disable com.amazon.settings.systemupdates"
adb shell su -c "pm disable com.amazon.kindle.kso"
5? You know everything failed in that pic right?

Pond-life said:
5? You know everything failed in that pic right?
Click to expand...
Click to collapse
Yeah, lol! [laughing with not at] It looks like the commands are failing because he's already in su! Something weird happened at the line:
adb wait-for-device && adb shell
. . . and he went into su (#), so subsequent shell and su fail, but the "pm hide" works! But then the one "exit" takes him out, as though he actually was only in shell. This is really strange.

Worked perfectly! Thanks

I was having issues with the supertool and even another manual entry way of blocking ads, but this seems to have worked.
Thank you!

If you're rooted, why not use an app instead of doing this via adb.
S6 EDGE TMO

dEris said:
If you're rooted, why not use an app instead of doing this via adb.
S6 EDGE TMO
Click to expand...
Click to collapse
Amazon lockscreen ads are not the same as google ads. The lockscreen ads don't go away with ad blockers. That was the first thing I tried after root. Of course, someone could just make an app that runs this script specifically for this device but I find this way pretty simple

phonehunter59 said:
Amazon lockscreen ads are not the same as google ads. The lockscreen ads don't go away with ad blockers. That was the first thing I tried after root. Of course, someone could just make an app that runs this script specifically for this device but I find this way pretty simple
Click to expand...
Click to collapse
You can disable apps with app freezer apps in the play store. Therefore, instead of using adb to disable apps, use an app. App app app lol
S6 EDGE TMO

Editting Build.prop

I'm trying to add net.tethering.noprovisioning=true to my build.prop but can't do it. I am rooted and have an unlocked bootloader. Rootexplorer and ES File Explorer can't do it. So I copied the build.prop, made my change, went to Twrp, mounted system, pasted my build.prop and rebooted and the original build.prop was back.
I guess I need to have a script run after boot to mount system and echo >> the statement into the buildprop. Any suggestions how to run the script or get my build.prop to stick.

Try disabling system write protection.
http://forum.xda-developers.com/axo...to-persist-t3440276/post68206618#post68206618

xtermmin said:
Try disabling system write protection.
http://forum.xda-developers.com/axo...to-persist-t3440276/post68206618#post68206618
Click to expand...
Click to collapse
I did get it to stick finally but I did not accomplish what I wanted. I was looking to hide tethering from the carrier. It worked on Nexus6P. I can't get my ATT unlimited ipad sim to work my Axon7 but it works fine every other device I own except Windows Phone. Guess my Moto E will continue to be my hotspot.

Try using terminal emulator and type these two commands
Su
Settings put global tether_dun_required 0
Worked no problems for me on my axon (also made the build.prop edit of course)

[Sprint/others?] Hotspot now functions correctly with root

Hi there, before now some people were having issues with the hotspot workarounds, where they could enable the hotspot but attached devices received no actual internet. I didn't do any polling but it seemed to be mostly a Sprint phenomenon, as after doing the magic hotspot trick most other people had no issues.
I just tested it, and the new root will get you functioning hotspot on Sprint, and possibly for other people too who were having the same problem. I ran the following code while the hotspot happened to be off, and after turning it back on I was able to get internet through it on other devices. If you try this with the hotspot already enabled please report back so we know if it needs to be either particular setting. Use a normal command line where you have adb.exe and run this command while the phone is on and no further action should be needed once you turn on the hotspot.
Code:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
Just having root itself has not enabled the normal hotspot switch locations, like in the notification drawer or in the tethering settings, and I still had to use the network refresh trick to get them to work. This may need another command to insert/change the correct protection setting, or something else entirely.
I also went back to the APN settings through the shortcut maker and received the same error I had before, about this user not being able to access them.
On a related note, I saw some people mention that their hotspot would automagically turn off after 10-20 minutes, so I'll post this now and keep an eye on whether it does so here, as I never watched before.

I used that code for my Nexus 5 on T-mobile without rooting. My Pixel is on back order and not able to test it on T-mobile. Is it necessary to root for only the phones on Sprint? Anyone test it on T-mobile (for native hotspot)?

Sorry, yes, I copied my post from a comment I made in another hotspot thread where the code was brought up and I tested it, but it didn't work for me without root. Some people were able to use hotspot after using a workaround, including Verizon, but it seemed like for Sprint doing that gave hotspot but no internet access. Once you get your phone I would check out that workaround comment, and if you have problems try the root command.

Sprint Tether working now for me on adroid 7.1
I tried many things including the above..but none worked. I was able to root the system and what worked for me.
I followed these directions
Go here http://www.theandroidsoul.com/enabl...ing-pixel-and-pixel-xl-verizon-sprint-others/
Setup ADB and Fastboot on your PC (link).
Download the CarrierEntitlement.apk file and save it to a separate folder on your PC.
Connect your Pixel phone to the PC.
Open a command window inside the folder where you saved CarrierEntitlement.apk file in Step 2 above. To do that, “Shift + Right click” on any empty white space inside the folder and then select Open command window here from the context menu.
Once the command window is open, issue the following commands one-by-one disable provishning checks on your Pixel phone:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
└ You may get a prompt on your phone to grant root access, accept it.
mkdir /su/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /su/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /su/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /su/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /su/su.d/05TetherMod
chmod +x /su/su.d/05TetherMod
reboot
Your phone will now reboot. Once that is done, go to Settings » More » Tethering & portable hotspot » and enable Portable WiFi hotspot. It should work.
I found this did work to enable the wifi hotspot app but this didnt let the computer connected browse the internet.
I then found this and now im able to browse on a computer connected to my hotspot
http://www.theandroidsoul.com/enable-tethering-nougat-alongside-android-pay/
I only used this part
Download/install a Terminal emulator app from Play Store (link →).
Make sure the terminal asked for rights when typing su because you have to grant it before it works correctly
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
Now my computer connected to the hotspot worked perfect and im very happy.
but i think if you follow this you can get it working right away without my above stuff.
Root your Android device running on Android 7.1 Nougat.
Edit build.prop file: Add the net.tethering.noprovisioning=true line to the bottom of build.prop file on your Android device. Use the link below for help with editing build.prop file.
How to edit build.prop on a rooted Android device
Reboot device after saving changes to build.prop file.
Download/install a Terminal emulator app from Play Store (link →).
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device.
That’s it. You should have Tethering enabled on your Android 7.1 Nougat running device now.
I hope this helps as I haven't found this info in one area on here and sorry if it is but I didnt find it.

HOW TO: Disable Carrier Tether Check

NOTE: See nvrpunk's 1st comment after post for a superior method. (attached files still apply)
I have the Pixel 2 (not xl) from the Google Play Store. I am using it on Verizon, with a plan that doesn't allow tethering.
I cobbled together these three sources and modified the commands till they worked on the Pixel 2 (nonxl), I'm sure it's not the prettiest, but it works.
I used a USB-C to USB-A 3.0 cable.
(On the november security update OPD1.170816.018)
I don't know if this survives OTA.
Sources:
https://forum.xda-developers.com/showpost.php?p=74388277&postcount=19
https://www.theandroidsoul.com/enab...ing-pixel-and-pixel-xl-verizon-sprint-others/
https://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
------------------------------------------------------------------------------------------------------------
1 - Unlock Bootloader----------------------------------------------------------------------------------
adb reboot bootloader
fastboot flashing unlock
2 - Root--------------------------------------------------------------------------------------------------
**(through computer command prompt with files in the same folder as adb&fastboot)**
fastboot boot twrp-3.1.1-alpha1-walleye.img (For temporarily booting twrp)
**allow changes to system**
**enable adb sideload in advanced menu of twrp**
adb sideload Magisk-v14.3(1437).zip
**reboot system - didnt install twrp app**
3 - Bind Modified Entitlement APK------------------------------------------------------------------
**(through computer command prompt with files in the same folder as adb&fastboot)**
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
mkdir /sbin/supersu/
mkdir /sbin/supersu/su.d/
mkdir /sbin/supersu/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /sbin/supersu/su.d/05TetherMod
chmod +x /sbin/supersu/su.d/05TetherMod
reboot
--------------------------------------------------------------------------------------
You should now be able to tether!
--------------------------------------------------------------------------------------
4. OPTIONAL unroot (tether is blocked again) ---------------------------
adb reboot bootloader
fastboot boot twrp-3.1.1-alpha1-walleye.img (For temporarily booting twrp)
*enable adb sideload in advanced menu of twrp*
adb sideload Magisk-uninstaller-20170928.zip

My steps:
1 - Fresh install + Unlock Bootloader
Use a fresh OTA firmware, flash_all.bat (I used image-walleye-opd1.170816.025.zip)
Boot into fastboot mode using Power + Volume down.
fastboot flashing unlock
2 - Root phone using Magisk
**(through computer command prompt with files in the same folder as adb&fastboot)**
fastboot boot twrp-3.1.1-alpha1-walleye.img (For temporarily booting twrp)
**allow changes to system**
**enable adb sideload in advanced menu of twrp**
adb sideload Magisk-v14.3(1437).zip
**reboot system - didnt install twrp app**
3 - Edit build.prop
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "net.tethering.noprovisioning=true" >> /system/build.prop
reboot

When I tried just a build.prop edit.. it didn't work. (Verizon Unlimited (old grandfathered plan w/o tethering))
I feel like the build.prop is only half of it.
I think the other half is this command, but I couldn't get it to run:
su
settings put global tether_dun_required 0
exit​
It just turned back errors. like "/sbin/sh: settings: not found" So I'm not sure what I did wrong.
Which is why I went the mod-ed apk route.

The build.prop edit worked for me (I used the app build.prop editor with Magisk as above). I'm on the same Verizon Unlimited-grandfathered plan.

build.prop edit via root explorer worked for me as well. same unlimited grandfather plan

So I did a clean flash-all.bat to OPD1.170816.025.
I can confirm nvrpunk's method worked for me.
Do this method.
(Note: un-rooting breaks it for me)

nvrpunk said:
My steps:
1 - Fresh install + Unlock Bootloader
Use a fresh OTA firmware, flash_all.bat (I used image-walleye-opd1.170816.025.zip)
Boot into fastboot mode using Power + Volume down.
fastboot flashing unlock
2 - Root phone using Magisk
**(through computer command prompt with files in the same folder as adb&fastboot)**
fastboot boot twrp-3.1.1-alpha1-walleye.img (For temporarily booting twrp)
**allow changes to system**
**enable adb sideload in advanced menu of twrp**
adb sideload Magisk-v14.3(1437).zip
**reboot system - didnt install twrp app**
3 - Edit build.prop
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "net.tethering.noprovisioning=true" >> /system/build.prop
reboot
Click to expand...
Click to collapse
I'm on image-walleye-opd1.170816.025.zip, just getting a blank screen after fastboot boot twrp-3.1.1-alpha1-walleye.img, what am I missing? I've tried it in all 4 USB ports and in both cmd and through SkipSoft.

Why don't you just use the Magisk module for tethering: Tethering Enabler.
VZW unlimited user here.
Also, the elevated commands I have used in the past where I would add them to a init.d script:
setprop net.tethering.noprovisioning 1
settings put global tether_dun_required 0

I bought a pixel 2 from Google play, I'm on Verizon and I can tether fine? I'm not getting charged. I must be lucky.
Sent from my Pixel 2 using Tapatalk

Izeltokatl said:
I bought a pixel 2 from Google play, I'm on Verizon and I can tether fine? I'm not getting charged. I must be lucky.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Which unlimited plan? The grandfathered one? or the new 22gb unlimited plan?

Alright so did these steps and was able to activate tether/hotspot on the Sprint network with a Pixel 2 XL however, no data is being passed through though.
Using Magisk Manager 5.4.3 on v14.5
My plan is the Everything Data Family 1500 Plan on Sprint
Sprint users may require an additional step if no data is able to pass through
Open adb shell.
Type following command
>settings put global tether_dun_required 0
>reboot

So step 1 that nvrpunk has posted.
Is it necessary if it's a brand new phone?
Thank You

I just edited my build.prop with net.tethering.noprovisioning=true
Sent from my Pixel 2 using Tapatalk

This really works!! But it's key to revert your phone to the image-walleye-opd1.170816.025.zip I did a factory wipe in recovery mode then used adb sideload to install it. Then followed the directions as stated.
THANK YOU THANK YOU THANK YOU!!

With January security update rolling out I was wondering is it possible to update and retain tethering without going through the whole process of re-rooting again?

highly unlikely

Mr.Bulldog said:
Alright so did these steps and was able to activate tether/hotspot on the Sprint network with a Pixel 2 XL however, no data is being passed through though.
Using Magisk Manager 5.4.3 on v14.5
My plan is the Everything Data Family 1500 Plan on Sprint
Sprint users may require an additional step if no data is able to pass through
Open adb shell.
Type following command
>settings put global tether_dun_required 0
>reboot
Click to expand...
Click to collapse
That worked for me

on Verizon newer 22GB unlimited plan. I have recently discovered that Big Red is able to see the tethered data and reporting it as hotspot data and not regular phone data. Needless to say i discovered this too late and am now above my 15gb limit and am now throttled. Is there any updated workaround? Anyone else seeing this now as well??

madspeed said:
on Verizon newer 22GB unlimited plan. I have recently discovered that Big Red is able to see the tethered data and reporting it as hotspot data and not regular phone data. Needless to say i discovered this too late and am now above my 15gb limit and am now throttled. Is there any updated workaround? Anyone else seeing this now as well??
Click to expand...
Click to collapse
I made the move to the new "Unlimited" Verizon plan as well and I'm searching for this answer too. I'd like a way to make Verizon think I'm using regular data still. For me (usually under 22GB) it would be nice to be able to toggle it too. You know, like use about 5 or 10 GB of tethered data with the obscured meeting and then remove the fix to allow Verizon to see the next 10 GB as hotspot data. Essentially it would allocate part of my normal un-prioritized 22GB to hotspot without going over the 10 GB mark.
I guess this is predicated on the idea that the new plan allows 10 GB tendering in addition to the 22 GB of normal data usage. If that's not accurate then I guess I'd still like the fix, but don't really need to ability to un-apply it.

I was successful for the time being using the app PDA+. Only downside is that it must work through a computer. I have the app installed on my spare android device as well as on a backup laptop. Plug in the USB from the phone to the computer, then i have an ethernet cable from computer to my home router. I am using usb tethering, but also works with wifi. I used 80gig of phone data and 25 gig of hotspot data last month. I only figured the work around after hitting my 15 gig hotspot cap. I will say it was a pain in the arse to get setup initially, but has been working flawlessly ever since. I do still get prioritized after hitting the 22 gig cap, but even streaming several Firesticks it works fine.
PDA+ will work in your case as long as you have a computer available.

Guide: Tweaking AOSP to Pass Integrity Test and Get Gear App working

Hey S7 Users!
I don't know how many of you have experienced the problems that I have encountered while trying to run AOSP (Specifically Resurrection Remix 6.2.0) on the S7 such as passing integrity check or getting the gear app to work but they have been an issue for me. I'll be putting here what I did to get these things to work that I figured out over time and hopefully will save some people time. And sorry if the format is weird it's my first time making a guide and posting.
The problems that I'm going to address specifically are:
- Passing CTS Integrity
- Getting the Gear App to Work
First off, the CTS integrity. When you first install the ROM, you might find that you cannot download certain apps or that apps don't work correctly. Thats because the CTS integrity is tripped. This is because the Phone does not have a proper build fingerprint since it is a Custom ROM.
To fix this you're going to need Magisk (Link) and Magisk Manager and also Terminal Emulator (Link). Follow the instructions and once installed go into Magisk Manager and you can check that your CTS Integrity is False.
Next go to the download modules section
Screenshot
Then search for Magisk Hide Props Config, install it and then reboot.
Once rebooted open terminal emulator, grant it SU access and type "props"
A menu should appear: Screenshot
Now type 1 and press enter and this should pop up: Screenshot
Next type f then this will pop up: Screenshot
From there select the number that corresponds to Samsung or whatever phone you want although I haven't checked this to see if it works but I don't see why not. Then look and find the one labeled "Samsung Galaxy S7 (8.0.0)" should be 16.
Once you have selected 16(or what ever one you picked) type y and press enter to change the fingerprint: Screenshot
After it is finished it will ask you to reboot. Once rebooted go into Magisk Manager and check that CTS Integrity is now true. Also, go and clear the data and cache of the Play Store and the Play Services. Now you can download apps and use Google Pay
Now for the real challenge the Gear app. This one stumped me for a long time and made me want to just go back to stock. But I kept going and eventually figured it out.
Setting the fingerprint was only the first step because before you could not install it. Now when you open it it'll tell you that you've made unauthorized changes etc. because it thinks that the S7 is on stock firmware but when it checks it sees that it isn't. So what we are going to need to do is change the build.prop to make it look like a different phone. I'll link mine down below if you want it but it is a herolte (S7 Exenos) so keep that in mind as it might brick your system. This will involve some Linux skills.
For this one it is easier if you do it from a computer and then do adb shell. Enable Debugging in the Developer settings and then adb into the device with:
Code:
adb shell
Then
HTML:
su
(Allow it the Super User Access)
Next you have to set the /system to R/W so do that with the command:
Code:
mount -o rw,remount /system
After you have done that type:
Code:
cd /system
And then set permissions on the build.prop:
Code:
chmod 644 build.prop
At this point what you want to do is exit out of the shell (so type exit twice). Now type:
Code:
adb pull /system/build.prop
This will pull the build prop but it goes to different places. I suggest you look up where it stores it as it will vary where it drops it depending on operating systems. For me in Windows it is the following:
Code:
C:\Users\<account_name>\AppData\Local\VirtualStore\Program Files (x86)\MyCustomADBInstallLocation\
Now that you have it simply open it in a text editor and edit the following lines:
Code:
ro.product.brand=htc (change from samsung to htc)
ro.product.manufacturer=htc (also change from samsung to htc)
After that save the file and then go back to the terminal and type(Assuming you haven't moved the file):
Code:
adb push build.prop /sdcard
This will move it to the internal storage since at least for me i could not push it directly to /system
Now do another adb shell and su then type these commands to delete the old one, copy the new one in and then change the system back to read only(This is very important to avoid bootloops!):
Code:
rm /system/build.prop
cp /sdcard/build.prop /system
mount -o ro,remount /system
And then exit out of the adb then reboot the phone. If all goes well then it should reboot and the gear app should work now. Woohoo! That was pretty involved and I'm sure there is a more efficient way to do that (feel free to comment and suggest one) but I can guarantee that it works. Also feel free to ask questions and I can try to answer them. Anyways guys if this helped please hit the thanks button. This took many hours for me to figure out and I hope it all works out for you. Cheers!