sb18180
TK Veteran
Getting no signal on F5 box with another satbox connected to same satdish but different lnb port?
I know for a fact its the f5 boxes not the lnbs(some peps been blaiming lnbs). I had two f5s set up(different lnb feeds) and when they were both switched on one would lose some channs through no signal. i checked through the transponder list half of them were no signal! with both boxes switched on. i switched one off and hey how all signals back. i tried the same test with two blade boxes with no problem at all no signal loss on both. so its NOT lnb issues its some dodgey f5 boxes going around. not all f5s do it because i also tried a seperate pair of f5s from different supplier with no issues at all!!! it also does it if you have a bad f5 connected and any other satbox say a sky+ box. thats the facts! tried and tested and put to bed!
next issue to be solved with f5s is file mismatch when trying to update firmware via usb. locking the usb from updating firmware is the excuse BUT firmware for these boxes is supposed to be closed source so how is it possible?? hmmm i can smell sum bull here!
I tried to flash one via null modem cable that had file mismatch on it. it flashed fine 100% rebooted but it just left it with a 97% bootloop!! tried different images all flashed fine but still 97% bootloop now a doorstop not advisable to try and flash an f5 with null modem cable if it has file mismatch issues!
I know for a fact its the f5 boxes not the lnbs(some peps been blaiming lnbs). I had two f5s set up(different lnb feeds) and when they were both switched on one would lose some channs through no signal. i checked through the transponder list half of them were no signal! with both boxes switched on. i switched one off and hey how all signals back. i tried the same test with two blade boxes with no problem at all no signal loss on both. so its NOT lnb issues its some dodgey f5 boxes going around. not all f5s do it because i also tried a seperate pair of f5s from different supplier with no issues at all!!! it also does it if you have a bad f5 connected and any other satbox say a sky+ box. thats the facts! tried and tested and put to bed!
next issue to be solved with f5s is file mismatch when trying to update firmware via usb. locking the usb from updating firmware is the excuse BUT firmware for these boxes is supposed to be closed source so how is it possible?? hmmm i can smell sum bull here!
I tried to flash one via null modem cable that had file mismatch on it. it flashed fine 100% rebooted but it just left it with a 97% bootloop!! tried different images all flashed fine but still 97% bootloop now a doorstop not advisable to try and flash an f5 with null modem cable if it has file mismatch issues!
Last edited: