How to Install Home Assistant Server on an ASUS CN60 Chromebox - Intel

Home Assistant OS installation on a Chromebox is reliable but is not as tested as the NUC installation. Because it is a budget-friendly option it gives automators a low-cost means of getting started with Home Assistant. See also Home Assistant x86 Install and these YouTube videos: Chromebox CN60 How to and Install Home Assistant
Enable Chromebox Developer Mode
Remove the write-protect screw
Attach a keyboard, mouse, monitor, and power cable
While inserting a pin and keeping the Recovery Button pressed, press the power button
Once a white screen is displayed remove the pin (It will say “Chrome OS is missing or damaged”)
Type Ctrl+D and then briefly reinsert the pin (The screen will black out for 2 or 3 seconds and then display “OS verification is Off”)
Do not touch anything (it will now boot into and display the developer mode)
Continue with Step 2
Install Custom UEFI Firmware
Connect to the internet using a Wi-Fi network or an ethernet cable Do Not Log In
Press Ctrl+Alt+F2 and allow the shell terminal to load
Type: chronos
Type: cd; curl -LO https://mrchromebox.tech/setup-kodi.sh && sudo bash setup-kodi.sh
At the options menu, select: Install/update: Custom UEFI Firmware (the firmware will now be flashed)
When back at the options menu: Exit, and Power Off
Prepare a USB Flash Drive using a PC
Download the latest Ubuntu LTS image file and flash it onto a USB drive (16GB or larger) using Rufus or Balena Etcher. If it's an option, maximize or allow up to 16GB of persistent storage.
Shut down the PC and boot from the USB Drive using the Try Ubuntu option
Once Ubuntu is running, connect to the internet
Open a terminal and install the necessary software:
sudo add-apt-repository universe
sudo apt install libfuse2
Close the terminal and use Firefox to download:
The latest Home Assistant OS Generic x86-64 image from the Home Assistant website. (The same or similar to: https://github.com/home-assistant/o...s/download/9.5/haos_generic-x86-64-9.5.img.xz)
Balena Etcher for Linux x64: https://www.balena.io/etcher
Right-click on the Balena Etcher file and select properties. In permissions enable: Allow executing file as a program
Power down Ubuntu (the flash drive is ready)
Install the Home Assistant OS
Insert the flash drive into the Chromebox and power on
When the bunny logo displays, press Esc to open the boot manager
In the boot manager, remove all other boot options, and in the boot menu, boot from the USB drive
Run Ubuntu using the Try Ubuntu option
Once Ubuntu is running, run Balena Etcher by double-clicking on its file
Using Balena Etcher, flash the Home Assistant file to the System Drive
The flash process usually completes perfectly, however, an error will usually be indicated or the system will (appear to) freeze up. Do not be alarmed, allow a few more minutes and then power down, removing the flash drive.
Power on, and within a few minutes “Home Assistant” will be displayed in large letters at the top of the screen. Success.
Begin using Home Assistant
Set up your box in its desired location, connecting its power adapter and connecting to the internet via an ethernet cable
Press the power button. Within 15 to 20 minutes you will be able to configure Home Assistant via the local webpage: http://homeassistant.local:8123

Thanks for sharing the instructions for installing Home Assistant on a Chromebox! It seems like a detailed and comprehensive guide. I'm sure it will be helpful for anyone looking to set up Home Assistant on a budget-friendly device.

Related

Dual Booting ubuntu and windows 8.1 on the Pipo W2

Ok, So I thought I would post this guide to installing ubuntu 14.04 on the Pipo W2. This guide might help on some of the similar tablets out there too, like the voyo a1 mini. But I can't be certain about the others
Also, to give credit where credit is due, this guide is mostly adapted with little adaptation from the following guides:
http://asus-t100-ubuntu.blogspot.com/
http://linuxnorth.wordpress.com/2014/08/23/installing-linux-on-the-asus-transformer-book-t100/
and work on wifi wouldnt be possible without help on the ubuntu forums
http://ubuntuforums.org/showthread.php?t=2249936&p=13151763#post13151763
and the wifi drivers were posted for the rlt8723bs by this guy here
http://www.hadess.net/2014/09/and-now-for-some-hardware-onda-v975w.html
First the information as to what works, and what doesn't . As of 11/02/2014 stock ubuntu 14.04 works, the touchscreen works. However wifi, sound, bluetooth, suspend, hibernation, power button, volume buttons, and the micro sd card do not.
Updating to newer kernels changes what works and what doesn't. I was able to get wifi working on kernels 3.16.2 and the power button, and volume buttons, but the touchscreen didn't work on 3.16.2 on kernels 3.17.0 and 3.17.1 I was able to get wifi working, and the touchscreen works, but the volume buttons and power button didn't. you can still boot up with these later kernels, but it's not as easy. I had to go into ubuntu advanced options and boot to recovery for each kernel, then from the recovery menu boot to desktop. A bit of a pain. I think it's a graphics related problem, and I'm working on it, but as of this writing, the kernels I tested from 3.15.x on wouldn't boot without this. (if they booted at all, 3.18.rc2 didnt boot at all)
I am still testing various kernels, to see which one seems the most stable and enables the most features I will update this as new information is worked out.
Ok, starting. Part 1. The Prep work.
--------------------------------------------------------------------------------------------------------------------
Things you will need. A USB hub, a USB keyboard, USB wireless adapter, (or USB LAN adapter) and a mouse. (or trackball) And a USB thumbdrive of course. Without these things, you wont be able to complete the installation easily. Plug them all in, and connect them to the tablet.
Download An ubuntu 14.04.1 lts image (you can substitute ubuntu gnome, 14.04.1 lts, or lubuntu 14.04.1 lts image etc) here's a link to Ubuntu though. you can do this on your tablet, or your desktop. up to you.
http://www.ubuntu.com/download/desktop
Select 32 bit. (NOT AMD64) and click on download, then unless you wish to donate, click on the link that says "not now, continue to the download"
now download Rufus from here
http://rufus.akeo.ie/ and use rufus to install the ISO image on your thumbdrive by clicking on the disk icon next to ISO image near the bottom, and selecting the ubuntu-14.04.1-desktop-i386.iso file (or ubuntu-gnome-14.04.1-desktop-i386.iso or whatever flavor you downloaded) The top option on the rufus menu should automaticly list the thumbdrive, if it doesnt, select the thumbdrive unless you want to screw up whatever drive it's pointing at. (you might be able to make your system unbootable if you don't do this carefully so PAY ATTENTION) Is it listing your thumbdrive? if so, click on start on rufus and let it finish.
now you need to download this file here: https://drive.google.com/folderview...&usp=sharing&tid=0B9C1WK1FQhjfcXNrbzN6djQzajg
Leaving the thumbdrive in, unzip the unpackit.tar.gz file to the thumbdrive root directory, and overwrite all files. when you are done, if you did this on your desktop, safely remove the thumbdrive and plug it into the hub connected to your tablet. if you did this with your tablet, leave it plugged in and continue.
Now, for the windows setup.
First, get to control panel. (you can access it by pressing the windows key to get to the start menu, then going to PC settings, and selecting control panel) click the view to small icons, then click on Power Options. Next click on "Choose what the power button does" and from the next menu, click on "change settings that are currently unavailable"
now scroll down and uncheck the box that says "turn on fast startup" then save.
IMPORTANT NOTE: if you want to screw up windows, so that it wont boot, do the next step in a hurry and pay little attention to what you are doing.
Next you need to set up up some space for Ubuntu. (NOTE: you must have 8-10GB or so empty space on windows partition first, so if you don't have 8-10GB free, go delete some things until you have enough space free.) Ready? Ok you need disk management. go to your desktop then right click on on the start button. and select Disk Management from the menu Expand the window so you can see what you are doing, and right click on "Windows (C select "Shrink Volume" from the list. You will see a window that lists
"Total size before shrink in MB"
"Size of available shrink space in MB"
"Enter the amount of space to shrink in MB"
"Total size after shrink in MB"
Now, using the "Enter the amount of space to shrink in MB" option, type in 10000 or so, (8000 works too) to shrink the volume by 10 gb or 8gb (yes I know it's overly rounded, forgive my OCD) and leave the space as unallocated. do NOT shrink to the max it will let you. always give windows some space to work with.
IMPORTANT NOTE: If you shrink the volume by more then the free space, you will probably screw up your windows installation. I am NOT going to help you figure out how to fix windows, if you ignored these warnings and screw it up. Mostly because I haven't the faintest idea how to fix your windows installation if you shrink the volume too much.
Next eject any Micro SD card you have in the tablet, and pull it out.
Lastly for windows side of things, go back to your desktop, and again right click the start menu, open the shut down options list, then hold shift down and click on restart
You should now be faced with a blue screen with several options, click on "Use a Device" then select "UEFI:Removable Device" and allow the tablet to restart. it will boot back up to windows, but now you should have the USB drive in your UEFI settings boot options. Power the tablet down, all the way, and this time, when you see it start to boot up, press f7 over and over and over until you see the boot option menu, select your thumbdrive and hit enter.
You should be faced with the Grub menu now, press e to edit, and arrow over to where it says video=VGA-1:1368x768e delete the 1368x768 and replace it with 800x1280 now the end of that line should say:
video=VGA-1:800x1280e reboot=pci,force
then hit f10 to boot. it should take a few min, but boot to desktop, if it doesnt, power off the tablet by holding down the power button for 12 seconds, and try again. If it doesn't boot and just errors with rpmb timeout errors for more then 5 min, just try again. (and unplug anything but the keyboard and usb thumbdrive from your hub until you reach desktop.
Once you hit desktop, wait a good 15 seconds before touching anything, otherwise kernel panic hits sometimes.
Once you are at your desktop, click in the upper right corner and go to system settings, and go to Brightness & Lock and uncheck the box that says "dim screen to save power" and change "Turn screen off when inactive for" to never.
Next exit that screen and connect to your wifi or make certain your wired network is working. check to make certain you have internet access. then hit ctrl-alt-t to open a terminal. type the following
sudo umount /dev/mmcblk0p*
now kill that window. you are now ready, FINALLY ready to install ubuntu.
Part 2 : Installing Ubuntu
-------------------------------------------------------------------------------------------------------------------------------------
Click on the icon to install ubuntu, then when the window pops up, select your language and continue
On the next window check both boxes to install updates and third party software, (third party is probably optional) and click continue
Now, we wait. wait wait wait and wait. the next window will take quite a while to pop up. probably rpmb timeout errors as it checks all the drives. might be 30 min or so. no way to speed this up.
Now PAY ATTENTION: Next window, click on the last option that says "Something Else" if you click standard install, you can kiss windows goodbye.
Following window, will list all your drives. do you see that 10000 or 8000 MB of space you created earlier? nice and round and most importantly, easily recognizable? click on that it should say "free space", then click on the "+" button., when the create partition box pops up, select logical instead of primary, and select the mount point to / and Use As: should say "Ext4 journaling file system" it will list the partition as something like mmcblk0p5 (might be mmcblk0p6 or mmcblk0p4 or whatever. pay ATTENTION to this, write it down. you will need it later.
don't worry about swap space, the installer crashes if you try to set any space aside as swap space. so just leave the entire unallocated space for the ext4 partition
click on "Install Now" and a warning will pop up, just click continue (this is a warning about it suggest swap space. you cant, so just continue)
select your timezone, keyboard layout, then username, computer name, password on the next screens, and DON'T encrypt your home partition. and let it install
It should run for a while and finish installing
When it finishes, don't reboot, and instead exit the installer and power off instead of rebooting. you will see it stops after system halted. once you see that, hold the power button for 12 seconds to power off the device.
Leave everything plugged in, and power on, when you see the grub menu, this time hit "C" to drop to a command line. and remember the number at the end of your partition where you installed linux? get out that paper. you need it now. now type:
linux (hd1,gpt5) (dont hit enter yet) if your partition was 6 instead of 5 (mmcblk0p6 instead of mmcblk0p5) then instead of gpt5 use gpt6 etc.
now continue and add /boot/vmlin so that the command line reads
linux (hd1,gpt7)/boot/vmlin now hit Tab
it should autofill and read something like
grub> linux (hd1,gpt5)/boot/vmlinuz-3.13.0-32-generic
still dont hit enter. now add root=/dev/mmcblk0p5 (or whatever your partition was) followed by video=VGA-1:800x1280e reboot=pci,force
the final line should read something like
grub> linux (hd1,gpt5)/boot/vmlinuz-3.13.0-32-generic root=/dev/
mmcblk0p5 video=VGA-1:800x1280e reboot=pci,force
NOW you can hit enter.
next line. type:
Initrd (hd1,gpt5)/boot/initrd and press Tab again
now it should read something like
grub> initrd (hd1,gpt5)/boot/initrd.img-3.13.0-32-generic
now hit enter
now type boot then hit enter.
it should boot to desktop now
ok now we need to fix grub so you can boot without the thumbdrive in
make certain you are connected to the internet, via wired or usb wireless adapter, and open another terminal by hitting ctrl-alt-t
now copy and paste this in and hit enter:
sudo apt-get update && sudo apt-get install git bison libopts25 libselinux1-dev autogen m4 autoconf help2man libopts25-dev flex libfont-freetype-perl automake autotools-dev libfreetype6-dev texinfo
when it asks to install hit a y and let it continue
when it finishes and you see a terminal prompt again, type or copy:
git clone git://git.savannah.gnu.org/grub.git
and hit enter at the next prompt type
cd grub
followed by enter again, then type or copy:
./autogen.sh
hit enter again and at the next prompt type or copy:
./configure --with-platform=efi --target=i386 --program-prefix=""
enter again, at when it finishes, at the next prompt type
make
and hit enter. At the next prompt (will take a while to finish) type or copy:
cd grub-core
and hit enter. then copy and paste in:
sudo ../grub-install -d . --efi-directory /boot/efi/ --target=i386
hitting enter again. At the next prompt, type or copy and paste in:
cd /boot/efi/EFI
hit enter then paste in:
sudo cp grub/grubia32.efi ubuntu/grubia32.efi
and hit enter
now we get to edit grub.
next command you type or paste in should be:
sudo nano /etc/default/grub
and we get to edit the following line
GRUB_CMDLINE_LINUX_DEFAULT
find that line, and delete the words quiet and splash. and replace with
video=VGA-1:800x1280e reboot=pci,force
hit ctrl-x and save as you exit.
now we have the LAST command you need to type here. it's:
sudo update-grub
and of course hit enter.
once you have the terminal prompt again, you can exit the terminal, and power off the tablet again. (you will need to hold the power button for 12 seconds after system halts. get used to this.)
Now, I'm going to assume you don't want ubuntu to be the default OS to boot into yet. if you really do, skip this part, if not, continue.
Disconnect the usb thumbdrive and then press the power button on your tablet., Now press F7 over and over until the UEFI boot menu shows up Select "Enter Setup"
arrow over to the boot menu, and select windows as the number 1 option.
now, your tablet should be set up, to boot into windows by default.
To boot to ubuntu, use F7 to enter the boot menu on startup, and select grub and ubuntu
you can leave it with grub as the bootloader if you want. there are ways to configure grub to boot into windows by default, but you will need to keep a keyboard with the tablet at all times then. since sometimes it wont auto boot, and will wait forever for the enter key to be pressed to select your boot option.
I'll add information to my next post to explain how to rotate the screen in ubuntu, as well as information for updating kernels and getting the internal wifi to work.
ok, tips and tricks. to rotate the screen, you need to enter two commands into the terminal
first to rotate the view to the right, you type:
xrandr -output VGA1 -rotate right
on my most recent installation (ubuntu mate 14.04) this didnt work. so I needed instead to use
xrandr -o right
then hit enter of course. this WONT rotate the touchscreen. to rotate that, we need xinput.
first you can type xinput list to list what devices are present. I assume you will see FTSC1000:00 2808:5056 listed. if so, this will work, if not, you will need to adjust this command to fit what you see listed. (most important if you are adapting this guide to another bay trail tablet other then the pipo w2) the command that you want, assuming that's your touchscreen is
xinput set-prop "FTSC1000:00 2808:5056" "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
and hit enter of course. your touchscreen should now be rotated to the right as well,
-----------------------------------------------------------------------------------------------------
ok, Wifi, to get wifi up and running, you will break screen rotation. Also it will break your normal boot process, requiring you to boot though advanced options for ubuntu, and recovery mode after that. The wifi is also unstable, and prone to hanging, requiring you to disconnect and reconnect at random intervals. It's not a perfect workaround, pretty far from it in fact, but it does at least prove the wifi is possible to get working. we probably need a better driver. Overall, you will get much much MUCH better performance with a usb wifi module. but that's extremely annoying to use so feel free to experiment here.
step one, go to here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc4-vivid/
and download the following files. http://kernel.ubuntu.com/~kernel-pp...eneric_3.18.0-031800rc4.201411091835_i386.deb
http://kernel.ubuntu.com/~kernel-pp...1800rc4_3.18.0-031800rc4.201411091835_all.deb
http://kernel.ubuntu.com/~kernel-pp...eneric_3.18.0-031800rc4.201411091835_i386.deb
now copy them to your desktop in ubuntu.
now in terminal type:
cd Desktop
then type:
sudo dpkg -i linux*.deb
once it's done, reboot your tablet. now go to grub, and select advanced options for ubuntu, then select recovery mode for the 3.18-rc4 kernel. and resume normal boot once you see the recovery menu show up
this should allow you to boot to desktop. after which go back to terminal, and type the following commands in, one line at a time of course, waiting for the next prompt before typing the next line
sudo apt-get install build-essential linux-headers-generic git
git clone https://github.com/hadess/rtl8723as.git
cd ~/rtl8723as
make clean
make
sudo make install
sudo depmod -a
sudo modprobe 8723bs
reboot. go through the recovery mode menu again to boot to desktop. wifi should now be working. you will need to use recovery mode to boot from this point on. since 3.18-rc4 wont boot without it. Be forwarned, suspend mode breaks wifi it seems. one time of the suspend, and you will need to reboot to get it working again. So I would suggest disabling everything applicable to your tablet screen shutting off. also, the wifi is extremely unstable. as noted above. it can quit for no reason, and need to disconnect and reconnect to use it more.
information for how to install the wifi driver was gained here:
http://ubuntuforums.org/showthread.php?t=2249936&p=13151763#post13151763
information as to why the wifi won't work, even with the drivers, on 14.04 default kernels was obtained from this thread https://bugzilla.kernel.org/show_bug.cgi?id=67921
would this work on a clovertrail device?
I don't think so. I don't think clovertrail is Linux friendly at all. Clovertrail+ should be, but not clovertrail. However the clovertrail+ devices I know of are the Asus padfone the Asus zenfone and the lenovo k900. All of which use droidboot. (Can't load grub). And have PowerVR graphics which are not open source, so no Linux drivers. There are probably more clovertrail+ devices out there I just haven't looked into them much.
I added information to the second post about screen rotation, and relevant information to the workaround for wifi. Be advised that it's not a perfect workaround. wifi works, and so does the power button. but it requires booting through recovery mode
It's cool. Do you know whether it works well on the latest W2f?
No idea. Probably though. But I can't be certain. I don't have a pipo w2f to test with.
Arch Linux
Have you tried to install ArchLinux on this tablet?
nope, sorry so far i've just experimented with ubuntu and fedlet. I have not installed fedlet, just booted and looked around a bit.
StridAst said:
nope, sorry so far i've just experimented with ubuntu and fedlet. I have not installed fedlet, just booted and looked around a bit.
Click to expand...
Click to collapse
I tried this guide , my interest was just trying to live mode ubuntu , but unfortunately the screen is distorted even changing resolution.
My though is a Pipo W6 .
Did you try to start Live Android X86 ?
Tony Evo said:
I tried this guide , my interest was just trying to live mode ubuntu , but unfortunately the screen is distorted even changing resolution.
My though is a Pipo W6 .
Did you try to start Live Android X86 ?
Click to expand...
Click to collapse
I've not tried android at all on mine. I keep meaning to do so, but have not found the time yet. Hmm though on the W6. did you try setting resolution settings at 1200x1920 or just 1920x1200? which number you put first matters and can result in a distorted screen. the w2 is listed as 1280x800 resolution, but to get ubuntu to work without the screen going all wonky, you have to reverse the numbers to 800x1280.
I tried different resolutions, the problem is that the screen is like tripled
---------- Post added at 04:37 PM ---------- Previous post was at 04:13 PM ----------
The solution was obvious ... Put the real screen resolution 1920x1200
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Touch screen no works
hmm, which kernel are you using? I've found some of the newer kernels made the touchscreen on the W2 work, some made it not work. things to try.
first post the results of
xinput --list
that might offer some clues. also you could try downloading and installing the 3.18.1 kernel from here
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.1-vivid/
assuming you are using the 32 bit version not the 64 bit version of ubuntu, you would want to download both of the generic i386.deb files, (not the low latency) as well as the all.deb file. I'm assuming that updating the kernel on a live-USB works. I've never tried it actually.
to install you go to terminal, and assuming the files are placed in desktop, type:
cd Desktop
sudo dpkg -i linux*.deb
reboot and see if it helps. if not, you can try some of the other more recent kernels. I've noticed a huge difference from one RC to another. a rc1 file might have working touchscreen and power buttons for the W2, and a rc2 file breaks the touchscreen but the power button works, while a rc3 would have the touchscreen work again, but fail on the power button, etc. see here for all the other kernels. top of the list is the oldest, bottom is the most recent.
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Sorry for my slow replies, I've only really had any spare time in the mornings lately.
StridAst said:
hmm, which kernel are you using? I've found some of the newer kernels made the touchscreen on the W2 work, some made it not work. things to try.
first post the results of
xinput --list
that might offer some clues. also you could try downloading and installing the 3.18.1 kernel from here
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.1-vivid/
assuming you are using the 32 bit version not the 64 bit version of ubuntu, you would want to download both of the generic i386.deb files, (not the low latency) as well as the all.deb file. I'm assuming that updating the kernel on a live-USB works. I've never tried it actually.
to install you go to terminal, and assuming the files are placed in desktop, type:
cd Desktop
sudo dpkg -i linux*.deb
reboot and see if it helps. if not, you can try some of the other more recent kernels. I've noticed a huge difference from one RC to another. a rc1 file might have working touchscreen and power buttons for the W2, and a rc2 file breaks the touchscreen but the power button works, while a rc3 would have the touchscreen work again, but fail on the power button, etc. see here for all the other kernels. top of the list is the oldest, bottom is the most recent.
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Sorry for my slow replies, I've only really had any spare time in the mornings lately.
Click to expand...
Click to collapse
But I have a problem .
I dowload ubuntu 14:04 32bit , I create the key with rufus , once finished the process I copy and paste the files that you had put in the folder called " unpackit " .
Starting my PIPO , I press esc , I go in and do the boot devices on the pendrive .
and everything ok .
If you want to try to create another pendrive with another Distro ( 64bit ubuntu , fedora or other ) when I create the key , I start the PIPO but I do not recognize the key ,
can not find the pendrive between devices boot .
Install a 64-bit version of Ubuntu, with a 32-bit bootloader
Take a look at this link: linuxnorth,wordpress,com/2014/12/11/installing-64-bit-linux-on-the-asus-transformer-book-t100/
(change , with .)
I tried to install Arch Linux but couldnt boot it, neither any Arch-derivated. I tried also fedlet and its not bad at all.
Sorry if my questions are a bit stupid. Using this instruction we can install ubuntu OS as the 2-nd OS in parallel with windows, can't we?
If I have ubuntu installed on my tablet am I able to run android apps on it? Is ubuntu equals to android?
StridAst said:
Ok, So I thought I would post this guide to installing ubuntu 14.04 on the Pipo W2. This guide might help on some of the similar tablets out there too, like the voyo a1 mini. But I can't be certain about the others
Click to expand...
Click to collapse
Superb! Works 100% on my £20 Voyo A1 Mini, thank you!
Better guide, no offence (and no need to edit anything in Grub):
https://github.com/Manouchehri/vi8/blob/master/Ubuntu_instructions.md
Working (for the majority of the hardware) on my Voyoa A1 Mini (5V2A version.)
mbwf said:
Better guide, no offence (and no need to edit anything in Grub):
https://github.com/Manouchehri/vi8/blob/master/Ubuntu_instructions.md
Working (for the majority of the hardware) on my Voyoa A1 Mini (5V2A version.)
Click to expand...
Click to collapse
no offense taken! much appreciated posting a newer/better guide that's the beauty of xda. theres always something newer and better showing up. I wish my pipo tablet still worked so I could experiment with it, But a factory reset with windows 10 bricked it with the TPM bug. It wants confirmation to clear or to not clear the Trusted platform module, but this request boots up before usb. so there is no way to answer the request. no buttons work, and no keyboard input works. =/ afaik its bricked for good.

[Q] REEDER W7iC TABLET=EMDOOR EM-I8170 WINDOWS 8.1 TABLET WON'T TURN ON

Hi,
Sorry, for my poor English. I'm from Turkey. I bought a Reeder W7iC windows Tablet in Turkey. It's the same EMDOOR EM-I8170. I installed the wrong bios file, while android trying to install. Now, tablet won't turn on. Back light is on. I connected keyboard and mouse on usb otg. It all works. l I found the original bios file. How do i run again it? How do i install android? Thank you in advance for your help.
Tablet specifications:
Intel Baytrail-CR Z3735G, Quad Core
1GB DDR3 FLASH 16GB
Windows 8.1
16:9, 7" 1024*600 IPS
Does it have hdmi? Then connect it to a monitor or tv. What happens if you keep pressing both Vol- and Vol+ and then power on the tablet?
Please send a link to the correct bios, then I can try to make a bios flash package for a usb pen drive.
Yes it has hdmi. I connected to tv. I keep pressed Vol+ and vol- and power on the tablet. dnx mode on the tv. Then, what will i do?
I can't write outside link because i'm new users. [*] is [.]
Correct bios file link:
www*reedertablet*com/reeder/yazilim/reeder_w7ic/bios/ReederW7iC_BIOS_UPDATE_V1.6.8.zip
I want to install android.
EM-I8170 Android Files is here. There is bios file, too. I think for android.
yiyun*baidu*com/wap/link?shareid=772798033&uk=3053780477&third=0&dir=%2Fintel%2F7%E5%AF%B8android-I8170&page=1&
How can i install android to tablet? Thanks for reply.
Ok sounds good. So first thing to do is to flash the original bios/firmware. I will prepare a package in the next half hour. You need a usb hub, a usb stick, a keyboard. Power off the tablet now and try to enter bios menu (press del or escape or f12) and post which bios version is installed. Best is to post a photo. PS: I don't own this tablet and will only help you to recover it with the original bios.
I'm at work right now. I can try them when you get home in the evening. I'll write the results.
Assuming you could enter bios and you have a USB hub, usb stick and keyboard, then you can flash the original bios as follows:
============
Flash new bios
============
1. Connect the USB hub to Reeder tablet and plug in the keyboard and the USB thumb drive containing the new bios files. Power on the device and press DEL or Escape to enter into BIOS.
2. Navigate to "[email protected]", and then choose "Launch EFI shell from filesystem device"
3. After entering shell, type FS?: and then press ENTER
( ? stand for a numeric character. It depends where your USB drive resides, for example, if your USB drive is at FS4, you type FS4: You can always try between FS0 and FS4 )
4. Then type dir and then press ENTER to check if you selected the correct drive
5. Type fpt32.efi -f ReederW7iCBIOS_V1.6.8.bin and press ENTER
6. Type fpt64.efi -f ReederW7iCBIOS_V1.6.8.bin and press ENTER
(PS: you may get an error after either running fpt32.efi or fpt64.efi, but make sure at least one of the flash commands succeeded !)
7. Type exit and press ENTER
8. When you return to BIOS, choose "save changes and reset"
Good luck!
Note1: there is a readme.txt which describes how to install dual-boot Android/Win8.1 on a Voyo A1 Mini (also a EMDOOR tablet). This may be helpful for you to install Android on your tablet.
Note2: if you can't enter BIOS then we must try to flash your tablet using DNX protocol
I tried what you wrote. It installed bios from fpt64.efi. Installation completed. I selected Save Changes and Reset in Bios Menu. Frozen in bios menu. I closed the tablet keep power button. It won't turn on. Now, backlight is off. I think it hard brick. Is there anyone who can help me?
I connected to the tv with hdmi cable. Nothing happened.
Are you sure that bios was the original version? Check if battery is charged and also if you can still enter dnx mode.
İt was original bios file v1.6.8. Battery is full. I can't enter Dnx Mode. I connected it to pc. My pc don't see it m3 or m6 chip also. I think it isn't hard brick. It is Deep Brick.
Try also power on with only Vol+ pressed, alternatively with Vol- pressed. It could be it will then switch to 32-bit mode. Otherwise try disconnecting the battery from the mainboard and reconnect after a minute. If that doesn't help you must buy a flash programmer. There are various at Alibaba for about 30$ with cable connectors for on-board programming.
I tried vol+ or vol- and power button, vol+ and vol- and power button. Nothing happened. I cannot try disconnecting the battery. Because i haven't soldering iron. I think i'll send service it.
hi I have a tablet identical to the Reed W7İC.j'ai reinstalled the system and I managed to install all the drivers but my touch is shifted. that is to say, when I press for example the top of the screen is down there he reponse.dans the system at the touch function is written, limited touch support with 10 points of contact. help me if you plait.il is Emdoor EM-I8170. thank you in advance
devinci1 said:
hi I have a tablet identical to the Reed W7İC.j'ai reinstalled the system and I managed to install all the drivers but my touch is shifted. that is to say, when I press for example the top of the screen is down there he reponse.dans the system at the touch function is written, limited touch support with 10 points of contact. help me if you plait.il is Emdoor EM-I8170. thank you in advance
Click to expand...
Click to collapse
My emdoor tablet i82h not are showing display. Does i reprogrammer the BIOS and also not showing the display. came at with windows 10.

How to unlock your bootloader, without losing your data

Disclaimer: Use at your OWN risk. Data loss is possible. If anything goes wrong, don't blame us. We are only trying to help.
Credit:
Person who came up with the idea @Naman Bhalla
Person who edited the rawprogram0_64G.xml @Naman Bhalla
Source to the original OPO Recovery tool and the drivers.
Credit to TWRP, for their 2.8.6.0 image we are using.
Source to the bootloader unlocker.zip
Special thanks to @indest on OP Forums for being a real trooper and risking its life for the community.
Download:
Tool + Driver + Bootloader Unlock zip
Also, download the ROM you currently have. The exact same version number!
I repeat, you must have a copy of your current ROM!
Setup:
Download the above files
Connect your OPO to the computer (Windows 7, 8 or 10)
Press the volume up + power button (at the same time) until you feel a vibration
If your device says fastboot, press the volume up + power button again, till your screen goes black and you hear a sound on the computer.
Start> Device Manager
The following drivers should be detected automatically in device manager (Qualcomm HS-USB QDLoader 9008)
If ADB interface is seen, read step 3 again
If you see QHSUSB_BULK
Start> CMD (RunAs Admin)
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Reboot your computer
Enter Device Manager (start> device manager)
Right click QHSUSB_BULK> Update driver software> Browse my computer for driver software> Browse
Select <path of unzipped files>\Drivers\Qualcomm 2012
Check "include subfolder"> hit Next
Navigate to '<path of unzipped files>\OnePlusRestoreTool" folder
Right click on the "OnePlusRestoreTool(64GB).exe" and 'RunAs Administrator"
The program should start automatically doing its thing. If not, select the line that says 'COM' and hit start.
Once you see green text, hit log and make sure you have a BIG GREEN OK.
Unplug the device and press the volume down + power button till you feel a vibration.
It is important that you do not boot into your system, else, your data partition will suffer!
TWRP should now load. Once loaded, click Mount.
Connect your OPO to the computer.
Toggle off/on MTP (MTP should be ON)
Using your computer, transfer your ROM and the OnePlusOne-BootUnlocker.zip to your "Internal Storage".
Hit the back button
Hit install> go to /sdcard/OnePlusOne-BootUnlocker.zip > swipe to install
Then hit install again> go to /sdcard/<rom zip> (the one you started with) > swipe to install
Reboot device.
Isn't indest the best?
Awesome as always
pass for archives?
Hi, the download link is asking for a decryption key
Also does this still work in 6.0.1?

[GUIDE] [FIX] How To Fix Error Can't Copy Files To From Phone To PC/Laptop Via USB

How To Fix Error Can't Copy Files To From Phone To PC/Laptop Via USB​
All Operating Systems Start Here
Remove usb cable from phone/pc
Enable usb debugging mode on phone by
Going to phones settings
Scroll to bottom and select about phone
Tap on build number until it tells you that you are a developer
Go back to phone settings
You now have developer options at the bottom of the list above about phone
Enter developer option and turn on using switch at top right
Scroll down and enable Android debugging
Now Carry On Depending On Operating System
Windows users
In/Re-install the moto g5 drivers from the attachment in this post
Connect phone to pc
Look on your phone screen and a pop-up box will ask you if you want to accept the connection
Agree and make sure you tick always allow connection from this pc
Remove the usb cable
Restart Phone
Once booted insert usb cable
Change connection type in status bar to file transfer
Ubuntu Users
Press ctrl + alt + T to open terminal window
Type the following pressing enter at the end of each line
Code:
sudo apt update
sudo apt install android-tools-adb android-tools-fastboot
To check it worked type
Code:
adb version
You should get an output that looks like this depending on version installed
Code:
Android Debug Bridge version 1.0.32
Now type
Code:
adb devices
You will get an output that looks like
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
ZY3222SJMV unauthorized
Look on your phone screen and a pop-up box will ask you if you want to accept the connection
Agree and make sure you tick always allow connection from this pc
Then check your device is now authorised type
Code:
adb devices
now you will get an output like this
Code:
List of devices attached
ZY3222SJMV device
Notice unauthorized has now changed to device
Remove the usb cable
Restart Phone
Once booted insert usb cable
Change connection type in phones status bar to file transfer
You can now copy files from the phone to ubuntu
Very thanks bro Installed the drivers but my problem is first of all my phone is charging when connected to windows and it doesn't show any option like file transfer,photo transfer etc. But this problem was coming only from previous week before and all it shows file transfer but it won't work but USB tethering and photo transfer works but now it too doesn't working not even showing the options only charging is working. Pls help me to solve without those functions it's really hard to transfer files to windows.hope u would find solution and reply soon very thanks in advance (sorry for my bad English)

[GUIDE/TUTORIAL/HOWTO] Nvidia Shield Tablet K1 Stock to Android 9

[GUIDE/TUTORIAL/HOWTO] Nvidia Shield Tablet K1 (shieldtablet) to Android 9 / LineageOS 16
This detailed step-by-step guide helps you transform your Nvidia Shield Tablet K1 tablet with Android 7 to a fresher one with Android 9.
### I'll make a few notes using this style: PLEASE READ THEM.
Before going further, make sure you have the correct model.
Go to Settings > About tablet > Model number: SHIELD Tablet K1
Make sure you have latest official updates.
Connect tab to Wi-Fi network.
Go to Settings > About tablet > System upgrade. Download if update is available.
See all my tutorials at https://github.com/djibe/Android-tutorials
CHANGELOG
v1. Initial release
1) DOWNLOAD
- djibe Shield pack: https://bit.ly/nvidiashielddjibepack
(contains USB drivers + fastboot & adb + TWRP 3.7 recovery + Magisk root).
Unzip pack on Windows desktop.
- ROM AOSPExtended Unofficial: https://forum.xda-developers.com/t/...ded-rom-v6-7-unofficial-shieldtablet.4063675/
Download latest build: https://androidfilehost.com/?w=files&flid=306219&sort_by=date&sort_dir=DESC
OR Android 8.1 / LineageOS 15 Unofficial: https://forum.xda-developers.com/t/...for-shield-tablet-omx-camera-working.4276915/
Download latest build: https://androidfilehost.com/?w=files&flid=325335&sort_by=date&sort_dir=DESC
And suitable Bitgapps package
+ BitGApps ARM 9 v1.8+: https://github.com/BiTGApps/BiTGApps-Release/releases/
+ Tablet must charged to 100%.
2) INSTALL WINDOWS DRIVERS AND BACKUP
Go to the folder you unzipped earlier.
navigate to SHIELD_Family_WHQL_USB_driver_201801 > SHIELD.
Right click on android_winusb.inf and select Install. Confirm with OK.
Restart Windows.
Make sure Google/provider account is synchronized.
Backup photos, documents, contacts before going any further (ex: use the backupyourmobile app).
Connect tab to PC and retrieve data.
3) UNLOCK BOOTLOADER OF NVIDIA SHIELD TABLET K1
In Android, go to Settings > About tablet.
Tap 7 times on "Build number", a notification confirms Developer menu is unlocked.
Go to Settings > Developer options and switch USB debugging ON.
Go to my /djibe folder you unziped earlier. In Windows address bar (ie E:\root\Nvidia Shield Tablet K1\djibe\flash), type cmd and hit Enter
to open a Windows Command.
Connect tablet to PC.
Enter command
Code:
adb devices
Command starts adb and returns
Code:
0424916025732008b275 unauthorized
ADB (Android Debug Bridge) has started but tab is waiting for authorization.
On tablet, authorize adb commands from Allow USB debugging dialog: tap on OK.
Then enter command
Code:
adb reboot bootloader
Tab restarts and displays nvboot screen.
Make sure [bootloader](version xxx) is 4.00.2016.04.
Go to Windows Device manager.
Check the Fastboot device > right click to update driver.
Select the manual installation and set SHIELD_Family_WHQL_USB_driver_201801 folder to install fastboot USB drivers.
Installation ends with Android Bootloader Interface.
You may have to unplug-replug tablet in USB.
Tablet should now be seen in Windows Device manager as Android Device > Android Bootloader Interface.
To test, back to Windows command, enter:
Code:
fastboot devices
Command returns
Code:
0424916025732008b275 fastboot
Enter command
Code:
fastboot oem unlock
Using Volume+, select Yes - Unlock bootloader, confirm by pressing Power.
Lowest message is now: LOCK STATE - unlocked
### Unable to run fastboot commands: < waiting for device > ? Go to Windows Device Manager
### While in ADB, driver for Android Device should be named Android Composite ADB Interface. In Fastboot: Android Bootloader Interface
### Click on View > Display hidden devices, right click on Nexus 7 > Uninstall. Reinstall drivers. No success ? Try from another computer
Use Volume keys to select Unlock bootloader and Power to confirm.
Tablet is unlocked.
Press Volume- to select Fastboot protocol and confirm with Power.
4) FLASH TWRP 3.7 RECOVERY
From Windows command, enter:
Code:
fastboot flash recovery twrp-3.7.0_9-0-shieldtablet.img
Command returns Finished. Total time: 0.995s
Back to tablet, use Volume keys to select Recovery mode, confirm with Power.
Wait during recovery boot.
Welcome to TWRP recovery.
Check Never show this screen during boot again and Swip to Allow Modifications.
Go straight to Backup > select Boot, System, Data partitions.
Swipe to Backup and wait during backup.
Back to home screen > Mount (tablet still connected to PC).
You can access tablet's storage folders from Windows Explorer if Data partition is checked and bottom right button show Disable MTP (within TWRP Mount menu).
From Windows Explorer, navigate to SHIELD Tablet > Internal Storage.
Copy TWRP folder and paste it somewhere safe on PC.
This is a perfect backup in case of crash.
5) FORMAT PARTITIONS
On tablet, now go to Wipe > Format data.
Type yes and confirm with bottom right check icon.
Now go to Wipe > Advanced Wipe. Select Dalvik / ART Cache, System, Cache, Data, Internal Storage and Swipe to Wipe.
We cannot flash on wiped partitions. Go to Reboot > Recovery and Swipe to Reboot.
6) FLASH ANDROID + GAPPS (+ MAGISK)
On restart, check Never show this screen during boot again and Swipe to Allow Modifications.
Connect tab to PC.
Back to Mount menu.
Copy ROM + GAPPS (+ Magisk) to Internal storage with Windows Explorer.
Go to TWRP Home > then Install.
Navigate to /data/media.
Select aosp-*.zip,
Add more zips > bitgapps*.zip
and Swipe to force install.
(For root, needed for Netflix : Reboot > Reboot to recovery then Install > Magisk.zip)
Android 9 is installed !
When done message prompts, tap on Wipe Cache/Dalvik and Swipe to Wipe.
Disconnect tab from PC.
Then Reboot System.
Let the tab start (a few minutes).
7) OPTIONAL: ROOT WITH MAGISK
### Only if you flashed Magisk via TWRP recovery
Configure Android as you like.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About tablet.
Tap 7 times on build number.
Back to Settings > Developer options
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x
- Tablet not seen by Windows ?
Activate Developer options.
Go to Settings > System > Developer options > Default USB configuration > File transfer
That's it.
Enjoy ;-)
Thanks: @followmsi, @k23m, @nbehary, @DevSwift1, @flex1911, @yattodettaman, @emmett.tsai, TopJohnWu, TWRP team, LineageOS team, BitGApps team
------------------------------------------------------------------------------------------
BOOT TO RECOVERY
Hold Power + Volume- until Droid logo appears and release buttons, this is Bootloader.
Press Volume- twice to show Recovery mode and confirm with Power
I've done this, then struggled a bit to pass safetynet, finally was able to install netflix, but it stays on boot logo and after a while gives me error 501 172. How can I make netflix work?
tandero said:
I've done this, then struggled a bit to pass safetynet, finally was able to install netflix, but it stays on boot logo and after a while gives me error 501 172. How can I make netflix work?
Click to expand...
Click to collapse
Same here.
I need time to investigate.
tandero said:
I've done this, then struggled a bit to pass safetynet, finally was able to install netflix, but it stays on boot logo and after a while gives me error 501 172. How can I make netflix work?
Click to expand...
Click to collapse
I'm back,
this tutorial worked like a charm for me at this hour: https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/
But I did pass the safetynet earlier, it is just the application still gave me error 501, 172. I will try to include missing steps because some are the same as I performed and see if application will run.
tandero said:
But I did pass the safetynet earlier, it is just the application still gave me error 501, 172. I will try to include missing steps because some are the same as I performed and see if application will run.
Click to expand...
Click to collapse
What YASNAC app is writing ?
Added Netflix to Zygisk DenyList and cleared app data ?
yasnac:
basic integrity - pass
cts profile match - pass
evaluation type - basic
no, but just did and rebooted and still there is the same problem (i think, it is still on netflix logo, did not give an error yet), i will update this post soon
edit:
resulted in error 500 172 (https://help.netflix.com/en/node/125643)
tandero said:
yasnac:
basic integrity - pass
cts profile match - pass
evaluation type - basic
no, but just did and rebooted and still there is the same problem (i think, it is still on netflix logo, did not give an error yet), i will update this post soon
edit:
resulted in error 500 172 (https://help.netflix.com/en/node/125643)
Click to expand...
Click to collapse
Add Netflix to Zygisk DenyList (+ other services like in Droidwin post) and clear Netflix app data
Done that once again (cleared app data of netflix and google play store, google play servcies and google services framework).
Unfortunately right now it is stuck on logo, and did not give me the error yet. Which method have you used?
Rom works pretty good on my K1, much better/faster than stock. Battery drain is still there but is nowhere near as bad on a stock rom (I have a brand new battery installed).
For some reason the headphone jack is not compatible with this rom at all (plugging in headphones does nothing). Anyone else notice this?

Categories

Resources