bushe777
Member
This will be quite a long post to read, but I don't know what else to do to make it right, I out of ideas and I can't install forceware because data verification fails and at the end of the flashing it says "New firmware sucessfully installed" but it doesn't really work.
I was able to make a 8mb original dump and a 3.07mb original firmware backup that I'm not sure if I backup them wrong and are actually corrupted, the flashing is successful on every writing without any failed message or mismatches, but I can't still enter 192.168.100.1 as when it was virgin, something is going wrong and now I can't use forceware or revive my modem. When I try with other 8mb dumps (which some include forceware and others are virgin) I get failed data verification from start to end, so only my backups have good results but for nothing since I can't even recover my modem back to normal after a successful 8mb original flash and/or the 3.07mb firmware.
I have a sb6120 that doesn't have the serial port, which that may explain why not any full dumps will work with my modem and just my backup that is from a "new" sb6120, is there someone else with a sb6120 with no serial port that has a full dump with forceware included? or do you know how can I make the forceware firmware to sucessfully get verified when flashing.
I think the script is also made for the older version of the sb6120, it will help knowing at what address I could start flashing just the forceware firmware from the "SPI Flash" tab and avoiding the use of an script.
Just for info, I have a BCUSB v1.7 with board firmware 2.02 and I have tried using BlackcatUSB builds 257, 267, 275, 304, and 318, they all detect the modem, with exception of the newest build 321 and all they say I have an Spansion S25FL064 and SPI compatible device (JEDEC ID: 01 0216) and I'm using a 3M SOIC clip so no soldering has been made to the modem.
I have uploaded my backups if that helps you compare something or try them to check if they are really corrupted. Also if someone has a valid dump to use with the SB6120_Forceware_SPI.BCS I might be able get it to work again if someone helps me, I will need the uboot, ubf1, ubf2, and nvram to try it.
The newest build 321 doesn't work because it doesn't detect my bcusb, the 320 also has the same issue, and also the new firmware for the bcusb (BCUSB.3.01.SPI.hex) that is included on this builds doesn't get my BCUSB detected on operational mode, so I have to stick to build 318 and bcusb firmware 1.09 or 2.02.
I have tried flashing with the script "SB6120_Forceware_SPI.BCS" and flashed both UBFI1 and UBFI2 with "forceWare_UBFI-v1.1r12-BETA2.bin" but I can see that the flashing is not going well and it isn't able to verify the date written to it (see picture "failed"), also the same errors happen when using "SBV6220_SPI.bcs" or "VMG300_SPI.bcs" script.
I have a screenshots ("backup finished") of when I'm flashing the backup I made when the modem was virigin, everything seems to go fine but no luck entering 192.168.100.1.
So I guess it will be necessary to start over and first focus on making the modem work back to normal with an original firmware before trying to flash the forceware firmware, but I can't make it go back to the virign state it had with my backup or other dumps I have collected.
I don't know if this has something to do, but the only way I'm actually able to detect the modem is by using the power supply and also the R362 cable, if I use power supply but don't use the R362 cable the modem has the the "power" and "online" lights in a dimmed green, the "receive" and "send" lights in blue and the "link" light somewhat purple (see pic "without r362") and it doesn't recognize the modem in this way or it does but it says "connected to device: 00 0000", also not using power supply but using the R362 doesn't correctly recognize my modem it says "connected to devide: 7F FFFF or other times 80 8080" so to make it work I have to use power supply and make sure the R362 is always making contact and all light get turned off but allows my modem to get detected (see pic "r362 contact").
After flashing the modem with my backup or any other backup the modem, and then connecting the ethernet cable, the modem has the green power light on and the blue link light with intermittent patterns but it never gets steady (see gif "light pattern"). Before trying to flash it I was able to get the four blue lights on.
When I power the modem I can see that send, receive, and online lights are dimmed and then they turn off after the "link" light blinks blue (see pic and gif "powering")
I have tried unchecking the "verify programming option" as well but that doesn't make the trick either.
I was able to make a 8mb original dump and a 3.07mb original firmware backup that I'm not sure if I backup them wrong and are actually corrupted, the flashing is successful on every writing without any failed message or mismatches, but I can't still enter 192.168.100.1 as when it was virgin, something is going wrong and now I can't use forceware or revive my modem. When I try with other 8mb dumps (which some include forceware and others are virgin) I get failed data verification from start to end, so only my backups have good results but for nothing since I can't even recover my modem back to normal after a successful 8mb original flash and/or the 3.07mb firmware.
I have a sb6120 that doesn't have the serial port, which that may explain why not any full dumps will work with my modem and just my backup that is from a "new" sb6120, is there someone else with a sb6120 with no serial port that has a full dump with forceware included? or do you know how can I make the forceware firmware to sucessfully get verified when flashing.
I think the script is also made for the older version of the sb6120, it will help knowing at what address I could start flashing just the forceware firmware from the "SPI Flash" tab and avoiding the use of an script.
Just for info, I have a BCUSB v1.7 with board firmware 2.02 and I have tried using BlackcatUSB builds 257, 267, 275, 304, and 318, they all detect the modem, with exception of the newest build 321 and all they say I have an Spansion S25FL064 and SPI compatible device (JEDEC ID: 01 0216) and I'm using a 3M SOIC clip so no soldering has been made to the modem.
I have uploaded my backups if that helps you compare something or try them to check if they are really corrupted. Also if someone has a valid dump to use with the SB6120_Forceware_SPI.BCS I might be able get it to work again if someone helps me, I will need the uboot, ubf1, ubf2, and nvram to try it.
The newest build 321 doesn't work because it doesn't detect my bcusb, the 320 also has the same issue, and also the new firmware for the bcusb (BCUSB.3.01.SPI.hex) that is included on this builds doesn't get my BCUSB detected on operational mode, so I have to stick to build 318 and bcusb firmware 1.09 or 2.02.
I have tried flashing with the script "SB6120_Forceware_SPI.BCS" and flashed both UBFI1 and UBFI2 with "forceWare_UBFI-v1.1r12-BETA2.bin" but I can see that the flashing is not going well and it isn't able to verify the date written to it (see picture "failed"), also the same errors happen when using "SBV6220_SPI.bcs" or "VMG300_SPI.bcs" script.
I have a screenshots ("backup finished") of when I'm flashing the backup I made when the modem was virigin, everything seems to go fine but no luck entering 192.168.100.1.
So I guess it will be necessary to start over and first focus on making the modem work back to normal with an original firmware before trying to flash the forceware firmware, but I can't make it go back to the virign state it had with my backup or other dumps I have collected.
I don't know if this has something to do, but the only way I'm actually able to detect the modem is by using the power supply and also the R362 cable, if I use power supply but don't use the R362 cable the modem has the the "power" and "online" lights in a dimmed green, the "receive" and "send" lights in blue and the "link" light somewhat purple (see pic "without r362") and it doesn't recognize the modem in this way or it does but it says "connected to device: 00 0000", also not using power supply but using the R362 doesn't correctly recognize my modem it says "connected to devide: 7F FFFF or other times 80 8080" so to make it work I have to use power supply and make sure the R362 is always making contact and all light get turned off but allows my modem to get detected (see pic "r362 contact").
After flashing the modem with my backup or any other backup the modem, and then connecting the ethernet cable, the modem has the green power light on and the blue link light with intermittent patterns but it never gets steady (see gif "light pattern"). Before trying to flash it I was able to get the four blue lights on.
When I power the modem I can see that send, receive, and online lights are dimmed and then they turn off after the "link" light blinks blue (see pic and gif "powering")
I have tried unchecking the "verify programming option" as well but that doesn't make the trick either.
