Hi,
I have a case with "wireless_tether_2_0_7_for_X8_X10mini.apk". I install iptables/netfilter succesfully and "DroidWall" is working perfect, but when I try to start WiFi Tethering in the log file appear these errors: (see attached pics). When I reboot the phone all modules are loaded, but tether wifi is still unavailable. I have stock rooted E15i 2.1.1.C.0.0. Can you help me with some advice?
Thanks in advance
Phone after the OTA update has a tendendancy to default CDMA carrier there are different methods of getting the phone to activate an aftermarket APN by rooting sucessfully and editing the buildprop on the phone
you need a fresh install and to make sure your external sd is formatted properly and clean so back up you files onto a pc and format the ext fresh
cdma_targa_9.8.2O-72_VZW-22_cfcfbmode.zip
If you dont know how to edit the radio using the established method and tools read a tutorial on it
Secondly successfully root the phone i used the Samba method on 4.1.2 OTA
then edited the build prop with now rooted phone supersuser is hidden but it will pop up on access
im using buildprop editor
1. Change both appearances of the value:
Code:
ro.telephony.default_network=0
To:
Code:
ro.telephony.default_network=10
change telephony.lteOnCdmaDevice=1
to
telephony.lteOnCdmaDevice=0
bingo! add your APN info should be good to go
4.2.2
things are slightly different on 4.2.2 you should automatically have a rooted phone from the stock rooting the OTA 4.1.2
basic GSM should be active ( ro.telephony.default_network=10 is already edited as well as ro.mot.phonemode.vzwglobalphone=0)
experimenting with strings (ro.mot.lte_cdma = 0 and telephony.lteoncdmadevice=0) produces effects on phone as to activate APN (access points in mobile networks) you can now enter your carrier data try editing one at a time as not to hang or cause a sys load error follow the process and reboot preventing a boot loop
matts stock rooted xt875 on OTA 4.1.2 jelly and 4.2.2 eclipse 5.0 with data ! on ATT little brother
Hi, so i have the XT1064, i rooted it with all the tools(?) [flashable .zip for SuperSU and .img for TWRP] from the Root Guide and root seems to be working fine with all apps requiring it but DroidWall; if i select just some apps to allow data/Wi-Fi consumption it just disconnects all apps, even the ones i select, it only allows connection if i mark the "(Any application) - Same as selecting all applications" box, both in 3G and Wi-Fi
Anyone else having this problem? Any suggestion?
Try another firewell which is based on droidwell.droidwell is discontinue.
Hello,
I've a slew of issues I'm trying to find solutions to I've searched but have been unable to find a solution.
I'm on MEC23G official firmware with developer options enabled and root.
1) I'm unable to get TWRP to stick permanently - I've tried Official 3.0.2.0 and an unofficial build with squashFS (the latter allowed me to flash SU with Busybox).
2) I'm unable to mount /system as RW either via adb or within TWRP which I was able to do pre Marshmallow (I want to update /system/usr/idc/synaptics_rmi4_i2c.idc with touch to wake disabled).
3) The watch often fails to update with the phone battery level, is there a way to fix this (I've set it to keep connected in Android Wear and to show all notifications etc.
4) I've installed Advanced Settings for Wear which claims to be able to make the change I want to in (2) but after it restarts the watch the setting is still the same.
Any help would be greatly appreciated.
3) Would appear to have been down to the watch face (in case anyone else finds this).
volte is not working in any custom rom in my oneplus 3t , i have tried all the solutions . but volte not worked ,,,,,,, but in the oxygen os the volte is working fine , the problem is only with the custom roms , i have tried evolution , havoc , pixel , crdroid , bliss rom , but same issue ,,,,, please help
[email protected] said:
volte is not working in any custom rom in my oneplus 3t , i have tried all the solutions . but volte not worked ,,,,,,, but in the oxygen os the volte is working fine , the problem is only with the custom roms , i have tried evolution , havoc , pixel , crdroid , bliss rom , but same issue ,,,,, please help
Click to expand...
Click to collapse
Start with comparing apns-conf.xml from oos to your prefered custom rom for your carriers mcc/mnc. (Ignore the line breaks in the oos version, just compare the variables/values.)
volte
nvertigo67 said:
Start with comparing apns-conf.xml from oos to your prefered custom rom for your carriers mcc/mnc. (Ignore the line breaks in the oos version, just compare the variables/values.)
Click to expand...
Click to collapse
can u please explain step by step ? so that i can do it easily
[email protected] said:
can u please explain step by step ? so that i can do it easily
Click to expand...
Click to collapse
Get apns-conf.xml from the OOS version volte has proofed to work for you. It's in /system/etc/apns-conf.xml.
Get apns-conf.xml from the custom rom you'd like to use. It's in /system/etc/apns-conf.xml for android 9 roms; $sys_root/system/[vendor|product]/etc/apns-conf.xml for android 10 roms. In doubt boot to twrp mount system and run
Code:
find / -name apns-conf.xml 2>/dev/null
in the twrp terminal.
Get the mcc (mobile country code) and mnc (mobile network code) of your sim (you can find the mcc/mmc e.g. in the settings of your active apn.
Find all entries in the OOS' apns-conf.xml (blocks beginning with "<apn carrier=" and ending on "/>"), which contain your sim's mcc/mnc.
Find all lines in the custom rom's apns-comf.xml containing your sim's mcc/mnc.
Compare all apn comfigs you've found. Consider all line breaks in the OOS apn blocks as white space.
Make the lines in tne custom rom's apns-conf.xml to have the same config (as one line) as in OOS' apns-conf.xml.
Replace the apns-conf.xml you've just created in the installed custom rom (check and restore - if necessary - permissions and selinux contexts before and after replacing; e.g. in the twrp terminal after mounting system
Code:
ls -lZ $(find / -name apns-conf.xml 2>/dev/null)
cp /sdcard/Dpwnload/apns-conf.xml.new $(find / -name apns-conf.xml 2>/dev/null)
ls -lZ $(find / -name apns-conf.xml 2>/dev/null)
;to restore original permission use chmod; to restore original selinux contexts use restorecon; both commands support "-?" for syntax).
After booting the custom rom reset network settings and reboot. Go to the apn settings and check if your changes are cortectly shown. Only if the changes are shown, test volte.
If that fails you need to compare the carrier settings for your sim's mcc/mnc. Get CarrierConfig.apk and Phone.apk from the custom rom and from OOS. Decompile all 4 apks with baksmali and compare all resources containing your sim's mcc/mnc. Documentation on smali/baksmali is found here: https://github.com/JesusFreke/smali/wiki and https://forum.xda-developers.com/showthread.php?t=2193735 (just starting points, there are many guides around).
volte
nvertigo67 said:
Get apns-conf.xml from the OOS version volte has proofed to work for you. It's in /system/etc/apns-conf.xml.
Get apns-conf.xml from the custom rom you'd like to use. It's in /system/etc/apns-conf.xml for android 9 roms; $sys_root/system/[vendor|product]/etc/apns-conf.xml for android 10 roms. In doubt boot to twrp mount system and run
Code:
find / -name apns-conf.xml 2>/dev/null
in the twrp terminal.
Get the mcc (mobile country code) and mnc (mobile network code) of your sim (you can find the mcc/mmc e.g. in the settings of your active apn.
Find all entries in the OOS' apns-conf.xml (blocks beginning with "<apn carrier=" and ending on "/>"), which contain your sim's mcc/mnc.
Find all lines in the custom rom's apns-comf.xml containing your sim's mcc/mnc.
Compare all apn comfigs you've found. Consider all line breaks in the OOS apn blocks as white space.
Make the lines in tne custom rom's apns-conf.xml to have the same config (as one line) as in OOS' apns-conf.xml.
Replace the apns-conf.xml you've just created in the installed custom rom (check and restore - if necessary - permissions and selinux contexts before and after replacing; e.g. in the twrp terminal after mounting system
Code:
ls -lZ $(find / -name apns-conf.xml 2>/dev/null)
cp /sdcard/Dpwnload/apns-conf.xml.new $(find / -name apns-conf.xml 2>/dev/null)
ls -lZ $(find / -name apns-conf.xml 2>/dev/null)
;to restore original permission use chmod; to restore original selinux contexts use restorecon; both commands support "-?" for syntax).
After booting the custom rom reset network settings and reboot. Go to the apn settings and check if your changes are cortectly shown. Only if the changes are shown, test volte.
If that fails you need to compare the carrier settings for your sim's mcc/mnc. Get CarrierConfig.apk and Phone.apk from the custom rom and from OOS. Decompile all 4 apks with baksmali and compare all resources containing your sim's mcc/mnc. Documentation on smali/baksmali is found here: https://github.com/JesusFreke/smali/wiki and https://forum.xda-developers.com/showthread.php?t=2193735 (just starting points, there are many guides around).
Click to expand...
Click to collapse
Thanks for the help . But is there any simple way to do it because i am just a beginner so it is very difficult for me to do this process
[email protected] said:
Thanks for the help . But is there any simple way to do it because i am just a beginner so it is very difficult for me to do this process
Click to expand...
Click to collapse
If you are a customer and not willing to learn to become a user, dubugging is beyond our scope. Try finding somebody doing it for you.
Good luck!
nvertigo67 said:
If you are a customer and not willing to learn to become a user, dubugging is beyond our scope. Try finding somebody doing it for you.
Good luck!
Click to expand...
Click to collapse
ok thank you