DB2010/J300: incorrect phone model / IMEI (firmware bug) #1

Open
opened 2024-04-08 10:59:54 +00:00 by fixeria · 0 comments
Owner

This looks more like a bug in the phone firmware itself:

$ ./sedbgmux-shell.py -p /dev/ttyUSB0 -v
DebugMux ('/dev/ttyUSB0')> connect 
[DEBUG] modem.py:77 MODEM <- b'AT\r'
[DEBUG] modem.py:95 MODEM -> b'OK\r\n'
[DEBUG] modem.py:77 MODEM <- b'AT*EDEBUGMUX\r'
[DEBUG] modem.py:95 MODEM -> b'CONNECT\r\n'

DebugMux ('/dev/ttyUSB0')> enquiry 
[DEBUG] peer.py:114 Tx frame (Ns=001, Nr=000, fcs=0x3e69) Enquiry 
[DEBUG] peer.py:147 Rx frame (Ns=000, Nr=002, fcs=0xbb02) Ident 81270000144a33303020736572696573333536313934303035
[INFO] client.py:185 Identified target: 'J300 ', IMEI=series356194005
[DEBUG] peer.py:114 Tx frame (Ns=241, Nr=001, fcs=0xfd20) Ack 
[DEBUG] peer.py:147 Rx frame (Ns=001, Nr=002, fcs=0xe7cd) DPAnnounce 6b44145072696e7420536572766572204368616e6e656c
[INFO] client.py:191 Data Provider available (DPRef=0x446b): 'Print Server Channel'
[DEBUG] peer.py:114 Tx frame (Ns=241, Nr=002, fcs=0xd748) Ack 
[DEBUG] peer.py:147 Rx frame (Ns=002, Nr=002, fcs=0x8da0) DPAnnounce 6c4403547670
[INFO] client.py:191 Data Provider available (DPRef=0x446c): 'Tvp'
[DEBUG] peer.py:114 Tx frame (Ns=241, Nr=003, fcs=0xce90) Ack 

DebugMux ('/dev/ttyUSB0')> show target-info 
Name: J300 
IMEI: series356194005

We may still attempt to handle this gracefully.

This looks more like a bug in the phone firmware itself: ``` $ ./sedbgmux-shell.py -p /dev/ttyUSB0 -v DebugMux ('/dev/ttyUSB0')> connect [DEBUG] modem.py:77 MODEM <- b'AT\r' [DEBUG] modem.py:95 MODEM -> b'OK\r\n' [DEBUG] modem.py:77 MODEM <- b'AT*EDEBUGMUX\r' [DEBUG] modem.py:95 MODEM -> b'CONNECT\r\n' DebugMux ('/dev/ttyUSB0')> enquiry [DEBUG] peer.py:114 Tx frame (Ns=001, Nr=000, fcs=0x3e69) Enquiry [DEBUG] peer.py:147 Rx frame (Ns=000, Nr=002, fcs=0xbb02) Ident 81270000144a33303020736572696573333536313934303035 [INFO] client.py:185 Identified target: 'J300 ', IMEI=series356194005 [DEBUG] peer.py:114 Tx frame (Ns=241, Nr=001, fcs=0xfd20) Ack [DEBUG] peer.py:147 Rx frame (Ns=001, Nr=002, fcs=0xe7cd) DPAnnounce 6b44145072696e7420536572766572204368616e6e656c [INFO] client.py:191 Data Provider available (DPRef=0x446b): 'Print Server Channel' [DEBUG] peer.py:114 Tx frame (Ns=241, Nr=002, fcs=0xd748) Ack [DEBUG] peer.py:147 Rx frame (Ns=002, Nr=002, fcs=0x8da0) DPAnnounce 6c4403547670 [INFO] client.py:191 Data Provider available (DPRef=0x446c): 'Tvp' [DEBUG] peer.py:114 Tx frame (Ns=241, Nr=003, fcs=0xce90) Ack DebugMux ('/dev/ttyUSB0')> show target-info Name: J300 IMEI: series356194005 ``` We may still attempt to handle this gracefully.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fixeria/sedbgmux#1
No description provided.