351 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

smereka napisał/a:

Ok I just check it

so it's enough to replace this file in the common folder, right?

yes

Idź do forum: Sprzęt / Hardware

352 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

smereka napisał/a:
stich86 napisał/a:
smereka napisał/a:

After specifying this content in SB3.0,% goes and in the uart console I have the following logs after this whole procedure:

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1-00311
S - IMAGE_VARIANT_STRING=MAATANAZA
S - OEM_IMAGE_VERSION_STRING=scl_xa242_062
S - Boot Interface: NAND
S - Secure Boot: Off
S - Boot Config @ 0x000a602c = 0x000000a1
S - JTAG ID @ 0x000a607c = 0x100320e1
S - OEM ID @ 0x000a6080 = 0x00000000
S - Serial Number @ 0x000a4128 = 0x100caf6f
S - OEM Config Row 0 @ 0x000a4150 = 0x0900000000000000
S - OEM Config Row 1 @ 0x000a4158 = 0x0000000000000000
S - Feature Config Row 0 @ 0x000a4160 = 0x14000000000009a0
S - Feature Config Row 1 @ 0x000a4168 = 0x0342f80200000005
B -      3324 - PBL, Start
B -      6728 - bootable_media_detect_entry, Start
B -      8035 - bootable_media_detect_success, Start
B -      8040 - elf_loader_entry, Start
B -     11449 - auth_hash_seg_entry, Start
B -     11701 - auth_hash_seg_exit, Start
B -     60212 - elf_segs_hash_verify_entry, Start
B -    112810 - PBL, End
B -    123769 - SBL1, Start
B -    215238 - pm_device_init, Start
B -    275384 - PM_SET_VAL:Skip
D -     59109 - pm_device_init, Delta
B -    276574 - usb: usb: hs_phy_nondrive_start
B -    280569 - usb: usb: hs_phy_nondrive_finish
B -    283955 - boot_config_data_table_init, Start
D -         0 - boot_config_data_table_init, Delta - (0 Bytes)
B -    294081 - CDT Version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:0
B -    300791 - sbl1_ddr_set_params, Start
D -        30 - sbl1_ddr_set_params, Delta
B -    308294 - Pre_DDR_clock_init, Start
D -       366 - Pre_DDR_clock_init, Delta
B -    323300 - pm_driver_init, Start
D -      1799 - pm_driver_init, Delta
B -    325160 - clock_init, Start
D -       183 - clock_init, Delta
B -    329827 - boot_flash_init, Start
D -     33001 - boot_flash_init, Delta
B -    370270 - Image Load, Start
D -     39162 - QSEE Image Loaded, Delta - (394044 Bytes)
B -    409462 - QSEE Execution, Start
D -     65941 - QSEE Execution, Delta
D -       213 - boot_pm_post_tz_device_init, Delta
B -    479002 - Image Load, Start
D -     19551 - RPM Image Loaded, Delta - (161732 Bytes)
B -    651358 - ZTE_POWER_ON_NORMAL
B -    703299 - Image Load, Start
D -     38003 - APPSBL Image Loaded, Delta - (426228 Bytes)
B -    741302 - sbl1_efs_handle_cookies, Start
D -         0 - sbl1_efs_handle_cookies, Delta
B -    748653 - SBL1, End
D -    627171 - SBL1, Delta
S - Throughput, 10000 KB/s  (982068 Bytes,  93661 us)
S - DDR Frequency, 518 MHz
S - Core 0 Frequency, 1190 MHz
Android Bootloader - UART_DM Initialized!!!
[0] welcome to lk

[0] SCM call: 0x2000601 failed with :fffffffc
[0] Failed to initialize SCM
[10] platform_init()
[10] target_init()
[10] Waiting for the RPM to populate smd channel table
[10] smem ptable found: ver: 4 len: 17
[20] ERROR: No devinfo partition found
[20] Neither 'config' nor 'frp' partition found
[20] zte_power_on_ctrl no operation
[30] ----fota cookie is [0xffffffff]----
[30] smem_power->efs_crash = 0x0
[30]  zte_crash_flag not  found
[40] Loading (boot) image (8941568): start
[870] Loading (boot) image (8941568): done
[870] Authenticating boot image (8941568): start
[950] Authenticating boot image: done return value = 1
[980] DTB Total entry: 170, DTB version: 3
[990] Using DTB entry 0x0000011b/00010001/0x00000008/0 for device 0x0000011b/00010001/0x00010008/0
[1000] cmdline: noinitrd  rw console=ttyHSL0,115200,n8 androidboot.hardware=qcom ehci-hcd.park=3 msm_rtb.filter=0x37 lpm_levels.sleep_disabled=1  earlycon=msm_hsl_uart,0x78b1000  an                                                        droidboot.serialno=100caf6f androidboot.authorized_kernel=true androidboot.baseba[1020] Updating device tree: start
[1080] Updating device tree: done
[1090] Channel alloc freed
[1100] booting linux @ 0x80008000, ramdisk @ 0x80008000 (0), tags/device tree @ 0x82000000

