settings put global tether_dun_required 0 NOT WORKING - OnePlus 7 Pro Questions & Answers

So I recently did a format a few weeks ago. Before that I was using the build.prop hack to enable hotspot on cricket wireless for years. I swear I've been able to turn on the hotspot since the format, but now all of a sudden it's not working. When I go to turn hotspot on it immediately turns itself back off.
I looked in build.prop editor and the net.tethering line was not in there. So I added that. Then I went into terminal to add settings put global tether_dun_required 0. I rebooted and it's still not working. "Dun" is not in my apn settings and the hotspot is doing the same thing.
Is this a recent change with cricket wireless? Am I just doing the hack wrong? Any help would be appreciated.
OnePlus 7 pro, OOS 10.1, xxx NoLimits 9.2, and smurfkernel

Bump. did oos10 break this method?

Update: it works on old Moto G5 Plus running Pie. So it's not the carrier blocking it.

that waa taken by carrier long ago its in the framework if rooted i have thread and pdanet+ works

that was stopped by carrier log ago if rooted try these or with your carrier like att do you have tether provision apk thats easy to fix i told you id try to help tell me os and mmc mnc tether_offload helps also try those 2 ill help others probably will

gravity box beta 5 will edit framework safely

Have you tried this (this is for usb tethering):
adb shell su -c service call connectivity 33 i32 1 s16 text

You have to put ",dun" in your APN type setting.

OR FROM TERMINAL
su
settings put global tether_dun_required

Does it work on TMobile?

pdaddy said:
OR FROM TERMINAL
su
settings put global tether_dun_required
Click to expand...
Click to collapse
I terminal I god bad arguments error

netgar said:
I terminal I god bad arguments error
Click to expand...
Click to collapse
Try
su
Press Enter
settings put global tether_dun_required 0
Press Enter
Should work

pdaddy said:
Try
su
Press Enter
settings put global tether_dun_required 0
Press Enter
Should work
Click to expand...
Click to collapse
Ok my friend. That one didn't give me an errors.
What actually that command give it to me?
Thank you for your help

Adding the dun
stooth said:
You have to put ",dun" in your APN type setting.
Click to expand...
Click to collapse
this worked for me on my e5 plus after many attempts to get tether to work without throttling. So it's adb shell command execute then going into my apn settings and adjusting apn type to include dun.

alonsovr4 said:
Adding the dun
this worked for me on my e5 plus after many attempts to get tether to work without throttling. So it's adb shell command execute then going into my apn settings and adjusting apn type to include dun.
Click to expand...
Click to collapse
thanks hopefully it work ive miss those APN settings, i did do boodt adb shell tether_dun_required 0 but still detected data while im using usb tethering, pdanet now ask for pay i try this old method

BiscuitsChips said:
thanks hopefully it work ive miss those APN settings, i did do boodt adb shell tether_dun_required 0 but still detected data while im using usb tethering, pdanet now ask for pay i try this old method
Click to expand...
Click to collapse
Thanks so much it worked on my moto g stylus 5G (2022) from Metro

Related

Rooted AT&T 3.18 JB Stock Wifi+USB Tethering/Hotspot

