The Problem That we are having is the Oculus Go won't turn on after Factory Reset last week. I Tried Everything, and it not work, I was Removing an account from it, after the factory reset It only showing the Oculus Logo. It turned into a brick. It also showing the Orange Light.
0
Comments
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
While other big players in the Android games have no issues to provide firmwares for their customers, Oculus forces us to hope nothing ever goes wrong.
If my phone or tablet crack the §$%&" and won't work proerly anymore then I just install the firmware fresh and am ready to go after putting my backup on it.
Worst case means about 2 hours of work.
For a GO the story is a few days of support talks, sending the thing in and waiting to get it back one day.
I mean: Oculus does block updates anyway, so doing them properly in the background and without the need for a paired device would prevent all this.
Same of course for the most obvious: Providing download links to install the firmware through the recovery using a USB stick.
Since the GO came out I see the factory reset brick problem about once a week somewhere.
Not so much of a support problem but more a problem of product quality.
I had a real lot of Android devices over the years but so far not a single one that turned itself into a brick through a firmware update or factory reset ROFL
Sadly users only find it once it is too late.
I have to agree with the statements made already by so many users - the "Please contact us!" reply is actually not helping anyone.
The actual problem is not a factory reset, not even a pending update.
The real problem is the impementation that Oculus uses.
A forced pairing with another device is not just totally inconvinient but also the sole source of many problems, including the bricks more and users need to send back for a fix.
Let me try to explain:
If the device needs or just receives a factory reset than usually this is a user choice.
Using the standard update procedure as on any Android device is a great idea - if you guys would not have stuffed it up by the forced pairing to another mobile device!
It is only a few lines of code that need changing.
Either make the update "pending" or simply check for updates AFTER the factory reset is finnished - and that would be once the device is fully running again.
Works totally fine on all Android devices I own, so it really is not hard to do if you think before using code that renders the device useless.
As for the fix:
All that is needed is a clean flash of the latest firmware, preferably of course in the form of a block based update as used for example on the Nvidia Shield or all Google conform devices.
In the most simple form even a flashable patch that just deletes the update flag and check for next boot will do fine.
My suggestion: Start listening to the ongoing problems and provide a real fix in the form of downloadable firmwares that can be flashed through fastboot with a simple script - ever heard of the famous "flash-all.bat" ?
A user could then just download the firmware, connect the GO to his computer and run the batchfile to get a working device.
No weeks of waiting, no fear the GO might get lost in the postal system, no ruined xmas...
Either way I can only suggest that Oculus starts cleaning up the mess their restriction cause as the bricks keep piling up on a weekly base.
Some might even say this all qualifies for a recall as the current system is toally failing
Only good that it is not a car that fails to work with a stuffed up computer because the driver had a flat battery and did a "factory reset" by putting a new one in ROFL
I wonder how long customers would tolerate this if they needed a tow truck instead of a return parcel....
If you actually are having problems, not just trolling (like dragging up a 1.5 yo thread, lol!), then share these and maybe you can get some help.
Edit; Plus, you may want to refer to another Go thread on this;
https://forums.oculusvr.com/community/discussion/71721/factory-reset-and-firmware-update-the-right-way#latest
Custom built gaming desktop; i9 9900k (water cooled) oc to 5ghz, gtx 1080 ti, 32 gb 3000hz ram, 1 tb ssd, 4 tb hdd. Asus ROG Maximus xi hero wifi mb, StarTech 4 port/4 controller sata powered usb3.0 pcie card, PCI-E PCI Express to USB 3.1 Gen 2 card, Asus VG248QE 1080p 144hz gaming monitor, Oculus Rift cv1 w/2x sensors, Vive Pro w/2.0 base stations/Index controllers, Quest 1 w/Link and VD wireless (good/close 5Ghz wifi and PC with Ethernet cable to my Router).