ARCHIVED FORUM -- March 2012 to February 2022READ ONLY FORUM
This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022
Normally I would say that any Beo6 can be brought back to life. I have had many different types of "dead" Beo5/6's, and up until now, they al have come to life.
But.... right now, I have a Beo6 that seems to be impossible to revive. It was DOA, and I gave it a new charged battery, it responded with "No valid configuration", so I figured, this will be easy, but no version of the config tool can upload anything to the remote.
Normally when uploading to these remotes, the remote will go black when upload starts, Windows will indicate that USB device does not work, and the upload will begin.
This is the bootloader mode kicking in, and this is fine, after upload, the remote restarts, Windows finds it and all is good.
This remote however, when upload starts, it goes black, Windows complains, and then the remote lights up with "No configuration". The "WiFi firmware" never starts, it just shows progress bar up until 100%, but does not write or indicate how many bytes to write. When it comes to 100%, it just stays there. Then you can disconnect the remote from USB, attach it again, and it will try "Animation", same thing, just goes to 100% without any bytes, disconnect and connect again, it will continue to "Configuration" and then after 100% without any bytes, it will stop.
So, this remote somehow is told to go into bootloader mode, but restarts or fails, and then cannot receive any bytes from the config tool.
I have tried all versions, different charged batteries, different drivers on different config tools, both Win7-32 and Win10 64(with 6.84), nothing can upload to this remote.
Anyone seen this before ?
/Weebyx
Hi Weebyx,
You're the master when it comes to Beo6 revivals and I can't be 100% sure, but I feel like it's a scenario I've been througt when trying to awake my first remote (the golden one if you remember).
I wonder if it would worth try to make a sort of dummy battery based on a PSU just for updates and awakes procedures and to take the battery power out of the equation?
matador43: Hi Weebyx, You're the master when it comes to Beo6 revivals and I can't be 100% sure, but I feel like it's a scenario I've been througt when trying to awake my first remote (the golden one if you remember). I wonder if it would worth try to make a sort of dummy battery based on a PSU just for updates and awakes procedures and to take the battery power out of the equation?
This is the only thing I have not tried yet, but the battery is new and charged in a working remote for 48 hours. The problem with this remote, is that it drops out of bootloader mode(I think).5.12 and 6.00 both wants to write BeoLo, but both just stops. Everytime it is the same, the Remote goes black, windows says "an error occured with the device" and the remote boots to "No Configuration".
I remember your gold remote, but cannot remember exactly if this was the thing you encountered ?
Error during BeoLo and reboot with "No Valid Configuration" sounds familiar but I can't recall the details.
Will try to find the thread and read it again if it brings back some memories.
After reading back all the thread, it seems my problem was only related to "low battery" issues, so I can't help, sorry.
matador43: After reading back all the thread, it seems my problem was only related to "low battery" issues, so I can't help, sorry.
No problem, I am beginning to actually not like these remotes anymore :) Now another of my Beo6's has issues with the touch of the bottom row of buttons, when pressing any of them, it will activate the "lower hardkeys", or the second row button instead :)
I think its not a remote problem, its more likely caused by the extensive use of those remotes.
What happen when you have more than two Beo5/6 is that over time, the pulp of your fingers become flat and no longer can assure precise touch over the screen thus creating wrong activations often above or under the key you want to trigger (cause by the angle of the finger).Contact member Dillen, he can provide new finger tips with the correct roundness and instruction to fit then to your hands.
More seriously, it would be sad if you dont like Beo6 anymore since I believe you have plenty of them and have done so much for their preservation.At the same time, if you look at Beodex, you'll see their actual price range is above… 1500€!
Cheers!
matador43: I think its not a remote problem, its more likely caused by the extensive use of those remotes. What happen when you have more than two Beo5/6 is that over time, the pulp of your fingers become flat and no longer can assure precise touch over the screen thus creating wrong activations often above or under the key you want to trigger (cause by the angle of the finger).Contact member Dillen, he can provide new finger tips with the correct roundness and instruction to fit then to your hands. More seriously, it would be sad if you dont like Beo6 anymore since I believe you have plenty of them and have done so much for their preservation.At the same time, if you look at Beodex, you'll see their actual price range is above… 1500€! Cheers!
It is funny there are so many different issues with them, but as you say, it must be because people use them differently. Some has been used a lot, some almost not at all.
This one with the touch issue, has been working for a long time, almost not used when I got it, and I have only used it for different testing purposes, it has been without battery for some time while I used its battery to see if I could get the one this thread is about, back to life. I then put in a new battery in the touch issue subject, and now the touch is causing problems. So the only thing is that it has been without battery for some weeks.
Weird.
I will not give up on the Beo5/6, since they still has great value if they are programmed correctly, but I suspect they all are just in a waiting game before they start dying slowly :(
Weebyx:I suspect they all are just in a waiting game before they start dying slowly :(
Make sense since they're a lot around with touch pad problems. I've once with unresponsive screen I use only with hard keys: the display still works so with a little bit of "tree" programming it still allows a lot of controls.
If I understand why old beomasters can age due to caps drying, I dont really understand why this things get corrupted in time.I mean for 90's up items there is always a physical reason for them to fail: foam, belt, overload, drying connections (Beolink 5000 screen), or bad servicing…
I can understand the beo6 is not as rugged as the demo clip shows and it won't really stand a 1 meter fall.But failing out of the blue like this, its not something I'm used to…