Related
{
"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"
}
ANDROID ON INTEL ARCHITECTURE
AboutProject summary
Android on Intel® Architecture (Android-IA) is an open source project based on the*Android Open Source Project*(AOSP). Intel is a contributor to the AOSP and provides code for enabling Android on Intel Architecture platforms. (read more: About A-IA )
this is a thread for installing, exploring, discussing dual boot Win 8-8.1 and Android for XE700T1C, and I have XE700T1C-A01AE which is one of many variants of XE700T1C, in the official site of A-IA only XE700T ( for installation see These instructions )is supported which is a whole different model, the XE700T1C comes with a keyboard dock that transfer it to laptop style, so the installation will be much easier because we don't need USB hub and USB keuboard.
I tried this on my own risk on both Windows 8 and 8.1 preview. so by doing so you accept any risk from this procedure ... be patient and read carefully before you start
Update: XE700T1C-A01US confirmed working ... Thanks to p0k3y...
Update: Also See another great guide by @Adrian DC
http://forum.xda-developers.com/showpost.php?p=57941649&postcount=134[/COLOR]
Before you Start ...
It is highly recommended that you download and install the latest BIOS firmware from Samsung while you still have windows on the device. The installer requires windows to run, and recent versions provide significant improvements.
Full Back up your PC using the Samsung recovery ( if it is pre installed ) or any back up program. And you should create recovery USB drive
HOW TO MAKE RECOVERY USB DRIVE: ------>>> Microsoft Windows 8 Support
What you need ...
1- USB thumb drive 1 Gb at least.
2- Download the latest build for Samsung XE700T installer from A-IA site ( https://01.org/android-ia/downloads )
3- Download "Image Writer for Windows" from https://launchpad.net/win32-image-writer/
4- A space on your PC for Android (more details in the installation)
Preparing the USB thumb drive
1- Back up the content in the USB drive because it will be erased ...
2- Extract Samsung XE700T installer
3- Extract windows image writer tool and run Win32DiskImager.exe
4- Browse for the image you extracted from the Samsung XE700T installer
5- Select your USB drive letter and hit "Write"
6- Done
Installing .....
1- Restart your PC with the USB drive inserted and as soon as it start press "F2" or you can follow the other way which is:
A- swipe from right and enter settings from the charm bar and choose "change PC settings
B- go to general and scroll down to advance start up and press restart now
C- after restart choose "Troubleshoot"
D- then "Advance options"
E- then "UEFI firmware"
F- then "Settings"
2- After going into settings ... go to " Boot " and set " Secure boot to OFF "
3- Then from the first option select Boot device priority and put your USB in the first place.
4- Choose "Save"
5- After restart the installer begin you will get five options. select run interactive installer
6- It will ask you " do you want to reserve windows and dual boot " Type: Y
7- Then " Do you want to resize windows to make more space " Type: Y
8- You will be asked " Enter the size in Mib for Windows " and the installer calculate the minimum and maximum size and it recommends the maximum size ... if you choose that value you will get about 350 MiB internal memory for android and it is too small if you want to install large apps. so the trick is to subtract the amount you need from the maximum value for ex: if you have 116000 Mib maximum then if you type 110000 you will have a 6000 MiB for the internal memory for Android.
9- After that you will be asked " Install GummiBoot bootloader " Type: Y
10- Then set the boot menu timeout ...
11- After the installation is completed remove your USB drive and press any key to restart.
12- Done.
Note:
1- When the PC start you got options, use down key or volume down to navigate. up key or volume up key to select.
2- After the first boot of windows you may be asked to do disc check...
Things you may need in Android:
Google services framework and Google Play store. Download and extract (Zip in the attachment)
And this how to install it
After connecting to Wi-Fi, open the browser and download a file manager with root capability for ex: search for ES File manager, download, install, open the file manager and then root explorer then Mount R/W and set all the options to RW.
copy Google services and play store to: system/app ... then change their permission to rw- r-- r--
image
Exit the file manager and pull the quick setting toggles area from the upper right corner and select power off " this is how to turn off Android "
Turn on the PC again and enter android and open play store and enter your user name and password .... because adding account from setting will not work and force close it...
In play store there are many apps that set to be not compatible but it may work and if I remember for example angry birds space free is working fine after I transfer and install it. so you can try...
Another thing you must try ... Is the Xposed framework by @rovo89 thanks to him for x86 support...
Link to original post ...
http://forum.xda-developers.com/showthread.php?t=1574401
Xposed installer 2.3.1 in the attachments... And scrennshots in the second post ...
Known Bugs:
1- Auto brightness is working by default even if disabled
2- If you want to use the on screen keyboard you have to disable the hardware keyboard after each reboot.(shortcut found in the notification area)
3- Battery left percentage is ok at start up ... but then it is not updating ...
4- Tell me to add if i forget something
Useful info
keyboard shortcuts:
ESC = Back
Windows home = Android Home
Alt+Tab =switch between opened background applications
Ctrl+P = settings
Ctrl+M = settings/all applications
Ctrl+N = Nova launcher settings (if installed)
Ctrl+S = play store (in Nova launcher if installed)
Ctrl+W = select wallpaper for home screen
Ctrl+Alt+Delete = kill android and restart ( don't do it because you may lose data )
Fn + (F6 or F7 or F8) = mute, volume down , volume up ---- respectively
Fn+ F4 =home ( so pressing windows home button is easier )
In home screen , typing any letter will trigger search
i will add more if i find or remember
Screenshots
With Xposed framework installed...
Added benchmark screenshots... In the attachments
Will add videos as soon as I can...
amazing!! do you think it will hurt if i download a copy and try it on the xe500t (Atom processor)?
edmondt said:
amazing!! do you think it will hurt if i download a copy and try it on the xe500t (Atom processor)?
Click to expand...
Click to collapse
How many times does it have to be said, it wont work.
AndroidIA is custom tailored for intel core series processors not atom. Clovertrail as in the xe500t is also hardware locked to windows 8 (no idea why).
edmondt said:
amazing!! do you think it will hurt if i download a copy and try it on the xe500t (Atom processor)?
Click to expand...
Click to collapse
SixSixSevenSeven said:
How many times does it have to be said, it wont work.
AndroidIA is custom tailored for intel core series processors not atom. Clovertrail as in the xe500t is also hardware locked to windows 8 (no idea why).
Click to expand...
Click to collapse
Sorry but it's the truth...
Sent from my Galaxy Nexus using Tapatalk 4
salahmed said:
Sorry but it's the truth...
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
awww.... thanks for the quick reply guys ?
Sharing files
I just wanted to know if android is installed will it be able to access files such as documents pdf pics etc from windows 8
if not how can we make this work
That would require NTFS drivers installed in Android; I know how to do it in "normal" Linux but have never attempted with Android.
I use the micro SD card slot as a shared storage... So everything there can be accessed from both operating systems...
Sent from my Galaxy Nexus using Tapatalk 4
uninstall
How can i uninstall this and return back to just windows
This looks very cool and I want to try it on my XE700T. But don't want to screw it up and brick the thing. Has anyone else tried it successfully? Also, will this affect the ability to apply Samsung updates or Windows upgrades later?
---------- Post added at 10:03 PM ---------- Previous post was at 09:52 PM ----------
bdroid said:
How can i uninstall this and return back to just windows
Click to expand...
Click to collapse
So did you install it? Don't care for it? If so, what don't you like?
p0k3y said:
This looks very cool and I want to try it on my XE700T. But don't want to screw it up and brick the thing. Has anyone else tried it successfully? Also, will this affect the ability to apply Samsung updates or Windows upgrades later?
---------- Post added at 10:03 PM ---------- Previous post was at 09:52 PM ----------
So did you install it? Don't care for it? If so, what don't you like?
Click to expand...
Click to collapse
Its a regular x86 machine, you can't just brick them. You can seriously bugger up windows, but get a fresh windows install USB (can buy them I think, or you can make one from an install DVD) and you can reinstall windows from scratch, but it will cost you. Or you could be logical and make a recovery USB for your system first which would then allow you to restore anyway, if you own a windows 8 system you should make a recovery USB anyway.
Having android wont effect your windows partition at all. Presuming you dont just go over-writing your windows partition, which would be a dumb idea, and is also why you dont try this guide unless you know what your doing.
SixSixSevenSeven said:
Its a regular x86 machine, you can't just brick them. You can seriously bugger up windows, but get a fresh windows install USB (can buy them I think, or you can make one from an install DVD) and you can reinstall windows from scratch, but it will cost you. Or you could be logical and make a recovery USB for your system first which would then allow you to restore anyway, if you own a windows 8 system you should make a recovery USB anyway.
Having android wont effect your windows partition at all. Presuming you dont just go over-writing your windows partition, which would be a dumb idea, and is also why you dont try this guide unless you know what your doing.
Click to expand...
Click to collapse
Thanks. I just made a recovery USB. Am going to try out the recovery feature and make sure I know what to do before taking the plunge. So I take it you got this installed? Do you like it? Other than the bugs listed on OP, are there any other issues? Does it perform well? I hope so with the all-powerful Core i5...
p0k3y said:
This looks very cool and I want to try it on my XE700T. But don't want to screw it up and brick the thing. Has anyone else tried it successfully? Also, will this affect the ability to apply Samsung updates or Windows upgrades later?
---------- Post added at 10:03 PM ---------- Previous post was at 09:52 PM ----------
So did you install it? Don't care for it? If so, what don't you like?
Click to expand...
Click to collapse
@p0k3y ... if you have XE700T ... not the XE700T1C then follow these instructions from A-IA site:
Android on Intel ArchitectureSamsung XE700T
The Samsung XE700T Slate is a PC-compatible SandyBridge platform with touch-screen, USB host port, world facing camera, and Wi-Fi. The device also includes orientation and acceleration sensors, but they are non-functional in Android-IA due to the fact that they communicate using a proprietary protocol.
BIOS Update
It is highly recommended that you download and install the latest BIOS firmware from Samsung while you still have windows on the device. The installer requires windows to run, and recent versions provide significant improvements.
Setting the device to boot from USB thumb drive:
1.Grab an USB keyboard and plug it into a device USB port
2.Power on the device
3.After the power led is on, press the Home button and keep it pressed until the BIOS screen appears
4.Go to Boot menu using right/left arrow keys
5.Select Boot Device Priority using the Enter key
6.Go to USB KEY and press F6 until it becomes the top-most list item
7.Exit the Boot menu using the ESC key
8.Go to the Exit menu and select Save Changes and Reset using Enter
9.Power off the device and then power it on again
10.After the power led is on, press the Home button and keep it pressed until the BIOS screen appears (we need to enter the BIOS again to check the Legacy USB Support, sometimes it is disabled, after the first change in the BIOS)
11.Go to the Advanced menu using the right/left arrows
12.If the UEFI Boot Support is Disabled, change it to Enabled
13.Exit BIOS with Save Changes and Reset, as described above
14.Power off the device
15.Unplug the USB keyboard
Samsung XE700T Machine Check Error
Several users ran into a situation (when experimenting with a different kernel) that the machine would just get a "Machine Check Error" when trying to boot, either with or without the USB stick. This occurred after booting from the USB stick both with and without install-to-disk. Recovery procedure:
1.Power-on the machine while holding down the upper volume button on the left-hand side. This goes into the the Windows Boot Manager as in the "Gotcha" section above.
2.Let it go ahead and attempt to boot. This fails, however the failure mode is different because it is now trying to boot off of hard-disk, and gets a "Boot error" in the upper-left corner of the screen, instead of "machine check error".
3.Reset the system and power-on while holding the "windows" button at middle-bottom. This enters BIOS setup screen.
4.Re-enable "legacy USB", if needed.
5.Change boot-order to boot from the USB-stick first, hard-disk second.
6.Reboot from the USB stick.
7.Re-install a working OS to hard-disk.
Samsung XE700T touchscreen anomalies
Occasional users find that the touchscreen is not working with a Samsung device. This can be caused by some unknown compatibility issues with some USB hubs. If you run into this, a workaround is to unplug all USB device including the hub and just plug in the keyboard directly. Similar issues have been seen with oddball USB network adapters.
Samsung XE700T Restore Procedure
As mentioned in the Quick Start, it is important to back up any user data on the device before erasing it and over-writing it with Android. In addition, it is important to retain the original OS installation media, in case you want to restore the originally installed OS. These are referenced in the following restoration procedure.
To restore the Samsung XE700T to its factory default state you will need the following items:
•USB hub with at least three ports available
•USB keyboard
•USB mouse
•Samsung System Recovery Media (shipped with your slate PC)
•Samsung System Software Media (shipped with your slate PC)
•If restoring directly from a DVD ◦USB DVD-ROM Optical Drive (if restoring directly from DVD)
•If restoring from USB thumb drive ◦DVD-ROM Optical Drive on a separate PC (instructions provided for Windows and Ubuntu)
◦USB thumb drive -- 8GB or larger
System Recovery Media Prep -- USB thumb drive (Ubuntu Linux)
1.Install gettext (sudo apt-get install gettext).
2.Install gparted (sudo apt-get install gparted), it's a GUI tool that we'll use to format the thumb drive.
3.Download the latest stable version of ms-sys from http://ms-sys.sourceforge.net/#Download
4.Unpack the ms-sys***.tar.gz, cd to it in the terminal, then execute the following commands:
5.make
6.sudo make install
7.Launch gparted, select your thumb drive in the upper right corner.
8.Delete all partitions on the thumb drive, if any are present.
9.Go to Device -> Create Partition Table , in the dialog that appears click "Advanced" and select ms-dos partition table.
10.Go to Partition -> New and select NTFS, select all available drive space.
11.After the formatting is over, go to Partition -> Manage flags and check the "boot" flag.
12.Copy all files and folders from the Samsung recovery DVD to the thumb drive.
13.Open your terminal and create Win 7 MBR by executing the following command(replace /dev/sdX with your thumb drive's path):
14.ms-sys -7 /dev/sdX
System Recovery Media Prep -- USB thumb drive (Windows)
Note: These steps are not necessary if you plan to use a USB optical drive and the System Recovery Media DVD for the restore.
1.If necessary, download and install a program that will rip DVD discs to an ISO file. We use LC ISOCreator, which can be found at http://lc-iso-creator.en.softonic.com/.
2.If necessary, download and install a program that will burn ISO images to the thumb drive. We use the tool at http://www.isotousb.com/.
3.Format your thumb drive with a FAT32 file system.
4.Rip the Samsung Recovery Media DVD into an ISO file with ISOCreator.
5.Burn the Samsung Recovery Media ISO onto the thumb drive with isotousb.
Restore Steps
1.Power down the XE700T.
2.Connect the USB hub to the USB port on the XE700T.
3.Connect the keyboard, mouse, and recovery media (using either an optical drive or a USB thumb drive) to the USB hub.
4.Insert the System Recovery Media DVD into the optical drive if using the optical drive.
5.Hold down the center button (Windows key) and power on the device. Continue holding the Windows button until the BIOS setup screen appears.
6.Hold down the rotate button (right edge of tablet below the power button) until the Advanced section of the BIOS UI is highlighted.
7.Select 'Legacy USB Support' and make sure it is set to 'Enabled.'
8.Hold down the rotate button and use the volume up or volume down buttons until the Boot section of the BIOS UI is highlighted.
9.Select 'Boot Device Priority', making changes so that the recovery media (DVD drive or thumb drive) is the primary boot device.
10.Make sure that the UEFI Boot option in the BIOS is also set to 'Enabled.'
11.Press the Windows key once, and then hold down the rotate button and use the volume up or volume down buttons, until the Exit section of the BIOS UI is highlighted and then select 'Save Changes and Reset.' The XE700T should now boot off of the recovery media and the Windows installer should start.
12.Select your language and go through the setup process, until it asks you for the type of install. Select 'Custom' and then delete all existing partitions.
13.Select the available disk space after deleting all of the partitions as the install location for Windows.
14.At this point, the Windows installation should proceed.
15.(Optional) Install the Samsung System Software packages from DVD-ROM or USB key by connecting your media and running SecSWMgrGuide.exe from the media and following the prompts.
Samsung XE700T Gotcha!
Take care, when powering-up the unit, that you don't accidentally press the Volume-Up button (for example, if grip the tablet with your left hand) at the same time as you press the Power button, or the unit will go into "Samsung Recovery Mode" (that is, to the Windows Boot Manager, which is looking for the Windows installation disc). After that, the unit will never boot Android, instead displaying the words "Boot error" in the upper-left corner of the screen. (You will need to install Android again.)
This problem will probably not be observed in images downloaded and built since 5/24/2012, when a patch fixing this issue was integrated.
Click to expand...
Click to collapse
as I mentioned in the OP the XE700T is officially supported ... link to the site https://01.org/android-ia/documentation/samsung-xe700t
@bdroid ... use a recovery USB to roll back to windows only...
if you accidently lost recovery ... here is the link for XE700T1C-A01US reocovery image zip ... just unzip it to USB then boot using it and follow the onscreen instructions...
BTW this Recovery zip is not mine ... but I tried it and it is 100% working ...
https://mega.co.nz/#!0FYGCA5T!YoITKE30U5l-O0UQGnJIslhx1f4uYiAKFbqnrB1FcbA
credit to (peterf) from another forum...
salahmed said:
@p0k3y ... if you have XE700T ... not the XE700T1C then follow these instructions from A-IA site:
Click to expand...
Click to collapse
I actually have the XE700T1C-A01US. So should I use the instructions from the OP or from your link? Thanks!
p0k3y said:
I actually have the XE700T1C-A01US. So should I use the instructions from the OP or from your link? Thanks!
Click to expand...
Click to collapse
From the First post...
And I added a third bug... Please check it...
Sent from my Galaxy Nexus using Tapatalk 4
salahmed said:
From the First post...
And I added a third bug... Please check it...
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Battery indicator? That's not a show-stopper. Back to my question - safe to use your original instruction for my model? Thanks!
p0k3y said:
Thanks. I just made a recovery USB. Am going to try out the recovery feature and make sure I know what to do before taking the plunge. So I take it you got this installed? Do you like it? Other than the bugs listed on OP, are there any other issues? Does it perform well? I hope so with the all-powerful Core i5...
Click to expand...
Click to collapse
I dont own a windows tablet no.
From what I have heard though, core i5 systems benchmark damn well for android but have 2 notable issues.
Firstly they don't use full hardware acceleration, I dont know if thats a thing being worked on or what, but for now the sheer CPU power just hammers its way through that.
Secondly its an x86 processor. Android apps use what is called a virtual machine (its called dalvik, alot of people claim its java, but its not) which allows them to run on any hardware. However some apps use what is known as the android NDK, or native code running outside of the virtual machine. Reasons for this are code re-use (android ports of some iOS apps take this approach) or performance. The android NDK is platform specific, with the default settings if you create an app using the NDK, it will throw the little dalvik bit in needed to start the app and then it will compile the native parts for ARMv7 (most android devices). Changing the settings allows for x86, ARMv6 and MIPS but not everyone changes that, especially as it leads to its own problems in either distributing separate x86 and ARMv7 apps (possible) or it will let you throw both x86 and ARM versions in one app but this leads to an app double the size it needs to be. So nice and simple, many developers ignore it entirely and leave it at ARM only.
So you may come across certain apps which don't function on your device. The x86 devices sold to consumers such as the galaxy tab 3, do include an ARM emulator to help avoid some of the above issues, sadly android-ia and androidx86 dont do that.
Have fun. And yeah, test that you can get into your recovery first, always a good idea.
p0k3y said:
Battery indicator? That's not a show-stopper. Back to my question - safe to use your original instruction for my model? Thanks!
Click to expand...
Click to collapse
You made a backup... And you have a recovery... And I give you a link to a working recovery image in case you need it...
Please try it... So it can be added to the OP...
It is not hard to recover your PC...
The long story:
I was running windows 8 then installed 8.1 preview to try it then installed android... Everything was OK... Then I was trying to play unlucky game with the partitions and corrupt them... But I used the recovery USB ... Back to windows 8 then installed android again...
Sent from my Galaxy Nexus using Tapatalk 4
salahmed said:
You made a backup... And you have a recovery... And I give you a link to a working recovery image in case you need it...
Please try it... So it can be added to the OP...
It is not hard to recover your PC...
The long story:
I was running windows 8 then installed 8.1 preview to try it then installed android... Everything was OK... Then I was trying to play unlucky game with the partitions and corrupt them... But I used the recovery USB ... Back to windows 8 then installed android again...
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Thanks, I will try it soon. What I meant by "safe" was whether your instruction applies to my model XE700T1C-A01US. I think it does. But let me know if it doesn't.
First of all, I not responsable for lost of keys and Data!
Stuff necessary:
2 Pen drive ( one for backup windows 8.1, and the other for windows 8.0)
Surface RT (LOL)
Use your surface to create a recovery USB stick with Windows 8.1
Download Windows RT 8.0 recovery image from Microsoft
Copy the file "install.wim" (located under "sources" from your downloaded 8.0 recovery image to your 8.1 recovery USB stick
Boot your surface with the 8.1 recovery USB
Start a cmd session (after choosing "Troubleshoot" -> "Advanced options" ...)
Use diskpart to delete both recovery partitions and the system partition
Create a new partition and format it with NTFS
Make it active and assign this partition a drive letter (for example G
Close diskpart
Use dism to install the Windows 8.0 image to your drive (if you saved the "install.wim" from the Windows RT 8.0 image to your USB sticks root dir, use this command: dism /apply-image /imagefile:\install.wim /index:1 /applydir:G:\
I Will update more step and most important
UPDATE
After follow all step your Surface will be bricked.
Use USB sick with WIN8.0 recovery to restore all partition, and DONE you have WIN8.0
your method is very very complicated mate.. it's actually MUCH easier than that:
1- get a 8gb usb
2- format it as fat32
3- extract the surface RT 8.0 zip into the flash. (get it from the piratebay link)
4- stick the flash disk in the surface.
5- go to: charms bar -> settings -> change pc settings -> last option -> advanced startup
6- select the USB then follow the rest of the steps here: https://thepiratebay.mn/torrent/9196163/Surface_RT_Downgrade_Image_8.0_Direct_from_Microsoft
Attach the USB recovery drive to Surface.
Hold the volume-down (-) rocker.
Press and release the power button.
When the Surface logo appears, release the volume rocker.
Choose your language options.
Choose your keyboard layout.
From the BitLocker screen, tap or click Skip This Drive.
The keyboard might appear so tap the non-text area of the screen to dismiss it so you can see the Skip This Drive link.
Tap or click Troubleshoot.
Tap or click Reset your PC.
Tap or click Next.
This is actually a button that says “Windows 8.1 Preview”. This kinda threw me. Select this button, it will give you Windows 8.0. You will have to wait a bit for the next screen to appear.
Surface Pro only: Tap or click No, keep the existing partitions.
I saw this on my Surface RT. I selected “No” like this says.
Tap or click Just remove my files.
When Surface displays All ready to go, tap or click Reset."
Click to expand...
Click to collapse
you'll get windows 8.0 very easily.
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.
Hello
I have a shield tv 2015 with nvidia experience 8.1 (android 9) - last October 2, I upgraded to 8.0.1, installed and when it was to restart, turned off and did not turn on.
Turns on the 2 sec green light and turns it off and the disc works (it seems to be in standby).
I opened a ticket (on nvidia) but it is being useless because the procedures that give me do not work.
I found that underneath is a snap-in cover. so i turned off the hard drive it always turns on the green light but i can't get into fastboot / recovery mode.
At the moment when I connect the usb cable to the pc I have an APX device. does anyone know anything about APX?
Thanks help me please i´m a nood
Your only bet is to get help from nvidia costumer support since it's not a pro version.
Apx mode = your device is bricked.
Mine is the 500GB version I suppose is the PRO version.
I've been reading here in the forum ... in the PRO version the
All software is on the hard drive. So I was trying to create the hard drive with a 500GB disk but to no avail.
parfuar said:
Mine is the 500GB version I suppose is the PRO version.
I've been reading here in the forum ... in the PRO version the
All software is on the hard drive. So I was trying to create the hard drive with a 500GB disk but to no avail.
Click to expand...
Click to collapse
You can try what has been done in this thread https://forum.xda-developers.com/shield-tv/general/bricked-shield-tv-pro-2015-version-t3841024
Or something like this https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
Hi,
One question.
My original hard drive
Info:
[email protected]:/home/ubuntu# hdparm -i /dev/sda
Model=ST500LM000-1EJ162, FwRev=SM16, SerialNo=W763XDYH
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: Reserved: ATA/ATAPI-4,5,6,7
* signifies the current active mode
-------------------------------------------------------------------------------------------------------------------------------------
fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb22c3a15
my new hard drive
info:
[email protected]:/home/ubuntu# hdparm -i /dev/sda
Model=HGST HTS545050A7E380, FwRev=GG2OACD0, SerialNo=TE85113R0Y5TPK
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: mode=0x01 (1) WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7
* signifies the current active mode
----------------------------------------------------------------------------------------------------------------------
--->> fdisk -l
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x4ca778fd
Hard drives are the same, I should with the tutorial, be able to get the shield to work without major problems.
what is wrong?
commands used:
dd if=start.bin of=/dev/sdX bs=4M
dd if=end_976574630.bin of=/dev/sdX seek=976574630
with these files:
https://forum.xda-developers.com/sho...2&postcount=23
My shield(2015 pro) was also bricked by the update reboot loop at nvidia logo and factory reset did not help and fastboot couldn't flash anything, so used this opportunity however to put a ssd in.
Used beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Just booted it up and its gotten past nvidia logo atleast so far
First time it bricked was updating to 8.0, after recovery it was able to get the updates up to 8.0, when i did the 8.0.1 update i also got the same error as those above where turns on then off and does not even wake the display.
HellToupee_nz said:
My shield(2015 pro) was also bricked by the update reboot loop at nvidia logo and factory reset did not help and fastboot couldn't flash anything, so used this opportunity however to put a ssd in.
Used beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Just booted it up and its gotten past nvidia logo atleast so far
Click to expand...
Click to collapse
It worked?
what version of android is it?
on mine it didn't work. only worked with the first part (firstpart.bin which is like this) and with the 5kb file that speak at the end of this thread.
parfuar said:
It worked?
what version of android is it?
on mine it didn't work. only worked with the first part (firstpart.bin which is like this) and with the 5kb file that speak at the end of this thread.
Click to expand...
Click to collapse
In my case, I have the fastboot. but this is difficult because we don't have active developer mode.
Yes, i had done a factory reset also, u can get stuck at the spinning android logo forever without that i find. For the end part of the disk i used my own from my disks image, i've just done it all again and updated back to 7.2.3 stopped there and copied my widevine key off my orginal image so got L1 support and going to make backup of its current state.
parfuar You don't use "sdX" you change the "X" to the letter your drive is from fdisk -l , looks like you need to use "sda", after after you write the two bin files reboot directly into bootloader and select boot recovery kernel which will bring up t wrp recovery and you need to perform a factory reset wipe then reboot and Android should boot up and you will have Nvidia experience 3.3 and you have to do a couple updates to get up to 8.0 just make sure you turn off automatic updates cuz mine automatically updated to 8.0.1 and crashed my hard drive a second time. I used my original hard drive
also posting here that my 2015 500gb gets bricked with 8.0.1. hdd swapped out for crucial mx500. i think the guy here said it happened on his stock 500 sshd?
OK... This is how I got it to work.
Using "DD for Windows"... since I don't have a Linux PC (tested working perfectly on Windows 10 x64)
Download link:
http://www.chrysocome.net/downloads/dd-0.6beta3.zip
Unzip the "dd.exe" file and copy it to:
%USERPROFILE%\AppData\Local\Microsoft\WindowsApps
This gives you the ability to use DD system wide.
Use the beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Connect your drive. I highly suggest using a Desktop PC because it is much faster than a USB to Sata cable.
If you don't have any open Sata slots, just disconnect your CD-rom drive temporarily and use the connectors.
Now:
1) Put the "start.bin" file in the root directory of drive C (example C:\start.bin)
2) Open a command prompt as Administrator and change directory to C: (command: cd C:\ )
3) Type command dd --list to determine the correct disk you want to write to.
4) Use command dd if=start.bin of=\\?\Device\HarddiskX\Partition0 --progress
whereas X is the drive number you determined earlier with the dd --list command
(replace the X with the drive number you want to write to)
5) Watch the write progress and stop the process at about 6GB (around byte 6,500,000,000)
(you can actually see the write counter running)
There is no need to write the "end file". Shut down the PC once finished and remove the drive.
6) Install the drive back into your Shield Pro and start. The green NVIDIA logo should show up soon.
Wait for about 10 minutes and if nothing happens unplug the Shield and do a restart.
Now wait patiently.... it will eventually boot past the green logo and the Android colors.
Now let your Shield self-update to whatever version you desire. It starts with version 3.0
That's it! You just successfully de-bricked your Shield Pro
Enjoy!
Hello, I have a laptop with both windows 10 and windows 11 installed (on the same SSD). Is it possible to access the windows 10 files from windows 11 and vice versa?
If it helps, i have:
AMD Ryzen 5 3500U
8GB DDR4 RAM
512 GB SSD
Lenovo Idea ThinkPad 15ADA05
JoshyJoshy said:
Hello, I have a laptop with both windows 10 and windows 11 installed (on the same SSD). Is it possible to access the windows 10 files from windows 11 and vice versa?
If it helps, i have:
AMD Ryzen 5 3500U
8GB DDR4 RAM
512 GB SSD
Lenovo Idea ThinkPad 15ADA05
Click to expand...
Click to collapse
Yes. It's possible to access files from both OS and vice versa.
You have to create Boot Paths of selected OS and add it's entry in Boot manager (boot.ini) file.
To do this in user friendly way, Download EasyBCD online and install the software, after installing you will see the input selected boot entries in main panel in side panel select to create new boot entry, in create section, select windows 10 or 11 based on where do you install software, just select opposite. If you install software on win 10 select windows 11, select it's installed hard-disk partition and select it's custom directory as - C:/Windows/system32/winload.exe
OR
It will be automatically select it's boot location based on HDD partition label (C:, D:, F:,etc) save the configuration, after saving you will see the 2 entries in selected boot entries. After that restart PC, after restarting, try to boot given Windows 10/11 in Windows boot manager prompt. But see that sometimes it happens if you select windows 10/11 then again it will switch on same OS where the software is installed. But if the boot manager found out the correct mentioned file/directory in given HDD partition, it will boot normally in that OS, but if not found, it will show error as "Recent hardware or software might changed, regarding file is missing from system and it's code as 0x0000cbd8, or any."
If you didn't understand, then kindly send me screenshots of given procedure..