And so it restarts over and over again. So that it lacks the correct IMEI?

have you used my latest partition_nand.xml on the MEGA folder?



Yes from your folder

i've uploaded new one (with correct recoveryfs partition), please try again and let me know

Idź do forum: Sprzęt / Hardware

353 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

pawol napisał/a:

I understand that modem recovery procedure is validated. Destribe it in details, please

still not, because on all of my attemps I got the MDM login shell (which this module refuse to get input from TX line), but the modem was not in the desired state (3 COMs as generic device and not like the working module, so missing ADB and all RNIS stuff).

I've done an attempt yesterday (flashing ALL without modem firmware) and then restore a XQCN from a working module, this has booted the modem in correct way (3 COMs + ADB shell + RNIS\RNIC)

Try it again tonight to see if I can found the correct way to do all tasks (it's important to restore the XQCN with correct IMEI)

Idź do forum: Sprzęt / Hardware

354 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

smereka napisał/a:

After specifying this content in SB3.0,% goes and in the uart console I have the following logs after this whole procedure:

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1-00311
S - IMAGE_VARIANT_STRING=MAATANAZA
S - OEM_IMAGE_VERSION_STRING=scl_xa242_062
S - Boot Interface: NAND
S - Secure Boot: Off
S - Boot Config @ 0x000a602c = 0x000000a1
S - JTAG ID @ 0x000a607c = 0x100320e1
S - OEM ID @ 0x000a6080 = 0x00000000
S - Serial Number @ 0x000a4128 = 0x100caf6f
S - OEM Config Row 0 @ 0x000a4150 = 0x0900000000000000
S - OEM Config Row 1 @ 0x000a4158 = 0x0000000000000000
S - Feature Config Row 0 @ 0x000a4160 = 0x14000000000009a0
S - Feature Config Row 1 @ 0x000a4168 = 0x0342f80200000005
B -      3324 - PBL, Start
B -      6728 - bootable_media_detect_entry, Start
B -      8035 - bootable_media_detect_success, Start
B -      8040 - elf_loader_entry, Start
B -     11449 - auth_hash_seg_entry, Start
B -     11701 - auth_hash_seg_exit, Start
B -     60212 - elf_segs_hash_verify_entry, Start
B -    112810 - PBL, End
B -    123769 - SBL1, Start
B -    215238 - pm_device_init, Start
B -    275384 - PM_SET_VAL:Skip
D -     59109 - pm_device_init, Delta
B -    276574 - usb: usb: hs_phy_nondrive_start
B -    280569 - usb: usb: hs_phy_nondrive_finish
B -    283955 - boot_config_data_table_init, Start
D -         0 - boot_config_data_table_init, Delta - (0 Bytes)
B -    294081 - CDT Version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:0
B -    300791 - sbl1_ddr_set_params, Start
D -        30 - sbl1_ddr_set_params, Delta
B -    308294 - Pre_DDR_clock_init, Start
D -       366 - Pre_DDR_clock_init, Delta
B -    323300 - pm_driver_init, Start
D -      1799 - pm_driver_init, Delta
B -    325160 - clock_init, Start
D -       183 - clock_init, Delta
B -    329827 - boot_flash_init, Start
D -     33001 - boot_flash_init, Delta
B -    370270 - Image Load, Start
D -     39162 - QSEE Image Loaded, Delta - (394044 Bytes)
B -    409462 - QSEE Execution, Start
D -     65941 - QSEE Execution, Delta
D -       213 - boot_pm_post_tz_device_init, Delta
B -    479002 - Image Load, Start
D -     19551 - RPM Image Loaded, Delta - (161732 Bytes)
B -    651358 - ZTE_POWER_ON_NORMAL
B -    703299 - Image Load, Start
D -     38003 - APPSBL Image Loaded, Delta - (426228 Bytes)
B -    741302 - sbl1_efs_handle_cookies, Start
D -         0 - sbl1_efs_handle_cookies, Delta
B -    748653 - SBL1, End
D -    627171 - SBL1, Delta
S - Throughput, 10000 KB/s  (982068 Bytes,  93661 us)
S - DDR Frequency, 518 MHz
S - Core 0 Frequency, 1190 MHz
Android Bootloader - UART_DM Initialized!!!
[0] welcome to lk

[0] SCM call: 0x2000601 failed with :fffffffc
[0] Failed to initialize SCM
[10] platform_init()
[10] target_init()
[10] Waiting for the RPM to populate smd channel table
[10] smem ptable found: ver: 4 len: 17
[20] ERROR: No devinfo partition found
[20] Neither 'config' nor 'frp' partition found
[20] zte_power_on_ctrl no operation
[30] ----fota cookie is [0xffffffff]----
[30] smem_power->efs_crash = 0x0
[30]  zte_crash_flag not  found
[40] Loading (boot) image (8941568): start
[870] Loading (boot) image (8941568): done
[870] Authenticating boot image (8941568): start
[950] Authenticating boot image: done return value = 1
[980] DTB Total entry: 170, DTB version: 3
[990] Using DTB entry 0x0000011b/00010001/0x00000008/0 for device 0x0000011b/00010001/0x00010008/0
[1000] cmdline: noinitrd  rw console=ttyHSL0,115200,n8 androidboot.hardware=qcom ehci-hcd.park=3 msm_rtb.filter=0x37 lpm_levels.sleep_disabled=1  earlycon=msm_hsl_uart,0x78b1000  an                                                        droidboot.serialno=100caf6f androidboot.authorized_kernel=true androidboot.baseba[1020] Updating device tree: start
[1080] Updating device tree: done
[1090] Channel alloc freed
[1100] booting linux @ 0x80008000, ramdisk @ 0x80008000 (0), tags/device tree @ 0x82000000

And so it restarts over and over again. So that it lacks the correct IMEI?

have you used my latest partition_nand.xml on the MEGA folder?

Idź do forum: Sprzęt / Hardware

355 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

smereka napisał/a:

So write down what you did that finally works. Can you give an instruction?

I need to fix IMEI issue before.. because on the procedure it's important to load an XQCN backup, otherwise you will never bring up the module

I've to broke it again and check if the steps that i've followed can be certified or not (hope to get it back in the same state that I need big_smile)

Idź do forum: Sprzęt / Hardware

356 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

I’ve tried to edit the XQCN file to change IMEI, but looks like it’s not allowed and it stays with the same of the working module where the backup was taken. Also Qualcomm NV Tools denies the write of IMEI because it’s marked as read-only

I’ve to find a way to change it…

EDIT: a little update.. some NV items in the memory are write-protected and IMEI is one of these.. So the only way is to brick/erase EFS and load XQCN/QCN file with the new IMEI. I should hope that brick EFS doens't bring back modem in the wrong way big_smile

Idź do forum: Sprzęt / Hardware

357 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

here we go!

https://i.ibb.co/f2GTk79/Schermata-2022-06-19-alle-19-05-53.png
https://www.speedtest.net/result/13301737528.png

it's working big_smile

Now i've to modify XQCN file to write back it's original IMEI

Idź do forum: Sprzęt / Hardware

358 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

smereka napisał/a:

Once you do all this, please write a detailed instruction on how to get it all. I'll edit the first post and put in what you did. If there will be changes later, we will change it. At the moment, you are the person who pushed the topic forward the farthest smile

Of course! But don’t want claim victory until I see the connection up on the router big_smile

Idź do forum: Sprzęt / Hardware

359 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

Work in progress big_smile

https://i.ibb.co/Bn9GLZW/FB3-B103-D-ADB1-42-CB-932-A-D5995-E66671-D.jpg

This evening I’ll put the module back into router and check if it’s working. Obviously I need to write back original IMEI (now EFS is the one of working modem)

Idź do forum: Sprzęt / Hardware

360 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

So digging on the working module, may be i've found why the bad one is working in this strange way.
All the stuff (QMI, ADB, VID/PID) are launched by script /etc/init.d/misc-daemon, I think the part that is not working is this one:

case "$1" in
  start)
        echo -n "Starting modem dependent daemons: "
                search_dir="/sys/bus/msm_subsys/devices/"
        for entry in `ls $search_dir`
        do

            subsys_temp=`cat $search_dir/$entry/name`
            if [ "$subsys_temp" == "modem" ]
            then
                break
            fi
        done

                sh /etc/rcS-zte-before-modem &