I made a thread for Rooted AT&T 2.20 about enabling factory tethering. I found out that using this same .db file on 3.18 was not working for me. So I went back and re-edited the telephony.db that came with 3.18 and it seems to work again. I have uploaded the 3.18 version of telephony.db to enable factory hotspot sharing again. I have CleanROM 6 R2 installed and this seems to work well on it. Should work on stock rooted phones as well.
To Install
1. Extract telephony.db into the same folder as your adb.exe
2. Run these commands (they create a backup as well as push the edited database):
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/data/data/com.android.providers.telephony/databases/telephony.db of=/sdcard/telephony.db.bak
>adb push telephony.db /sdcard/telephony.db
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/telephony.db of=/data/data/com.android.providers.telephony/databases/telephony.db
[email protected]:/ # reboot
After reboot everything should work fine.
this is awesome, but you got my hopes up with the "rooted 3.18" title. you may want to move that bit to the end of the title. will definitely use this if my phone is ever unlocked again :\
Ha I got all excited too. And I may be wrong, but shouldn't this be in the development section?
lightpost712 said:
I made a thread for Rooted AT&T 2.20 about enabling factory tethering. I found out that using this same .db file on 3.18 was not working for me. So I went back and re-edited the telephony.db that came with 3.18 and it seems to work again. I have uploaded the 3.18 version of telephony.db to enable factory hotspot sharing again. I have CleanROM 6 R2 installed and this seems to work well on it. Should work on stock rooted phones as well.
To Install
1. Extract telephony.db into the same folder as your adb.exe
2. Run these commands (they create a backup as well as push the edited database):
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/data/data/com.android.providers.telephony/databases/telephony.db of=/sdcard/telephony.db.bak
>adb push telephony.db /sdcard/telephony.db
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/telephony.db of=/data/data/com.android.providers.telephony/databases/telephony.db
[email protected]:/ # reboot
After reboot everything should work fine.
Click to expand...
Click to collapse
I downloaded file, but seems zip file is empty... I am using Peazip
diekastro said:
I downloaded file, but seems zip file is empty... I am using Peazip
Click to expand...
Click to collapse
I just re-downloaded it and the file is there. Try using a different unzipping program.
lightpost712 said:
I just re-downloaded it and the file is there. Try using a different unzipping program.
Click to expand...
Click to collapse
I tried again with windows pack and winzip... Both shows empty file.
I disabled Eset Enpoint, and I downloaded it 3 times.
However, I am using stock rom and I have the SQLite Editor. What changes did you do? Do you just have to change file 12 'broadband' to 'pta'?
Thanks
diekastro said:
I tried again with windows pack and winzip... Both shows empty file.
I disabled Eset Enpoint, and I downloaded it 3 times.
However, I am using stock rom and I have the SQLite Editor. What changes did you do? Do you just have to change file 12 'broadband' to 'pta'?
Thanks
Click to expand...
Click to collapse
I don't remember which line exactly off the top of my head. I am reattaching the zip file see if that works if that fails then I will go in a compare the standard .db with the new one. It was a simple one line change just don't remember which line it was. Trial and error is how I found it.
Thank you
lightpost712 said:
I don't remember which line exactly off the top of my head. I am reattaching the zip file see if that works if that fails then I will go in a compare the standard .db with the new one. It was a simple one line change just don't remember which line it was. Trial and error is how I found it.
Click to expand...
Click to collapse
I guess you did it using SQLite editor, it works for me.
Make a backup of telephony.db
Your internet APN should be configured (Settings - Mobile data - Access Point names)
1)Open Telephony.db (flange files: data/data/com.android.providers.telephony/databases)
2)Select 'carriers'
3)Search second row, then select Edit field
4)Change ID field with a number non used in this db (ex: in my case the last row is "42" so I used "43") - Save
5)Repeat the 3 and 4 steps, but using row 12.
6)Search the last line (or line with your carrier internet APN)
7)Select the row and Edit Field.
8)Change the ID field to "2". - Save
9)Chose the second row, then Clone Record and change ID field to '12' - Save
Just need to change a lot of things
Row number 2 -> Edit field
1)Change name to ATT Phone
2)Type to "default"
2)Insert_by field to "internal".
3)State to "readonly"
Row number 12 -> Edit field
1)Change name to Entiltlement
2)Type to "entitle"
2)Insert_by field to "internal".
3)State to "hidden"
My phone: HTC One X AT&T 3.18 unlocked and root. Stock rom
Worked great for me with a rooted, s-off HTC First and ST (ATT) SIM. Thank you!
diekastro said:
I guess you did it using SQLite editor, it works for me.
Make a backup of telephony.db
Your internet APN should be configured (Settings - Mobile data - Access Point names)
1)Open Telephony.db (flange files: data/data/com.android.providers.telephony/databases)
2)Select 'carriers'
3)Search second row, then select Edit field
4)Change ID field with a number non used in this db (ex: in my case the last row is "42" so I used "43") - Save
5)Repeat the 3 and 4 steps, but using row 12.
6)Search the last line (or line with your carrier internet APN)
7)Select the row and Edit Field.
8)Change the ID field to "2". - Save
9)Chose the second row, then Clone Record and change ID field to '12' - Save
Just need to change a lot of things
Row number 2 -> Edit field
1)Change name to ATT Phone
2)Type to "default"
2)Insert_by field to "internal".
3)State to "readonly"
Row number 12 -> Edit field
1)Change name to Entiltlement
2)Type to "entitle"
2)Insert_by field to "internal".
3)State to "hidden"
My phone: HTC One X AT&T 3.18 unlocked and root. Stock rom
Click to expand...
Click to collapse
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
brilliant_smart said:
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
Click to expand...
Click to collapse
The AT&T ROMs are a real pain in the butt in regards to tethering and WiFi hotspot. As you are already bootloader unlocked and rooted, I would suggest just flashing any non-AT&T base ROM, and the tethering functions should work properly. Especially if you are not on AT&T, and your carrier does not limit tethering in any way (it looks like you are not located in the US?).
In my opinion, there is nothing "good" about being on the AT&T ROM. Many functions are intentionally broken or hidden, with nothing useful added. So going to a non-AT&T based ROM is "win" all around.
brilliant_smart said:
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
Click to expand...
Click to collapse
Maybe Its late for answer, but did you restar your phone after edit the file?
diekastro said:
Maybe Its late for answer, but did you restar your phone after edit the file?
Click to expand...
Click to collapse
No offense to the OP, but I would suggest not wasting any more time with this method (its been 6 months after all). As I already mentioned in Post #11 above, just flash any custom or stock rooted ROM that is not AT&T base (Sense base - I don't follow AOSP ROMs enough to know how well WiFI hotspot works on those), and WiFi hotspot will work fine.
You are right
redpoint73 said:
No offense to the OP, but I would suggest not wasting any more time with this method (its been 6 months after all). As I already mentioned in Post #11 above, just flash any custom or stock rooted ROM that is not AT&T base (Sense base - I don't follow AOSP ROMs enough to know how well WiFI hotspot works on those), and WiFi hotspot will work fine.
Click to expand...
Click to collapse
yes, really I flashed with T-mobile Sense 5 ROM five months ago, and its better option.

