Hello,
I just tried to install Remix OS 2.0.205 64-bit UEFI boot on my brand new Samsung Galaxy Tab Pro S. The procedure went well and I could boot ok. Unfortunately the touch screen and the wireless are both not working. Rest seems to be ok, but without wireless, there is not much I can do...
Hello....we're you ever able to get this running on your tabpro s? I'm contemplating buying a tabpro.
Sent from my SM-P905V using XDA-Developers mobile app
I just bought this tablet and I would like to know too. I feel like remix on this would be amazing...
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
mrDmola said:
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
Click to expand...
Click to collapse
How can this be sorted out as I would love to have this on my Tabpro S!
mrDmola said:
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
Click to expand...
Click to collapse
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
nielo360 said:
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
Click to expand...
Click to collapse
I'm going to install it on my Tabpro S tonight and will report back.
Biggenz said:
I'm going to install it on my Tabpro S tonight and will report back.
Click to expand...
Click to collapse
EDIT2: or these methods also from the xda remix 3.0 threads
In /system/build.prop change ro.remixos.box=true to false (should give brithness icon on the bottom)
or
Use Fn+left or right key combination
or
Edit: try this https://play.google.com/store/apps/details?id=com.curvefish.widgets.brightnesslevelGreat!
it was mentioned on another xda remix 3.0 thread.
looking forward to it Im waiting for my usb adapter but might consider the partition method if brightness can be lowerd via a work around to save battery or fixed.
I installed it last night and can confirm what mrDmola said. Everything works fine apart from wifi and screen brightness. For me the keyboard and track pad DID work. Such a shame as it's a brilliant OS.
Are there any developers who can sort this out for some beer money?
I'd donate if someone was willing to fix WiFi and brightness as its an excellent device for dual booting. Currently I use splashtop windows store version to stream ami duo os android from my desktop. It works flawlessly lag free with most games and touch screen works well with splashtop. I'd prefer remix however as a native os.
nielo360 said:
I'd donate if someone was willing to fix WiFi and brightness as its an excellent device for dual booting. Currently I use splashtop windows store version to stream ami duo os android from my desktop. It works flawlessly lag free with most games and touch screen works well with splashtop. I'd prefer remix however as a native os.
Click to expand...
Click to collapse
I tried installing Android-x86 but that doesn't even boot. I just get a black screen and my Tabpro S becomes unresponsive. I couldn't switch it back on and nearly got worried. A soft reset sorted it out.
Then I also tried Phoenix OS which works fine on my PC, but same again on the Tabpro, it won't boot. Just goes black screen and then nothing.
Nielo have you tried Phoenix OS by any chance? If not could you try to install it and let me know your findings please?
Biggenz said:
I tried installing Android-x86 but that doesn't even boot. I just get a black screen and my Tabpro S becomes unresponsive. I couldn't switch it back on and nearly got worried. A soft reset sorted it out.
Then I also tried Phoenix OS which works fine on my PC, but same again on the Tabpro, it won't boot. Just goes black screen and then nothing.
Nielo have you tried Phoenix OS by any chance? If not could you try to install it and let me know your findings please?
Click to expand...
Click to collapse
I haven't tried that OS, I will try remix os if I can find a wifi fix. I'm still waiting for my Samsung usb adapter to boot via usb
nielo360 said:
I haven't tried that OS, I will try remix os if I can find a wifi fix. I'm still waiting for my Samsung usb adapter to boot via usb
Click to expand...
Click to collapse
Phoenix OS is very similar but I prefer Remix OS.
Why is it so hard for someone to tell us how to fix this problem?
nielo360 said:
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
Click to expand...
Click to collapse
I installed on a partition It automatically gave me the option to boot into windows or remix OS. I had to change the boot settings in my bios first before I was able to do any of this though
Without wifi most games wont work so trying it would not be useful, but its good to see the touchscreen working. 2.0 had issues with touchscreens
WiFi drivers needed
Hey, I just installed the latest version of 3.0 as of 12th october 2016
Touch screen WORKS! (Unlike Surface Pro 4)
Touch pad now works
Keyboard works
*But the deal breaker remains Wifi*
Tab Pro S uses a Qualcomm wifi chip and obviously there are no drivers for it installed in the build of Android x86 that Remix OS are using.
Can't we just add these ourselves? Or do the drivers simply not exist for Android on x86?
Other quibbles but not as problematic...
No bluetooth
No screen brightness control
No battery info or charge levels
All again just driver issues.
It really would be wonderful to get this working as there are no other premium Android tablets on the market with a faster chipset than an iPad Pro and an AMOLED screen for 750 euros
Hey guys I have been making some progress with a rooted custom build of Remix OS.
The WiFi adapter chipset in the Tab Pro S is the Qualcomm QCA6174. The Linux drivers which come packaged with the Remix OS kernel as it stands do not work.
There are the same QCA6174 issues with Linux based OS - https://bbs.archlinux.org/viewtopic.php?id=204871
Following from that research I downloaded a few different versions of the QCA6174 driver from Github and it appears the filenames need to be a certain way for it to be picked up by Remix OS / Android x86 (see guide below).
The result is I can now get the WiFi hardware to be detected OK by Remix OS and it switches on, starts searching for access points... However we are not quite there yet. It does not actually detect any SSIDs or connect to the internet. So I need to figure out from the error logs why that is.
Bluetooth seems to now work as well - was able to show a list of discoverable devices and pair with my phone, but not pick up a LTE personal hotspot for the internet.
Seems something basic to do with TCP/IP or Ethernet connectivity is broken?
By the way all this needs root access to Remix OS. I used this guide to root - http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
Also I had to install a custom version of Remix OS with the bloatware removed and a more powerful File Manager along with Super User app pre-installed. I used this version based on Jide's v3.0.202 -
http://forum.xda-developers.com/remix/remix-os/remix-os-pc-hacked-edition-ota-v2-0-201-t3345968
You also need to edit a file on the EFI partition in Windows before rebooting to get proper root access. To add the REMOUNT_RW=1 flag to the kernel you are going to be editing the grub.cfg file in the /BOOT directory of your EFI partition and this won't be mounted in Explorer. To mount this using the guide I linked to above in Windows 10 it is important to run the command prompt as an administrator (right click, run as...) even if you are logged in as admin. By default it will run in user mode and you won't get permission to access the EFI partition at all.
So in summary -
1. In Windows install the custom version of Remix OS from here:
2. You do NOT need to install it on a separate partition, put it on C:/ drive
3. Do not reboot Windows after the installer finishes, instead run the Command Prompt (right click, run as admin)
4. Type command and enter - taskkill /im explorer.exe /f
5. Type command and enter - mountvol X: /s
6. Type command and enter - explorer.exe
7: Type command and enter X: and then cd to directory boot/grub
8: Edit the grub.cfg file in X:/boot/grub (command prompt - notepad grub.cfg) - please note DOS edit command removed from Windows 10 so it will open in Notepad
9. Add the line REMOUNT_RW=1 in the kernel commands, the line should look like this -
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
10. Reboot
11. At dual boot option screen select Remix OS and it will finalise installation, before booting to Remix OS desktop
12. Run Super User app, ignore message about it needing to search for an update
13. At the desktop run cyanogenmod File Manager (not the Mac OS style Remix OS one as it has no root access) and go to the root /system folder, grant full read/write privileges in Super User app when prompted
14. You will need to copy the QCA6174 driver files from a USB drive. These files you should download from here on a machine with internet access:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0
In Remix OS these belong in the following folder:
/system/lib/firmware/ath10k/QCA6174/hw3.0/
In the driver package downloaded from github the file "firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1" needs to be renamed firmware-4.bin
Make sure files are named as follows:
firmware-4.bin
board-2.bin
board.bin
15. Reboot and the WiFi hardware will now switch on in Remix OS and begin searching for access points, bluetooth should detect nearby devices.
Other stuff which I found currently works:
Touchscreen (it does not on Surface Pro 4 so big reason to use Tab Pro S!!)
Trackpad
Keyboard
Audio, with reservations (system sounds audible like tapping in calculator app, but MP3 media audio didn't work in bundled player)
To do:
Final fixes to WiFi
Screen brightness control
Battery charge level and standby (it can only tell if connected to A/C, no battery polling levels detected)
Further check audio and app compatibility once WiFi is working
Great job thanks for your work on the issues looking forward to working wifi!
Is Remix OS better in terms of battery life?
My ProS doesnt last long with screen switched off, unless I shutdown windows.
commanderspike said:
Hey guys I have been making some progress with a rooted custom build of Remix OS.
The WiFi adapter chipset in the Tab Pro S is the Qualcomm QCA6174. The Linux drivers which come packaged with the Remix OS kernel as it stands do not work.
There are the same QCA6174 issues with Linux based OS - https://bbs.archlinux.org/viewtopic.php?id=204871
Following from that research I downloaded a few different versions of the QCA6174 driver from Github and it appears the filenames need to be a certain way for it to be picked up by Remix OS / Android x86 (see guide below).
The result is I can now get the WiFi hardware to be detected OK by Remix OS and it switches on, starts searching for access points... However we are not quite there yet. It does not actually detect any SSIDs or connect to the internet. So I need to figure out from the error logs why that is.
Bluetooth seems to now work as well - was able to show a list of discoverable devices and pair with my phone, but not pick up a LTE personal hotspot for the internet.
Seems something basic to do with TCP/IP or Ethernet connectivity is broken?
By the way all this needs root access to Remix OS. I used this guide to root - http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
Also I had to install a custom version of Remix OS with the bloatware removed and a more powerful File Manager along with Super User app pre-installed. I used this version based on Jide's v3.0.202 -
http://forum.xda-developers.com/remix/remix-os/remix-os-pc-hacked-edition-ota-v2-0-201-t3345968
You also need to edit a file on the EFI partition in Windows before rebooting to get proper root access. To add the REMOUNT_RW=1 flag to the kernel you are going to be editing the grub.cfg file in the /BOOT directory of your EFI partition and this won't be mounted in Explorer. To mount this using the guide I linked to above in Windows 10 it is important to run the command prompt as an administrator (right click, run as...) even if you are logged in as admin. By default it will run in user mode and you won't get permission to access the EFI partition at all.
So in summary -
1. In Windows install the custom version of Remix OS from here:
2. You do NOT need to install it on a separate partition, put it on C:/ drive
3. Do not reboot Windows after the installer finishes, instead run the Command Prompt (right click, run as admin)
4. Type command and enter - taskkill /im explorer.exe /f
5. Type command and enter - mountvol X: /s
6. Type command and enter - explorer.exe
7: Type command and enter X: and then cd to directory boot/grub
8: Edit the grub.cfg file in X:/boot/grub (command prompt - notepad grub.cfg) - please note DOS edit command removed from Windows 10 so it will open in Notepad
9. Add the line REMOUNT_RW=1 in the kernel commands, the line should look like this -
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
10. Reboot
11. At dual boot option screen select Remix OS and it will finalise installation, before booting to Remix OS desktop
12. Run Super User app, ignore message about it needing to search for an update
13. At the desktop run cyanogenmod File Manager (not the Mac OS style Remix OS one as it has no root access) and go to the root /system folder, grant full read/write privileges in Super User app when prompted
14. You will need to copy the QCA6174 driver files from a USB drive. These files you should download from here on a machine with internet access:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0
In Remix OS these belong in the following folder:
/system/lib/firmware/ath10k/QCA6174/hw3.0/
In the driver package downloaded from github the file "firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1" needs to be renamed firmware-4.bin
Make sure files are named as follows:
firmware-4.bin
board-2.bin
board.bin
15. Reboot and the WiFi hardware will now switch on in Remix OS and begin searching for access points, bluetooth should detect nearby devices.
Other stuff which I found currently works:
Touchscreen (it does not on Surface Pro 4 so big reason to use Tab Pro S!!)
Trackpad
Keyboard
Audio, with reservations (system sounds audible like tapping in calculator app, but MP3 media audio didn't work in bundled player)
To do:
Final fixes to WiFi
Screen brightness control
Battery charge level and standby (it can only tell if connected to A/C, no battery polling levels detected)
Further check audio and app compatibility once WiFi is working
Click to expand...
Click to collapse
Great work! Hope we will see the wifi working soon. I bought the tab pro s to replace my ipad pro, now it basically sit in dust, was thinking about selling it until I see this post.
Related
I am not responsible for any damage happening to your device by doing this!
I believe Windows 8 is great for productivity, but that's not Always what we are looking for. We want to experiment with our devices and get as much out of them as possible. Android gives us the freedom to do with this tablet what we never thought possible, the overall performance is incredible and graphics are buttery smooth. However, I couldn't find a suitable guide, so I created one myself. So let's get started!
Bug list:
Everything should be working fine, contact me if not
Requirements:
USB Stick with at least 512 MB storage
USB Keyboard
USB-hub, because the tablet only has 1 USB port
Latest image available for Generic UEFI Installer from here
Image Writer Tool from here
Setting up a bootable USB
1. Download Image Writer Tool, unpack it and run the ''Win32DiskImager.exe" file
2. Once opened, navigate to your *.img file you downloaded earlier in the requirements and hit "Write" (This will format the USB drive)
3. Let it run and once it's done your USB is good to go.Setting up tablet to boot from USB
1. Enter BIOS settings by pressing the power (and hold it) and the Windows button
2. Once there, make sure UEFI boot modus is set
Booting from USB
1. Make sure your tablet is turned off
2. Plugin your USB-hub with USB Stick and Keyboard insered
3. Power on your devices while pressing the ''F12'' button
4. Now choose your USB device from the boot options
5. You'll get a few options, choose the option that fits your expectations
Note: I'd dualboot and install gummibootloader
6. Choose your prefered option and wait, the installation will run automatically
7. Once done, unplug everything and power off the device
8. When you turn your tablet back on, you'll see (if you've chosen option a. or b.) a menu with the option to boot Windows or Android
9. Navigate with volume DOWN key and select with volume UP key
This Method could also be used for the Samsung XE700T
Thanks to
LuNaTum
For creating a guide on how to change DPI
For creating a guide on how to pair bluetooth devices to Android and Windows
__________________________________
Q&A
Q:
How do I install Google Play Store and other Gapps?
A:
1. Download a root explorer from Internet in .apk format, I recommend ES file explorer. (I think you are familiar with the way to install these)
2. Go in ES file explorer, then click settings and enable root exploring and root access (allow any prompt)
3. Download GoogleServicesFramework.apk from here
4. Copy with ES file explorer the downloaded .apk to /system/app/
5. Now reboot the tablet into Android
6. Download PlayStore_v4.1.10.apk from here
7. Repeat step 4. and 5. with PlayStore_v4.1.10.apk
8. Congratulations, you've installed the Google Play Store
9. If you want to install other Gapps, download the .apk and repeat step 4. and 5.
Note: If you don't see the app installed after reboot, try changing the .apk's permission to RW-R--R-- and reboot again
Q:
I can't enter BIOS by holding ''Windows''-button and ''Power''-button
A:
1. Press ''Windows''-button and ''Power''-button at the same time
2. Let go when the ''Acer''-bootlogo appears
3. Congratulations, you've entered the BIOS
Q:
I can't boot from USB, because the secure boot prohibits it
A:
1. Enter BIOS by pressing ''Windows''-button and ''Power''-button at the same time
2. Set up a supervisor password
3. Congratulations, now you can disable secure boot
Q:
The ''Gummibootloader doesn't appear when booting, but Windows boots normally
A:
1. Enter BIOS by pressing ''Windows''-button and ''Power''-button at the same time
2. Change bootorder so Android comes in first place and Windows second
3. Congratulations, you've now got Gummibootloader at boot
Q:
Android-ia1 installed perfectly, but later versions fail to install
A:
1. Go to Acers site
2. Navigate to Home page > Support > Drivers and Manuals > Select [your..tablet] > BIOS
3. Download the latest BIOS
4. Update the devices BIOS
5. Congratulations, you'll be able to install Android-ia2 and later
Q:
What other devices will also be combatible with this method?
A:
Samsung XE700T
Q:
How to get bluetooth mouse and keyboard working on Android and Windows at the same time?
A:
1. Pair your bluetooth devices first with android and the with Windows
2. On Windows download PsExec
3.Then from downloaded file copy PsExec.exe in Windows to directory C:\Windows\System32 or to directory where your System32 folder is.
4. Write in the search cmd and run it as administrator
5. Then use command: psexec -s -i regedit.exe
6. Now go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys
7. From \Keys you can find your paired bluetooth devices. First there is the devices bluetooh mac address and 32 numbers long linkkey. Now write those linkeys and mac addresses up or copy them.
8. Now everything is set on Windows side. Next boot to android.
9. On android you need again for example ES file Explorer and R/W rights
10. With file Explorer fro root go to /data/misc/bluedroid/
11. Open file called BT_config.xml
12. From text find your devices using mac address
13. When you find you devices mac addres scroll down and you should see line with linkkey and 32 number code.
14. Now take that 32 number code you got from Windows
15 You have to change it little so the linkey works and here how it's done:
for example your Windows linkkey is "12345678qwertyuiasdfghjkpoiuytre" now set it as 8 number clusters like this
"12345678 qwertyui asdfghjk poiuytre"
Now you have to reverse those 8 number clusters
Take the set on far right "poiuytre" and mark it like this "po iu yt re"
Now reverse those pairs like this "re yt iu po"
Now "reytiupo" this is the first line in the new linkkey
Do the same for other three cluster. After it's done this example linkkey looks like this "reytiupojkghdfasuityerqw78563412"
16. When you have your modified Windows linkkey ready you can just replace the old one from the file BT_config.xml
17. Now just reboot android and your keyboard and mouse should work.
Q: How to change DPI from 213 to 160 (or something else)
A:
1. Get file manager on android like ES file Explorer
2. R/W rights to whole system on android
3. From root go to /system/etc/machine-props/
4. Open acer-w700.prop with ES Explorer and edit line "ro.sf.lcd_density = 213" and change 213 to 160
5. Reboot android and system should now be 160 DPI
Could this work on the surface?
Sent from my SGH-T999 using xda premium
will this working on Iconia W500?
sstory792 said:
Could this work on the surface?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
mmm273 said:
will this working on Iconia W500?
Click to expand...
Click to collapse
Since these devices aren't officially supported by android-ia, because its android on Intel Architecture. On surface pro android-x86 might work, you can try installing it shown above
Sent from my HTC One X+ using xda app-developers app
Sorry I meant Surface RT
Sent from my SGH-T999 using xda premium
sstory792 said:
Sorry I meant Surface RT
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hmm, then this may not work since RT's processor is ARM based
Sent from my HTC One X+ using xda app-developers app
Pretty sure even if you didn't run into any architecture problems (and you will) trying this on RT, you'll probably be blocked by Secure Boot preventing the use of a non-Microsoft bootloader. We haven't managed to crack that yet. You can try it anyhow, and report back what you find, but don't expect it to work.
GoodDayToDie said:
Pretty sure even if you didn't run into any architecture problems (and you will) trying this on RT, you'll probably be blocked by Secure Boot preventing the use of a non-Microsoft bootloader. We haven't managed to crack that yet. You can try it anyhow, and report back what you find, but don't expect it to work.
Click to expand...
Click to collapse
That's right, Microsoft locked everything down, just as installing legacy software (although it won't run that fast with nvida processor
Sent from my HTC One X+ using xda app-developers app
mmm273 said:
will this working on Iconia W500?
Click to expand...
Click to collapse
No as that is a clovertrail device. Clovertrail is physically incapable of booting into anything other than windows 8, Intel locked it for this generation silicon only, bay trail has the restriction lifted.
sstory792 said:
Sorry I meant Surface RT
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thatgrass said:
Hmm, then you could try this image, but I can't promise anything at least this one isn't especially for x86 system
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
surface RT is ARM. Android IA is android Intel architecture, ie, x86 with Intel extensions, ie Intel core i3 and above only. There is no such thing as an operating system which is not architecture locked, I would have looked into that before writing the tutorial if I were you....
SixSixSevenSeven said:
surface RT is ARM. Android IA is android Intel architecture, ie, x86 with Intel extensions, ie Intel core i3 and above only. There is no such thing as an operating system which is not architecture locked, I would have looked into that before writing the tutorial if I were you....
Click to expand...
Click to collapse
I wrote it for Acer iconia W700, my own device. I know how that device works, but other devices aren't well known by me.
Thanks for your information
Sent from my HTC One X+ using xda app-developers app
(big edit)
Many thanks for your help.
I followed your guide since I've got an Iconia W700, like you. Which option should I take? If I choose "run..." I got an error.
Live-installation works, though.
Did Bluetooth work in your sistem? In my w700 it just goes ON but doesnt recognize any device.
Suggestions?
Delete, because of Big edit above
Sent from my HTC One X+ using xda app-developers app
baffone001 said:
(big edit)
Many thanks for your help.
I followed your guide since I've got an Iconia W700, like you. Which option should I take? If I choose "run..." I got an error.
Live-installation works, though.
Did Bluetooth work in your sistem? In my w700 it just goes ON but doesnt recognize any device.
Suggestions?
Click to expand...
Click to collapse
Bluetooth does not function under Android-IA, its in their FAQ.
SixSixSevenSeven said:
Bluetooth does not function under Android-IA, its in their FAQ.
Click to expand...
Click to collapse
Thanks guys for your help
I'll wait they fix bluetooth.... it is worthless for me this way because I need android for GPS-mapping programs, which I only use with an external gps-bluetooth receiver...
I can't find a good gps-offline-software for windows... (like sygic for android, for example)
baffone001 said:
Thanks guys for your help
I'll wait they fix bluetooth.... it is worthless for me this way because I need android for GPS-mapping programs, which I only use with an external gps-bluetooth receiver...
I can't find a good gps-offline-software for windows... (like sygic for android, for example)
Click to expand...
Click to collapse
Hit up the car computer forums, they often manage to hunt down absolute gems of GPS navigation software.
Alternatively, there are quite a few good linux navigation software suites out there apparently. Ubuntu is reasonably easy for a newcomer to use and also works alright with touch, I prefer linux mint normally but it doesnt play so nicely with touch (but it may be possible to install the ubuntu UI atop mint as mint is already a fork from ubuntu).
3rd choice. An FTDI cable may work under Android-IA in which case you can use one of the many serial GPS units out there. Most bluetooth GPS recievers are just serial based units with a bluetooth radio attached in the SPP mode.
I think the bluetooth should work fine with the linux option.
SixSixSevenSeven said:
I think the bluetooth should work fine with the linux option.
Click to expand...
Click to collapse
I've always been a big fan of ubuntu. I used to have Lubuntu like only OS on my old 1000H eeepc.
But I lost a day and a full night trying to install Ubuntu 13.04 on this w700 keeping Win8 (so, dual boot) and I got really MAD since there's no way it could recognize the hard-drive partitions. I have to abort the linux thing at the moment, hoping that 13.10 or whatever could solve the problem I have with Acer W700.
I think I'll try Autoroute or some freeware option....
SixSixSevenSeven said:
Bluetooth does not function under Android-IA, its in their FAQ.
Click to expand...
Click to collapse
but under the major change for Version: android-4.2.2_r1-ia2,they did mention the bluetooth is working
Major Changes:
* Secure-boot support (not default)
* Mesa rebased onto freedesktop upstream
* Bluetooth working on Iconia W700 (bluedroid stack)
* ADB TCP sessions auto-reconnect
* Linux kernel 3.9.1
however i faced the same problem..live installation work only,able to turn on the bluetooth but unable to connect to other devices..guess have to wait for more update
baffone001 said:
I've always been a big fan of ubuntu. I used to have Lubuntu like only OS on my old 1000H eeepc.
But I lost a day and a full night trying to install Ubuntu 13.04 on this w700 keeping Win8 (so, dual boot) and I got really MAD since there's no way it could recognize the hard-drive partitions. I have to abort the linux thing at the moment, hoping that 13.10 or whatever could solve the problem I have with Acer W700.
I think I'll try Autoroute or some freeware option....
Click to expand...
Click to collapse
There is a guide on these forums for installing ubuntu on the surface pro which under the hood is essentially the same device as the W700. Might be worth taking a look at to see if it offers any help.
marcus70 said:
but under the major change for Version: android-4.2.2_r1-ia2,they did mention the bluetooth is working
* Bluetooth working on Iconia W700 (bluedroid stack)
however i faced the same problem..live installation work only,able to turn on the bluetooth but unable to connect to other devices..guess have to wait for more update
Click to expand...
Click to collapse
See? I experience the same you do on my W700. Let's hope for an update :good:
There is a guide on these forums for installing ubuntu on the surface pro which under the hood is essentially the same device as the W700. Might be worth taking a look at to see if it offers any help.
Click to expand...
Click to collapse
Hi Six, thanks for answering. Can't find the guide, though. Would you please link me whenever you have a second? Thanks in advance
baffone001 said:
See? I experience the same you do on my W700. Let's hope for an update :good:
Hi Six, thanks for answering. Can't find the guide, though. Would you please link me whenever you have a second? Thanks in advance
Click to expand...
Click to collapse
http://www.geek.com/microsoft/how-to-install-ubuntu-on-the-surface-pro-1539262/
The forum thread only linked to that page, might aswell skip the middle man.
ok! where to even start...
I like many got this 2in1 at wal-mart and I live it. unfortunately I like many am not yet familiar with the new UEFI bootloader bios SOC stuff
heres what I do know and please correct me if im wrong. also please tell me if this 2 in 1 is and can be flashed the same as the asus t100
ok the Flexx11 has a bayntrail-t CR quad core processor 1.33-1.83ghz model Z3735F the t100 is3740
11.6" screen ips touchscreen at 1366x768 res
Efun is the corp and yifang vers.NX1106.1.02.008\139
THE BIOS IS YFG0315009112
it is a 32bit EFI bootloader
the reason I mention all of this is I have tried several times to dualboot androoid and each time ruined the computer and had to return it and I simply no longer wish to return it and love it to much to get something else
the first try the time began to lag and was unfixable for some reason the second time i somehow lost the keys booting and formatted wrong or something and the tablet bricked it would remain black with keyboard lit and no button combo could get it back no boot at all.
I am currently using AMIDUOS to run android kitkat and I love it but from what I understand it isnt compatible with win10 and really still isnt the same as the full android being on the tablet although really really close and awesome
but honestly I have been doing this stuff for years and now with this new windows secure boot and system on a chip stuff im lost
ever get anywhere with this?
I'm curious as well.
It has to be possible. I say that because I recently owned a ChuWi dual-boot device with the same Baytrail processor and SOC.
I wonder if it wouldn't be possible to take a system dump from one of the chuwi dualboot devices and flash it to the nextbook.
Sent from my Ascend Mate 2 using XDA Free mobile app
I'm also interested in doing this. It appears that the Nextbook Ares has the same hardware (minus 1GB RAM) but has Android. I contacted Nextbook to see if I could get a copy of the Ares Android firmware but was denied. If someone with the Ares could upload a backup that would be helpful.
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
64 bit processor?
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
Click to expand...
Click to collapse
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
GeneticJulia said:
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
Click to expand...
Click to collapse
It just won't boot the USB. At all. Unless it's 32-bit.
rowdyrocket said:
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
Click to expand...
Click to collapse
I'm loving Remix OS on here with dual boot. Having some issues though and I really want this to work.
Main and I mean main issue is no sound at all, no rotation is next in line and Bluetooth isn't working. Everything else works great.
This is so awesome its like Android lollipop with windows desktop functionality. Now if I can get the bugs fixed I will be in android hog heaven.
GREAT FIND BRO!!!!! EXACTLY what I was looking for maybe even better than.
for those interested here is the XDA section for all things REMIX OS
http://forum.xda-developers.com/remix
By the way for those who may want to know I installed dual boot onto the hard drive it went with no issues.Here's some tips for flexx 11
1. I used a partition manager such as easy partition manager to partition the C: drive regardless of what the tutorial said. Couldn't use windows disk management. I deleted the recovery for an extra 5 gigs (make a backup if you do) I used about 19 gigs from the C: drive and made an E: NTFS.
2.Also do not use the remix files from that tutorial use the ones here from the main site http://www.jide.com/remixos-for-pc they are newer and the ones from the other post where incomplete. Also the newer ones on the site now include OTA updating which is totally awesome.
3. I'm hoping this will help someone..... After I was all finished I expected it to dual boot as any other dual boot restart and then i would see options for the OS's not the case here I got stuck on this I was using easy BCD and trying all sorts of stuff, once I looked at the tut a little closer I realized you don't need any of that. Once your all done do a restart and it will go back to windows as usual. Now go to settings, then recovery, then advanced startup and choose from devices I think its the second option on the left list. There you will find Android OS click that and it will take you to your dual boot options. Sounds a lot more complicated than it really is. But believe me once you know this your better off.
And that's all I've got please and I mean please post here with any fixes especially for sound and if you have questions I will try to help.
Thanks
PS: I AM GETTING OCASIONAL LOCK UPS, MEANING THE OS FREEZES AND I HAVE TO RESTART BY HOLDING POWER.
Im not sure if this is good news or not...
Using the methos outlined I was not able to get audio bluetooth autorotate and other things to work but after a bit of digging I found out that remix os has an image specifically for nextbook baaytrail (Our PC) here: http://www.jide.com/remixos/devices
click other upper left.....
I cannot find instructions to install this though and using the other install instructions from here fail because the only part of the file to replace is the system image.
I also attempted the other install methods and easy BCD does not work for this PC
So if anyone can help to install this file specifically for our computer as well as verify that it works and what works and how you installed would be great
OK this is really cool I have made headway sort of.
I have installed kit kat android-x86-4.4-r3.img using the Androidx86-Installv24-5800.exe installer and i have rotation, root and it works pretty good for the most part wifi works great so far no bluetooth, it freezes during shut down and the major issue as in most cases is the sound. Im not sure about the camera now that I think about but i will check and report back here.
I really want the sound working on this and I woud be bigtime happy this forum could be solved as far as im concerned
From what I understand there is a bug with baytrail and linux where the spp port is pointed automatically to the usb or something. but for the life of me after weeks of scouring the internet cannot find a laymens guide to a simple fix for this. I'm really not even sure there is one because I'm yet find a rock solid confirmation of a solution
Update: camera doesn't work either
So far the 4.4.3 port is the best. I just can't seem to find any help whatsoever so its looking like so close yet so far away. Its a pure shame that audio and a few other major bugs are the only things in the way of this being a fully working and easy dual boot method.
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
murlig123 said:
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
Click to expand...
Click to collapse
Sorry for the late reply, use the installer and create a separate drive using C: like a D: or E: and get android 4.4 the .IMG that should work for you and the installer should do everything for you.
So use the uefi android installer after you partition a drive to load android 4.4 the uefi IMG
Its just going to piss you off though because there's no audio and seemingly no way to fix it, which is a crying shame ��
P.S. typically secure boot is off in the bios on this machine, but if by any chance you turned it on or the newer ones come that way make sure it is off or this will not work.
UEFI Settings
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
korycooper said:
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
Click to expand...
Click to collapse
Okay. So I was able to test this one of my co workers Nextbook and it seems like its a problem with mine.
This might be beneficial for us Flexx 11 users. It's a full port of Remix 2.0 to the Ares 8 with everything working except the camera rotation issue. Very promising. I've heard the hardware is similar. Working on attempting to install on mine. Anyone else tried it?
http://forum.xda-developers.com/remix/supported-devices/port-remix-os-2-0-nextbook-ares-8-t3498015
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
KorishanTalshin said:
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
Click to expand...
Click to collapse
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Wiebenor said:
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Click to expand...
Click to collapse
I realize this is a dead thread, but I had to chime in... I bought my NextBook Flexx 11 from Walmart 3 or 4 years ago and it shipped with Windows 10 Home, not Windows 8.1... However, IMHO, Windows 10 is a resource hog on this little device. I'm currently looking in to installing Linux...
Here' s my general experience with Remix OS (v 3.0.206) on my Asus T100. Not surprisingly, it's much the same to my Android x86 experience.
First, a big thanks to the team members at Jide and Anroid x86! And now on to my experience...
The install to my hard drive didn't proceed smoothly. I'm not sure it was because I already had Android x86 installed or because I have my Z drive mapped to my LAN and the install program tries (and fails) to mount my EFI partition there in order to install grub. To get past the failed install, I manually modified my EFI partition to add a menu item for Remix OS alongside Android x86.
After resolving the installation woes, Remix booted fairly quickly and the setup option worked fine. The OS works pretty well and seems to allow all my Android apps to run. I haven't installed and tried them all yet though.
Not all the hardware works. Here's what works and doesn't:
Working
Touchscreen - works
WiFi - 2.4 and 5 GHz both work. WiFi seems to stop working and can't be re-enabled if the tablet sleeps.
Track pad - works, but can't be disabled using the keyboard function key
Keyboard function key volume up and down
Keyboard function key brightness up and down
Dock USB
GPS
Suspend. (The notification light did not go out, so it wasn't fully suspended.) I didn't fully test suspend, so it may or may not be working properly.
Battery icon
External speakers
Accessing my dock hard drive
Not working
Auto brightness
Camera. It doesn't work at all.
HDMI Out. Video displayed does not fully fill width of screen. Audio still comes out of the T100. Booting will not complete if HDMI is connected; it stalls at the command line.
Notification/camera on light - stuck permanently on.
Auto rotate (and no manual rotate either)
Keyboard function key volume mute
Keyboard function key to disable/enable the track pad
Esc key doesn't always behave as the back key.
After putting the tablet into the keyboard dock, Remix launches its File Manager *every time*. It's annoying.
Not tested
Bluetooth
I had freezing issues with a previous Release Candidate of Remix, so this version is usable by comparison. However, with so many non-working items, Remix on the T100 is just passable and not quite ready for a daily driver for me. v 3.0.206 fixed an issue with not being able to use WiFi after it was turned off (and back). If auto-rotate was working, I'd consider using it as a daily driver...
Can you please share your installation procedure?
awyeong said:
Can you please share your installation procedure?
Click to expand...
Click to collapse
Hi, I must have missed the notification of your reply...
I purposefully omitted the installation procedure because it was a pain, I started with android-x86, and I don't really recall the exact steps. Are you having a specific issue?
Hi,
I also have a T100ha & was thinking about putting Remix on it. Actually i was debating buying a Chuwi hibook pro 2 to play with (windows 10 + remix). But its really identical to the T100HA I already have in terms of hardware specs (or at least close).
I am a little fuzzy on if the remix os plays with the partition for a dual boot experience or if this runs on top of the windows 10 OS.
For those starting from scratch, what would you suggest on a Remix OS install - or is it not even close to usable?
RichTJ99 said:
I am a little fuzzy on if the remix os plays with the partition for a dual boot experience or if this runs on top of the windows 10 OS.
For those starting from scratch, what would you suggest on a Remix OS install - or is it not even close to usable?
Click to expand...
Click to collapse
You don't need to create a new partition or resize an existing partition. It gets installed on your C Drive, most of it being installed in C:/RemixOS or whereever you choose. Your MBR will be modified to allow it to boot to WIndows or Remix.
Remix does not "run on top of" WIndows 10, like an emulator or VM. It is installed on the same hard drive, but is booted separately. But that reminds me...if you power on your tablet, it will boot straight to Windows. In order to boot to Remix, you have to a) hold power/Volume down to get to grub where you can select Remix, or b) Use Advanced Startup within Windows 10 to boot to Remix. It would be better if the Grub menu was presented on boot without the button mashing. Thanks, Microsoft/Asus!
You can/should try out a USB install to test it out. You can see what works/doesn't work for yourself and judge whether you want to install it to your hard drive or not. I still have it installed, but only use it occassionally.
So this isnt like Bluestacks which runs within windows? What I dont like about Bluestacks is the resources it uses even when its not running. The T100HA has very limited ones.
I see a number of posts on reddit with people trying to figure out how to install this on the T100HA.
Because I am a little fuzzy - Can you live install the ISO on a USB drive (like Ubuntu) for testing?
Anything not working for you on Remix?
So with the bootable ISO & usb. I power up, hit escape, choose the usb drive. I get the option of resident or guest - i choose guest, it says android-686, a black screen with a border pops up, then the system reboots & ends up in windows.
RichTJ99 said:
So with the bootable ISO & usb. I power up, hit escape, choose the usb drive. I get the option of resident or guest - i choose guest, it says android-686, a black screen with a border pops up, then the system reboots & ends up in windows.
Click to expand...
Click to collapse
This is the part that I don't exactly remember what I did to get it working.
You've probably disabled Secure Boot in Windows (required). I used Rufus to make my USB stick. I had problems when I made it with LiLi. So, if you didn't use Rufus, give it a whirl. Try the resident mode too.
Also, I think I used the Android-x86 USB install and copied the RemixOS files over top of it. Alternatively, go to http://www.jfwhome.com/2016/01/04/latest-steps-to-install-ubuntu-on-the-asus-t100ta/ and follow Step 1 only... First Steps: Prepairing for the Ubuntu Install
I'm stuck on logo...can you put your grub.cfg file here?
or al least the remix os entry...in other PCs, changing parameter I solve that...but now I can't in my asus T100taf...thanks.
TeamPrimeOS is pleased to present you PrimeOS 2.x.x for Raspberry Pi4 and Pi4B
PrimeOS is an android based OS that provides a desktop experience with user top-of-the-line features like multi-window, taskbar, swipe simulation, and deca-pro key mapper for gaming.
Warning: PrimeOS 2.x.x is a free-to-use software in its beta version and is constantly under development. We are not responsible for any kind of damage, data loss, or anything else that happens to you or your device due to PrimeOS. Please feel free to report bugs and other suggestions. This is not for commercial use, please contact us if you wish to do that.
Feature Summary -
Desktop Experience:
Multi-window support with maximize, minimize, close, resize, etc
Taskbar with the ability to pin apps, show notifications, and system icons
Mouse scroll will actually send touch swipes for android apps support
Right click support for homescreen, app icons on taskbar etc.
General keyboard shortcuts like alt + tab, alt + f4, win + d etc
Android Gaming:
Decapro key mapping tool to play games with keyboard and mouse
Press F10 when running a game to manually adjust the controls
Pre-mapped some popular games like PUBG, Freefire, Subway surf, etc
Gaming Centre is available to browse recommended games
Others:
Based on LineageOS 18.1 (android 11)
Our own desktop browser based on kiwi
Gapps included, no need to install them manually
Settings to change resolution, frequency, cpu governer are present
Known Bugs:
Hardware video encoding/decoding
Same as other android roms
Screenshots -
https://imgur.com/a/7ctTity
Installation -
Write the image to sdcard using balena etcher.
Download PrimeOS -
https://www.primeos.in/download/
!! Please do not mirror without permission !!
Consider donating to us to keep this awesome project up and running.
Credits -
PrimeOS on RPi4 would not have been possible without the awesome contributions of LineageOS, OMNI ROM, Konstakang.
Community -
Get Support on Telegram
Reserved
what about Raspberry Pi 3B+
coming here from ETA Prime youtube video! nicee
What about "Hey Google" wakeword? HOw activate it?
MechWarriorZero said:
what about Raspberry Pi 3B+
Click to expand...
Click to collapse
It's arm64 based so Raspberry PI 3B+ is supported. You can tweak the boot.conf a little to match your needs after flashing it to a usb or an sd card.
I've been using this on Raspberry Pi 4b for the last 2 weeks since they first posted there release on the Rasbian Forums. And I will say it's pretty good. I've been running it off of a 64gb Sandisk Cruizer USB. Besides a few glitches in the graphics while using my 4k Roku TV and the original mini-hdmi to hdmi adapter. I would say this is going to go far. I have lots of hopes for this OS!
For everyone who is trying to boot these builds from USB you can follow this:
Q: How to boot from USB device?
A: Warning, this is still an experimental feature. Especially TWRP seems to have some issues with USB boot.
Install EEPROM that supports booting from USB
Write image to your USB device as above
Mount the USB device on your computer and make following changes to /boot/config.txt under ‘Boot device’ section:
#dtoverlay=android-sdcard
dtoverlay=android-usb
Plug in the USB device to your Raspberry Pi, remove any sdcard, and boot
Click to expand...
Click to collapse
Quote by @KonstaT . A very good developer that has made Android on the Raspberry pi much more easier. Don't forget about @maxwen though(for all of you OmniROM fans ))
NonStickAtom785 said:
It's arm64 based so Raspberry PI 3B+ is supported. You can tweak the boot.conf a little to match your needs after flashing it to a usb or an sd card.
I've been using this on Raspberry Pi 4b for the last 2 weeks since they first posted there release on the Rasbian Forums. And I will say it's pretty good. I've been running it off of a 64gb Sandisk Cruizer USB. Besides a few glitches in the graphics while using my 4k Roku TV and the original mini-hdmi to hdmi adapter. I would say this is going to go far. I have lots of hopes for this OS!
For everyone who is trying to boot these builds from USB you can follow this:
Quote by @KonstaT . A very good developer that has made Android on the Raspberry pi much more easier. Don't forget about @maxwen though(for all of you OmniROM fans ))
Click to expand...
Click to collapse
USB boot not working correctly. Every time need to change /boot/config.txt file to boot from USB!
Newbie here. I have just installed this on a 64gb sd card and using it on raspberry pi 4. BTW, big thanks to everyone involved in this. It looks and feels amazing to be able to do this on a raspberry pi. I have two questions if anyone can answer these.
1. I can't seem to be able to expand the userdata partition. I have expanded the main boot parition but that doesnt seem to be of any help. I still have only 5gb disk space when I check on the Prime OS.
2. How do I shut it down. I assume there is a way to shut it down before actually unplugging the rasppberry pi.
Thanks.
mshs013 said:
USB boot not working correctly. Every time need to change /boot/config.txt file to boot from USB!
Click to expand...
Click to collapse
Same trouble for me
andrei_retro said:
Newbie here. I have just installed this on a 64gb sd card and using it on raspberry pi 4. BTW, big thanks to everyone involved in this. It looks and feels amazing to be able to do this on a raspberry pi. I have two questions if anyone can answer these.
1. I can't seem to be able to expand the userdata partition. I have expanded the main boot parition but that doesnt seem to be of any help. I still have only 5gb disk space when I check on the Prime OS.
Click to expand...
Click to collapse
Okay so the Userdata can be expanded using another device. Or from the recovery image itself. I'm not sure if PrimeOS has a recovery mode by default. You can use this zip to flash to the devices recovery if it has one.
lineage-18.1-rpi-resize.zip
2. How do I shut it down. I assume there is a way to shut it down before actually unplugging the rasppberry pi.
Thanks.
Click to expand...
Click to collapse
You can shut it down by pressing F5 on your keyboard and holding it. But you can not boot it back up that way. You can check out one of his guides for setting up manual hardware keys here: https://konstakang.com/devices/rpi4/LineageOS19/
@vontoff @mshs013 could either of you help me out a little and send me the `/boot/config.txt` I'm on some pretty bad wifi and I don't want to redownload the entire PrimeOS file just to see it. You may both also have to get the latest Raspberry Pi bootloader and flash it. Here's a simple guide on how to do that:
https://pimylifeup.com/raspberry-pi-bootloader/
Otherwise if your SD Card is still in the Raspberry Pi then you might have issues.
Last case scenario is that you're both telling me you're stuck in a bootloop because the `boot.config` isn't applying the changes to tell PrimeOS and the bootloader you're booting from USB.
I hope some of this works out for you any of you three. If you need more help feel free to ask.
Hello, sorry for late answer... Each time need to modify boot settings for usb..... Join my config.txt after boot Ok.
Really weird because USB boot seems to be OK
tHANKS
# normal boot
kernel=Image
initramfs ramdisk.img followkernel
device_tree=bcm2711-rpi-4-b.dtb
arm_64bit=1
# audio
dtparam=audio=on
[HDMI:0]
[HDMI:1]
hdmi_force_edid_audio=1
[all]
# disable kms audio path and force bcm2835 card 0 = hdmi card 1 = headphone jack
dtoverlay=vc4-kms-v3d-pi4,noaudio
disable_fw_kms_setup=1
# usb adb
dtoverlay=dwc2,dr_mode=peripheral
# booting from sdcard
#dtoverlay=rpi-android-sdcard
# booting from usb
dtoverlay=rpi-android-usb
# serial console
enable_uart=1
# SPI
dtparam=spi=on
# I2C
dtparam=i2c_arm=on
# I2S
#dtparam=i2s=on
# max oc - can be adjusted in rom during runtime
over_voltage=2
arm_freq=1750
# gpio fan - start 55 deg stop 45 deg
#dtoverlay=gpio-fan,gpiopin=12,temp=55000
# pi camera
#gpu_mem=256
#start_x=1
Is there a way to mount NTFS drives? I would like to use PrimeOS as a local video player.
Hi there!
How can I add hardware buttons for power down, volume up and volume down?
Thank you!
how do i exit TWRP ? i changed boot mode to recovery for installing a recovery-zip. But how do i boot to system again ? It always boots recovery now.
i need to install "volkspc" - need root for that. magisk.25.2.zip ends with error.
How can i get root ?
Hi,
I'm stuck at 'System UI isn't responding' on Pi4B 1GB. btw is that too low for this rom?
I want to see if it'll run kodi
thanks!
Vik0_ said:
Hi,
I'm stuck at 'System UI isn't responding' on Pi4B 1GB. btw is that too low for this rom?
I want to see if it'll run kodi
thanks!
Click to expand...
Click to collapse
I guess that's too low spec for it, flashed it a couple more times, just to make sure the SD card/USB was not the issue, but never loaded the OS. System not responding messages and reboot in a loop.
Judging by the other ROMs posted for Pi, probably a 2GB RAM minimum also applies to this one.
RPI400: fn+f10 does not work.
Normally a rpi400 can be powered on by fn+f10.
But when i shutting down primeos this does not work. I have to unplug and plug again to make it start.
How can i fix this ?
@TeamPrimeOS hoping you will contribute back to opensource as part of your ethics & commercial model. ATB for Primebook.
I recently bought Asus Zenfone, because here in Ukraine is war, so I want small device with Windows (electricity often is off here because rockets fall on our electrric infrastructure etc).
So I've bought Asus Zenfone 2 used (it costed 16,25$). It came without accumulator, and 1/3 screen working. So I went to radio-market to buy new battery, it costed + ~10.25$ + 2,5$ to install battery. Then I've bought new touchscreen for it for ~22,5$, plus payed ~6,25$ to install it. Then around 7,5$ to restore battery connectors (on device and accumulator). So finally it worked, and wanted to see how to install Windows on Zenfone. Sure, if I had possibility to buy anywhere Zenfone better, new, not used, - I'ld do it, but it is not that easily available, just like any other Intel smartphone.
So, I started reading - how to make my device rooted. I don't understand how to get root. I found on wikipedia, that rooting is different from unlocking bootloader, and realized - yes. I need to unlock bootloader, and to boot from external flash-disk and install windows, or at least - new kernel with KVM support. I used pn my Android (non intel) Limbo x86 emulator, it can run some old windows 98 etc, maybe even xp, never win 2000, and if it runs win-7 or win-8 - it is so terribly slow. So I decided to buy Asus Zenfone. As in KVM mode I can send commands to CPU directly, and hope this Windows works much faster than in emulator. I hope just at least to run Windows XP on it, I need to code some C# code, so that Andorid phone is not only for mp3-playing, internet on the go and make calls, but to learn, study and to work. I don't know why Microsot, Intel and other companies don't like Intel CPUs in mobiles. They could do it if they wanted. I like WIndows because most programs are for Windows. And I want desktop x86 windows also on every mobile, intead of all Androids.
Anyway, What I tried to with my Zenfone. I found one amazing experience - that our hero and inspirer (ley God blesses him, maybe he will work in Intel/AMD/Asus/Microsoft etc to make more newer KVM kernels for future x86 phones with windows) - so Ycavan made KVM for Asus Zenfone 2. Great, I've read his thread - https://forum.xda-developers.com/t/...0-with-kvm-bridge-compiled-need-help.3145055/ - completely, with pen and paper writing down important information, downloaded all the files, and decided to start flashing.
I copied them to root of my Zenfone, unpacked tars and converted them into ZIPs. I also unpacked .img files to root of phone (I mean its folder which is visible if I connect it thorught USB, I know it is not "/" root of file system of Andoird, but anyway it is visible even inside CWM... sorry, was visible)...
So, I made some mistakes. I downloaded the kernel, tried to flash it using commands like :
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150710.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150714.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150717.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
fastboot flash boot boot_2.19_kvm_bridge.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
but non of them produced bootable Zenfone. So I had to revert to previous bootloader using the CWM tool.
In fact I liked this CWM most. I found this thread - https://forum.xda-developers.com/t/...root-ze500-ze550-ze551-temporary-cwm.3114063/
or similar here on forum, and it worked amazingly. I attached Zen-phone to USB, turned it off, then on while pressing, keeping pressed volume-up key, and after Asus logo appeared and some "zzz" vibration, again it blinked and I saw bootloader with Android robot, and possibility to scroll through menu using volume up-down, to choose normal boot, or reboot/power off, or to run restore etc.
For some reason, Restore there not worked. So anyway, I understood that I can use tool like ADB (Android debug bridge) and fastboot to copy new firmwares/kernels/bootloaders etc to it, so I guessed I can do it myself, and was ready for risks... And this what bad can happen - it happened.
So, I runned in CWM - file cai_dat_CWM.bat - which asked to type ACCEPT and then T4, and phone started to go into amazing mode, some "clouds" started appearing on phone, and it loaded into special secret menu, from which I could select what to do next. To me it looked like default boot manager which I wanted to see like in Dos/Windows machines - so I can choose to run into safe mode windows, or set some settings before booting, or even use "reanimator dvd" etc to load Windows and other tools to do partitioning, passwrods recovery etc. So it looked like on desktops, and very nice. I went inside the menu, and found good option to make backup. I did it all. Then in same CWM tool (I think it is called SuperSU for Android), I finally choose to restore bootloader/kernel/boot (custom recovery), and this saved my from bricking the first time after I followed the manual from Ycavan. Well, I know I can read a lot more threads how to do this and that, but there is always risk that something wrong can happen. So I tried to read as much as I could, and follow manuals as precisely as I could understand. But my phone is kind of "bricked".
Now it shows some scfreen like TV which can't catch any tv program. So it is some random colors - see attached picture. It is good that it shows at least this. But in worse situation - it doesn't show anything. So let me tell how I achieved this, and if you can tell me how to avoid this mistake and to recover it. I hope to get help from anyone here who installed KVM kernel(s) and acheieved running Windows on their zenfone 2 (or maybe anyone who has XPerience with other x86 phones may help, or if it is general issue how to unbrick - then also non x86 users please help).
So, CWM made backup, I became more non-scared to make more experiments with firmware. But main problem is that I don't know which firmware to use. I ideally suggested that when I change kernel to KVM-supported from Ycavan - that it will work with my Andorid 5.0 (it was installed when I bought it). So, but unfortunately, after installing any of KVM kernels of Ycavan - I was unable to understand which OS to install, which version. So even I tried to try to flash whole 1GB+ image (I have downloaded UL-Z00A-WW-2.20.40.59-user.zip from official asus.com - https://www.asus.com/ua-ua/supportonly/asus zenfone 2 (ze551ml)/helpdesk_bios/ - but. I was unable to upload it to zenfone (flash it), as it said it is older than installed version.
Anyway, now it doesn't matter as I cannot run into ANdroid at all. Worse - I cannot even get Bootloader working in Android, as I see after turning phone on - only "white screen" with non-working TV-like image (see attached picture of my Zenfone 2).
So, to make this happen, I did this: I found some information about TWRP. I tried to install as recovery tool. Even though it was flashed into mobile, and I installed it from apk from Google-Play, still, I was unable to run it... So then I found even cooler tool - which was too risky to install. I was good, but Andorid stopped running at all.
This tool is called - preroot601. I runned in it preroot.bat, and then it did something similar to CWM, but several times it restartd the phone _ i have added screenshots of how it looked like on PC / Windows. So after several restarts, it did a lot of changes - Android didn't start after it. Phone always was able to start into recovery mode - into TWRP (I downloaded its .img and flased it as recovery for phone). But in TWRP I think I did something wrong. I made backup of all files (syste,, bootloader, everything). I saw it is cool - to see there terminal, ability so set attributes for files, mount partitions ... even USB -hey, can I run from flash-disk? or from external DVD/Bluray which I have in this mode? I have USB-hub, and can connect to it keyboard, mouse, flash-usb, ssd/hdd - all through Microusb-usb adapter and to usb-hub. So what I wanted to do is to try to see flash-disk, mount it on my android zenfone. And then after restart - I had black screen or this 'non-working analog-TV screen when no program/channel/wave is caught for signal"...
So, I don't even understand what I did, and why this all happened, and why I have to do to restore bootloader at least.
My aim is to have KVM enabled in the kernel. I don't mind if it is old Windows like XP working on this Zenfone, but I like windows to be my main OS on every phone which I may use in future (and hope they all be x86-64 and not ARM). So as I don't have Steamdect now (it has also AMD x86 CPU, like Zenfone), I want to do this, achieve it - having Windows on mobile - Zenfone.
I can carry it in pocket everywhere, so why not people like having desktop Windows x86-64 in each and every mobile? Even Lenovo are collaborating with IBM - then why not make also IBM-Mobile / IBM-smartphone, which will also be as good as PC - to unassemble it, change any part like on desktop, why not do it? I think everyone will enjoy it, and it will boost everything to better hights, levels.
So, please. If anyone here has similar experience of going to same screen like I have (see screenshot), or like that - black screen - indeed my device also may not even show any thing - even no ASUS logo, no bootloader (even if I press Volume-UP after powering and after flash it usually showed bootloader with robot - no... not now)...
So I don't see anything on screen of Android Zenfone now. no text, no bootloader, no recovery even - no TWRP menu. I think I am ready to format whole zenfone, and install there maybe some partition manager (like you know there is Partition magic on PCs, when I can split HDD/SSD nto two parts, one for Windows, and say other for Unix - Ubuntu or Android x 86 - all on same physical drive)... So I want some re-partitioning for intern SD memory, and be able to install there some ISOs, say with DOS, Win3.11, win 95, 98, 2000, xp, 7, 8,1 and maybe even 10. But guess last will be slow. I think Windows XP would be ideal OS for my Zenfone, if it can run fast. Win 7/8 maybe will be slow. But for some sceintific aims - like I just write some algorythm in Visual studio, and can do it even in WinXP, so why don't do it on my Zenfone? I don't like many Andorids, as they are not for work much - they are used by many people to play games, watch videos on phones, surf social networks, but not for real work. Real work is usually on WIndows, and no laptop can replace "Windows x86 in pocket" (on mobile). And I wonder why Microsoft develops "Windows for ARM" instead of investing millions into efforts like which Ycavan did - to make Windows run in KVM mode fast on x86 smartphones.
Ok, So, any ideas? What should I do now? I need some special tool to fix my phone first. Fix its loader. I think I need to bypass fastboot.exe restriction, which shows "waiting for device". Command in cmd like this: ADB.exe devices -L --- shows device from time to time - it shows:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
So, I cannot even flash some recovery device in this way. In devices manager I see "ADB interface" in "USB devices" category in devices treeview. And sometimes Moorefield appears, but with exclaimation mark - I have no idea how to make it disappear. I found here some info that I can install tool - xFSTK_Downloader_v1.7.0.zip - I downloaded it, installe,d but it doesn't run (I have win10 x64bit). hm... And driver required - iSOC_USB_Driver_Setup_v1.2.0.zip - I installed - but nothing.
So, what to do? How to make bootloader appear again? And how to write there prob=per bootloader with KVM kernel, and which firmware to flash so I can use KVM fast there with fast Windows...? Is it possible at all to make it run WIndows natively on Zenfone? or it will always be only in virtual machine inside some ArchLinux or in Limbo x86 on Android?
I read that Ycavan used this ArchLinux, but I don't understand why. Is he installing it over Android? Then also which version he uses? I need to know each and every version whcih he uses to make everything works. I 'ld require all the firmwares which he uses to make it work also - to make some Windows iso run on my Zenfone 2.
Did anyone achieved this successfully, except for Ycavan - to run Windows on Zenfone? Or except for him noone was able to install KVM kernel, and it was similar to mine situation? And maybe this is the reason why manufacturers of phons don't like x86 phones? I don't know. Any ideas?
See screenshots. What to do in this state?
IF anyone can please upload to somewhere whole pack of files ("WIndows on Zenfone starter kit") to make anyone able to just follow instaructions which will work in all cases to install WIndows there like Ycavan has - it would be great. There is lack of more detailed information - which .img files, .zips, firmwares etc, which OSes are supported by Ycavan's KVM kernels?
I have no idea. if anyone passed this path, and achieved Windows on Zenfone, please share your experiences, Ireally need it. Here in Ukraine when electricity disappears almost daily, we need devices like x86 phones almost for everyone. And mo matter if Windows is a bit old. KVM mode I guess must be much faster, almost native speed, so (like on tablet PCs), so please help...
Thank you all in advance, whoever will answer me.
indubhushan said:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
Click to expand...
Click to collapse
wrong mode. adb is only working in
- normal/boot mode
- recovery mode
fastboot is only working in
- bootloader mode
- fastboot mode
You can see 0123456789ABCDEF device in adb devices, therefore you are either in TWRP or in Android (Win?)
type adb shell and check the prompt is either $ (shell) or # (root shell)
in root shell you can flash partitions from cmd line. you can also reboot into bootloader/fastboot mode from cmd line.
Code:
adb reboot bootloader
I had success in restoring my bootloader (logo with android robot) - I intalled xFSTK, so somehow I had success to make it run, and I added threee files (1, 2, and 4th) and tried to flash it. Phone was visible as Moorefield. Then I tried to use Asus flash tool to flash big RAW image, but for some reason I don't know why - I had even whole day left it to flash, it didn't do the task - Android stopped booting - no logo showing at all - have to use xFSTK to recover. Maybe I use wrong RAW image (from official site it is .zip, so have no idea where to get those raw files).
When try to flash using flashboot - I get error: - flash cmd error.
As for devices list. My device rarely appear there. It may appear for some seconds, and then xfstk can have success to flash it, and maybe even make it runnable into Android robot scren (bootloader).
I am thinking that I need to install maybe ArchLinux, which Ycavan is using, but have no idea where to get RAW file for it, and how to flash it. Maybe some problem with my USB port on old laptop, or maybe even with USB cable (though have few good almost new cables, even new 4Amperes one). So maybe even problem in port of Zenfone itself (to change it). No idea. Because even when I tried to flash it (that huge 1GB file), phone disconnected, or showed "ready for commands", instead of showing process of ownloading RAW image/Android into phone's memory.
Flashboot/adb almost unusable. Well, I'll try, maybe it'll work.
My hope is try to go into CWM, run from it into "secret menu" on phone, and from it - to access internal memory of phone, and restore phone from backup. But when I tried to load into it once - it hanged on "clouds". I don't know...
And I don't think I'm ready now to format internal memory of phone or to repartition. At least I don't have backup on some external card (sd-card) etc.
as for adb. maybe it can't see my device, even if it is "recovery mode" (when see in devices manager in Windows - Moorefield). Now I'm stuck on xFSTK and can't go anywhere further like adding TWRP into phone, or foing into backup/restore menu on phone, and of course there is no Android. Even when I see Android robot (boot menu) - I feel happy, that at least phone shows anything, so at least bootloader workds. Maybe difference is in drivers - when I have Moorefield driver, then maybe it contradicts with Zenfone driver, and I have to reinstall them? Or use other OS? I have dual-boot (two Windowses on my laptop), so maybe I need to use one Windows - to work with Moorefield (xfstk) - when phone is in "worst" situation when no logo shows / no bootloader. And the other Windows I have to run on laptop - with Zenfone driver installed (I think it shows something like Asus device in device manager). But they seem to use contradicting drivers, I am not sure. And maybe it's some problem with my usb ports, but hope no. They seem to be ok... Maybe I'll have to go some day to give phone for diagnostics to repairing center again ;-(