Dit is iets wat vaak over het hoofd geziien word het eerste uur
Sagem Scarlet Box Firmware
Hi!
I need help. I upgraded my flash on a scarlet box to FAST3464_60A040.img.secure.bin from the web menu. The box did not reboot. I reboot it manually and now all the leds are green but I can not connect to the box anymore. I tried to reset the box. The box leds flashed a few times and then all shut off. What went wrong? What can I do? Thanks for your help in advance!
best regards
Adis
I need help. I upgraded my flash on a scarlet box to FAST3464_60A040.img.secure.bin from the web menu. The box did not reboot. I reboot it manually and now all the leds are green but I can not connect to the box anymore. I tried to reset the box. The box leds flashed a few times and then all shut off. What went wrong? What can I do? Thanks for your help in advance!
best regards
Adis
-
philippe_d
- Moderator
- Berichten: 18398
- Lid geworden op: 28 apr 2008, 11:22
- Locatie: Waregem
- Uitgedeelde bedankjes: 1001 keer
- Bedankt: 3732 keer
- Recent bedankt: 21 keer
-
Provider
Not surprised ... I guess your Box is dead 
That is the risk you take by flashing your modem
.
In normal circumstances, there is absolutely no reason why people want to update firmware’s on the modem, this is done automatically by the ISP when needed.
Unless you know what you do, and you are aware of the risks, and you have no problem taking the risk and ending up with a dead modem, you should stay away of such experiments.
PS. Ik besef dat dit geen antwoord is op de vraag van vorige poster, maar ik wil iedereen toch waarschuwen dat er wel degelijk risico's verbonden zijn aan het manueel flashen van firmwares.
Tenzij je echt weet wat je doet, 100pct bewust bent van de risico's, en het risico wil nemen om te eindigen met een kapotte modem, begin je best niet aan zulke "experimenten".
That is the risk you take by flashing your modem
.In normal circumstances, there is absolutely no reason why people want to update firmware’s on the modem, this is done automatically by the ISP when needed.
Unless you know what you do, and you are aware of the risks, and you have no problem taking the risk and ending up with a dead modem, you should stay away of such experiments.
PS. Ik besef dat dit geen antwoord is op de vraag van vorige poster, maar ik wil iedereen toch waarschuwen dat er wel degelijk risico's verbonden zijn aan het manueel flashen van firmwares.
Tenzij je echt weet wat je doet, 100pct bewust bent van de risico's, en het risico wil nemen om te eindigen met een kapotte modem, begin je best niet aan zulke "experimenten".
VoIP: EDPnet (gratis vaste lijn), Sipgate.de, Sipgate.co.uk, MegaVoip.
Provider: EDPnet Fiber XS (150/50 mbps down/up).
Modem/Router: Fritz!Box 5590 Fiber, OS 8.03, Fritz!SFP GPON aangesloten op Proximus ONTP.
Telefoon centrale: Euracom 181 achter FritzBox So. 3 Fritz!DECT toestellen
TV: Telenet CI+, Fritz!DVB-C.
Provider: EDPnet Fiber XS (150/50 mbps down/up).
Modem/Router: Fritz!Box 5590 Fiber, OS 8.03, Fritz!SFP GPON aangesloten op Proximus ONTP.
Telefoon centrale: Euracom 181 achter FritzBox So. 3 Fritz!DECT toestellen
TV: Telenet CI+, Fritz!DVB-C.
Thanks for your feedback. What dead means? I believe there is a way to reflash the box like any router right? I wanted to enable the box with WPA2. The sagem is with Scarlet not with Belgacom. How can I do now?
-
Petervanakelyen
- Elite Poster
- Berichten: 1628
- Lid geworden op: 30 dec 2009, 22:36
- Locatie: Antwerpen
- Uitgedeelde bedankjes: 96 keer
- Bedankt: 179 keer
You can reflash the firmware using serial or JTAG. There are some instructions here: http://www.zoobab.com/bbox2
-
honda4life
- Moderator
- Berichten: 6135
- Lid geworden op: 03 jan 2010, 21:42
- Locatie: 127.0.0.1
- Uitgedeelde bedankjes: 213 keer
- Bedankt: 391 keer
-
Provider
seems fun to try 
(I mean it :d)
Send me all your bricked BBOXes for free
(I mean it :d)Send me all your bricked BBOXes for free
✂ – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Many thanks. Serial sounds good. I used to flash Cisco routers in the past over serial. Can I connect the RX TX GND directly to serial or I need a converter to USB? Once connected over serial, I presume that it loads the image over tftp right? Got some hopes.Petervanakelyen schreef:You can reflash the firmware using serial or JTAG. There are some instructions here: http://www.zoobab.com/bbox2
-
honda4life
- Moderator
- Berichten: 6135
- Lid geworden op: 03 jan 2010, 21:42
- Locatie: 127.0.0.1
- Uitgedeelde bedankjes: 213 keer
- Bedankt: 391 keer
-
Provider
for that I recommend you to buy a cheap MAX232 IC or equivalent, what you need is in the datasheet.
4 capacitors, and of course the connectors and a power supply.
I think it's by usb memory stick
4 capacitors, and of course the connectors and a power supply.
I think it's by usb memory stick
✂ – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
-
Petervanakelyen
- Elite Poster
- Berichten: 1628
- Lid geworden op: 30 dec 2009, 22:36
- Locatie: Antwerpen
- Uitgedeelde bedankjes: 96 keer
- Bedankt: 179 keer
As you can see in this picture, it seems to be neccessary to use an USB converter. You can make one yourself using a MAX232 as honda4life suggests. Flashing the firmware is probably done over TFTP as you already presumed.adis schreef:Many thanks. Serial sounds good. I used to flash Cisco routers in the past over serial. Can I connect the RX TX GND directly to serial or I need a converter to USB? Once connected over serial, I presume that it loads the image over tftp right? Got some hopes.Petervanakelyen schreef:You can reflash the firmware using serial or JTAG. There are some instructions here: http://www.zoobab.com/bbox2
-
honda4life
- Moderator
- Berichten: 6135
- Lid geworden op: 03 jan 2010, 21:42
- Locatie: 127.0.0.1
- Uitgedeelde bedankjes: 213 keer
- Bedankt: 391 keer
-
Provider
This pinout is different than the table so be careful
I think you copy your files to a temp directory from usb drive (formatted as ext because of linux kernel), and flash it then.
Why you need the IC is because of RS232 is negative locic: 1 is -11V and 0 is +11V.
Many elektronics work at +5V, with positive logic: 1=+5V and 0 is +5V (TTL)
So you need to invert and level shifting (down and up), the capacitors are used as a charge pump for sending to computer +-11V
I think you copy your files to a temp directory from usb drive (formatted as ext because of linux kernel), and flash it then.
Why you need the IC is because of RS232 is negative locic: 1 is -11V and 0 is +11V.
Many elektronics work at +5V, with positive logic: 1=+5V and 0 is +5V (TTL)
So you need to invert and level shifting (down and up), the capacitors are used as a charge pump for sending to computer +-11V
✂ – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
-
Petervanakelyen
- Elite Poster
- Berichten: 1628
- Lid geworden op: 30 dec 2009, 22:36
- Locatie: Antwerpen
- Uitgedeelde bedankjes: 96 keer
- Bedankt: 179 keer
I don't think so. Shouldn't be there some flash memory on the USB converter board in that case? Most of the time you just use HyperTerminal/any of the linux serial consoles to start a TFTP client that loads up the configuration from the TFTP server in the network.I think you copy your files to a temp directory from usb drive (formatted as ext because of linux kernel), and flash it then.
-
xming
- Pro Member
- Berichten: 434
- Lid geworden op: 06 okt 2005, 10:35
- Uitgedeelde bedankjes: 9 keer
- Bedankt: 47 keer
Recovery is possible!
Recently I've tried to flash the BGC fw and "bricked" the sagem, it seemed that my sagem doesn't like 60A042. After a bit fiddling I found out that one can recover from a bad flash w/o resorting to JTAG as long as you have a good recovery image.
Thing that you need:
- a dhcp server
- a tftp server
- s sniffer (tcpdump wireshark)
- some common sense
how this works? Booting in recovery mode and samgem will get an IP from dhcp server then do a netboot/etherboot and download the image from tftp server, then you can access the web/telnet interface again then reflash with a good image, that's it.
Step by step howto:
- start a sniffer
- boot the samgem in recovery mode by pressing the reset button and power on
- you will see that it asks an IP and should get it from the dhcp server
- you will see that it tries to download a file from an IP (write down this IP as tftp server) with a path (write it down) and filename (write it down)
- give your tftp server the IP address that you wrote
- rename the FAST3464_<whatever> to the filename you wrote and move it to the direcoty (relative to your tftp root) path that you wrote
- reboot the sagem in recovery
- surf to the IP of sagem (the one it got from the dhcp server)
- flash as usual
- done
As said earlier you need to find a good image, my sagem doesn't like 60A042 no matter what I do, but 60A040 works like a charm.
Recently I've tried to flash the BGC fw and "bricked" the sagem, it seemed that my sagem doesn't like 60A042. After a bit fiddling I found out that one can recover from a bad flash w/o resorting to JTAG as long as you have a good recovery image.
Thing that you need:
- a dhcp server
- a tftp server
- s sniffer (tcpdump wireshark)
- some common sense
how this works? Booting in recovery mode and samgem will get an IP from dhcp server then do a netboot/etherboot and download the image from tftp server, then you can access the web/telnet interface again then reflash with a good image, that's it.
Step by step howto:
- start a sniffer
- boot the samgem in recovery mode by pressing the reset button and power on
- you will see that it asks an IP and should get it from the dhcp server
- you will see that it tries to download a file from an IP (write down this IP as tftp server) with a path (write it down) and filename (write it down)
- give your tftp server the IP address that you wrote
- rename the FAST3464_<whatever> to the filename you wrote and move it to the direcoty (relative to your tftp root) path that you wrote
- reboot the sagem in recovery
- surf to the IP of sagem (the one it got from the dhcp server)
- flash as usual
- done
As said earlier you need to find a good image, my sagem doesn't like 60A042 no matter what I do, but 60A040 works like a charm.
-
Basil Fawlty
- Starter
- Berichten: 7
- Lid geworden op: 27 aug 2010, 09:28
Wat is nu eigenlijk de meest recente Scarlet firmware die veilig te flashen is? Ik heb momenteel 6OS105-6OS005 draaien, maar ik zie dat er ook recentere Scarlet images zijn zoals 6OS105. Deze heeft wel een andere extensie.
Sinds ongeveer een week loopt ZTC (Zero Touch Configuration) nu wel op Scarlet lijnen, onafhankelijk van de firmware.redman schreef:Ook al zet je de belgacom firmware om de scarlet box, de zero touch zal nooit lopen op een scarlet lijn.
Het kan wel zijn dat je een nieuwe firmware binnen haalt, maar dat is iets anders dan de zero touch.
Sir xming, thank you for your post, you are my hero.
I had the 6OS105-6OS005 and flashed to 6OS105_60A046, and allthough there were no apparent interruptions during the process, it broke the sagem box (all leds green, can't connect to it).
Luckily I had a copy of xming's instructions, a dhcp deamon, a tftp deamon and wireshark preinstalled for exactly this reason.
For me, after the recovery boot, the sagem modem looked for a "0305A8C0.img" in the tftp root folder at ip 192.168.5.2, and when everything was configured correctly I could see it download that file and sure enough it came to life again, sort of.
1) I tried flashing 6OS105-6OS005 again to undo my mistake, strangely enough that broke it again immediately.
2) I tried FAST3464_60R10A.img.secure.res, a recovery firmware, which made the modem available again at 192.168.1.1 and the dhcpd works but apparently this firmware doesn't give you a functional modem, The webinterface only shows a recovery page saying it is waiting for functional firmware, which I assume will automatically arrive on a belgacom line, but no such luck. (Should probably have downloaded the 60R109 recovery firmware Dean3009 suggested).
3) Since those were the only 3 firmware's I had, I flashed 6OS105_60A046 again, which actually worked while it was on, but broke again after the first reboot.
4) I tried reflashing 6OS105_60A046 again, didn't even start.
5) I went back to the recovery firmware, then back to 6OS105_60A046, logged in and did a reset to factory defaults, reconfigured everything and now everything seems to work, even after a reboot.
I can't say what exactly made work, but it does. There seems to be some version upgrades that work and some that don't.
In conclusion:
1) Messing with the firmware is not for the faint of hearted, don't.
2) If you are to go through with it, make certain you understand what xming did to recover his box and be prepared to do the same. (for example by using his method to do the upgrade in the first place)
3) Plainly flashing to the latest belgacom firmware 6OS105_60A046 at the time of this writing seems a bad idea.
Dean3009 suggested flashing 60R109 (a recovery firmware) first and then something else, he used (60R109-60A022 for him), so that will probably work. If i were to try again to go to the latest firmware, I'd probably try.
60R109 -> 60R109-60A022 -> factory reset -> 60S105-60R040 -> factory reset -> 60S105-60R046 -> reconfigure
But no guarantees this will work or you need all the steps. Again be prepared to follow xming's instructions, or don't.
On the upside, running the latest belgacom firmware on a sagem box does work, the tr98 process is no longer the terrible resource hog. Can't tell yet if it improved stability.
I had the 6OS105-6OS005 and flashed to 6OS105_60A046, and allthough there were no apparent interruptions during the process, it broke the sagem box (all leds green, can't connect to it).
Luckily I had a copy of xming's instructions, a dhcp deamon, a tftp deamon and wireshark preinstalled for exactly this reason.
For me, after the recovery boot, the sagem modem looked for a "0305A8C0.img" in the tftp root folder at ip 192.168.5.2, and when everything was configured correctly I could see it download that file and sure enough it came to life again, sort of.
1) I tried flashing 6OS105-6OS005 again to undo my mistake, strangely enough that broke it again immediately.
2) I tried FAST3464_60R10A.img.secure.res, a recovery firmware, which made the modem available again at 192.168.1.1 and the dhcpd works but apparently this firmware doesn't give you a functional modem, The webinterface only shows a recovery page saying it is waiting for functional firmware, which I assume will automatically arrive on a belgacom line, but no such luck. (Should probably have downloaded the 60R109 recovery firmware Dean3009 suggested).
3) Since those were the only 3 firmware's I had, I flashed 6OS105_60A046 again, which actually worked while it was on, but broke again after the first reboot.
4) I tried reflashing 6OS105_60A046 again, didn't even start.
5) I went back to the recovery firmware, then back to 6OS105_60A046, logged in and did a reset to factory defaults, reconfigured everything and now everything seems to work, even after a reboot.
I can't say what exactly made work, but it does. There seems to be some version upgrades that work and some that don't.
In conclusion:
1) Messing with the firmware is not for the faint of hearted, don't.
2) If you are to go through with it, make certain you understand what xming did to recover his box and be prepared to do the same. (for example by using his method to do the upgrade in the first place)
3) Plainly flashing to the latest belgacom firmware 6OS105_60A046 at the time of this writing seems a bad idea.
Dean3009 suggested flashing 60R109 (a recovery firmware) first and then something else, he used (60R109-60A022 for him), so that will probably work. If i were to try again to go to the latest firmware, I'd probably try.
60R109 -> 60R109-60A022 -> factory reset -> 60S105-60R040 -> factory reset -> 60S105-60R046 -> reconfigure
But no guarantees this will work or you need all the steps. Again be prepared to follow xming's instructions, or don't.
On the upside, running the latest belgacom firmware on a sagem box does work, the tr98 process is no longer the terrible resource hog. Can't tell yet if it improved stability.
-
xming
- Pro Member
- Berichten: 434
- Lid geworden op: 06 okt 2005, 10:35
- Uitgedeelde bedankjes: 9 keer
- Bedankt: 47 keer
I am glad that it helped you.
Nu dat ik erover nadenk, het is mogelijk om een nieuwe fw te testen zonder te flashen.
- booten in recovery mode met de nieuwe fw op de tftp server
Dit is een net/etherboot zonder te flashen, dus na een normale reboot, heb je terug je oude fw.
Nu dat ik erover nadenk, het is mogelijk om een nieuwe fw te testen zonder te flashen.
- booten in recovery mode met de nieuwe fw op de tftp server
Dit is een net/etherboot zonder te flashen, dus na een normale reboot, heb je terug je oude fw.
Ah, dus die recovery procedure vervangt de huidige firmware niet, maar start eenmalig op met de firmware van de tftp server, dit verklaart waarom een reboot telkens opnieuw de sagem box deed vastlopen.
Ik veronderstel dan dat de reset to factory defaults uiteindelijk hetgene geweest is wat de zaak terug herstelt heeft. Of met andere woorden, de nieuwe belgacom firmware werkt op de sagem box, maar niet met de instellingen die je overerft van je scarlet firmware.
Ik veronderstel dan dat de reset to factory defaults uiteindelijk hetgene geweest is wat de zaak terug herstelt heeft. Of met andere woorden, de nieuwe belgacom firmware werkt op de sagem box, maar niet met de instellingen die je overerft van je scarlet firmware.
-
xming
- Pro Member
- Berichten: 434
- Lid geworden op: 06 okt 2005, 10:35
- Uitgedeelde bedankjes: 9 keer
- Bedankt: 47 keer
idd, sagem boot gewoon met de img van de tftp server, het staat ook in mijn uitleg dat je na het booten van tftpAh, dus die recovery procedure vervangt de huidige firmware niet, maar start eenmalig op met de firmware van de tftp server, dit verklaart waarom een reboot telkens opnieuw de sagem box deed vastlopen.
Wss was het bij jou een factory reset genoeg geweest. Bij mij wou v. 42 echt niet werken, 40 doet het wel goed, heeft iemand een linkje voor 46?- surf to the IP of sagem (the one it got from the dhcp server)
- flash as usual
-
Petervanakelyen
- Elite Poster
- Berichten: 1628
- Lid geworden op: 30 dec 2009, 22:36
- Locatie: Antwerpen
- Uitgedeelde bedankjes: 96 keer
- Bedankt: 179 keer
-
ToMiKoN
- Pro Member
- Berichten: 425
- Lid geworden op: 31 okt 2002, 12:12
- Locatie: Blankenberge
- Uitgedeelde bedankjes: 8 keer
- Bedankt: 39 keer
-
Provider
Misschien niet helemaal een vraag die on topic, maar toch in de lijn van de topic.
Ik heb een ScarletBox en Bbox2. Ik was vroeger Belgacom klant en nu al meer dan één jaar Scarlet klant.
Als ik mijn ScarletBox aankoppel heb ik:
down 25008 kbps en up 3104 kbps
Als ik mijn Bbox2 (60R109-60A022 ) aankoppel heb ik:
down 20064 kbps en up 2040 kbps
Heeft iemand een idee waardoor dit komt?
Beide boxen werken trouwens voor de rest prima.
De snelheid is trouwens ook gewoon gelijk gebleven:
Is dit dan gewoon een andere notatie?
Ik heb een ScarletBox en Bbox2. Ik was vroeger Belgacom klant en nu al meer dan één jaar Scarlet klant.
Als ik mijn ScarletBox aankoppel heb ik:
down 25008 kbps en up 3104 kbps
Als ik mijn Bbox2 (60R109-60A022 ) aankoppel heb ik:
down 20064 kbps en up 2040 kbps
Heeft iemand een idee waardoor dit komt?
Beide boxen werken trouwens voor de rest prima.
De snelheid is trouwens ook gewoon gelijk gebleven:
Is dit dan gewoon een andere notatie?
Mobiel: iPhone 16 Pro + Proximus werk abonnement
Tablet: iPad 2020+2021 128 Gb
Home: Hey Telecom vast internet
Tablet: iPad 2020+2021 128 Gb
Home: Hey Telecom vast internet
Thanks!!! 
It works very well. I have now 6OS105-60A046 running on the box. WPA2 works finally. I got a Belgacom logo thus.
It works very well. I have now 6OS105-60A046 running on the box. WPA2 works finally. I got a Belgacom logo thus.xming schreef:Recovery is possible!
Recently I've tried to flash the BGC fw and "bricked" the sagem, it seemed that my sagem doesn't like 60A042. After a bit fiddling I found out that one can recover from a bad flash w/o resorting to JTAG as long as you have a good recovery image.
Thing that you need:
- a dhcp server
- a tftp server
- s sniffer (tcpdump wireshark)
- some common sense
how this works? Booting in recovery mode and samgem will get an IP from dhcp server then do a netboot/etherboot and download the image from tftp server, then you can access the web/telnet interface again then reflash with a good image, that's it.
Step by step howto:
- start a sniffer
- boot the samgem in recovery mode by pressing the reset button and power on
- you will see that it asks an IP and should get it from the dhcp server
- you will see that it tries to download a file from an IP (write down this IP as tftp server) with a path (write it down) and filename (write it down)
- give your tftp server the IP address that you wrote
- rename the FAST3464_<whatever> to the filename you wrote and move it to the direcoty (relative to your tftp root) path that you wrote
- reboot the sagem in recovery
- surf to the IP of sagem (the one it got from the dhcp server)
- flash as usual
- done
As said earlier you need to find a good image, my sagem doesn't like 60A042 no matter what I do, but 60A040 works like a charm.
-
Petervanakelyen
- Elite Poster
- Berichten: 1628
- Lid geworden op: 30 dec 2009, 22:36
- Locatie: Antwerpen
- Uitgedeelde bedankjes: 96 keer
- Bedankt: 179 keer
De bbox2 en de scarlet box zijn op de behuizing en de firmware na identiek. Wireless-N heeft nooit in één van beide gezeten en zal ook nooit door middel van een firmware update geactiveerd kunnen worden.
-
woete
- Plus Member
- Berichten: 153
- Lid geworden op: 09 jun 2007, 23:16
- Uitgedeelde bedankjes: 12 keer
- Bedankt: 2 keer
Ah zut, had ooit gelezen dat deze sagem 3464 dit wél had.
Hier http://userbase.be/forum/viewtopic.php?f=44&t=26463 meer over wifi N in belgacom draadje, optie blijkbaar te duur voor Belgacom & Scarlet.
Hier http://userbase.be/forum/viewtopic.php?f=44&t=26463 meer over wifi N in belgacom draadje, optie blijkbaar te duur voor Belgacom & Scarlet.
-
krisken
- userbase crew
- Berichten: 19763
- Lid geworden op: 07 nov 2006, 12:11
- Twitter: kriskenbe
- Locatie: Massemen - 91WET0
- Uitgedeelde bedankjes: 1857 keer
- Bedankt: 1035 keer
bbox2 is identiek aan sagem, geen van beiden hebben dit!
maar...vijs hem open en haal het wifi kaartje eruit...en vervang het
maar...vijs hem open en haal het wifi kaartje eruit...en vervang het
Internet = Orange 150/15Mbps + WirelessBelgië
Telefonie = EDPnet + OVH
GSM = Orange Go Extreme SE + Scarlet Red
TV = TVV App + Netflix + Disney+ + Streamz
Netwerk = Mikrotik + Ubiquiti
-
Petervanakelyen
- Elite Poster
- Berichten: 1628
- Lid geworden op: 30 dec 2009, 22:36
- Locatie: Antwerpen
- Uitgedeelde bedankjes: 96 keer
- Bedankt: 179 keer
...om er dan achter te komen dat dat ook niet werkt omdat de benodigde modules voor de chipset niet in de firmware geïntegreerd zijn.
Een bbox3 met gigabit, wireless-n en een paar optimalisaties zou niet slecht zijn Maar ik ben al lang blij dat je er je eigen router met zijn eigen publiek IP aan kan hangen (in tegenstelling tot bij Telenet).
Een bbox3 met gigabit, wireless-n en een paar optimalisaties zou niet slecht zijn
Maar ik ben al lang blij dat je er je eigen router met zijn eigen publiek IP aan kan hangen (in tegenstelling tot bij Telenet).-
Converted
- Pro Member
- Berichten: 352
- Lid geworden op: 11 aug 2006, 16:08
- Locatie: Antwerpen
- Uitgedeelde bedankjes: 29 keer
- Bedankt: 18 keer
-
Provider
Onlangs hebben ze bij hier bij edpnet op men sagem 3464 een andere firmware ingeladen die blijkbaar problemen geeft icm mijn siemens ip telefoon. Hoe moet ik juist terug naar de vorige firmware?
Is dit mogelijk, of toch enig risico aan verbonden?
De huidige firmware is 6OS105-6OC009. De firmware waar ik absoluut geen problemen mee ondervond is de laatste scarlet firmware (6OS105-6OS005) Waar vindt ik die laatste en is het aan te raden deze er terug op te zetten met behoud van instellingen?
Dank alvast
[
Post made via mobile device ]
Is dit mogelijk, of toch enig risico aan verbonden?
De huidige firmware is 6OS105-6OC009. De firmware waar ik absoluut geen problemen mee ondervond is de laatste scarlet firmware (6OS105-6OS005) Waar vindt ik die laatste en is het aan te raden deze er terug op te zetten met behoud van instellingen?
Dank alvast
[
Post made via mobile device ]