if the script found "modem" too early stop to do other action.. still don't understand why, because the AT command and RF search on the modem works, so it not broken

any suggestion?

Idź do forum: Sprzęt / Hardware

361 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

smereka napisał/a:

In first post you have pinout uart which work i my died modem.U use cp2102 work good

Yea but in that modem RX pin doesn’t respond… I don’t know if the problem was related to my older adapter that has broken the line

Used new adapter that support 1.8v works.. but I don’t know the root password yet smile

Looks like the modem doesn’t run some unit init (so adb and qmi interface are not initialized). I’ve found a python script on edl’s git repos that should enable ADB over AT commands… hope it works

Idź do forum: Sprzęt / Hardware

362 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

I did a try on TTL with 1.8v adapter but without success sad

@smereka @Leo-PL
are you get input read on TTL console of the modem? Just to understand if it's my module broken or it's disabled by kernel\boot

EDIT: bad news.. i've soldered the TTL to the working modem and RX is working, so may be the other module has been fried by 3.3v TTL sad

thx

Idź do forum: Sprzęt / Hardware

363 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

someonethtuknw napisał/a:

Hi everyone! Hope I'm not offtopic. I installed openwrt on a raspberry pi 3b + and connected the modem of the zte mf286d via an adapter.

It is recognized, but I cannot find the qmi interface.

