Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Thanks for this. Will try now.
Worked great. Had to copy the apk and odex file.
Good job! It's great to see the steps for Windows users!
Just a heads up that I simply extracted the files I needed from and on my N7 using Root Explorer, without using my PC at all.
Great guide! Method worked perfectly on my Nexus 7 going from 4.1.2 to 4.2, thanks
Please... is there some other way to update the files w/o installing Java on my Windoze PeeCee? I accidentally messed up my YouTube.apk with Titanium Backup... now I can't update from 4.1.2 --> 4.2 JB.
EDIT: JavaPortable FTW... updating (fingers crossed)
EDIT: SUCCESS TY OP!
For anyone who flashed the 4.2 clock/keyboard already
Hey, for anyone who flashed the 4.2 clock and keyboard on their Nexus 7 already and need to roll back to do the 4.2 update, I used OP's method to make a flashable zip that puts the 4.1.2 clock and keyboard back.
Worked perfectly for my Nexus 7 to get me up and running. Hope it helps anyone!
cantthinkofa.com/files/RestoreClockKeyboard.zip
galaxy nexus
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Nice Guide
perfect, the guide works just fine. Now finally running 4.2.
Awesome guide... Thanks... Happily running 4.2 now aften beeing stuck at libutils.so...
Sent from my Nexus 7 using xda premium
damagno said:
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Click to expand...
Click to collapse
I don't have a Galazy Nexus, but I think the steps should be the same. Here is a link to the factory images: https://developers.google.com/android/nexus/images#takju . It looks like they now have links for older versions, rather than just the newest images (which is how it was when I made my guide). So that's pretty sweet.
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1.
Click to expand...
Click to collapse
I was wondering if you could tell me how you did it? I'm searching a way to install 4.2.1 with no avail as of yet :crying:
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
Click to expand...
Click to collapse
Yes. I am having the same issue. I cannot update mine from 4.2 to 4.2.1. I wonder to know which original stock image you have used. Can you list a detail procedure?
Thank you very much.
Ric
dev/block/param
legom said:
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Click to expand...
Click to collapse
my error 7 was generated by emmc: dev/block/mmdblk0p7 (the file is "param" any suggestions?
Thanks. After searching for a lot of time, this post helped me updating my SGS3.:victory: I previously tried to integrate youtube update into rom using titanium backup.
GallStones said:
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual)
Click to expand...
Click to collapse
Yes, that's what I mean. The reason I didn't want to do this on my device is because I had modified some other system files that I wanted to keep the modifications for.
Wow, thanks a lot OP! Your guide helped me fixing an error during the update to 4.2.2 on my Nexus 4.
please include a video ,im getting lost in the details
solved.
If you are like me, you own an LG G4 with a bootloader that cannot be unlocked. This, at least for the moment, means that we cannot have both Android 6.0 Marshmallow and our beloved root access. We must choose one or the other. I assume that if you are reading this, that you have chosen root over marshmallow. If you did choose to stay rooted on 5.1, then I am sure you are being harassed to update. Well, I believe that I have your solution.
First, I must explain what this guide will do and what you will need.
What we're doing.
1. We will delete the update.zip.
2. We will make a dummy update.zip that will not be replaceable or modifiable, even by the root user. This fake update file will prevent a legitimate update from downloading and installing.
3. [OPTIONAL] We will remove the annoying update notification.
What is needed.
1. Root. [duh...]
2. File explorer with root privileges a.k.a. a "root explorer". (If you need one, I personally recommend the free yet feature packed ES File Explorer.)
3. A proper Busybox installation.
4. A terminal emulator.
5. A few minutes of your time.
***AS ALWAYS, I, XDA, XDA MODERATORS, XDA MEMBERS, OR ANYONE ELSE IS NOT RESPONSIBLE FOR THE CONSEQUENCES OF FOLLOWING THIS GUIDE. THE DEVICE YOU HOLD IS YOURS AND ANYTHING THAT HAPPENS TO IT IS YOUR FAULT. YOU HAVE BEEN WARNED!***
The procedure.
-Part 1.
1. Open your root explorer and make sure that it has root privileges.
2. Navigate to /cache
3. If you have a file called update.zip then delete it, if not, then just move on to part 2.
-Part 2.
4. Make a new .zip file with nothing in it and save it as update.zip (make sure it is saved to "/cache" and nowhere else, not even in a folder inside "/cache"!)
5. From here move on to your terminal emulator.
6. Once inside the terminal emulator, type the following commands.
Code:
su
cd /cache
ls
chattr +i update.zip
From here I recommend that you check that it worked by typing in
Code:
lsattr update.zip
If the command works you will see a lowercase 'i' amongst a string of letters and dashes.
-Part 3. [Optional] (I don't recommend doing this, but the harm is non-existent as far as I can tell.)
The annoying update notifications are actually Google Play Services fault. All you have to do is go to "Settings > Apps > All" and find Google play services and disable the apps ability to show you notifications.
Thats pretty much it. Now I must tell you that you will still receive notifications saying an update was downloaded, verified, and is ready to install, assuming that you did not go through with part 3. All you have to do is click the install button, and let it restart to install the bogus update. The update process will error and all you have to do now is pull and reinsert the battery and power on the phone. I have been doing this myself for a few weeks now and have not had a single issue. This also includes 4 times that it has failed to install the update from within recovery.
I hope that you find this useful and happy modding!
Reserved
Reserved.
It seem that there is a lot of confusion about how to update your phone with
the "OTA"s provided in the Stock firmware threads and from Huawei's own
support websites.
Rant Warning:
ALL Huawei Support website are totally useless to find any FW updates for any of their devices you have. They only ever show a few and most of the time none.
Once you do find FW (from another source like XDA) the accompanying "changelog.xml" file doesn't tell you anything about what the update is actually doing. They also don't tell you anything about any applied security patches. In addition it often tell you different things depending on the language you're reading. JFC!!
[EOR]
One problem is that we keep on using the term OTA for something that is essentially always
an OTA. Instead what we call it, should depend on what it is doing. What can it be doing?
1. A full factory update, that can wipe all, usually using the "dload" bootloader folder. Using /dload/UPDATE.APP of your SD-card.
2. A partial update that uses an Edify installation script in:
Code:
/META-INF/com/google/android/updater-script
but also has a one or more SOMETHING.APP in it. These are all coming in the form of an update.zip.
How to Manually update from update.zip?
Code:
0. Do not try to flash update.zip with TWRP/CWM, only use Stock Recovery.
1. Dial: *#*#2846579#*#*
2. Choose option called "Software Upgrade" and then "SDCard Upgrade" and confirm with OK.
1. Go to: Settings > Updater > "New version" > Quick Download
2. When you see the progress bar starting after a few %, hit "Pause".
3. Now open the File browser and got to the "Local" tab.
4. Navigate to the file: "Internal Storage" > "HwOUC"
5. You will see another folder with a 5-digit number, XXXXX.
This is the actual "v" number used in the URL query to fetch the OTA.
It simply corresponds to the XXXXX in:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/vXXXXX/f1/full/update.zip
6. Save time (and your data-plan) by manually downloading this file. (You should get ~10 MB/s on a good day.)
7. Inside the XXXXX folder, you will find a file called "update.zip".
Now you need to replace that file with your recently downloaded one.
8. Used adb to tranfer the file to your device
wget --show-progress -d http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/vXXXXX/f1/full/update.zip -O XXXXX.zip
adb devices
adb shell rm -fr /sdcard/HwOUC/*
adb shell mkdir /sdcard/HwOUC/XXXXX
adb push XXXXX.zip /sdcard/HwOUC/XXXXX/update.zip
# Note: speed is ~7 MB/s, so a 1.4GB OTA will take about 200 sec to transfer.
9. Enable WiFi or Mobile Data again, then hit "Resume" in the Updater.
10. The progress bar will instantly hit 100% and you will be asked to
restart right away or wait until later.
(You only have 15 seconds to decide!)
11. Your phone will reboot a few times to optimize (!?) the system.
Thanks to @shashank1320 useful but hard to read post.
Other very useful things to know about Huawei's updates.
Let's look at the last part (the file) of the Huawei update URL.
Code:
http://update..././././././././vXXXXX/f1/full/update.zip
1. To get a list of files in, and the MD5 of the OTA, use "filelist.xml".
2. To get the changelog of the OTA, use: "changelog.xml".
3. To get the "precheck-script" that does the "apply_patch_check" for
each file, use: "precheck-script". Not all updates has this.Question: Where the fcuk is the latest update?
Answer:
Quoting THIS article on how updates are pushed.
According to one of Google developers, Dan Morrill, (goo.gl/L85mSS), the
first few OTA updates are sent to 1 % of devices. It happens at random,
regardless of the location or point of sale of a phone/tablet. During
this time, bugs are identified allowing the updating process to be put
on hold if any critical errors are registered with a large number of
users.
After that over a couple of weeks, updating is provided to 25, 50, 100 %
of users, i.e. at the initial stage only one device out of a hundred
stands a chance of getting an upgrade. If the update is not received,
the device drops from the list, and subsequent repeated clicking on the
button ‘check for updates’ automatically sends the device to the bottom
of the list. When a new stage of distribution starts, clicking on the
button get a 25 % chance of receiving the update. Since the device
checks for updates on its own once a day (upon reboot), clicking on the
button might ‘jump the gun’ before it may run its course. But whatever
the outcome, only one check will be made. Subsequent clicking will not
help matters. This is not a situation where ‘first press, first receive’
(first come first serve). In any case, the over the air update will be
available to everyone within a couple of weeks.
Click to expand...
Click to collapse
.Question: WTF does that OTA do?
Answer:
If the OTA is not a UPDATE.APP, but an update.zip, then simply extract it,
and navigate to: /META-INF/com/google/android/ and open the updater-script.
For example, this line:
Code:
# v80166
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "HONOR/KIW-L21/HNKIW-Q:5.1.1/HONORKIW-L21/C432B140:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Android/msm8916_64/msm8916_64:6.0.1/MMB28B/d0090306503211916:user/test-keys");
tell you that you will not be able to use this (v80166) update, unless
your ro.build.fingerprint matches any of the shown strings. Clearly,
this FULL OTA was meant as an update to KIW-L21C432B140 build only.
New Proposal
I propose to start using the following terminology instead of just "OTA".
- DLOAD for anything that is factory reset and bootloader flashable, with no previous dependencies. (Everything that uses /dload/UPDATE.APP.)
- PATCH for anything incremental, that depend on some previous or particular state of the phone FW.
- FULL for any update that can be used to skip all previous PATCH's within the same Build (B-number). Like a cumulative update.
Let's call this "type".
In addition we should try standardize our OTA file-naming scheme. Since the current method make it
nearly impossible to distinguish between various OTA patches, we should use something like this:
Code:
<"model">_<v-number>_<type>_<build_ref>.zip
# For Example:
KIW-L21C432_v80166_FULL_C432B370CUSTC432D002.zip
And the file description should also say something about what the update does, since Huawei's changelog does not.
Something like:
"Cumulative 1% test-update for B140 EMUI 4.0.0 to B370 EMUI 4.0.3, ASPL: 20170522"
Click to expand...
Click to collapse
Where "ASPL" is referring to the resulting Android Security Patch Level date.
Finally, if someone can also squeeze in what exact security patches has been applied that would be huge!
Anyway, just some ideas I throw together to try to clear up this firmware nightmare.
(And yeah , this is not meant for you kernel devs!)
reserved to dogs running around
Thanks for the credit but I did not see anything in my post that is hard to read..no worries, keep up the good work
Nice that someone wrote this for noobs !
I am not getting update on my honor kiw-l21c185B130 plzz help
Anish karki said:
I am not getting update on my honor kiw-l21c185B130 plzz help
Click to expand...
Click to collapse
Download the later firmware from firmware finder and see if you can use dload method to update
PLEASE NOTE:This is NOT a guide to root your phone but i did provide the links to the tools to do so for most Samsung's for help with root check your own phone model forum's section.
WARMING; Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. Some methods may install additional apps/software on your device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing! Additionally this may go against your service contract which I'm not responsible for as well.
Worked for my j700p running 7.1.1 stock rooted with TWRP/SUPERSU latest. If works for you leave a thank you and confirm device.
What you need to do to get tethering on Nougat is root the device (temporarily at least), enable tethering and then (if you want) unroot it so that everything is back to normal and you can take OTA updates and use Android Pay without any issues.
All you’ll need to enable tethering on Android nougat is TWRP recovery installed on your device and the latest systemless SuperSU zip (should work with magisk as well, if someone could confirm that'd be nice) to root the device. (Always remember to backup your system just in case)
How to Enable Tethering on Android Nougat
Root your android running nougat
Edit build.prop file: Add the
net.tethering.noprovisioning
line to the bottom of build.prop file on your Android device. (Download Build.Prop Editor from the play store if you don't know how to get to this, I suggest Rom toolbox as it has build.prop included as well as terminal emulator which you will need for the next step. LINKS BELOW)
Reboot device after saving changes to build.prop file.
Download/install a Terminal emulator app from Play Store (I used the terminal emulator included in ROM toolbox but you can choose whichever you'd like.) You also WILL need busy box installed as well to be able to execute this line. (will be prompted to install upon rom toolbox install with a 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 3 apps when asked.
Reboot device
DONE!
If you wish to unroot now you can. I have not tested this so can't confirm if works after unroot but just go to SuperSu settings full unroot. Restart and you should be good. This should renable android pay.
CREDIT goes to Shivam Malani, Thank You!
Links;
Odin (for my sm-j700p I used latest everything)
https://samsungodin.com/download/
SUPERSU
http://www.supersu.com/download
TWRP
https://twrp.me
Rom toolbox lite (for build.prop editor and terminal emulator)
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
Busybox https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
Lineage 17 and last version Magisk installed.
Buildprop last version installed.
Buildprop shows SuperUser rights
I want the entry then
ro.product.system.brand
change from samsung to htc
Why? To get the Samsung Wear app working for Watch 3 ...
But I got an error.
Report from BuildProp:
Please ensure the app has root ...
But they are there and are displayed under properties ...
What am I doing wrong?
Problem solved with a workaround.
Finding: You don't need a BuildProp ...
After installing MagisK you have root rights.
As a file manager you take the TotalCommander and give it root rights.
You can then access the build.prop file in the system directory and change it with the integrated text editor.
Just stupid:
My SamsungWear app still does not start.
But this is another story...