Obihai bricked my Obi110
SteveInWA:
Quote
As soon as I added the device to the dashboard on obitalk, and tried to set "disable" on the auto firmware update (obitalk dashboard has it set to "periodically" by default), it went back to recovery mode with the alternating green/red lights. Is Obihai intentionally sabotaging people with old 100/110 models and intentionally bricking their devices? Because this seems like the case for me.
No, it's not a conspiracy. My 110 works fine, as do thousands of others. You'd see a s**tstorm of posts here if it was some evil deed.
I don't think anyone mentioned this already, but based on your symptom above, did you actually completely delete the device from the OBiTALK dashboard before adding it again, as a new device? This would kick off the device discovery procedure, whereby you would key in ***5 on the attached telephone, and OBiTALK would find it, remotely reset it to default, and add it to your dashboard. It would not copy any locally-configured settings from the device, and it would not write any previously-configured bad settings to the device
If you didn't do that, then OBiTALK may be overwriting bad information onto your 110, from a previous setup.
If you DID do that, then you have a bad device.
I don't consider their response to be "bad customer service". Your device is out of warranty, and, just like any other consumer product, the cost of repair or replacement is your responsibility. You may be able to buy a new power adapter from them, if it's suspect, and you don't happen to have a compatible adapter laying around.
Otherwise, you can get a brand new OBi 200 for $48.89 from Amazon. Considering how much time you've spent troubleshooting, I'd say it's worth it.
MikePA:
Quote from: Tor2626 on September 06, 2014, 02:58:01 pm
Is Obihai intentionally sabotaging people with old 100/110 models and intentionally bricking their devices? Because this seems like the case for me.
Check to make sure your tinfoil hat didn't fall off and short something out. ::)
No, Obi isn't sending out death signals to some devices.
Remember, software eventually works and hardware eventually dies.
Tor2626:
Quote from: SteveInWA on September 06, 2014, 06:21:02 pm
No, it's not a conspiracy. My 110 works fine, as do thousands of others. You'd see a s**tstorm of posts here if it was some evil deed.
I don't think anyone mentioned this already, but based on your symptom above, did you actually completely delete the device from the OBiTALK dashboard before adding it again, as a new device? This would kick off the device discovery procedure, whereby you would key in ***5 on the attached telephone, and OBiTALK would find it, remotely reset it to default, and add it to your dashboard. It would not copy any locally-configured settings from the device, and it would not write any previously-configured bad settings to the device
If you didn't do that, then OBiTALK may be overwriting bad information onto your 110, from a previous setup.
If you DID do that, then you have a bad device.
I don't consider their response to be "bad customer service". Your device is out of warranty, and, just like any other consumer product, the cost of repair or replacement is your responsibility. You may be able to buy a new power adapter from them, if it's suspect, and you don't happen to have a compatible adapter laying around.
Otherwise, you can get a brand new OBi 200 for $48.89 from Amazon. Considering how much time you've spent troubleshooting, I'd say it's worth it.
Maybe not a 'conspiracy', but looking at the forums, I'm far from being the only one with the red/green lights problems. Both times I successfully recovered from that problem, the device was working fine on its own when it was not attached to Obitalk dashboard. The red/green lights problem arose as soon as I added the device to Obitalk. According to this: https://www.obihai.com/support/troubleshooting/alt
"The unit with red/green alternate flashing means that there was a power loss in the midst of firmware update of the OBi. And it is possible to recover the OBi operation."
The fact is, I haven't initiated a FW update in months. My device default for automatic firmwares was on "disable". Obitalk has it on "periodically" update on default. The website initiated a forced FW update and bricked my device. It should have never been on "periodically" on the first place. It should have at least ONE warning or notification when adding a device to Obitalk that you're about to be set on "periodically" automatic forced FW updates and risk bricking my Obi device while I'm sleeping.
I fail to see how I'm at fault here in any way and how I shouldn't be compensated, even if out of warranty. So far my support ticket is being ignored on this matter.
I'm done troubleshooting for now, since the last time I added my Obi110 to the dashboard bricked it for good. Now I cannot even update, as it fails every single time.
Quote from: MikePA on September 07, 2014, 01:09:12 am
Check to make sure your tinfoil hat didn't fall off and short something out. ::)
No, Obi isn't sending out death signals to some devices.
Remember, software eventually works and hardware eventually dies.
More like hardware works perfectly for 1+ year, software gets updated automatically without my consent and hardware dies.
WelshPaul:
As far as I'm aware when it comes to Firmware/Bios updates/flashing, if it fails and bricks your device then even if in warranty your out of luck. I don't know of any manufacturers who will allow a warranty claim on hardware defective due to a failed software/firmware update.
I'm on edge every time my 55" LG smart TV updates :-\
That being said, I hate manufacturers who force updates without allowing the end user to turn off the feature. After all if it fails and the manufacturer forced the update on you then yes they should be held liable. However they own the software, you the hardware and in the many, many, many, many pages of terms and conditions they have their backsides covered...
OBIHAI though do not force updates on anyone, out of the box automatic firmware updates are disabled by default. When registering the device against an OBiTALK account it is enabled although you can switch it off again. (if your aware it was enabled that is)
The OBi1032 however when registered against an OBiTALK account does not have automatic firmware enabled by default. I suspect this is because it's a new device and in time just as the other devices it too will have this feature enabled when registered against an OBiTALK account.
RFC3261:
Quote from: Tor2626 on September 07, 2014, 01:43:15 am
Maybe not a 'conspiracy', but looking at the forums, I'm far from being the only one with the red/green lights problems.
Not the only one, but small numbers, and a self selected group (people "post" only when they have problems, not when things are working fine, so you get into the statistics of selection bias. No one disputes that you have an issue, but individuals are not statistically significant).
My "guess" (and it is just a guess) is that you may have been one of the unlucky to be at the low end of the flash memory life expectancy (someone has to be). Sometimes repeated resets can result in sufficient bad block reassignments to get things working again. And sometimes, not so much.
Navigation
[0] Message Index
[#] Next page
[*] Previous page