Obviously I installed the packages recommended by openwrt, but nothing.

Solutions?

Thank you very much and I apologize for the translation, I'm Italian smile

Are you the man on FibraClick?

Idź do forum: Sprzęt / Hardware

364 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

some updates. I've played with "partition_nand.xml" for upload all other partitions (modem\system\boot\recovery and so on) directly with SB3.0 so I can skip fastboot and be able to write also efs.mbn into EFS2/EFSBK partitions.

Now the modem seems more "complete", but still missing some parts. Good news:

i've login's prompt on console (so HSL0 is the one on top of the module), but input is not accepted. I'm using 3.3v TTL adapter, i've order one at 1.8v and should get it tomorrow from AMNZ.

Here is the current state of the module:

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1-00311
S - IMAGE_VARIANT_STRING=MAATANAZA
S - OEM_IMAGE_VERSION_STRING=scl_xa242_062
S - Boot Interface: NAND
S - Secure Boot: Off
S - Boot Config @ 0x000a602c = 0x000000a1
S - JTAG ID @ 0x000a607c = 0x100320e1
S - OEM ID @ 0x000a6080 = 0x00000000
S - Serial Number @ 0x000a4128 = 0x19146b45
S - OEM Config Row 0 @ 0x000a4150 = 0x0900000000000000
S - OEM Config Row 1 @ 0x000a4158 = 0x0000000000000000
S - Feature Config Row 0 @ 0x000a4160 = 0x14000000000009a0
S - Feature Config Row 1 @ 0x000a4168 = 0x0342f80200000005
B -      3343 - PBL, Start
B -      6753 - bootable_media_detect_entry, Start
B -      8082 - bootable_media_detect_success, Start
B -      8087 - elf_loader_entry, Start
B -     11496 - auth_hash_seg_entry, Start
B -     11751 - auth_hash_seg_exit, Start
B -     60263 - elf_segs_hash_verify_entry, Start
B -    112860 - PBL, End
B -    127368 - SBL1, Start
B -    221399 - pm_device_init, Start
B -    282064 - PM_SET_VAL:Skip
D -     59566 - pm_device_init, Delta
B -    283223 - usb: usb: hs_phy_nondrive_start
B -    287218 - usb: usb: hs_phy_nondrive_finish
B -    290604 - boot_config_data_table_init, Start
D -         0 - boot_config_data_table_init, Delta - (0 Bytes)
B -    300730 - CDT Version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:0
B -    307440 - sbl1_ddr_set_params, Start
D -        30 - sbl1_ddr_set_params, Delta
B -    314943 - Pre_DDR_clock_init, Start
D -       366 - Pre_DDR_clock_init, Delta
B -    329949 - pm_driver_init, Start
D -      1799 - pm_driver_init, Delta
B -    331809 - clock_init, Start
D -       183 - clock_init, Delta
B -    336476 - boot_flash_init, Start
D -     31323 - boot_flash_init, Delta
B -    445849 - Image Load, Start
D -     39345 - QSEE Image Loaded, Delta - (394044 Bytes)
B -    485224 - QSEE Execution, Start
D -     65941 - QSEE Execution, Delta
D -       213 - boot_pm_post_tz_device_init, Delta
B -    554764 - Image Load, Start
D -     19520 - RPM Image Loaded, Delta - (161732 Bytes)
B -    727089 - ZTE_POWER_ON_NORMAL
B -    779031 - Image Load, Start
D -     37942 - APPSBL Image Loaded, Delta - (426228 Bytes)
B -    817003 - sbl1_efs_handle_cookies, Start
D -         0 - sbl1_efs_handle_cookies, Delta
B -    824354 - SBL1, End
D -    699243 - SBL1, Delta
S - Throughput, 10000 KB/s  (982068 Bytes,  93688 us)
S - DDR Frequency, 518 MHz
S - Core 0 Frequency, 1190 MHz
Android Bootloader - UART_DM Initialized!!!
[0] welcome to lk

