51 Odpowiedź przez MiG25

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

T2 should be cheaper since ipq4019 has onlu MIMO 2x2 and wide band 80MHz ,vs QCA9984 MIMO 4x4 and 160MHz....

52 Odpowiedź przez stich86

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

ok adding into DTS the wifi1 (and leaving @wifi2 as pci-E), the 5Ghz on T2 rev is recognized (also without custom board-2), because is using same board-ID (20/21) of MF286D

5Ghz Wi-Fi speed on T2 rev are very bad compared to T1 :\

53 Odpowiedź przez stich86

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

another funny thing:

T2 rev modem, is exposed with a different PID\VID from T1 rev.

T1 has same as MF286D, while T2 same as MF286\286A

54 Odpowiedź przez Leo-PL

  • Leo-PL
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2019-11-05
  • Posty: 502

Odp: ZTE MF289F - Porting OpenWRT

stich86 napisał/a:
Leo-PL napisał/a:

Maybe defining two variants is needed then, or just defining . Either way, congratulations!
A nitpick:

spi-nand@0 {

spi-nand@1 {

the nand is the same, only difference is the 5Ghz radio.
VFDE doesn't have it, while VFID has it, very vary strange

EDIT: may be I’ve misunderstood your message.
You suggest to use @1 because is an index Also if the name of the object is different?

SPI-NAND is at CS1, not CS0, so "1" is the bus address for SPI.

55 Odpowiedź przez MiG25

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

@stich86 , ddo you have working compilations ?
I got MF289F T2 version from vodafone germany , so during weekend i could do some tests...

56 Odpowiedź przez stich86 (edytowany przez stich86 2022-08-05 09:24:54)

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:

@stich86 , ddo you have working compilations ?
I got MF289F T2 version from vodafone germany , so during weekend i could do some tests...

Hi MiG25,

yes i've a working build that you can find on my MEGA folder:
https://mega.nz/folder/v4ZiBQxJ#5trHUVXNsZgS6mmuSxf7sw

the build contains also the 4IceG package (3ginfo-lite, modemband, sms-tool)

some caveats:

- because the module of T2 revision present it with different VID\PID, you have to copy the script into path /usr/share/3ginfo-lite/3ginfo-addon/ 19d21485 (one used by MF286D module) over 19d21432 (one used by MF286\286A)
- all tools form 4IceG need to be reconfigured on ttyUSB1 or 2, default they point to USB0 that is the DIAG port, so on first boot it's necessary to make this change otherwise they don't work
- don't flag "Restart WAN\Modem" on the modemband plugin, looks like the modem doesn't like the restart and it change the band dynamically without any disconnection\reconnection

Let me know smile

57 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,050

Odp: ZTE MF289F - Porting OpenWRT

@stich86 could you show me output of cat /sys/kernel/debug/usb/devices from T1 and T2?

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

58 Odpowiedź przez stich86 (edytowany przez stich86 2022-08-05 09:32:56)

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

Cezary napisał/a:

@stich86 could you show me output of cat /sys/kernel/debug/usb/devices from T1 and T2?

yes, see below:

AT1

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 5.10
S:  Manufacturer=Linux 5.10.131 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.0.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 5.10
S:  Manufacturer=Linux 5.10.131 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.0.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=5000 MxCh= 0
D:  Ver= 3.20 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
P:  Vendor=19d2 ProdID=1485 Rev=58.11
S:  Manufacturer=ZTE,Incorporated
S:  Product=ZTE Mobile Broadband
S:  SerialNumber=P685M135MZTED000000
C:* #Ifs= 7 Cfg#= 1 Atr=80 MxPwr=896mA
A:  FirstIf#= 0 IfCount= 2 Cls=e0(wlcon) Sub=01 Prot=03
I:* If#= 0 Alt= 0 #EPs= 1 Cls=e0(wlcon) Sub=01 Prot=03 Driver=(none)
E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=83(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=85(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=84(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=87(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=86(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
E:  Ad=88(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
E:  Ad=8e(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=0f(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 6 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
E:  Ad=05(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=89(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms

T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 5.10
S:  Manufacturer=Linux 5.10.131 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.1.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 0
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 5.10
S:  Manufacturer=Linux 5.10.131 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.1.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=(none)
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

AT2

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 5.10
S:  Manufacturer=Linux 5.10.131 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.0.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 5.10
S:  Manufacturer=Linux 5.10.131 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.0.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=5000 MxCh= 0
D:  Ver= 3.20 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
P:  Vendor=19d2 ProdID=1432 Rev=58.11
S:  Manufacturer=ZTE,Incorporated
S:  Product=ZTE Mobile Broadband
S:  SerialNumber=P685M135MZTED000000
C:* #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=896mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=83(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=85(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=84(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
E:  Ad=86(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
E:  Ad=8e(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=0f(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
E:  Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=87(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms

T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 5.10
S:  Manufacturer=Linux 5.10.131 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.1.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 0
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 5.10
S:  Manufacturer=Linux 5.10.131 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=xhci-hcd.1.auto
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=(none)
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

Do you know how to remove gpio-restart? Looks like that sometime it's triggerd, and is also triggered if you reboot the modem module.

Thx

59 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,050

Odp: ZTE MF289F - Porting OpenWRT

Remove from dts? https://github.com/openwrt/openwrt/blob … 6d.dts#L29

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

60 Odpowiedź przez MiG25

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

This feature was added in MF286D ,since on ofw  when you type reboot modem is not rebooting ( only mf286d it self) , but it working ok there.
Maybe it is triggering wrong gpio ?

61 Odpowiedź przez stich86

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:

This feature was added in MF286D ,since on ofw  when you type reboot modem is not rebooting ( only mf286d it self) , but it working ok there.
Maybe it is triggering wrong gpio ?

yes on MF286D rebooting the modem doens't take down the board router

i'll take look to the original DTS to see the mapping

62 Odpowiedź przez MiG25

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

And what about adding microusb ? from list there are identical no of usb ports...

63 Odpowiedź przez stich86

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:

And what about adding microusb ? from list there are identical no of usb ports...

i've to buy micro-USB smd connector. There is a pad near the nanoSIM\reset button that should

64 Odpowiedź przez MiG25 (edytowany przez MiG25 2022-08-05 12:09:37)

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

Ok , i'll test it , have one of them.

EDIT I got it , and it have:
Software Version CR_VDFDEMF289FV1.0.0B04
Hardware Version Ver.A(T1)

Exacly how this is wrote ,even that on the label it is written HW Version:T2...

ZTE is very consistent in their inconsistency ( same with MF286 ,MF286A ....)

Result of ATI:

Manufacturer: ZTE CORPORATION
Model: MF289F
Revision: BD_VDFDEMF289FMODV1.0.0B07
SVN: 04

And placed inside MF286D it represents like this:

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=5000 MxCh= 0
D:  Ver= 3.20 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
P:  Vendor=19d2 ProdID=1432 Rev=58.11
S:  Manufacturer=ZTE,Incorporated
S:  Product=ZTE Mobile Broadband
S:  SerialNumber=P685M135MZTED000000
C:* #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=896mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=83(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=85(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=84(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
E:  Ad=86(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
E:  Ad=8e(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=0f(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
E:  Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=87(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms

It only turn on power diode and 3G/4G , no signal bar ,
And it agregtes 4 bands:

+ZCAINFO: 262, 20, 59100, 6350, 10.0;          367, 2, 1, 225, 15.0;          100, 1, 3, 1599, 10.0;          118, 2, 7, 3175, 15.0;

65 Odpowiedź przez stich86

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:

Ok , i'll test it , have one of them.

EDIT I got it , and it have:
Software Version CR_VDFDEMF289FV1.0.0B04
Hardware Version Ver.A(T1)

Exacly how this is wrote ,even that on the label it is written HW Version:T2...

ZTE is very consistent in their inconsistency ( same with MF286 ,MF286A ....)

Result of ATI:

Manufacturer: ZTE CORPORATION
Model: MF289F
Revision: BD_VDFDEMF289FMODV1.0.0B07
SVN: 04

And placed inside MF286D it represents like this:

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=5000 MxCh= 0
D:  Ver= 3.20 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
P:  Vendor=19d2 ProdID=1432 Rev=58.11
S:  Manufacturer=ZTE,Incorporated
S:  Product=ZTE Mobile Broadband
S:  SerialNumber=P685M135MZTED000000
C:* #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=896mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=83(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=85(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=84(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
E:  Ad=86(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
E:  Ad=8e(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=0f(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
E:  Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=87(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms

It only turn on power diode and 3G/4G , no signal bar ,
And it agregtes 4 bands:

+ZCAINFO: 262, 20, 59100, 6350, 10.0;          367, 2, 1, 225, 15.0;          100, 1, 3, 1599, 10.0;          118, 2, 7, 3175, 15.0;

to confirm if it's T1 check if you have 3rd chip on the board or into "dmesg" of original firmware if it loads QCA9984

66 Odpowiedź przez MiG25

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

Do you know under with shild it should be ? : https://fccid.io/SRQ-MF289F/Internal-Ph … 333543.pdf

I have another not expected problem , tried to use prepaid card Plush , and it can't connect.. In WEB this swith is always on OFF , and when i try to turn it on it said connection failed..... Have two of these cards and each of them works on MF286D ,and other routers , but not on MF289F... Another cards works fine and connects ( also Aero2 with use the same PLUS BTS...)

67 Odpowiedź przez MiG25

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

How to made a buckup of all mtd without usb ?

68 Odpowiedź przez stich86 (edytowany przez stich86 2022-08-05 20:15:11)

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:

How to made a buckup of all mtd without usb ?

Create a simple http server on your pc where router is connected and put the busybox_armv7l into the root (you can download from this link)

https://busybox.net/downloads/binaries/1.21.1/

Then on the router via serial console use cURL to download that binary and make it executable with “chmod +x”

After that you can use ./busybox_armv7l nc to run netcat client and send as STDIN all mtd to your pc using nc as server (in listening mode)

Let me know if you have understood smile

69 Odpowiedź przez stich86

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:

Do you know under with shild it should be ? : https://fccid.io/SRQ-MF289F/Internal-Ph … 333543.pdf

I have another not expected problem , tried to use prepaid card Plush , and it can't connect.. In WEB this swith is always on OFF , and when i try to turn it on it said connection failed..... Have two of these cards and each of them works on MF286D ,and other routers , but not on MF289F... Another cards works fine and connects ( also Aero2 with use the same PLUS BTS...)

May be APN is not configured…
You should use AT or QMI to force it, I had same problem with mine sad

70 Odpowiedź przez MiG25 (edytowany przez MiG25 2022-08-05 21:59:16)

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

I upladed your compilation to nand ,and had the same problem ,APNs was:

AT+CGDCONT?

+CGDCONT: 1,"IP","internet","0.0.0.0",0,0,0,0

+CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

+CGDCONT: 3,"IPV4V6","sos","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1

+CGDCONT: 6,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

I removed all leving only first , reboot and works... strange.

Anyway , i have T2 acc what you wrote ( nothing in log about QCA9984 , modem present as Vendor=19d2 ProdID=1432 )
So info in WEB about Hardware version was wrong...

EDIT: And in on OFW from VFDE there is no Bridge Mode... Is there in VFIT ?

71 Odpowiedź przez MiG25

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

stich86 napisał/a:

Create a simple http server on your pc where router is connected and put the busybox_armv7l into the root (you can download from this link)

https://busybox.net/downloads/binaries/1.21.1/

Then on the router via serial console use cURL to download that binary and make it executable with “chmod +x”

After that you can use ./busybox_armv7l nc to run netcat client and send as STDIN all mtd to your pc using nc as server (in listening mode)

Let me know if you have understood smile

I just make backup of 19 mtd's running on initramfs , looks ok ,hopfully it will be possible to restore mtd17 smile

on owf i tried wget , and i belive also curl , and booth commands where not availble....

72 Odpowiedź przez stich86 (edytowany przez stich86 2022-08-05 22:17:44)

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:
stich86 napisał/a:

Create a simple http server on your pc where router is connected and put the busybox_armv7l into the root (you can download from this link)

https://busybox.net/downloads/binaries/1.21.1/

Then on the router via serial console use cURL to download that binary and make it executable with “chmod +x”

After that you can use ./busybox_armv7l nc to run netcat client and send as STDIN all mtd to your pc using nc as server (in listening mode)

Let me know if you have understood smile

I just make backup of 19 mtd's running on initramfs , looks ok ,hopfully it will be possible to restore mtd17 smile

on owf i tried wget , and i belive also curl , and booth commands where not availble....

You should restore mtd16 for web and mtd17 for root_uimage_s (the commands are presen on uBoot, make sure to do nand erase from root_uImage otherwise ubi stuff fails in first attempt

cURL is present on both firmware. I’ve done a backup for both VFIT and VFDE variant using that method wink

73 Odpowiedź przez MiG25

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

mtd16 should not be touched by openwrt , only mtd17 should be enough ( on mf286d restoring mtd9 only works).

74 Odpowiedź przez stich86 (edytowany przez stich86 2022-08-05 22:29:56)

  • Zarejestrowany: 2022-05-24
  • Posty: 392

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:

mtd16 should not be touched by openwrt , only mtd17 should be enough ( on mf286d restoring mtd9 only works).

I had to restore also 16, otherwise I get error when trying to access web interface of OFW.

Funny thing: VFIT use the module as VoIP (not
voice over LTE), but the module itself cannot access internet so any configuration doesn’t work big_smile

It’s possible to switch voice changing an nvram value in the module thru ADB.
I see that module has a br-lan and usb0 interface, but in router just wwan (that should be a bridge created by QMI) is exposed.

do you know if it’s possible to give access to the modem thru router bridge?

I was able to enable VoLTE wringing back mcfg_sw.mbn with EfsTools.

All stuff are inside /firmware of the module, there are a lot of configuration for various telco provider

75 Odpowiedź przez MiG25 (edytowany przez MiG25 2022-08-06 07:51:35)

  • MiG25
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-23
  • Posty: 3,799

Odp: ZTE MF289F - Porting OpenWRT

stich86 napisał/a:

I had to restore also 16, otherwise I get error when trying to access web interface of OFW.

In previous post you wrote to " nand erase from root_uImage " , if you did that ,then not suprising ,since root_uImage = web + root_uImage_s .....
you should do nand erase from root_uImage_s only ,and then restore only mtd17...

EDIT: I had general problem with go back to ofw.... I tried to flash mtd17 3 times ,and all the time i had UBI error on boot. So then i erased whole root_uImage , and flash mtd 17 and mtd16 , and again UBI error.  Finally i restore again only mtd17 and went ok this time... Not sure what went wrong....