Related
I'm trying to edit the build.prop file on the G2 803 model. It's rooted and unlocked on a stock Bell Rom. The phone has the wi-fi forgetting problem. everytime I reboot it I have to reset the wifi password. I've tried editing the build.prop file to change the wifi.lge.patch line to=false but I can't seem to enter more than 4 characters after the = on that line. Am I missing something?
Use build prop editor free on playstore
_____________________________________Read more write less and be smart
siggey said:
Use build prop editor free on playstore
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
Thanks, I tried that but the changes don't appear to stick.
Fraggle_Shamy said:
Thanks, I tried that but the changes don't appear to stick.
Click to expand...
Click to collapse
Reason 1: Some build.prop values get their values from the ramdisk on each boot, so that's why some values wont stick.
Reason 2 (requires root): build.prop is located in /system. Your /system may be read-only, we want it to be read-write to make changes, so.. run the following command in a Terminal Emulator downloaded from the play store. Run the following commands,
Code:
su
mount -o rw,remount /system
Now make your build.prop changes. Once finished run the following command to get your system back to how it was,
Code:
mount -o ro,remount /system
If the app isnt helping you, download a file explorer such as ES and navigate to /system/build.prop, open the file and edit the values you want.
Note: It's nice to hit the "Thanks" button under our posts if you indeed are thankful. Saying thanks and not hitting the thanks button is a slap in the face .
Thanks for the suggestion, but the emulator didn't help. I'm guessing it's because it's locked to the boot rom (your first suggestion)? Any way around this? I have anohter 803 that doesn't have this issue. Can I copy the ROM from that phone to the problematic one?
Fraggle_Shamy said:
Thanks for the suggestion, but the emulator didn't help. I'm guessing it's because it's locked to the boot rom (your first suggestion)? Any way around this? I have anohter 803 that doesn't have this issue. Can I copy the ROM from that phone to the problematic one?
Click to expand...
Click to collapse
Try this. (Pretty much the same as a previous suggestion, doubt it will work)
Get a root capable browser. Jrummy has one that's free, I think it's called Root Browser.
Browse to /system there should be a button to mount it r/w, if not it may prompt you when you go to edit the file... Long click the file, and try to open for editing. (it may be some other combination, I don't have my phone handy right now). Make the a change or two, reboot and see if they stick.
Or the other thing you cna do is:
The other thing you can try is to do is check if they're being set on boot.
adb pull /*.rc
which will pull all of the ramdisk's initialization scripts into your current folder on your computer. Look through them and see if the values are indeed being set by the boot image. If they are, you'll need something like AIK (android image kitchen) to extract the ramdisk, either change or delete those lines, rebuild the boot.img and flash it (using flashify or manually using adb and dd). You have to rebuild them into the boot.img, any changes you make to them directly on the phone will never stay as they get re-created every boot. It's a pretty roundabout way to do it, but it's entirely possible to do.
A much easier, and less likely to cause you issues would simply be to create an init.d script that sets it. This will occur after whatever is setting it in your boot.img so there would be no need to recreate that.
create a file in /etc/init.d called something like... "Set_wifi_pass" set the permissions so that it can be executed and read by everyone.
Then enter the following:
Code:
[B][I]#!/system/bin/sh[/I][/B]
setprop wifi.lge.patch = WifiPassword
You can check that it worked by going through adb shell with
adb shell
getprop wifi.lge.patch
which should return that value you set. Same thing that build.prop is ultimately doing, just in a different way.
Hope that helps.
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.
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.
UPDATE: November 26.
It also works with Tmobile and Verizon (unlocked phone)
Running on latest Pie 9.0 and November update, and magisk beta 17. 3
Original.
you need to root the phone. Or else it does not work.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
@filthysanches did a detailed step by step for newbies down below.
Thanks.
filthysanches said:
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
Click to expand...
Click to collapse
I can confirm this method works. Well, instead of editing build.prop directly, I used the Magisk module Tethering Enabler which does the same build.prop modification but will allow it to pass safety net checks, then used the adb command above. Thanks for posting the commands!
beezar said:
I can confirm this method works. Well, instead of editing build.prop directly, I used the Magisk module Tethering Enabler which does the same build.prop modification but will allow it to pass safety net checks, then used the adb command above. Thanks for posting the commands!
Click to expand...
Click to collapse
Do you have a tutorial link for this, I've followed at least 3 of them I've found online and I can't get Magisk modules to install. Says that /system can't be mounted.
eloko said:
you need to root the phone.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell.
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
Click to expand...
Click to collapse
does this work the same way using android sdk?
Step 1: open command window
Step 2: type "cd (folder location of the platform-tools sdk)"
step 3: type "settings put global tether_dun_required 0"
step 4 :type "reboot"
I'm going to try this when I get home, just wanted to confirm if this method makes sense.
Step 2.5 type adb devices. If you see your device then step 2.6. type adb shell
Boom! Works now. Thanks ya'll.
I did everything with adb... I think modules with magisk are tricky sometimes
Am I getting the error on startup about something being wrong with my system because I didn't run the settings put global tether_dun_required 0 command? (I only installed the Magisk Module)
uofirob said:
Am I getting the error on startup about something being wrong with my system because I didn't run the settings put global tether_dun_required 0 command? (I only installed the Magisk Module)
Click to expand...
Click to collapse
If Magisk is showing installed you are you able to download root explorer from play store. If so then open the system folder in root explorer and then drill down to build.prop. Click on it and choose to open with text editor. Scroll way down to the bottom and on the first empty line put
net.tethering.noprovisioning=true
Save and exit.
Reboot.
Should have native tethering now. ADB shell is not needed. I do this on Verizon. LMK if there are extra steps required for other carriers.
Thanks!!
cedargreen said:
If Magisk is showing installed you are you able to download root explorer from play store. If so then open the system folder in root explorer and then drill down to build.prop. Click on it and choose to open with text editor. Scroll way down to the bottom and on the first empty line put
net.tethering.noprovisioning=true
Save and exit.
Reboot.
Should have native tethering now. ADB shell is not needed. I do this on Verizon. LMK if there are extra steps required for other carriers.
Thanks!!
Click to expand...
Click to collapse
Magisk works, tethering works with the module. Only issue I have is when I startup I get a popup that says "There's an internal problem with your device. Contact your manufacturer for details." but nothing seems to be really wrong with the phone... It still works, makes calls and can tether... so it's just an annoyance. I've seen some mentions of that system error from other phones, and it was because the vendor buildprops doesn't match the system buildprops. I'm wondering if the extra command that was mentioned would fix this. Has anyone else seen this error?
uofirob said:
Magisk works, tethering works with the module. Only issue I have is when I startup I get a popup that says "There's an internal problem with your device. Contact your manufacturer for details." but nothing seems to be really wrong with the phone... It still works, makes calls and can tether... so it's just an annoyance. I've seen some mentions of that system error from other phones, and it was because the vendor buildprops doesn't match the system buildprops. I'm wondering if the extra command that was mentioned would fix this. Has anyone else seen this error?
Click to expand...
Click to collapse
Had that too on wife's phone that was rma'd due to constant boot loops. Only thing I have done differently is to delete the net.tethering.noprovisioning=true as well as going into magisk and uninstalling back to normal boot img, prior to taking the Nov OTA. Once that was done I went into twrp and reflashed the magisk zip then redid the build.prop.
My noob understanding of that popup is that something in system has been modified (build.prop?) Causing the notification.
I rma'd before I was able to read about it so couldn't test to see if I could complete uninstall then back to factory then update everything and finally magisk, edit build.prop.
eloko said:
you need to root the phone.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell.
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
Click to expand...
Click to collapse
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
I know this is mentioned for Sprint but on stock 025, Nov sec, rooted with Magisk, the above did not work on MetroPCS
access unravel
As a side note, installing a root access "app hider" will reverse the second part of this process breaking connectivity. Not a huge deal but worth noting, as I'm not sure what root access apps will also reverse this.
Has anyone confirmed this works with T-Mobile by checking their tether allowance after testing tethering?
filthysanches said:
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
Click to expand...
Click to collapse
Worked perfect. Thank you.
I am looking for non root solution but so far I can't find it
Got it work
https://forum.xda-developers.com/pixel-2-xl/how-to/root-sprint-hotspot-t3738118
Thank you for breaking this down and explaining it. I performed the first part with the buildprop editor using ES File Explorer with root permissions. It still didn't work so I had to wait till I was done with work to perform the second process with ADB and all is working now so happy. I just got my pixel 2XL and wasn't sure if this would work or not.
Thank you so much too whoever solved this.
rockingondrums said:
Has anyone confirmed this works with T-Mobile by checking their tether allowance after testing tethering?
Click to expand...
Click to collapse
did anyone ever confirm this?
Can anyone confirm if this works on pie? Carrier has my tethering disabled.
Hi Guys,
I am no developer but I need to edit the libnfc-nxp.conf in /system/vendor/etc to use nfc-sim.
I guess I need to unlock bootloader, flash the working twrp, get root and just use root explorer to edit the file?
Will it reset back to original file bcos of A/B partition thing when reboot?
Thanks if any android expert can let me know.
laocheebye said:
Hi Guys,
I am no developer but I need to edit the libnfc-nxp.conf in /system/vendor/etc to use nfc-sim.
I guess I need to unlock bootloader, flash the working twrp, get root and just use root explorer to edit the file?
Will it reset back to original file bcos of A/B partition thing when reboot?
Thanks if any android expert can let me know.
Click to expand...
Click to collapse
Yes, you need to be rooted.
It will not alter the file on reboot.
I tried to edit libnfc-nxp.conf in /system/vendor/etc, but it resset to default after phone reboot.
Also, i can's repair my gpay with free bootloader and magisk intalled. So i deside to return device to closed one.
Well if you still have a locked Bootloader and unrooted, why would you need to edit that file for? If Google Pay, there is no reason why it wouldn't work. Those that are unlocked and rooted a little research the latest Magisk Canary(18.2) fixes Google Pay not working.
acuma14 said:
I tried to edit libnfc-nxp.conf in /system/vendor/etc, but it resset to default after phone reboot.
Also, i can's repair my gpay with free bootloader and magisk intalled. So i deside to return device to closed one.
Click to expand...
Click to collapse
You will need to mount "/" as read-write, in a terminal emulator (or adb shell):
Code:
$ su
# mount -o rw,remount /system
**NOTE: The above syntax might be different depending on ROM is use. Please use at your own risk.
sandix said:
You will need to mount "/" as read-write, in a terminal emulator (or adb shell):
Code:
$ su
# mount -o rw,remount /system
**NOTE: The above syntax might be different depending on ROM is use. Please use at your own risk.
Click to expand...
Click to collapse
Root explorer offer me to mount directory aftomatically, and successfully save my config, but after reboot it returns to default values. I found information about to create a magisk patch for usefully edit config at all, but not sure it's the simpliest solution for me, and i can find step-by-step instruction...
I need this to use my nfc-transport sim card, here's the discussion https://forum.xda-developers.com/oneplus-5/themes/mod-nfc-swp-sim-enabler-oneplus-3-3t-t3650482
Do i need to set NXP_DEFAULT_SE as 0x02 instead 0x07 (should 07 implement UICC correctly)?
Idk how, but after reinstall magisk gpay starts working fine