[0] SCM call: 0x2000601 failed with :fffffffc
[0] Failed to initialize SCM
[10] platform_init()
[10] target_init()
[10] Waiting for the RPM to populate smd channel table
[10] smem ptable found: ver: 4 len: 17
[20] ERROR: No devinfo partition found
[20] Neither 'config' nor 'frp' partition found
[20] zte_power_on_ctrl no operation
[30] ----fota cookie is [0xffffffff]----
[30] smem_power->efs_crash = 0x0
[30]  zte_crash_flag not  found
[40] Loading (boot) image (8941568): start
[870] Loading (boot) image (8941568): done
[870] Authenticating boot image (8941568): start
[950] Authenticating boot image: done return value = 1
[990] DTB Total entry: 170, DTB version: 3
[990] Using DTB entry 0x0000011b/00010001/0x00000008/0 for device 0x0000011b/00010001/0x00010008/0
[1000] cmdline: noinitrd  rw console=ttyHSL0,115200,n8 androidboot.hardware=qcom ehci-hcd.park=3 msm_rtb.filter=0x37 lpm_levels.sleep_disabled=1  earlycon=msm_hsl_uart,0x78b1000  androidboot.serialno=19146b45 androidboot.authorized_kernel=true androidboot.baseba[1020] Updating device tree: start
[1080] Updating device tree: done
[1090] Channel alloc freed
[1100] booting linux @ 0x80008000, ramdisk @ 0x80008000 (0), tags/device tree @ 0x82000000
[   23.675937] console [ttyHSL0] enabled
[   23.691308] msm_serial_hsl_init: driver initialized
[   23.699841] cnss_pinctrl_init: Can not get active pin state!
[   23.720176] cnss_probe: Failed to enable PCIe RC0!

msm 201911020732 mdm9650 /dev/ttyHSL0

mdm9650 login:

On the AT COM, to ATI command now reports better information:

ati
Manufacturer: ZTE CORPORATION
Model: MF286DMODULE
Revision: BD_TELIAMF286DV1.0.0B02
SVN: 01
IMEI: 86xxxxxxxxxxxxxxxxxxx
+GCAP: +CGSM,+DS

In the mega folder you will found the new partition_nand.xml that can be used to upload whole stuff. A note.. if your modem is stick with just one port (ZTE Diagnostic), here is the procedure to put it in 9008 and write with SB3.0:

X = your port COM number

qdload.exe -k12 -q  -pX
qcommand.exe -pX -c "m 193d100 1"
qcommand.exe -pX -c "d 7980000 4" <-- stop this one when the modem switch to 9008 device, usally just two printed outputs

If you have a semi-worked modem like me, to enter EDL mode (and run the above commands) just send this one, try twice if on the first attempt doesn't work:

X = your ZTE Diagnostic port number

qcommand.exe -pX -e -c "c 3a"

Idź do forum: Sprzęt / Hardware

365 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

arekx napisał/a:

About IMEI

"Ok so changing the IMEI on basically any Qualcomm device is just a matter of modifying index 550 in the NVRam? Fantastic"

https://twitter.com/mjg59/status/1537631895403450368

Yea with Qualcomm NV tools or Revskills, using DIAG interface you can easily change IMEI smile

