HELP can't send SMS messages error 111 with TFW??

Lbeaster11

Need some help with this, nobody can figure out what happened and I've tried everything short of factory resetting which I really don't want to do. If anyone knows anything else to try I would greatly appreciate it!!

Novalissoide

Lbeaster11 Are you using the stock GrapheneOS Messaging app?

Johnnyloans

From OP's older, deleted post

I can receive calls and all texts. Sending MMS works, sending SMS fails.

@"Lbeaster11"#p214858

It'd be better to add a comment to the older post rather than create a new one. Commenting: "bump" (the name of this action) or "anyone have an idea?" Suffices. It'll place your post at the very top for people to see.

First try mobile settings reset:
Settings > system > reset mobile network settings
Then reboot

Reinstall your texting app if you can. Also logs helps with pinpointing the issue. Your text history is in an android database--not the app's--so you won't lose any messages.

Going to your carrier can help in this situation. They can help you navigate the various possible causes.

Or try stock OS. Back up anything important which would be deleted.

Or telecoms in China don't provide updated connectivity info to AOSP. If that applies to you.

Lbeaster11

Yes original messaging app, I've tried everything short of a factory reset but the weird thing is I can call and receive calls and receive messages and actually send messages just have to attach a pic or something to be able to send it. Never seen anything like it before?

Novalissoide

Lbeaster11 original messaging app

I recommend trying this app instead, it solved the issues of the stock one for me.
https://github.com/FossifyOrg/Messages/releases

Lbeaster11

I'll post the logs and see if someone can decrypt the problem because I can't find it. Thanks!

Lbeaster11

type: logcat
osVersion: google/cheetah/cheetah:16/BP4A.251205.006/2026021201:user/release-keys
flags: dev options enabled
package: com.android.messaging:20000012, targetSdk 35
buffers: main,system,crash,events,kernel
level: warn

--------- beginning of main
02-28 20:48:09.120  4009  4009 E MessagingApp: SmsSender: failure in sending message part.  requestId=content://sms/12694 partId=0 resultCode=112 errorCode=111
02-28 20:48:09.131  4009  4009 E Toast   : setGravity() shouldn't be called on text toasts, the values won't be used
02-28 20:48:09.136  4009  4009 E MessagingApp: SmsSender: Unexpected sent intent resultCode = 112
02-28 20:48:09.138  4009  9697 E MessagingApp: MmsUtils: SMS permanent failure
02-28 20:48:09.194  4009  4050 E SpannableStringBuilder: SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
02-28 20:48:17.856  4009  4009 E MessagingApp: SmsSender: failure in sending message part.  requestId=content://sms/12696 partId=0 resultCode=112 errorCode=111
02-28 20:48:17.866  4009  4009 E Toast   : setGravity() shouldn't be called on text toasts, the values won't be used
02-28 20:48:17.871  4009  4009 E MessagingApp: SmsSender: Unexpected sent intent resultCode = 112
02-28 20:48:17.872  4009  9707 E MessagingApp: MmsUtils: SMS permanent failure
02-28 20:48:17.926  4009  4050 E SpannableStringBuilder: SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
02-28 20:48:22.419  4009  9717 W InteractionJankMonitor: Initializing without READ_DEVICE_CONFIG permission. enabled=false, interval=1, missedFrameThreshold=3, frameTimeThreshold=64, package=com.android.messaging
02-28 20:48:22.433  4009  4009 W WindowOnBackDispatcher: OnBackInvokedCallback is not enabled for the application.
02-28 20:48:22.433  4009  4009 W WindowOnBackDispatcher: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
02-28 20:48:22.445  4009  4009 W ViewPager: Requested offscreen page limit 0 too small; defaulting to 1
02-28 20:48:22.449  4009  4009 W ViewPager: Requested offscreen page limit 0 too small; defaulting to 1
02-28 20:48:23.974  4009  4009 E MessagingApp: SmsSender: failure in sending message part.  requestId=content://sms/12697 partId=0 resultCode=112 errorCode=111
02-28 20:48:23.979  4009  4009 E Toast   : setGravity() shouldn't be called on text toasts, the values won't be used
02-28 20:48:23.981  4009  4009 E MessagingApp: SmsSender: Unexpected sent intent resultCode = 112
02-28 20:48:23.981  4009  9713 E MessagingApp: MmsUtils: SMS permanent failure
02-28 20:48:24.030  4009  4039 W com.android.messaging: Cleared Reference was only reachable from finalizer (only reported once)
02-28 20:48:24.054  4009  4039 W com.android.messaging: Reducing the number of considered missed Gc histogram windows from 439 to 100
02-28 20:48:50.794  4009  4009 W WindowOnBackDispatcher: OnBackInvokedCallback is not enabled for the application.
02-28 20:48:50.794  4009  4009 W WindowOnBackDispatcher: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
02-28 20:48:51.944  4009  4009 W WindowOnBackDispatcher: OnBackInvokedCallback is not enabled for the application.
02-28 20:48:51.944  4009  4009 W WindowOnBackDispatcher: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
02-28 20:48:51.968  4009  4009 W ImeBackCallbackProxy: Ime callback not found. Ignoring unregisterReceivedCallback. callbackId: 254079681 remaining callbacks: 0

Novalissoide

Lbeaster11 flags: dev options enabled

This should be OFF on your device.

Lbeaster11

I just turned them on for a second to take a full interactive report and that other messaging app is an extremely high security risk

Novalissoide

Lbeaster11 more than stock? They are both highly insecure since both are about SMS.

Johnnyloans

Lbeaster11

Another SMS app is a good idea to test.

SMS doesnt have any encryption, can't really mess up privacy/security there. I think it wouldn't hurt to send out 1 text and quickly delete the app.

The log, to me, seems vague unfortunately. I'd exhaust the suggestions in this thread that youre comfortable with.

Make sure to ask the carrier to go through everything and make sure it's all configured right. Try a new sim card--mind as well.

Lbeaster11

Tried a new one and received the same error code, message can't be sent with TFW, ERROR 111. Carrier said factory resetting is the only way they can see it getting fixed so looks like that's what it has come down to unfortunately! Thanks for the help!

Novalissoide

Lbeaster11 a simple websearch for TFW, ERROR 111 gave lots of claimed notions of the issue, and a good bunch of alleged solutions, here's the first one I saw:
https://etechshout.com/fix-t-mobile-error-111/

Johnnyloans

Lbeaster11

Did you follow these suggestions?

Novalissoide https://etechshout.com/fix-t-mobile-error-111/

Also could be that your phone is using the wrong SMSC number for your carrier. I have google messages. I check it by:
open the app > top right profile icon > message settings > advanced > SMSC = +1234567890
(your SMSC number will be different)

Confirm that this SMSC number is correct for your carrier--contact them. Say you can receive texts and pictures. You can also send pictures but you can't send word texts AKA SMS. Have them confirm all settings are correct for your account and the SMSC number is right.

Lbeaster11

I've tried everything, even factory reset and still recievr the same error, any real hrll would be awesome!!! This is absolutely insane its worked perfectly for over s year and all the sudden does this so any helpful advice would be awesome and yes I've looked up and tried every single thing it says online to fix it and talked to my carrier and they can't even figure it out. Thanks!

Lbeaster11

I've tried new messaging apps and same thing. Surely this has happened to someone else??? I don't know egat to do or try at this point, its driving me absolutely crazy !!!!!