Any hope for A series (A40/A60)?

[zeroping]

I notice that we have the source to build a uboot image for the A series devices.
true-systems/openmesh-gpl-u-boot@bfd80b8

Is there any hope for unlocking an A60? It appears to be locked down in the same way, but I wasn't able to get this unlocker to work.

[pepe2k]

Hi @zeroping,

Do you have serial console access to this device? Are you able to provide flash dump?

Cheers,
Piotr

[zeroping]

I have physical access to the serial console, but it doesn't look like that does me much good - the
bootloader won't talk to me!

That said, I have surface-mount soldering equipment, and there's an MX25L12835FMI SPI flash in a nice big 16-SOIC package on the board....

Edit: and yes, it asks for the .sig file over TFTP.

[pepe2k]

Edit: and yes, it asks for the .sig file over TFTP.

Could you make a simple test, feed it with 128 MB size .sig file over TFTP and check how much data is loaded? I'm curious if A40/A60 has this fix: https://source.codeaurora.org/quic/qsdk/oss/boot/u-boot-1.1.4/commit/?h=1.1&id=335640eda6d920fe23534ce1db5d8f05d8b5014c

[zeroping]

First off, just to post more info on the behavior:
uboot being locked, as expected: https://gist.github.com/zeroping/61cd043ab1287f28728f233e372d3450
The console being disabled, as expected: https://gist.github.com/zeroping/cdb6d00b3c9888cd18dbd90f283c057c

And here's my attempt to use this unlocker tool (with the A60 bootloader):
https://gist.github.com/zeroping/47f089391d6c8f7254239247f5aec858

There's some notable differences vs your blog post.

om5p:
Top of RAM usable for U-Boot at: 88000000
Reserving 200k for U-Boot at: 87fcc000
Reserving 192k for malloc() at: 87f9c000
Reserving 44 Bytes for Board Info at: 87f9bfd4
Reserving 36 Bytes for Global Data at: 87f9bfb0
Reserving 128k for boot params() at: 87f7bfb0
Stack Pointer at: 87f7bf98
Now running in RAM - U-Boot at: 87fcc000

A60:
Top of RAM usable for U-Boot at: 88000000
Reserving 237k for U-Boot at: 87fc4000
Reserving 192k for malloc() at: 87f94000
Reserving 44 Bytes for Board Info at: 87f93fd4
Reserving 36 Bytes for Global Data at: 87f93fb0
Reserving 128k for boot params() at: 87f73fb0
Stack Pointer at: 87f73f98
Now running in RAM - U-Boot at: 87fc4000

Does that mean that I'm awfully close, and we just need a little tweaking for changed addresses?

[pepe2k]

Does that mean that I'm awfully close, and we just need a little tweaking for changed addresses?

No, it seems they fixed bootloader and tftp upload is now limited:

TFTP error: Invalid address 0x82100000 with size 512
Retry...

[zeroping]

I hope to get a flash dump as soon as I get the correct JTAG hardware working, hopefully within a week.

[LINZZG]

@zeroping Have you solved the problem about A60 series?

[zeroping]

I've managed to get my A60 messed up to the point that it doesn't make it to the bootloader, and I can't get back into it with JTAG. I'm not 100% sure what I've done, and there's a fair chance it's partly due to my JTAG setup being iffy, but it might be fatal. I had control of the bootloader before everything went sideways, and was working on getting an OpenWRT system image flashed to it.

I've been putting off working on it, but I suspect I'll end up having to de-solder the flash and dump it to figure out what happened. I'm hoping to try some different JTAG hardware first (this weekend perhaps), in case there's any chance of not having to de-solder parts.

[LINZZG]

