Sophos APX 120 bricked ?!

Hello Comm'

i got two bricked Sophos APX 120 access points.
The Sophos Flash Tool can not help me at my problem:
https://support.sophos.com/support/s/article/KB-000039314?language=en_US

I plugged in an UART-cable to check what the problem is.
I can not stop at the point "Hit any key to stop autoboot: 0" for a TFTP-boot.

Is there any possibility to reflash / unbrick the access points or are the APs totally dead ?

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.1-00120
S - IMAGE_VARIANT_STRING=DAABANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x00000020
S - Reset status Config, 0x00000010
S - Core 0 Frequency, 0 MHz
B -       261 - PBL, Start
B -      1338 - bootable_media_detect_entry, Start
B -      1677 - bootable_media_detect_success, Start
B -      1691 - elf_loader_entry, Start
B -      5068 - auth_hash_seg_entry, Start
B -      7210 - auth_hash_seg_exit, Start
B -    577087 - elf_segs_hash_verify_entry, Start
B -    694249 - PBL, End
B -    694273 - SBL1, Start
B -    785279 - pm_device_init, Start
D -         7 - pm_device_init, Delta
B -    786725 - boot_flash_init, Start
D -     52831 - boot_flash_init, Delta
B -    843802 - boot_config_data_table_init, Start
D -      3833 - boot_config_data_table_init, Delta - (419 Bytes)
B -    851006 - clock_init, Start
D -      7586 - clock_init, Delta
B -    863064 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:1,Subtype:0
B -    866477 - sbl1_ddr_set_params, Start
B -    871573 - cpr_init, Start
D -         2 - cpr_init, Delta
B -    875955 - Pre_DDR_clock_init, Start
D -         4 - Pre_DDR_clock_init, Delta
D -     13175 - sbl1_ddr_set_params, Delta
B -    889693 - pm_driver_init, Start
D -         2 - pm_driver_init, Delta
B -    959596 - sbl1_wait_for_ddr_training, Start
D -        27 - sbl1_wait_for_ddr_training, Delta
B -    975198 - Image Load, Start
D -    152195 - QSEE Image Loaded, Delta - (297752 Bytes)
B -   1127822 - Image Load, Start
D -      1445 - SEC Image Loaded, Delta - (2048 Bytes)
B -   1138225 - Image Load, Start
D -    223896 - APPSBL Image Loaded, Delta - (458523 Bytes)
B -   1362518 - QSEE Execution, Start
D -        60 - QSEE Execution, Delta
B -   1368739 - SBL1, End
D -    676574 - SBL1, Delta
S - Flash Throughput, 2010 KB/s  (758742 Bytes,  377342 us)
S - DDR Frequency, 537 MHz


U-Boot 2012.07 [Chaos Calmer unknown,unknown] (Nov 02 2018 - 08:13:09)

smem ram ptable found: ver: 1 len: 3
DRAM:  256 MiB
@machid : 0x8010100
NAND:  spi_nand: spi_nand_flash_probe SF NAND ID 0:ef:ab:21
SF: Detected W25M02GV with page size 2 KiB, total 256 MiB
SF: Detected MX25L1605D with page size 4 KiB, total 2 MiB
ipq_spi: page_size: 0x100, sector_size: 0x1000, size: 0x200000
258 MiB
MMC:
In:    serial
Out:   serial
Err:   serial
machid: 8010100
flash_type: 0
Hit any key to stop autoboot:  0
Creating 1 MTD partitions on "nand1":
0x000000000000-0x000010000000 : "mtd=0"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd2
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
Error, no UBI device/partition selected!
Creating 1 MTD partitions on "nand1":
0x000000000000-0x000010000000 : "mtd=0"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd2
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
Error, no UBI device/partition selected!
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Creating 1 MTD partitions on "nand1":
0x000000000000-0x000010000000 : "mtd=0"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd2
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
Error, no UBI device/partition selected!
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...

Hardware-Picture:
https://h0schi.cloud/apps/files_sharing/publicpreview/pQHigQyPsDSw2CD?x=2548&y=947&a=true&file=21-06-30%2021-52-47%205106.jpg&scalingup=0

Tried keeping any physical button pressed, to force a TFTP boot?

1 Like

Yes, already tried.
I see that the AP recognized the press of the Reset-button (during COM-connection), but the boot will not stop.

Hi,

are you shure that you connected both (RX and TX) correctly? Because if the device only sends you the boot output it would not listen to your inputs at all if Rx on the device is not correctly connected.

I have also a bricked APX 120 lying around, but I didn't do anything yet with it because of too few spare time....
Could you send some pictures of your cabling though?

Cheers

1 Like

Hi, @att12

here a pic of the cabling:
https://h0schi.cloud/s/kYiatLmJb32gZ2B/preview

I tried some combination, but these combination is working and i have a screen output via putty.

Should i try another UART-adapter ?

If you have a different one, you could try that. sometimes it helps. I remember my Aruba AP was also very picky about the Converter.

BTW: Is it a 5 V Converter? You should use a 3.3V one, maybe its already "fried" if you bombard it with 5V

Cheers

att12

1 Like

Do you have a prefered UART-Adapter ?
Can you send me a link ?

https://www.amazon.com/dp/B07WX2DSVB

Works very well.

1 Like

I received the new UART-adapter but it's not working - it seems likte that the counter-value of "press any key" is 0 :frowning:
Maybe a RJ45 to Serial-cable can help here ?

I have no clue anymore.

Try pressing any key before you actually see the counter, proactively, one might say.

What does the physical format of the cable have to do with the 0 sec timeout?
Get a new mouse mat, it's just as relevant ,)

1 Like

That exactly what i do :smiley:

I click on the Putty-windows and press any keys on my keyboard, all the time - i tried it about 15 minutes.

Are you from germany, @frollic ?