Develop Bugs

LG G4 WiFi Fix - Always all channels on 2.4 GHz

WiFi Fix - always all channels on 2.4 GHz
IMPORTANT:
Only for advanced users!
You are an advanced user if you know exactly what you are doing.
You are an advanced user if you know what to do if something went wrong.
You are NOT an advanced user if you know how to do copy+paste.
You can bring your smartphone into a state, so it no longer works.
I am not responsible for anything. The following instructions are only suggestions.
Hello,
I want to show you a way how you prevent your LG G4 to limit wireless channels to 1-11.
This happens when no SIM card is inserted or if the airplane mode is activated.
You get messages like:
"Some Wi-Fi networks unavailable due to unknown location" (English)
"Einige Wi-Fi-Netzwerke sind wegen des unbekannten Standorts nicht verfügbar" (German)
"Algunas redes Wi-Fi no están disponibles debido a una ubicación desconocida" (Spanish)
I studied the log entries and found a line that said "[LGE_PATCH] For Country code DC. ....".
After a long search in the code I have discovered the place that is responsible for the limitation.
It is located in the wifi-service and it sets the WifiCountryCode to "DC" if your location could not be obtained.
For me living in Germany it should be "DE".
The WifiCountryCode named "wifi_country_code" is stored in the "global" table of "/data/data/com.android.providers.settings/databases/settings.db".
Changing it has no effect as it is overwritten instantly.
So we need to modify the program code of "wifi-service".
According to this post: http://forum.xda-developers.com/showpost.php?p=64636618&postcount=8
this guide seems to work on other models from LG and newer Android versions too.
You have to search for the wifi-service.odex file and replace "DC" with your two-letter country code.
Alter the paths of the instructions if you use another phone than LG G4 with Android 5.1 Lollipop!
The following instructions show how to do it on the LG G4 with Android (5.1) Lollipop.
Prerequisites:
ROOT
USB debugging enabled
Procedere:
Connect your G4 to your computer.
Open the command promt and enter the following lines:
Code:
adb shell
mkdir /sdcard/wifi-service
cp /system/framework/arm64/wifi-service.odex /sdcard/wifi-service/64wifi-service.odex
Now a file named "64wifi-service.odex" is on your internal memory located in the folder "wifi-service".
Copy the file to your computer.
Now you have to edit the file.
Don't use the "editor" on windows, use Notepad++
With Strg+F search for "DDD".
You will find exactly one line that contains this::
"DATE_TIME DBG DC DCM DDD DDFName"
Change the value "DC" to "DE" for example (search the internet for the two-letter country code of your country (ISO 3166-1 alpha-2))
"DATE_TIME DBG DE DCM DDD DDFName"
Save the file.
Delete the file "64wifi-service.odex" on your smartphone.
Copy the edited file from your computer to the folder "wifi-service" on your smartphone.
Go back to the command prompt and type this:
Code:
su
You should see an confirmation promt on your smartphone that asks to grant root rights.
Confirm the message.
The command promt should change from $ to # now.
To verify your rights type this:
Code:
id
You should see "uid=0" etc.
Now type in the following lines (I recommend to execute each row seperately):
Code:
mount -o remount,rw /system
cd /system/framework/arm64
cp wifi-service.odex /sdcard/wifi-service/64wifi-service.odex.bak
rm wifi-service.odex
cd /sdcard/wifi-service
cp 64wifi-service.odex /system/framework/arm64/wifi-service.odex
cd /system/framework/arm64
chown 0:0 wifi-service.odex
chmod 0644 wifi-service.odex
echo "restart device"
Check the outputs. There must be no errors!
After hitting the Enter button the last line should output "restart device".
In the folder "wifi-service" on your internal storage you find the original "wifi-service.odex".
It is named "64wifi-service.odex.bak".
Restart your smartphone now.
As from now it does not matter whether a SIM card is inserted or if the airplane mode is activated.
The WiFi channels are no longer limited to 1-11. You can now always use 12 and 13.
Did the instructions help you?
Please give a "Thanks!"
Thank you
For users who speak German:
I wrote this guide in German at first. You can find it on android-hilfe.de
Title: "LG G4 WLAN Fix - immer alle Kanäle"
http://www.android-hilfe.de/thema/lg-g4-wlan-fix-immer-alle-kanaele.710265/

