Ok, here I am, I've missed the posts about the RAM, thank Draco to call my attention to this. oxygen84 and kevin I'm sorry about your issue. I believe you already asked for support through the contact form right? http://www.udoo.org/support/contact-us/ If now, do it, if yes, PM me with your email address so I'll check for your request and reply to you via mail. We are moving from a too basic mail based support system to something more adequate, aka ticketing system.
Hi andcmp, I've sent you a PM with my email address. I also tweeted @UDOO_Board (I'm __kb) as I wasn't sure the best way to get your attention. Thanks for your help!
Thanks; how long do you think it'll take for someone to respond, now that it's in the ticketing system?
@andcmp (or anyone): should I expect to have heard from the support ticket yet? I've had a non-working Udoo for a few weeks now, and no response from the Udoo team. Even just knowing that someone's looking in to whether it's a systemic problem with manufacturing or an unlucky 1-off (although at least 2 of us have the problem...) would be a start. Or alternatively something like "there's a lot of support enquiries, bear with us..." or "we're dispatching replacements after the Kickstarter boards have all been sent" or some other nugget of information I can cling on to. I like the idea of the product and hopefully I'll enjoy using it, and I understand that there's a lot to do around the end of the Kickstarter campaign, but a little communication can go a long way. Thanks!
Extracted zip reveals cpgz file, fixed with 7zip on OS X I just thought I would post this for anyone that maybe experiencing the same issue. I downloaded both the android 1.1 and ubuntu 1.3 dual image zips and extracting on OS X Mavericks yields *.cpgz files for both archives. After a few attempts using these files and failed boots, I installed 7zip from Homebrew, http://brew.sh/. Code: brew install p7zip Open a new shell, or use the direct path to 7z, ex: Code: 7z x udoo_dual_ubuntu_1.3.zip Now you should see a .img file and you can follow the sd bootable image instructions. Has anyone else experienced the same?
Yes it's a known issue, in fact in our Tutorial "Creating a bootable Micro SD card with Mac OS X from image" we suggest to use StuffIt Expander or Zipeg to unzip the image file. http://www.udoo.org/ProjectsAndTuto...rd-with-mac-os-x-from-image/?portfolioID=1394
I've received mine and it looks like it's working beautifully! Now... what was the root password on the default boot...
Hello. At Nov.09 I send to info@udoo.org message. My UDOO Quad seems dead - serial output shows nothing. At Nov.13 I got a reply "your request has been inserted in our system". There was last message from UDOO team. This is not funny. What should I do with dead device? I want to send it back to UDOO team to exchange on normally working device. Is that possible?
Hi Cib0rg, sorry to hear that. We switched to a more efficient customer care method using a ticketing system instead of the email. Regarding your issue: please try to follow this troubleshooting: http://www.udoo.org/faq-items/why-my-udoo-wont-boot/ and if nothing happens open a ticket in our customer care section (http://www.udoo.org/customer-care/) asking for a RMA (tell that you already tried the troubleshooting procedure). In this way you'll return the dead UDOO and we'll send you a new working one. Let me know and sorry again for the delay.
It has two UDOO(s). One is started normally. One does not BOOT. It tested using the same power supply and the same SD card. Since it is initial failure clearly, I want you to exchange. Order # 100002047