Adb global settings?

So I can across this on my Google + feed and was wondering what the exact command would be and if there are other "global settings " commands to use with adb? I am on stock 8.1 on my sailfish and I'm curious to see if this can help resolve my Volte issue or not:
"Can I (and should I) enable VoLTE on my Nexus 6?
While messing around in adb's "settings list global" command I came across this toggle: volte_feature_disabled=1
Is this something that we can play around with?"
What do you guys/gals think?
Xdevillived666 said:
So I can across this on my Google + feed and was wondering what the exact command would be and if there are other "global settings " commands to use with adb? I am on stock 8.1 on my sailfish and I'm curious to see if this can help resolve my Volte issue or not:
"Can I (and should I) enable VoLTE on my Nexus 6?
While messing around in adb's "settings list global" command I came across this toggle: volte_feature_disabled=1
Is this something that we can play around with?"
What do you guys/gals think?
Click to expand...
Click to collapse
Yeah, adb will let you change anything in the settings database. Not going to hurt anything to try. I changed some settings on my Pixel to force wifi calling to be preferred.
Sent from my Pixel using Tapatalk
baknblack said:
Yeah, adb will let you change anything in the settings database. Not going to hurt anything to try. I changed some settings on my Pixel to force wifi calling to be preferred.
Click to expand...
Click to collapse
So for that volte disabled command , what would the actual adb command be ?
Xdevillived666 said:
So for that volte disabled command , what would the actual adb command be ?
Click to expand...
Click to collapse
This was for the wifi calling. I guess just substitute your VOLTE variable. An easier way is to get settings database editor from the play store. It gives you instructions on how to grant the app system permission with adb. Then you can edit the database directly from your phone.
ADB shell prompt: settings put global wfc_ims_mode 2
Sent from my Pixel using Tapatalk
baknblack said:
This was for the wifi calling. I guess just substitute your VOLTE variable. An easier way is to get settings database editor from the play store. It gives you instructions on how to grant the app system permission with adb. Then you can edit the database directly from your phone.
ADB shell prompt: settings put global wfc_ims_mode 2
Click to expand...
Click to collapse
You da man.thanks so much
baknblack said:
This was for the wifi calling. I guess just substitute your VOLTE variable. An easier way is to get settings database editor from the play store. It gives you instructions on how to grant the app system permission with adb. Then you can edit the database directly from your phone.
ADB shell prompt: settings put global wfc_ims_mode 2
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Ive got the app setup. I authorised it via adb shell.
Do I just click on a command and save the value as is or do I need to edit anything?
Xdevillived666 said:
Ive got the app setup. I authorised it via adb shell.
Do I just click on a command and save the value as is or do I need to edit anything?
Click to expand...
Click to collapse
I think just change the 1 to a 0 save and reboot. Setting changes persist through reboots and security updates
Sent from my Pixel using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:20 AM ----------
baknblack said:
I think just change the 1 to a 0 save and reboot. Setting changes persist through reboots and security updates
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
If the string you're looking for isn't already in your database I doubt you'll be successful in adding a new string as not all phones have the same settings.
Sent from my Pixel using Tapatalk
baknblack said:
I think just change the 1 to a 0 save and reboot. Setting changes persist through reboots and security updates
Sent from my Pixel using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:20 AM ----------
If the string you're looking for isn't already in your database I doubt you'll be successful in adding a new string as not all phones have the same settings.
Click to expand...
Click to collapse
Here are the strings
Does" 1 "enable ?
Xdevillived666 said:
Here are the strings
Does" 1 "enable ?
Click to expand...
Click to collapse
Is your phone a pixel and what exactly are you trying to enable? You wanting VOLTE and wifi calling? Even with it enabled in the Database your phone will need to be provisioned by the carrier for it to work.
Sent from my Pixel using Tapatalk
baknblack said:
Is your phone a pixel and what exactly are you trying to enable? You wanting VOLTE and wifi calling? Even with it enabled in the Database your phone will need to be provisioned by the carrier for it to work.
Click to expand...
Click to collapse
Yeah, it's a pixel. Yes I want wifi and volte. I'm guessing my phone really does need to be bought from the carrier to work because I already chatted with phone support and they sent the config but nothing changed. Thought maybe I had to something else. Damn. Thanks again man.