OK. Hope you find out the reason. Btw, the devices in my hand are A62 router. I thought it may be similar with A60, but actually they're different platforms. And fortunately, I've already got a way to install a custom firmware on A62. Regards, Yongsheng From: Scott G Date: 2018-11-07 11:38 To: true-systems/om5p-ac-v2-unlocker CC: LINZZG; Comment Subject: Re: [true-systems/om5p-ac-v2-unlocker] Any hope for A series (A40/A60)? (#5) I've managed to get my A60 messed up to the point that it doesn't make it to the bootloader, and I can't get back into it with JTAG. I'm not 100% sure what I've done, and there's a fair chance it's partly due to my JTAG setup being iffy, but it might be fatal. I had control of the bootloader before everything went sideways, and was working on getting an OpenWRT system image flashed to it. I've been putting off working on it, but I suspect I'll end up having to de-solder the flash and dump it to figure out what happened. I'm hoping to try some different JTAG hardware first (this weekend perhaps), in case there's any chance of not having to de-solder parts. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[ack100]

I found a way to flash openwrt without unlocking uboot. You have to open the device and short 2 pins on the flash memory chip at the right time. Chip select and data out. On my a60 it's pins 7-8 but check the data sheet for the memory chip to be sure.

I stumbled on the idea here
https://carvesystems.com/news/pin2pwn-how-to-root-an-embedded-linux-box-with-a-sewing-needle/

1. Use the ap51-flash method with openwrt firmware.
2. When the router tries to download fwupgrade.cfg.sig momentarily short the pins and if you get the timing right it will then download the kernel, roofs and write them to flash. Then it will boot up openwrt and will cold boot just fine.

[Choo-lux]

thanks ack100
I have the Datto AP62 and it too has pins 7,8 but shorting did nothing

When you say 'get timing right' will there be any indications over serial?

[njjl]

This should help: https://gitlab.com/pbcom_bobac/altiwi-doc/blob/c51dcf40d2046917bcba31484423d0482b147de6/OM_flash.md

[Choo-lux]

oh thanks again, but I have the Datto version and don't have the option to access the new dashboard and therefore no ssh access

[zeroping]

Just to leave the update here for others: I actually gave up on my A60 after I fried something during a swap of the flash IC.

I eventually found happiness with the Edge-core ECW7210 with swapped-out mini-pcie wireless cards (a QCA9880 and an AR93xx). It has very similar specs to the A60, including the PoE and dual-ethernet, so it works just great as a home NAT router. I think the internal antenna design is nice too. Since it's otherwise abandoned hardware, they are occasionally cheap on eBay.

My work getting it running openwrt (which I need to follow up on...): openwrt/openwrt#2660

[DFF-fred]

HI! Any progress on this? On top of that I don't have the device on Cloudtax as it's been registered by someone else who disappeared. Any clue on what my options are now?
Thank you.

[Y784u]

I found a way to flash openwrt without unlocking uboot. You have to open the device and short 2 pins on the flash memory chip at the right time.

Excellent! Worked fine on an A42:

Eeprom is a Winbond 25Q256JVFQ. Looking at the cli feedback it really is just a matter of shorting Data Out somewhere; it can't send the requests back to the flash tool then. Kept DO shorted while booting and connected to the flash tool. No issues with timing that way.

Bought four of these used and original firmware was official 6.4.7 (or a bit later), flashed official latest 6.5.3 and finally OpenWrt 22.03.5. Desoldered the eeproms and made full dumps of the versions:
Open-Mesh A42 - eeprom dump - Open-Mesh 6.4.7.zip
Open-Mesh A42 - eeprom dump - Open-Mesh 6.5.3.zip
Open-Mesh A42 - eeprom dump - OpenWrt 22.03.5.zip

OpenWrt has stock settings. Only logged in once to verify it was operational and kept root pw blank.

[djowen40]

I found a way to flash openwrt without unlocking uboot. You have to open the device and short 2 pins on the flash memory chip at the right time. Chip select and data out. On my a60 it's pins 7-8 but check the data sheet for the memory chip to be sure.

This worked on my A62.
I did have to fiddle a little to get the timing right as the process did not work with the pin 8 grounded on boot up. Just shorted Pin 8 on the Winbond W25Q256JV Flash IC to ground after seeing the first feedback in serial on the ap51-Flash utility.

[techyporcupine]

Hello! I am trying to do this with an A42 Access Point and have successfully gotten it to say "Flash complete. Device ready to unplug" but when I unplug it and plug it back in, it seems to boot right back into Open-Mesh's software.

How I'm flashing it:
Connect: Computer <> PoE injector <> AP
Start command on computer to flash
Connect: Power to PoE injector
Short DO pin to ground when light goes red
Watch it upload, flash, complete flash
Unplug AP
Plug AP back in
Watch it boot back to Open-Mesh and not OpenWRT

Any help would be appreciated.

[techyporcupine]

Actually, I just got it to work!

How I did it:
Still short the DO pin to ground when the light goes red, but then when the flashing software started to send the fwupgrade file, I let go of the pins and then let it finish and then it started booting OpenWRT