I am using Ultraedit. Nevertheless I only see a hex file and I can not locate a string: "DCM DDD DDFName" Any suggestions?

It is also passible with your editor.
There are two ways:
1. In HEX mode (default mode)
After hit "Strg + F" enter the string "DDD"
Activate the checkboxes "ASCII suchen" and "Groß-/Kleinschreibung beachten".
You will find excatly one result. (DC is in line 00c6e40h)
2. Deactivate HEX mode (Strg + H)
After hit "Strg + F" enter the string "DDD"
The first result is what you need. (line 10528)
Change "DC" to "DE". Don't change anything else!
Hope I could help.
You are also on V10c? Otherwise line numbers will differ.
Tip:
Make a system.img with "dd" of your current system partition.
If it don't work or you did something wrong you can simply copy it back with "dd".

dominik-p said:
It is also passible with your editor.
There are two ways:
1. In HEX mode (default mode)
After hit "Strg + F" enter the string "DDD"
Activate the checkboxes "ASCII suchen" and "Groß-/Kleinschreibung beachten".
You will find excatly one result. (DC is in line 00c6e40h)
2. Deactivate HEX mode (Strg + H)
After hit "Strg + F" enter the string "DDD"
The first result is what you need. (line 10528)
Change "DC" to "DE". Don't change anything else!
Hope I could help.
You are also on V10c? Otherwise line numbers will differ.
Tip:
Make a system.img with "dd" of your current system partition.
If it don't work or you did something wrong you can simply copy it back with "dd".
Click to expand...
Click to collapse
Thanks for all the help! I switched to notepad ++. Found the entry
Code:
DATE_CLASS DATE_KEY DATE_TIME DBG DE DCM DDD DDFName DEBUG
in line 17126 though. Changed it successfully! Copied successfully to my phone! No effect! Still no channel 13 without sim. Double checked (copy wifi-service.odex to pc) and look for
Code:
DATE_TIME DBG DE DCM
.
It IS in there. Somehow not taking effect? I had problems when doing "chown 0:0 wifi-service.odex" It tells me "read only file system". I did set the owner and permissions with ES File Explorer. TO: root, root and Read, write; read; read.

