How to fix unread SMS waiting | timeout on ZTE and ZLT MiFis

[Tutorial] How to fix unread SMS waiting | timeout on ZTE and ZLT MiFis

hovatek
Administrator

49,774

26-11-2023, 04:55 PM

#1

This guide will explain how to clear unread SMSs which cause the SMS section of your ZTE or ZLT MiFi's dashboard to be inaccessible. Whenever you try to open the SMS section, All you see is 'Waiting' with a spinner until you get logged out due to a timeout.

Although an easy fix is resetting the MiFi by inserting a pin into the reset hole, there are cases where you do not wish to do a reset or the SMSs remain even after a reset. The goal of this guide is to delete the SMS or reduce them to a number which would make the SMS section available once again.

This has been tested on the ZTE MF927U and the ZLT M30S using a Windows PC.

Requirements

A PC
Google Chrome browser
Install WebSpy Chrome extension @ https://chromewebstore.google.com/detail...ccebgapije

How to clear SMS on a ZTE or ZLT MiFi, Router or CPE using WebSpy

See the video below or @ https://youtu.be/hH3zSui2uU8

Login at your MiFi's Dashboard e.g 192.168.0.1
Open the Chrome developer tools by pressing either Fn + F12 or Ctrl + Shift + i
Click the right chevron at the top then choose Spy
You should see a stream of request logs
Click on any of the requests
Copy and save the request header (you'll need it soon)
To get a list of SMSs, Click the '+ New' button at the bottom right. The request to send is:

For ZTE

Request

Code:

GET

URL

Code:

http://192.168.0.1/goform/goform_get_cmd_process?isTest=false&cmd=sms_data_total&page=0&data_per_page=500&mem_store=1&tags=10&order_by=order+by+id+desc&_=1700930263981

Request Header (You may replace with the one you copied earlier)

Code:

Accept: application/json, text/javascript, */*; q=0.01 Accept-Encoding: gzip, deflate Accept-Language: en-US,en;q=0.9 Connection: keep-alive Host: 192.168.0.1 Referer: http://192.168.0.1/index.html User-Agent: Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36 X-Requested-With: XMLHttpRequest

For ZLT

Request

Code:

GET

URL

Code:

http://192.168.0.1/reqproc/proc_get?isTest=false&cmd=sms_data_total&page=0&data_per_page=100&mem_store=1&tags=1&order_by=order+by+id+desc&_=1700931075270

Request Header (You may replace with the one you copied earlier)

Code:

Accept: application/json, text/javascript, */*; q=0.01 Accept-Encoding: gzip, deflate Accept-Language: en-US,en;q=0.9 Connection: keep-alive Cookie: pageForward=home Host: 192.168.0.1 Referer: http://192.168.0.1/index.html?t=7338561 User-Agent: Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36 X-Requested-With: XMLHttpRequest
Click Send
Once sent, scroll down to the response section in WebSpy. You should see all the SMSs and their info.
Make a list of their IDs separated by %3D e.g IDs 100, 101, 102 and 103 would be 100%3B101%3B102%3B103
The request body for the above example would look like

Code:

isTest=false&goformId=DELETE_SMS&msg_id=100%3B101%3B102%3B103%3B&notCallback=true

Notice that the list of I.Ds are inserted between = and %3B&notCallback=true
Get the number of characters in the request body using a website like https://www.charactercountonline.com/ . It's 81 in this example. Its value will be used as Content-Length in the SMS deletion request
Get the request headers for POST requests by adding or deleting a contact in the phone book then clicking the output from the log (in green)
The request to delete these SMSs will then be:

For ZTE

Request

Code:

POST

URL

Code:

http://192.168.0.1/goform/goform_set_cmd_process

Request Headers (You may replace with the one you copied from the POST request earlier and don't forget to replace the Content-Length)

Code:

Accept: application/json, text/javascript, */*; q=0.01 Accept-Encoding: gzip, deflate Accept-Language: en-US,en;q=0.9 Connection: keep-alive Content-Length: 81 Content-Type: application/x-www-form-urlencoded; charset=UTF-8 Cookie: pageForward=home Host: 192.168.0.1 Origin: http://192.168.0.1 Referer: http://192.168.0.1/index.html?t=7338561 User-Agent: Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36 X-Requested-With: XMLHttpRequest

Request Body

Code:

isTest=false&goformId=DELETE_SMS&msg_id=100%3B101%3B102%3B103%3B&notCallback=true

For ZLT

Request

Code:

POST

URL

Code:

http://192.168.0.1/reqproc/proc_post

Request Headers (You may replace with the one you copied from the POST request earlier and don't forget to replace the Content-Length)

Code:

Accept: application/json, text/javascript, */*; q=0.01 Accept-Encoding: gzip, deflate Accept-Language: en-US,en;q=0.9 Connection: keep-alive Content-Length: 81 Content-Type: application/x-www-form-urlencoded; charset=UTF-8 Cookie: pageForward=home Host: 192.168.0.1 Origin: http://192.168.0.1 Referer: http://192.168.0.1/index.html?t=5931805 User-Agent: Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36 X-Requested-With: XMLHttpRequest

Request Body

Code:

isTest=false&goformId=DELETE_SMS&msg_id=100%3B101%3B102%3B103%3B&notCallback=true
Click Send
You should get a 'Success' response and the SMSs with those I.Ds should have been deleted