Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 28 subscribers
  • Views 4830 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Access Point APX120 Firmware / Recover

vlee

Access point stuck in boot loop. LED stays solid RED from boot. XG Firewall cant see it in the pending list. Tried to reset, didnt work. How can i recover it?

Tried to reset from Serial Port but U-Boot is not responding to any key to stop autoboot "Hit any key to stop autoboot:  0". Because of that I cant run uboot command.

How do i stop autoboot?

Thanks so much.

Firewall: Sophos XG Firewall Home Edition (Latest)

Access Point: APX 120

License: No license

Log from Serial Port:

[00]
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, 0x00000021
S - Reset status Config, 0x00000000
S - Core 0 Frequency, 0 MHz
B -       261 - PBL, Start
B -      1338 - bootable_media_detect_entry, Start
B -      1678 - bootable_media_detect_success, Start
B -      1691 - elf_loader_entry, Start
B -      5068 - auth_hash_seg_entry, Start
B -      7209 - auth_hash_seg_exit, Start
B -    577087 - elf_segs_hash_verify_entry, Start
B -    694221 - PBL, End
B -    694245 - SBL1, Start
B -    785250 - pm_device_init, Start
D -         7 - pm_device_init, Delta
B -    786695 - boot_flash_init, Start
D -     52830 - boot_flash_init, Delta
B -    843665 - boot_config_data_table_init, Start
D -      3831 - boot_config_data_table_init, Delta - (419 Bytes)
B -    850863 - clock_init, Start
D -      7570 - clock_init, Delta
B -    862907 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:1,Subtype:0
B -    866321 - sbl1_ddr_set_params, Start
B -    871419 - cpr_init, Start
D -         2 - cpr_init, Delta
B -    875801 - Pre_DDR_clock_init, Start
D -         4 - Pre_DDR_clock_init, Delta
D -     13175 - sbl1_ddr_set_params, Delta
B -    889540 - pm_driver_init, Start
D -         2 - pm_driver_init, Delta
B -    959698 - sbl1_wait_for_ddr_training, Start
D -        27 - sbl1_wait_for_ddr_training, Delta
B -    975316 - Image Load, Start
D -    152333 - QSEE Image Loaded, Delta - (297752 Bytes)
B -   1128076 - Image Load, Start
D -      1446 - SEC Image Loaded, Delta - (2048 Bytes)
B -   1138496 - Image Load, Start
D -    224138 - APPSBL Image Loaded, Delta - (458523 Bytes)
B -   1363032 - QSEE Execution, Start
D -        60 - QSEE Execution, Delta
B -   1369252 - SBL1, End
D -    677115 - SBL1, Delta
S - Flash Throughput, 2008 KB/s  (758742 Bytes,  377712 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 ...



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi ,

    Thank you for reaching out to Sophos Community.

    Check out the article below to recover bricked APs using a flash tool.

    support.sophos.com/.../KB-000039314

  • 0 in reply to FormerMember

    Thanks for your reply. I tried the link. I had no luck. The flash tool can't connect to access point.

  • FormerMember
    0 FormerMember in reply to vlee

    Hi ,

    Did you select the correct network interface to which you’ve connected the access point? 

    These are the possible reasons why an access point can't connect to the flash tool:

    • If the tool isn’t displaying your access point, either the access point isn’t bricked, or the wrong network interface was chosen.
    • In some APs, if the Device Type is missing, the AP would try to look for the ".uimage" file without the model name to the Flash Tool. The workaround is to open that specific access point model firmware file using "notepad++" and save the file as ".uimage" with the file filter "*.*" in the "Firmware" folder.

    Thanks,

Reply
  • FormerMember
    0 FormerMember in reply to vlee

    Hi ,

    Did you select the correct network interface to which you’ve connected the access point? 

    These are the possible reasons why an access point can't connect to the flash tool:

    • If the tool isn’t displaying your access point, either the access point isn’t bricked, or the wrong network interface was chosen.
    • In some APs, if the Device Type is missing, the AP would try to look for the ".uimage" file without the model name to the Flash Tool. The workaround is to open that specific access point model firmware file using "notepad++" and save the file as ".uimage" with the file filter "*.*" in the "Firmware" folder.

    Thanks,

Children
  • 0 in reply to FormerMember

    Hi Harsh,

    Thanks for your help. I selected the correct network interface. I tried as you said by renaming "uimage" in the Firmware folder. Still Flash tool cant connect to AP. Can you check my log i posted from serial port? To me it looks like AP was not able to load even kernel, where flash tool could be used to unbrick it. Its in boot loop, I cant even go to U-Boot shell or console to run any command. It says "Hit any key to stop autoboot:  0 " but the boot is not interrupted by any key i press.