Rooted Pixel 2 Hotspot -- "To enable, go to att.com/mywireless or dial 611."

Rooted Pixel 2 Hotspot -- "To enable, go to att.com/mywireless or dial 611."
Ex-squeeze me? You're a Pixel! You're not supposed to respect carrier crap!
Is there a good way to bypass this with root? All I have done so far is upgrade completely to the latest version of 8.1 and installed Magisk.
Thanks.
starkruzr said:
Ex-squeeze me? You're a Pixel! You're not supposed to respect carrier crap!
Is there a good way to bypass this with root? All I have done so far is upgrade completely to the latest version of 8.1 and installed Magisk.
Thanks.
Click to expand...
Click to collapse
in build.prop add line:
net.tethering.noprovisioning=true
build.prop is at root level/system
Probably you can put it anywhere in build.prop, but I put it just after the other "net" command.
Then you should be good to go. Type carefully. Not sure what would happen if you type an invalid command in build.prop.
tedr108 said:
in build.prop add line:
net.tethering.noprovisioning=true
build.prop is at root level/system
Probably you can put it anywhere in build.prop, but I put it just after the other "net" command.
Then you should be good to go. Type carefully. Not sure what would happen if you type an invalid command in build.prop.
Click to expand...
Click to collapse
Thanks for this
starkruzr said:
Thanks for this
Click to expand...
Click to collapse
Did that solution work? I'm contemplating buying a Pixel 2 but want to make sure the hotspot feature works. I'm on the original Verizon unlimited and still want to be able to hotspot.

Call recording