OK I think you are an advanced user. (aren't you?)
You did it right with your app, but it should be possible with the shell too.
Readonly means you are not "su" in shell or/and did not "mount -o remount,rw /system".
Check su with "id" (uid=0) and mount should output something like this:
Code:
/dev/block/bootdevice/by-name/system /system ext4 [B]rw[/B],seclabel,relatime,data=ordered 0 0
Please check that /system/framework/arm64 has only one file named wifi-service.odex in it.
While testing I got to a point where I had two "wifi-service.odex" files with different file permissions in it.
Post an "ls -l" of the folder please.
After removing the SIM card and rebooting your phone look in the "global" table of settings.db and check that "wifi_country_code" is set to "DE".
Please also use catlog to check if wpa_supplicant sets the CountryCode to DE.
PS: for me it's line 17073 in notepad++ Don't know why lines differ.
Filesize of wifi-service.odex is 3903976 bytes for me. You are also on V10c?

Thanks for this! just fixed my G3 Marshmallow,
I'm using another region rom, and i think sim country is not properly detected.

Thanks for reply.
Didn't know that the G3 has this "problem" too and that my solution works on Android M.
I guess it's not the same line "DATE_TIME DBG DC DCM DDD DDFName"
but also a line with the value "DC"?

dominik-p said:
Thanks for reply.
Didn't know that the G3 has this "problem" too and that my solution works on Android M.
I guess it's not the same line "DATE_TIME DBG DC DCM DDD DDFName"
but also a line with the value "DC"?
Click to expand...
Click to collapse
I just noticed the problem when updating to 6, its another line but very similar:
the full path for the file is /system/framework/oat/arm/wifi-service.odex
Line is 24139
values for the line are "DATE_CLASS DATE_KEY DATE_TIME DATUM_WIDTH DBG DC DCM DD DDD DDFName "
Just changed DC to BR.

Perfect.
Thank you.

dominik-p said:
Perfect.
Thank you.
Click to expand...
Click to collapse
Hello, I know that the thread is quite old, but I have a small problem with the wifi-service.odex file on my phone. Looks scrambled in n++. Is there any setting for n++ that I should use?
My phone is a Le Max2 and I don't have GSM signal at my workplace. The routers are set to automatic and they also use channels 12 and 13.
From what I understand by the commands, you are just pulling the file from system to internal storage, and copying it to the computer, changing it with n++ and copying it back to system. There is no transformation to .jar as I can see...
The file is about 4mb.
Can you provide any help please?

valy_cta said:
Hello, I know that the thread is quite old, but I have a small problem with the wifi-service.odex file on my phone. Looks scrambled in n++. Is there any setting for n++ that I should use?
My phone is a Le Max2 and I don't have GSM signal at my workplace. The routers are set to automatic and they also use channels 12 and 13.
From what I understand by the commands, you are just pulling the file from system to internal storage, and copying it to the computer, changing it with n++ and copying it back to system. There is no transformation to .jar as I can see...
The file is about 4mb.
Can you provide any help please?
Click to expand...
Click to collapse
Hi,
you already created a thread here: https://forum.xda-developers.com/le-max-2/help/wifi-channels-12-13-unable-to-t3773144
Please stay at your own thread for further discussion. This thread here is only for LG devices and the provided fix is only working on some LG devices.
You're right, the odex file looks "scrambled" in Notepad++, but that's no problem. We only had to change one or two letters.
I will answer at your thread "WiFi channels 12 and 13 - unable to see them". (https://forum.xda-developers.com/showthread.php?t=3773144)
For all other users, please read these threads to understand the problem:
WiFi regional problem on Android https://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android
[GUIDE] WiFi Country Problem Solving for AOSP, MIUI & others https://forum.xda-developers.com/showthread.php?t=2368501

Double post by mistake - slow internet connection

Worked cool on LG G4 Stylus
Just a few "logistics" to comment:
-on some devices/models seems to be that /sdcard is no possible to access. Instead, /storage/emulated/0/ or the real path /data/media/0
-when copying the modified wifi-service file to /system/... folder, step on with a "Permission Denied" message. I was Root and /system was mounted as wr. Finally continued by copying using a root explorer and then continuing in the shell.
-after i rebooted, tried to connect on a channel 13 without sucess. I had plain mode. I put off plain mode, changed the country in wpa_supplicant.conf file and rebooted again. After that, all went good

DarkBader said:
Just a few "logistics" to comment:
-on some devices/models seems to be that /sdcard is no possible to access. Instead, /storage/emulated/0/ or the real path /data/media/0
-when copying the modified wifi-service file to /system/... folder, step on with a "Permission Denied" message. I was Root and /system was mounted as wr. Finally continued by copying using a root explorer and then continuing in the shell.
-after i rebooted, tried to connect on a channel 13 without sucess. I had plain mode. I put off plain mode, changed the country in wpa_supplicant.conf file and rebooted again. After that, all went good
Click to expand...
Click to collapse
Thanks for your feedback!
Would you please share your model number and Android version of your "LG G4 Stylus"?

dominik-p said:
Thanks for your feedback!
Would you please share your model number and Android version of your "LG G4 Stylus"?
Click to expand...
Click to collapse
LG G4 Stylus H635 LL 5.0.2
Thank to you for the good work

Question!
dominik-p said:
Thanks for your feedback!
Would you please share your model number and Android version of your "LG G4 Stylus"?
Click to expand...
Click to collapse
I had a situation i yet did not solve.
Yesterday i went to some friend's house, where before i could not see their wifi network. And i still can not see it ! :0 :0
I know this method worked, because changed the channel on my router to 12 or 13 and i can see them and connect. Also country code show as i changed it in Wpa_Supplicant and in CountryCode in Android.Providers. I also know is not a hidden network, as my friends can see it and connect normally without problem. Also tried with WPS button, and nothing.
.
-As the "problematic" network is a 5G, maybe is something related with this? lack of technology as my phone model is a bit old nowadays?
But what i understood about 5 G, is that they assure backwards compability :/
.
Maybe u see something i am missing?

Enable Multiuser

Hey,
i just got a new tablet for me and my wife and was shocked, that the android multiuser feature is disabled in EMUI 4 (MM).
So, since i've a rooted device, i just tried something working on other devices:
1. Get rooted - no way around i think (probably adb...?)
2. Get a root file manager with notepad (e.g. ES Explorer)
3. Navigate to /system/build.prop and open it with editor
4. Add the following 2 lines at the end:
Code:
fw.max_users=3
fw.show_multiuserui=1
5. Exit and save, reboot.
6. Check Settings -> User
7. Be Happy.
Hope this helps someone!
Greetings, Chris

.sirhc said:
Hey,
i just got a new tablet for me and my wife and was shocked, that the android multiuser feature is disabled in EMUI 4 (MM).
So, since i've a rooted device, i just tried something working on other devices:
1. Get rooted - no way around i think (probably adb...?)
2. Get a root file manager with notepad (e.g. ES Explorer)
3. Navigate to /system/build.prop and open it with editor
4. Add the following 2 lines at the end:
Code:
fw.max_users=3
fw.show_multiuserui=1
5. Exit and save, reboot.
6. Check Settings -> User
7. Be Happy.
Hope this helps someone!
Greetings, Chris
Click to expand...
Click to collapse
Thanks for this. You should probably move this post to the "Guides" subforum if you can (mods, please help)

[SCRIPT][17.04.22][v1.2.0] MIUI Power Menu Patcher - add recovery & fastboot reboot

[SCRIPT][17.04.22][v1.2.0] MIUI Power Menu Patcher - add recovery & fastboot reboot
This patch your system to have got recovery & fastboot reboot from power menu.
Download latest release
Changelog
-Added visual menu
-Added function to restore backups
-Added ability to supply environment directory as argument with `-d <dir>`
-Added a lot of code improvements
-Fixed correct build number in backup folder
-Fixed some Busybox issues
Thanks to @DarthJabba9 for all the work of this update.
All releases and changelogs
Source code on Github
How-To
This script is to use from Android, need a terminal app as Terminal Emulator for example and a rooted device. Tested in Redmi Note 2 with Xiaomi EU & MultiROM
Run from terminal this
Code:
su
sh DIR/miui-powermenu-patcher.sh
Change "DIR" to the location where is the script.
Pro tip: move the script to /data and rename to mpp for example to have easy access from terminal.
Example (click image)

Patch sh no such, following dir change it, any solution?
Sent from my Redmi Note 2 using Tapatalk

if i move file to /data so what command..still DIR?

rockadz9 said:
View attachment 4095317
Patch sh no such, following dir change it, any solution?
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
The problem is that tail search for $0 variable and in your case is miuipm.sh, so as in the script the current directory is changed and the script isn't in it, occurs that.
Thanks for report it, I will fix it. ATM run as: sh $(pwd)/miuipm.sh
harizamzi said:
if i move file to /data so what command..still DIR?
Click to expand...
Click to collapse
Run from terminal this
Code:
su
sh DIR/miui-powermenu-patcher.sh
Change "DIR" to the location where is the script.
Click to expand...
Click to collapse
Please read...

Updated to v1.1.1

Deic said:
The problem is that tail search for $0 variable and in your case is miuipm.sh, so as in the script the current directory is changed and the script isn't in it, occurs that.
Thanks for report it, I will fix it. ATM run as: sh $(pwd)/miuipm.sh
Please read...
Click to expand...
Click to collapse
Yes mate my ROM 7.3.23 xiaomi.eu, this file change name & directory same problem. (Miui-powermenu-patcher.sh =old version / mpp.sh =new version)
Any solution?
Sent from my Redmi Note 2 using Tapatalk

rockadz9 said:
Yes mate my ROM 7.3.23 xiaomi.eu, this file change name & directory same problem. (Miui-powermenu-patcher.sh =old version / mpp.sh =new version)View attachment 4096809
Any solution?
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
Did you try run as "sh /data/mpp.sh" (add "/" before "data") or "cd /data" and after "sh mmp.sh"?

Deic said:
Did you try run as "sh /data/mpp.sh" (add "/" before "data") or "cd /data" and after "sh mmp.sh"?
Click to expand...
Click to collapse
I try run as "sh data/mpp.sh" and run as "sh /data/mpp.sh"
Sent from my Redmi Note 2 using Tapatalk

rockadz9 said:
I try run as "sh data/mpp.sh" and run as "sh /data/mpp.sh"
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
and the result is the same? that is strange... what is your busybox version? and you can provide miui-powermenu-patcher.log under /data/miui-powermenu-patcher folder? looks like you have not got proper unzip busybox built-in command...

@Deic There seem to be 2 problems:
1. wget.zip - it seems that it does not get decoded properly with base64; in any case, the error log shows that it cannot be unzipped
2. The call to patch.sh - you might want to provide the full pathname
Edit: I think the wget problem is that the zip file is corrupt - probably a result of a wrong START_LINE

DarthJabba9 said:
@Deic There seem to be 2 problems:
1. wget.zip - it seems that it does not get decoded properly with base64; in any case, the error log shows that it cannot be unzipped
2. The call to patch.sh - you might want to provide the full pathname
Edit: I think the wget problem is that the zip file is corrupt - probably a result of a wrong START_LINE
Click to expand...
Click to collapse
The START_LINE is good in all versions released, I tested before of release them and all is fine... And the output of no patch.sh is because, no wget = no patch.sh. I will wait to @rockadz9 to see what is the issue, I maybe due to bad unzip or that seems.

Deic said:
and the result is the same? that is strange... what is your busybox version? and you can provide miui-powermenu-patcher.log under /data/miui-powermenu-patcher folder? looks like you have not got proper unzip busybox built-in command...
Click to expand...
Click to collapse
Yes results is the same, version Busybox1.26-2_arm64. and patch log attch
Sent from my Redmi Note 2 using Tapatalk

@rockadz9 Open the script file with a text editor, and add these lines near the top of the file
Code:
alias basename="busybox basename"
alias dirname="busybox dirname"
alias tail="busybox tail"
alias base64="busybox base64"
alias unzip="busybox unzip"
alias sed="busybox sed"
alias awk="busybox awk"
Then add 7 to the value of START_LINE, save the file, and run the script again.

1.2.0 released!
All the nice stuff of this update is thanks to @DarthJabba9, I did almost nothing.
Go to OP to download!

It's work for me, first one i run as 'sh data/mpp.sh and i got message no such....
and second time i run as 'sh /data/mpp.sh its work fine. thx bro

I'm trying to get this to work on stable EU version 7.0.6. After running the script the menu can be displayed but only the reboot option works. Both the fastboot and recovery cause the screen to become blurred and nothing happens. Pressing the back button clears the screen and I'm back at the point prior to pressing the power button. I've attached the script log. Can anyone tell me what's wrong ?

Cannot show text bellow addition icon
MIUI 9 7.9.7 global dev

worked great
thanks a lot

How to enable Camera2API on Redmi Note 5 AI without root for Google Camera?

Hi
I know there may have been numerous threads on here and various websites setting out how to enable camera2API without root on Redmi Note 5 AI, however, I am struggling to get this installed to enable me to ultimately get the Google Camera app.
I have followed through the steps on this particular website (https://www.technobuzz.net/google-camera-redmi-note-5-pro/) to enable the camera2api and all seems to go well until I get to the step before 'adb shell' where nothing really happens. I have tried so many times and each time the result is the same. I am not sure where I have gone wrong. I have already had the phone unlocked from Xiaomi. I hope someone on here would be able to help me out on this.

Any help would be greatly appreciated.

Unlock bootloader
Install twrp
From twrp mount system partition
Disable system partition read only option
Copy build.prop file from /system/ and add these lines to build.prop file
persist.camera.HAL3.enabled=1
persist.camera.eis.enabled=1
Save build.prop file and copy updated buildprop file to /system/ file

SunilSuni said:
Unlock bootloader
Install twrp
From twrp mount system partition
Disable system partition read only option
Copy build.prop file from /system/ and add these lines to build.prop file
persist.camera.HAL3.enabled=1
persist.camera.eis.enabled=1
Save build.prop file and copy updated buildprop file to /system/ file
Click to expand...
Click to collapse
Hi, thanks for the reply.
Is there a detailed step by step guide to follow and links to download the relevant files ? Sorry, I'm not too savvy on technology.

Android 10 Rooted Can't Edit build.prop

So, grabbed the latest OTA, and went through the usual re-root cycle, but was unable to edit the build.prop. While /root is mountable, /root/system is not, which means no tethering for me.
Anyone else running into the same issue?

I have the same issue, I've been fighting with it all day.
I patched the boot.img with Magisk Manager and flashed it, Magisk Manager show's I'm installed and Root Checker says I'm rooted, I was even able to install Adaway. But i cannot use any root app that needs to mount /System
I tried using Root Uninstaller and it says it has root access but cannot mount /system as R/W
It seems Magisk is only able to partially root on Android 10
I tried this with the Canary version and the standard version of Magisk and the same issue both times

Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame

bbarnes1 said:
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
Click to expand...
Click to collapse
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228

This has been a problem since the Q beta came out, with each update I tried to figure something out. With no luck! I tried the Magisk Mod but it didn't seem to work.
suggestions would be most appreciated!!
Thinkin about a clean install....maybe.....
Edit: It was also a problem with the P beta until it was out of beta (That was my hope for this)

sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....
Click to expand...
Click to collapse
I'm trying to add a prop, which seems like a different need, but will look into it.
tufyuma said:
Thinkin about a clean install....maybe.....
Click to expand...
Click to collapse
Was thinking about this, but realized a clean install for every update isn't worth a hotspot to me.

sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
I gave this a whirl, its doesn't appear to actually be change build.prop

bbarnes1 said:
I gave this a whirl, its doesn't appear to actually be change build.prop
Click to expand...
Click to collapse
It doesn't physically change anything in system. The intent is to offer the same functionality as physically editing the build.prop without modifying that file. It creates the prop and value setting and loads into into memory at boot time.....(similar to the way the build.prop file is read at boot time for those settings.) At least that is my understanding. It works for me on Android 9 for setting the prop for tethering...for example. You can confirm it works by using the getprop command to verify the prop you set is set as you intended.

Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.

somethingsomethingroot said:
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
Click to expand...
Click to collapse
Can you tell me what the process is that got you tethering capability?

Having the same issue on my P2XL which was upgraded via flash of full image minus -w. Using latest canary build of Magisk. I couldn't mount system or anything under it.
I then downgraded Magisk to v19.3 and had no issues mounting system using FX File Explorer, etc. and still had root. But I couldn't mount anything under system so I still can't edit build.prop.

For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59

IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
Thanks for posting this, it worked great on my Pixel XL on Sprint. I had about given up on being able to edit the build.prop.

You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:

Your prop
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Are you sure that your screenshot of the props output is correct? Because it looks like you have the value set to "net.tethering.noprovisioning" and the prop name has =true in it. I'm just trying to figure this out because I've tried this and everything else trying to get my hotspot to work. My hotspot will turn on and devices can connect to it, but they don't have internet access. Any ideas at all?
Edit: Nevermind, I had the custom prop set to post fs data when it was supposed to be set at boot stage (default). My hotspot is working now. Thank you all.

DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Confirming that this works on rooted pixel 4. Thank you for this btw

IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
This seems to have worked for me, though I don't really understand why or what did it.

For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!

wolvmarine said:
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
Click to expand...
Click to collapse
Why need to turn on Hotspot for build.Prop editing? What's wamo?

truelies1 said:
Why need to turn on Hotspot for build.Prop editing? What's wamo?
Click to expand...
Click to collapse
Does anyone know a way to enable gestures on 3rd party launchers on stock rom