GrogBuild Grogbuild 6.4 update?

I initialized my one, just like you told me and it worked 100%. Do I need to do anything to it after it initializes?
Nope once it's completed initialising you should be good to go.
That doesn't mean the box can access it for storage of temp files which it needs to do during flashing.
Asda do cheap SanDisk usbs about eight quid, probably better getting one and it'll flash first time
 
This one worked fine for the GrogBuild install and upgrades, ah well. I reinitialized and retried and this time I got:
Connecting to www.openvix.co.uk|176.31.181.161|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 121746534 (116M) [application/zip]
Saving to: ‘latestvix.zip’

latestvix.zip 99%[==================> ] 116.01M 298KB/s in 56s


Cannot write to ‘latestvix.zip’ (Function not implemented).
I have no easy access so I will have to buy another recommended one online.
 
This one worked fine for the GrogBuild install and upgrades, ah well. I reinitialized and retried and this time I got:

I have no easy access so I will have to buy another recommended one online.
Did you run the command line posted by Willo?
Not sure it's supposed to download a zip file
 
It downloads the latest vix zipped file on HDD then flashes the image.

To the OP have you tried flashing latest vix image then run willobuild?
 
Ok, I have learned that the USN needs to be formatted to fat32, not sure if the openvix interface does that so I tried via a windows machine. The result is still:

--2023-07-24 22:46:21-- https://www.openvix.co.uk/openvix-builds/formuler1/openvix-6.4.002.release-formuler1_usb.zip
Resolving www.openvix.co.uk... 176.31.181.161
Connecting to www.openvix.co.uk|176.31.181.161|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 121746534 (116M) [application/zip]
Saving to: ‘latestvix.zip’

latestvix.zip 99%[==================> ] 115.93M 340KB/s in 56s


Cannot write to ‘latestvix.zip’ (Function not implemented).
 
Ok, I have learned that the USN needs to be formatted to fat32, not sure if the openvix interface does that so I tried via a windows machine. The result is still:
Once you've formatted it to FAT32, you have to put it in your box and initialise it.
It won't work if still FAT32
 
Why not just try the old usb method of installing either openatv 7.3or openvix6.4 rather than putty , just to get a working image on as a starting point.
 
Thanks for advice. I was going with the custom build as of like it offset friendly got the habit and I'm not a huge fan of all of the setup needed, well it's more the know how needed to do the setup....
 
Thanks for advice. I was going with the custom build as of like it offset friendly got the habit and I'm not a huge fan of all of the setup needed, well it's more the know how needed to do the setup....
What image is on the box now?
Press menu, information, about
What image name and version number is showing?

You can flash it using the remote
 
Once you've formatted it to FAT32, you have to put it in your box and initialise it.
It won't work if still FAT32
I initialised via the openvx interface and did another WilloBuild install via putty, this time it got this far:

Saving to: ‘latestvix.zip’

latestvix.zip 100%[===================>] 116.11M 3.29MB/s in 32s

2023-07-26 17:14:27 (3.59 MB/s) - ‘latestvix.zip’ saved [121746534/121746534]

Archive: latestvix.zip
inflating: formuler1/imageversion
inflating: formuler1/kernel.bin
inflating: formuler1/noforce
inflating: formuler1/rootfs.bin

ofgwrite Utility v4.6.6
Author: Betacentauri
Based upon: mtd-utils-native-1.5.1 and busybox 1.24.1
Use at your own risk! Make always a backup before use!
Don't use it if you use multiple ubi volumes in ubi layer!

Flashing rootfs
Flashing kernel
Searching image files in ./ resolved to /media/hdd/imagebackups/willobuild/formu ler1
Found rootfs file: /media/hdd/imagebackups/willobuild/formuler1/rootfs.bin
Found kernel file: /media/hdd/imagebackups/willobuild/formuler1/kernel.bin
Found UBIFS rootfs
Found mounted /newroot
Found mountpoint for rootfs file: /media/hdd

Found /proc/mtd entries:
Device: Size: Erasesize: Name: Image:
mtd0: 1fb00000 00020000 "complete"
mtd1: 00600000 00020000 "kernel" -> /media/hdd/imagebackups/ willobuild/formuler1/kernel.bin
mtd2: 1f500000 00020000 "rootfs" -> /media/hdd/imagebackups/ willobuild/formuler1/rootfs.bin
Using kernel mtd device: /dev/mtd1
Using rootfs mtd device: /dev/mtd2
Read /proc/cmdline
Kexec mode is:
Current rootfs is: ubi0:rootfs
Current kernel is:
Current root sub dir is:


killall: nmbd: no process killed
killall: rpc.mountd: no process killed
killall: rpc.statd: no process killed
killall: CCcam: no process killed

Usage:
kill [options] <pid> [...]

Options:
<pid> [...] send signal to every <pid> listed
-<signal>, -s, --signal <signal>
specify the <signal> to be sent
-q, --queue <value> integer value to be sent with the signal
-l, --list=[<signal>] list all signal names, or convert one to a name
-L, --table list all signal names in a nice table

-h, --help display this help and exit
-V, --version output version information and exit

For more details see kill(1).

Usage:
kill [options] <pid> [...]

Options:
<pid> [...] send signal to every <pid> listed
-<signal>, -s, --signal <signal>
specify the <signal> to be sent
-q, --queue <value> integer value to be sent with the signal
-l, --list=[<signal>] list all signal names, or convert one to a name
-L, --table list all signal names in a nice table

-h, --help display this help and exit
-V, --version output version information and exit

For more details see kill(1).
killall: kodi.bin: no process killed
killall: hddtemp: no process killed
killall: transmission-daemon: no process killed
killall: openvpn: no process killed
sh: line 1: /etc/init.d/sabnzbd: No such file or directory
Stopping automount: done.
Syncing filesystem
daemonize
successful
start umount_rootfs
root@formuler1:~# cp: can't stat '/lib/libcrypt*': No such file or directory
Switching to user mode 2
Checking E2 is running...
Execute: ps
E2 still running
Execute: ps
E2 is stopped
Move mountpoint of image files
Moving /oldroot/media/hdd to /media/hdd
umounting: /media/autofs
umounting: /media
umounting: /sys/kernel/debug
/bin/automount: error while loading shared libraries: libautofs.so: cannot open shared object file: No such file or directory
Error starting autofs
init: /run/initctl: No such file or directory
Execute: fuser -k -m /oldroot/
 
Yes flashing on the fly..I thought he was using usb method.
I think the usb is at fault, he's tried several times and methods and it's always failing to read/write to or from the usb
I can't remember now what you guys sometimes recommend to format usb HP format tool was one at one time.
 
Back
Top