Can anyone confirm that this 9.0 pie update breaks all call recording app from the play store. Thanks for your feedback.
Updated to Android 9 today and boldbeast no longer works, it will record my voice but not that of the call )-: I am considering root now to get the feature back as i did find it useful.
Update: found this on the play store https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools&hl=en_GB
Its all working fine now as it enables the oneplus6 built in recorder.
Thanks
But that also means that it wouldn't work without root like myself. Right?
Guess I gotta stick with my 8.1 until someone figures this one out. This one feature is like super important to me atm.
Thanks again for your kind reply.
Hi,
No root required, my phone is standard no unlocked bootloader and no root.
You just need to install the software, then enable developer options on your phone, enable usb debbugging and send the following command to your phone. adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
Then you will have the option in the software (joneplustool) to enable call recording and also restore calling recorder at boot.
Then on the phone dialler , go into settings and enable call record.
xtruss said:
restore calling recorder at boot.
Click to expand...
Click to collapse
That's a bummer...
But hey, thanks a lot for your kind reply. And as for myself, I've been using Cherinbo, pretty decent I would say.
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
vibo2013 said:
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
Click to expand...
Click to collapse
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
You seem as though you just want to promote a product to me, and one that doesn't work.
Darkest shades said:
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
Click to expand...
Click to collapse
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
xtruss said:
You seem as though you just want to promote a product to me, and one that doesn't work.
Click to expand...
Click to collapse
Lol, not my intention. But the one thing that I like about this one is that all saved, recorded files doesn't appear into my music player, where as for others, they always does. Thanks for confirming that it doesn't work.
vibo2013 said:
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
Click to expand...
Click to collapse
It's ok, you help a lot already.
Thanks for your help guys.
I am very happy with the built in call recorder. What is the benefit of having a third party app to record calls?
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Void
---------- Post added at 02:57 AM ---------- Previous post was at 02:49 AM ----------
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
dgunn said:
Void
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
"adb shell settings put global op_voice_recording_supported_by_mcc 1"
It enables the default, native Call Recorder found on op6 and op5 and I really like it. It recorded all my today's calls ranging from 625KB to 2.29MB all good quality(aac files)
eliaspizarro said:
Requeriments:
root
terminal with su permisions
Manual steps
Method 1 (works until reboot):
Create a file ex. incall.sh:
Code:
#!system/bin/sh
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
execute from terminal: $ sh incall.sh
Method 2 (works until reboot):
with adb: > adb shell "settings put global op_voice_recording_supported_by_mcc 1"
My steps (permanent):
Install termux (add su permisions)
in termux: $ termux-setup-storage
Install termux boot
create folder un termux home path (default) named: .termux
in termux: $ ln -s /storage/emulated/0/<your boot script folder> ~/.termux/boot
create script in /storage/emulated/0/<your boot script folder>
Code:
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
exit
reboot
Click to expand...
Click to collapse
..
This is what I'm getting
sh: $: not found
Just by telling us to install this and add home path here..... We need instructions
---------- Post added at 06:26 PM ---------- Previous post was at 06:04 PM ----------
and again
sh: adb: not found
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
You can also use Tasker to enable native call recording (provided you've granted WRITE_SECURE_SETTINGS permission to Tasker).
It seems the system deactivates jOnePlus from activating call recorder after 8 hours. Anyway to make it a permanent activation?
Even after removing jOnePlus from the battery optimize list, the call recorder still gets deactivated after a couple of hours.
obislu said:
mzsquared said:
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
I took the official OTA Pie upgrade and enabled the recorder with adb command after that. I'm not planning to root my phone, at least not yet. I'm enjoying the Pie Rom as is. It's all good, actually great with the night mode, there is no bloat. I disabled few apps, mainly from google and that's that. I remember times when rooting was an important necessity, I've had a Motorola Defy XT, long time ago, with 1GB RAM and no space for any extra apps, rooting was mainly used for getting the bloat out and moving apps to SD card by way of creating ext4 partition.
My OP6 has 256GB storage space, 8GB RAM and I just don't feel like constantly reloading the system, chasing newest twrps and Magisk versions, softbricking etc,etc.. and having my phone 'off line' for hours while I'm fixing it.
Click to expand...
Click to collapse

Rooted H910 with drastically lower reception, trying to flash modem files from dump

Hello,
I've rooted a few phones, but I don't really do too much with them, I mostly root them to have an easier time transferring all data from one phone to the next, and for being able to use a couple of root apps. Basically, I'm not all that good at this stuff, but I can get by most of the time with enough research and time. I have not been able to find a thread that's been able to help me with this problem, though.
My V20's reception practically fell off the map after rooting it. I've been researching and trying to find a way to flash the modem files that I dumped with LGUP before I rooted it via dirtysanta, but I'm not having any luck. The files don't have an extension, but from what I can gather, they should be image files. I'm not 100% on that because I can't seem to find what file type they actually are, my computer only lists them with the description of "file". I run Windows 7 if that matters.
Anyway, based on what I've found so far, the files I need to flash in order to fix my reception problem are:
modem_COM5
modemst1_COM5
modemst2_COM5
fsg_COM5
I can't get fastboot to work, I'm not sure how to link my phone to a file path on my computer from command terminal so that's not been working for me. I've also tried renaming the files by adding ".img" to the end, zipping them and installing them with twrp afterward, but they won't install, giving me an error of "META-INF/com/google/android/update-binary"
Ultimately, I'm lost. Any help is greatly appreciated, as I've spent hours pouring over threads and trying to fix my stupid reception problems. I have no reception at home, none at work, and I have spotty reception while driving or out in other places, but it's generally terrible. I used to have low reception at home, but I could always make a call if I needed to, and I'd have great reception driving around. Then I rooted my phone and my reception tanked.
platypus25_5 said:
Hello,
I've rooted a few phones, but I don't really do too much with them, I mostly root them to have an easier time transferring all data from one phone to the next, and for being able to use a couple of root apps. Basically, I'm not all that good at this stuff, but I can get by most of the time with enough research and time. I have not been able to find a thread that's been able to help me with this problem, though.
My V20's reception practically fell off the map after rooting it. I've been researching and trying to find a way to flash the modem files that I dumped with LGUP before I rooted it via dirtysanta, but I'm not having any luck. The files don't have an extension, but from what I can gather, they should be image files. I'm not 100% on that because I can't seem to find what file type they actually are, my computer only lists them with the description of "file". I run Windows 7 if that matters.
Anyway, based on what I've found so far, the files I need to flash in order to fix my reception problem are:
modem_COM5
modemst1_COM5
modemst2_COM5
fsg_COM5
I can't get fastboot to work, I'm not sure how to link my phone to a file path on my computer from command terminal so that's not been working for me. I've also tried renaming the files by adding ".img" to the end, zipping them and installing them with twrp afterward, but they won't install, giving me an error of "META-INF/com/google/android/update-binary"
Ultimately, I'm lost. Any help is greatly appreciated, as I've spent hours pouring over threads and trying to fix my stupid reception problems. I have no reception at home, none at work, and I have spotty reception while driving or out in other places, but it's generally terrible. I used to have low reception at home, but I could always make a call if I needed to, and I'd have great reception driving around. Then I rooted my phone and my reception tanked.
Click to expand...
Click to collapse
I can make you a zip to flash the files in TWRP
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
I can make you a zip to flash the files in TWRP
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
Thanks! Do I just need to email you the modem files?
platypus25_5 said:
Thanks! Do I just need to email you the modem files?
Click to expand...
Click to collapse
no you can put them in the zip below
Here's your zip > https://drive.google.com/open?id=1RiNnyS-iF34a543zQAchi70-YAUvc3hn
rename your files to
modem
modemst1
modemst2
fsg
and add them to the zip and save it
copy to phone and flash it
clsA said:
no you can put them in the zip below
Here's your zip
rename your files to
modem
modemst1
modemst2
fsg
and add them to the zip and save it
copy to phone and flash it
Click to expand...
Click to collapse
I appreciate you making the zip, but after flashing the files my phone won't boot up. When I power it on it says that my device has failed a routine safety check and will not boot. I'm accustomed to my phone saying that when I boot it up, as it's done that ever since rooting it, but then it shows the LG logo and then shuts off and will not turn on again unless I take the battery out and reinsert it. I have to go through that process at least 2 or 3 times to get the phone to load up. When I got it to load up again, the top bar of my phone said I had no service, which it did not before flashing the files. I've gone back into twrp and tried re-flashing it again to no avail.
If it makes a difference there were two sets of files when I went to flash, even though I only put in one set. I renamed them according to your instructions, and there were one set that just had the file name and .img at the end (like fsg.img) and another set that started with ._ and ends with .img (like ._fsg.img)
Thanks again for taking the time, I really appreciate the help.
platypus25_5 said:
I appreciate you making the zip, but after flashing the files my phone won't boot up. When I power it on it says that my device has failed a routine safety check and will not boot. I'm accustomed to my phone saying that when I boot it up, as it's done that ever since rooting it, but then it shows the LG logo and then shuts off and will not turn on again unless I take the battery out and reinsert it. I have to go through that process at least 2 or 3 times to get the phone to load up. When I got it to load up again, the top bar of my phone said I had no service, which it did not before flashing the files. I've gone back into twrp and tried re-flashing it again to no avail.
If it makes a difference there were two sets of files when I went to flash, even though I only put in one set. I renamed them according to your instructions, and there were one set that just had the file name and .img at the end (like fsg.img) and another set that started with ._ and ends with .img (like ._fsg.img)
Thanks again for taking the time, I really appreciate the help.
Click to expand...
Click to collapse
I tested the zip myself it works as expected.
The unlocked bootloader message has nothing to do with your issue.
What sim card are you using?
What are your apn settings?
What was the last Rom you flashed?
Are you on Oreo?
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
I tested the zip myself it works as expected.
The unlocked bootloader message has nothing to do with your issue.
What sim card are you using?
What are your apn settings?
What was the last Rom you flashed?
Are you on Oreo?
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
It's a nano sim from at&t, and at&t is my carrier. I doubt it's relevant, but I use a prepaid plan.
My app settings are:
Name: ATT Nextgenphone
APN: nxtgenphone
Proxy: Not set
Port: Not set
Username: Not set
Password: Not set
MMSC: http://mmsc.mobile.att.net
MMS proxy: proxy.mobile.att.net
MMS port: 80
MCC: 310
MNC: 410
Authentication type: None
APN type: default,mms,supl,hipri,fota
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6
I believe the last ROM I flashed was H91510e_VTR_CA_OP_1205.kdz
Using the DirtySanta method of rooting, I think I flashed that so I could actually root the phone and then updated to another version, possibly. I'll include my software info in case that is helpful.
I'm not on oreo, I'm running nougat
Android version: 7.0
Android security patch level: November 1, 2017
Baseband version: MPSS.TH.2.0.1.c3-00011M8996FAAAANAZM-1.69323.1. 69645.2
Kernel version: 3.18.31
Build number: NRD90M
Software version: H91010r
Security software version: MDF v2.0 Release 4
Thanks again for all of your help.
platypus25_5 said:
It's a nano sim from at&t, and at&t is my carrier. I doubt it's relevant, but I use a prepaid plan.
My app settings are:
Name: ATT Nextgenphone
APN: nxtgenphone
Proxy: Not set
Port: Not set
Username: Not set
Password: Not set
MMSC: http://mmsc.mobile.att.net
MMS proxy: proxy.mobile.att.net
MMS port: 80
MCC: 310
MNC: 410
Authentication type: None
APN type: default,mms,supl,hipri,fota
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6
I believe the last ROM I flashed was H91510e_VTR_CA_OP_1205.kdz
Using the DirtySanta method of rooting, I think I flashed that so I could actually root the phone and then updated to another version, possibly. I'll include my software info in case that is helpful.
I'm not on oreo, I'm running nougat
Android version: 7.0
Android security patch level: November 1, 2017
Baseband version: MPSS.TH.2.0.1.c3-00011M8996FAAAANAZM-1.69323.1. 69645.2
Kernel version: 3.18.31
Build number: NRD90M
Software version: H91010r
Security software version: MDF v2.0 Release 4
Thanks again for all of your help.
Click to expand...
Click to collapse
Maybe theirs a setting in the Hidden menu that will help
using a build.prop editor (thanks @ezzony)
Change ro.build.target_operator from ATT to OPEN to bring back all the missing Modem_Settings and the ones that were also missing in regular Settings>Mobile Networks. Also reverted to stock icons in status bar.
in the dialer type > *#546368#*910#
then go to Field Test>Modem Settings>Network Mode and set to Automatic
reboot
you can also check that Volte and VoWifi are enabled from the hidden menu Modem settings
Also in Settings>Mobile Network>Network Mode be sure it's set to the top one (GSM/WCDMA/LTE auto)
clsA said:
Maybe theirs a setting in the Hidden menu that will help
using a build.prop editor (thanks @ezzony)
Change ro.build.target_operator from ATT to OPEN to bring back all the missing Modem_Settings and the ones that were also missing in regular Settings>Mobile Networks. Also reverted to stock icons in status bar.
in the dialer type > *#546368#*910#
then go to Field Test>Modem Settings>Network Mode and set to Automatic
reboot
you can also check that Volte and VoWifi are enabled from the hidden menu Modem settings
Also in Settings>Mobile Network>Network Mode be sure it's set to the top one (GSM/WCDMA/LTE auto)
Click to expand...
Click to collapse
I downloaded a build.prop editor and changed the build target operator setting, but I'm not sure what you mean by reverting to stock icons in status bar or how to do that. Which settings were missing in Settings>Mobile Networks?
I got into that other menu, but under field test>modem settings I can choose either engineering mode or PDP setting.
Engineering mode says "modemprotocol" in the top corner, with previous, up, down, and next buttons. Under that it says ITEM_2G: 0
[Serving Cell Information]
ARFCN: 0
FL_Timeout_v: 0
RXLEV: 0
C1: 0
C2: 0
Other pages for engineering mode are for Item HSPA:0 [HSDPA Information], Item_NM [general information], Item_3G: 0 [RRC State and Serving Cell information], Item_LTE: 0 [LTE Information]
PDP settings says ModemProtocol at the top and has options for [0] Set LG Fast Dormancy, [1] APN setting, [2' Block DataRecovery.
VoLTE and VoWifi are enabled in the hidden menu, but I can't access Settings>Mobile Network>Network Mode. I can't figure out how to check the GSM and other options. I can go to Settings>Mobile Networks and then I can go to:
Mobile data - just turns it on or off
Mobile data reminder
Review reminder settings
International data roaming
Disable 2G
Access Point Names
Search for AT&T MicroCell - When I search, none are found
I hope I'm not just throwing too much useless information for you to sift through. I'm just not entirely sure of what all is relevant.
platypus25_5 said:
I downloaded a build.prop editor and changed the build target operator setting, but I'm not sure what you mean by reverting to stock icons in status bar or how to do that. Which settings were missing in Settings>Mobile Networks?
I got into that other menu, but under field test>modem settings I can choose either engineering mode or PDP setting.
Engineering mode says "modemprotocol" in the top corner, with previous, up, down, and next buttons. Under that it says ITEM_2G: 0
[Serving Cell Information]
ARFCN: 0
FL_Timeout_v: 0
RXLEV: 0
C1: 0
C2: 0
Other pages for engineering mode are for Item HSPA:0 [HSDPA Information], Item_NM [general information], Item_3G: 0 [RRC State and Serving Cell information], Item_LTE: 0 [LTE Information]
PDP settings says ModemProtocol at the top and has options for [0] Set LG Fast Dormancy, [1] APN setting, [2' Block DataRecovery.
VoLTE and VoWifi are enabled in the hidden menu, but I can't access Settings>Mobile Network>Network Mode. I can't figure out how to check the GSM and other options. I can go to Settings>Mobile Networks and then I can go to:
Mobile data - just turns it on or off
Mobile data reminder
Review reminder settings
International data roaming
Disable 2G
Access Point Names
Search for AT&T MicroCell - When I search, none are found
I hope I'm not just throwing too much useless information for you to sift through. I'm just not entirely sure of what all is relevant.
Click to expand...
Click to collapse
reboot after build.prop edit
then all the options show up
the icons change on their own as a result of the build prop edit
clsA said:
reboot after build.prop edit
then all the options show up
the icons change on their own as a result of the build prop edit
Click to expand...
Click to collapse
Alright, I've done this, I've also made a few different access point names for att to try and see if any of those have better reception. Nothing's working all that great, but hopefully at least one of them works a little better than what I've been used to.
Currently I still have no reception where I'm used to having one or two bars around the house. I'm not sure if there is anything else to do without opening up the phone and replacing any parts. If there is anything else you can think of that I might try, please let me know.
Do you think that changing the screen would make any difference on reception? I did have to have mine changed shortly after rooting the phone, but I can't really imagine that could be the cause since I still do get occasional reception.
Thanks again for all of your help.
platypus25_5 said:
Alright, I've done this, I've also made a few different access point names for att to try and see if any of those have better reception. Nothing's working all that great, but hopefully at least one of them works a little better than what I've been used to.
Currently I still have no reception where I'm used to having one or two bars around the house. I'm not sure if there is anything else to do without opening up the phone and replacing any parts. If there is anything else you can think of that I might try, please let me know.
Do you think that changing the screen would make any difference on reception? I did have to have mine changed shortly after rooting the phone, but I can't really imagine that could be the cause since I still do get occasional reception.
Thanks again for all of your help.
Click to expand...
Click to collapse
Any hardware change could easily damage the antenna or it may be completely unplugged. Check the tear down video on ifixit
Sent from my ONEPLUS A6010 using Tapatalk
I am having the same problem after following the root guide - no data. I'm on T-Mobile with an ATT phone running H91010r. I installed your modem.bat file with my dumped modem files using twrp, I changed the ATT buildprop to open, rebooted and made sure to select the first auto option. I tried dialing the secret menu number but it gives an error. Zero data. Everything else seems to be working phone. Data worked on stock phone before rooting. Please help!
Classpro said:
I am having the same problem after following the root guide - no data. I'm on T-Mobile with an ATT phone running H91010r. I installed your modem.bat file with my dumped modem files using twrp, I changed the ATT buildprop to open, rebooted and made sure to select the first auto option. I tried dialing the secret menu number but it gives an error. Zero data. Everything else seems to be working phone. Data worked on stock phone before rooting. Please help!
Click to expand...
Click to collapse
it's most likely an APN problem
what do you mean the dialer code did not work ? it works on all H910
When I put in the dialer code and hit call I get "ussd code RUNNING" and then "connection problem or invalid mmi code"
I did get 4g working by reseting the Sim card, so I'm not panicking, but it seems slower than before. APN is off the t-mobile site.
Classpro said:
When I put in the dialer code and hit call I get "ussd code RUNNING" and then "connection problem or invalid mmi code"
I did get 4g working by reseting the Sim card, so I'm not panicking, but it seems slower than before. APN is off the t-mobile site.
Click to expand...
Click to collapse
are you sure you have a H910 ?
the dialer code depends on the Motherboard
*#546368#*910#
see the 910# at the end must match your phone
the Verizon LG V20 VS995 dialer code is disabled > worth reading
The unlocked LG V20 US995 would use dialer code *#546368#*995#
I'm not sure what works with the F800 version
clsA said:
are you sure you have a H910 ?
Click to expand...
Click to collapse
Yes, I'm sure. AT&T version, model number LG-H910. Running rooted software version H91010r.
I have the same problem on 800l entered the menu changing the model 996 at the end, as I understand it, without twrp how can I fix the problem?

Categories

Resources