Idź do forum: Sprzęt / Hardware

366 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

so I've investigated a little bit on the working modem (i'll solder the TTL in the next days). I think the device cannot boot into the UBIFS and start from recovery-fs which doesn't have all the ZTE stuff

Now the problem may be can be the flash procedure of system, because this modem use UBI as container for all partition

Idź do forum: Sprzęt / Hardware

367 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

what do you think if we create a Discord channel to discuss each other?
I think we can share ideas and have a better communcation, then we can share useful information on the forum

Let me know smile

Idź do forum: Sprzęt / Hardware

368 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

ok i've taken a look to the working modem.. and there is a big world behind.

As expected adb server is started by the system, and then there are other zte_* services that emulate the device correctly.

So I think at the moment my modem is booting like a normal Qualcomm device without any personalization. I need to understand which partition is missing, because everything is overlayed by UBIFS and not real partition.

If we can make QLIF working, when can dump the whole modem and write back on the briked one, like one user has done on the MF286A module..

But QLIF needs a lot of information and i'm not sure that we have firehourse to write on that card

If you find the UART1 let me know, with that console we can see what's going on the OS side

Idź do forum: Sprzęt / Hardware

369 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

Leo-PL napisał/a:

@stich86, see the udev rules above.

I guess I'll have to try with a fresh VM once again - big thanks for the compilation of the tools. And I'll have to look at the testpoints for a different console output with a o'scope - glad I have one on my desk :-D

let me know if you found something smile

Idź do forum: Sprzęt / Hardware

370 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

Leo-PL napisał/a:

I wonder if you could put it back in the router, with stock router firmware, and then run the ZTE update framework thing to reflash it again from scratch. Such bundle is in that MEGA folder, for example "zte mf286d Nordic to Nordic_B11 192.168.32.1 pw admin.rar".


i've already tried, but the framework doesn't see the router..

Idź do forum: Sprzęt / Hardware

371 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

in meantime... i've attached the modem to a Linux VM, but I see only ttyUSB0, 1 (that is the AT port) and 2. Using ADB doesn't display anything..

i think that all "ZTE" proprietary stuff is lost, so the modem startup as simple one. I'll try to connect this evening the working module on the Linux VM to understand how is working

Idź do forum: Sprzęt / Hardware

372 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

ok i've uploaded some stuff on my MEGA share:

https://mega.nz/folder/K8pVmSzR#TOjtD75bk654lmhjajHwzA

- 9008 Drivers: Qualcomm Drivers when modem is in "Download Mode" with E-Bootloader loaded
- SB3.0 recover folder: contains the files that i've uploaded on my modem and "common.xml" file modified, please open readme.txt file for more information
- Win Drivers (Normal Mode): this pack was taken from ZTE MF283 recovery utility, it will install all drivers when the modem is booting in is mini Android. There is a small program that will install drivers if the device is correctly detected
- Tools: i've uploaded program used at this time: QPST (v.2.7.496 for SB3.0 reprog), EFS_Professional (where you can change IMEI\MEID\ESN and other parameters using Qualcomm NV Tools and "ZTE Diagnostic Port", MF286D_qtools-2022-03-1-win.7z that cointains also the modded MF286D loader. This was used to going out from EDL and put in Download mode to flash with "Software Download", Revskills that i'm using to send modem in DOWNLOAD MODE

Note that when you write with "SB3.0", the modem should boot directly into fastboot mode, so you have to rewrite all stuff with it.

Idź do forum: Sprzęt / Hardware

373 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

smereka napisał/a:

zte diagnostic interace in windows I only see. On mf286d i can't check because he work as ap client in my parents wink I and I can say he do it very well

so you don't see NUMA and Proprietary USB? or may be other "Unknown" devices

Idź do forum: Sprzęt / Hardware

374 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

smereka napisał/a:

Three device where on widonws or linux? Or in oryginal router mf286d?

on all of them..

Idź do forum: Sprzęt / Hardware

375 Odpowiedź przez stich86

(890 odpowiedzi, napisanych Sprzęt / Hardware)

smereka napisał/a:

For me, about 2-3 months ago, I managed to enter the fastboot mode and gave him 2 files, now he has such a loop over and over again and unfortunately SB3.0 does not work. That's why I asked for your files and contenet and the mayby will work smile

your boot log seems like mine.. so you don't see the three USB after some seconds?

Idź do forum: Sprzęt / Hardware