thanks so much!
I have a BNIB if you want something tested.
say what? a National Background Investigations Bureau?
just that we added support for a couple more bootloader versions, and itd be nice to know if they work.
1 Like
Typo, should have been BNIB 
1 Like
oh, nice! i googled that one and found it. well it's a good device, what are you waiting for?
I'm traveling, won't be able to get it hooked up for another couple of days.
1 Like
It was an open box, not BNIB 
haven't hooked up serial yet, but the status screen says
still interested, and what do you want to do ?
if not, I'll just reflash it.
try my install script/procedure on github
1 Like
will do.
need to disassemble it further.
for now, wiki page is being built https://openwrt.org/toh/spectrum/sax1v1k.
3 Likes
cool! ill contribute when im back home in a few weeks.
1 Like
Thnx.
I'll add the flashing details once I've soldered the serial header.
2 Likes
Done, worked like a charm, thanks !
PS
I noticed there's an empty 4.5GB partition at the end of the eMMC
DS
3 Likes
did the script find any of the untested BL hacks? it would have said so. (if you know which ill remove the untested label from it)
the partition:
i have argued to the team that on large emmc devices (anything above 512MB rootfs overlay imho) the old recommendation to use all space for the overlay is no longer sane.
there are several reasons for that. i am traveling, but when i get back i can look for that and link it.
the TL;DR is that it is better to have most of these large flash memories devoted to extra storage partition that does not participate in sysupgrage and survives flashes.
there is a LuCI app to manage extra mounts btw. and on my routers i usually mount this partition as /extra.
whatever you do, dont modify the GPT as it may be signed as part of secure boot and brick the device.
1 Like
nope, the complete output is posted on the wiki page.
I have no problem with that, just think it should be mentioned in the wiki, as usable, if usable.
that's def going into the wiki.
1 Like
just saw the wiki. it wouldnt have, the script you ran wont tell you that. i thought u had ran my install script.
anyway, my insrall script have several protections for bricking. if you currently sysupgrade to a flawed image you will irrevocably brick. my script has safeguards for that and you probably want to upgrade to it. (links are posted earlier, search for unbrickable.)
1 Like
then no, I was following the git commit, didn't search/read through all the posts in the thread.
since it's possible to execute it post install, I'll do it next time I hook up the SAX.
(ok you dont need serial, you can do it over ssh.)
I mean plug it in, it's sitting on a shelf atm .... 
starting configuration script...
GPT hash: 56e9617a45826e7e6bb4106e6ad40c59
found known GPT!
U-Boot slot 0 hash: ab709449c98f89cfa57e119b0f37b388
U-Boot slot 1 hash: ab709449c98f89cfa57e119b0f37b388
U-Boot hashes for slots 0 and 1 match
found known U-Boot! version: 1.3.3 [spf11.1_csu2] Jan 27 2021 (hash2)
WARNING: about to configure U-Boot environment
enter 'yes' to continue or ctrl+c to stop...
yes
success!
the new boot code has been configured but not activated
the current boot command is:
bootcmd=run fix_uboot; run setup_and_boot
to activate the new code, it needs to be set to:
bootcmd=run boot_stage1
WARNING: about to set 'bootcmd' to activate the new code
enter 'yes' to continue or ctrl+c to stop...
yes
success!
it seems that this device has older boot code configured
the code in these U-Boot variables is no longer needed:
fix_uboot, read_hlos_emmc, set_custom_bootargs, setup_and_boot
WARNING: do you want to delete this variables? (recommended)
enter 'yes' to continue or ctrl+c to stop...
yes
success!
notes:
this script does NOT install main or recovery OSes
you have to do that yourself to complete the installation
if you have serial console access you can type:
- 'ctrl+c' during boot to access the U-Boot shell
- 'run boot_tftp' to boot via TFTP
- 'run boot_write_recovery_from_tftp' to flash the recovery OS
- 'run boot_recovery' to boot the recovery OS now
- 'run boot_queue_recovery' to queue recovery for next boot
in OpenWrt you can flash a recovery image by typing:
- 'dd if=recovery.img of=/dev/mmcblk0p36'
1 Like