Hi, I've bricked my x96 (2G ram, 16G rom) box, the reset button isn't working and I don't have a windows machine to use aml burning tool, I've been playing with the linux versions of the tools but with no luck, I can't put my box in "burn mode", someone has any similar experience with this box?
Thanks!
pablitok said:
Hi, I've bricked my x96 (2G ram, 16G rom) box, the reset button isn't working and I don't have a windows machine to use aml burning tool, I've been playing with the linux versions of the tools but with no luck, I can't put my box in "burn mode", someone has any similar experience with this box?
Thanks!
Click to expand...
Click to collapse
what system do you have, why not set up a windows VM?
also check out my s905x ROM
https://forum.xda-developers.com/an...om-android-tv-custom-rom-7-1-2-s905x-t4098131
aidanmacgregor said:
what system do you have, why not set up a windows VM?
also check out my s905x ROM
https://forum.xda-developers.com/an...om-android-tv-custom-rom-7-1-2-s905x-t4098131
Click to expand...
Click to collapse
Thanks for your reply.
I have a macbook and a raspberry, tried to run virtualbox with linux on the mac but it couldn't see the attached usb device (don't know if it's related to having everything connected through an usb c hub and my lack of knowledge).
The raspie detected the tv box but not in burn mode and I cannot put it in that mode.
Should I try again with a virtualbox windows image? should I throw the box?
pablitok said:
Thanks for your reply.
I have a macbook and a raspberry, tried to run virtualbox with linux on the mac but it couldn't see the attached usb device (don't know if it's related to having everything connected through an usb c hub and my lack of knowledge).
The raspie detected the tv box but not in burn mode and I cannot put it in that mode.
Should I try again with a virtualbox windows image? should I throw the box?
Click to expand...
Click to collapse
Never throw the box, thats admiting defeat, would try windows vm if you can
aidanmacgregor said:
Never throw the box, thats admiting defeat, would try windows vm if you can
Click to expand...
Click to collapse
You are 100% right. I'll make a windows vm and see if can make some magic
These boxes are generally quite resistant, what about bootcamp on your mac?, used to have a small partition on my imac that had windows dual boot, it has official apple drivers for windows and is available to download via apple
https://support.apple.com/en-gb/boot-camp
Would have best chance of working as things will be native like USB rather than emulated
aidanmacgregor said:
Never throw the box, thats admiting defeat, would try windows vm if you can
Click to expand...
Click to collapse
Didn't have any luck with virtualbox vm, didn't detect anything, but my mac also can see the device... but when I try to run the linux amlogic utilities, they say that there is no amlogic device connected (I guess is something related to different device paths between mac and linux).
Resuming: The board is detected, but I can't put it in burn mode... maybe I should give up this time for a while... after covid, maybe I can get someones windows pc...
Hopefully get it sorted
aidanmacgregor said:
These boxes are generally quite resistant, what about bootcamp on your mac?, used to have a small partition on my imac that had windows dual boot, it has official apple drivers for windows and is available to download via apple
https://support.apple.com/en-gb/boot-camp
Would have best chance of working as things will be native like USB rather than emulated
Click to expand...
Click to collapse
Sadly, I can't, it's from the company I work for... Tomorrow I'll try with an old pc with win xp if I can make it work...
pablitok said:
Sadly, I can't, it's from the company I work for... Tomorrow I'll try with an old pc with win xp if I can make it work...
Click to expand...
Click to collapse
The burning tool should work with windows XP
heres the link to the version i use
https://drive.google.com/open?id=1oS0WAjJ-u9IaKb4GSd8zqHL4VbCHjhiW
Good luck, let me know how you get on
Related
I wonder how I can upgrade my x10 mini pro to android 2.1 from my linux pc. I don't have any windows box at all. I'm looking for somthing like htc-flasher, but for x10.
Anyone?
Well, I dont know if that would help, but i just updated in Linux through Virtualbox
ambrosiosanchez said:
Well, I dont know if that would help, but i just updated in Linux through Virtualbox
Click to expand...
Click to collapse
Can you elaborate on how you did this? Because it wasn't possbile for me in VirtualBox, due to the fact that it didn't keep the USB connection.
I’m guessing he is using the non-free version of virualbox with usb support. I don't have a windows cd, so that’s no option.
Maybe the java tool posted in this thread forum.xda-developers.com/showthread.php?t=826455 can be used on linux after some modifications?
Yes, that was a must.
To keep the USB connection you have to add it as a filter in the settings tab:
Without starting the virtual machine, connect the phone and go to settings > usb, select to add a filter and select the phone. I think that should work for PC Companion. If you plan to update with seus the usb device is a different one, so you should put the phone in flash mode and add the filter for the corresponding device. After the update, the name of the devices will change again, so you need to add new filters again.
Btw, I wasn't able to root through Virtualbox using Superoneclickroot but I think it was because I didn't stop PC Companion properly...
mr_cos said:
I’m guessing he is using the non-free version of virualbox with usb support. I don't have a windows cd, so that’s no option.
Maybe the java tool posted in this thread forum.xda-developers.com/showthread.php?t=826455 can be used on linux after some modifications?
Click to expand...
Click to collapse
Yes, you also need usb support.
If you don't have any windows at all maybe you could try flashtools in wine...
ambrosiosanchez said:
If you don't have any windows at all maybe you could try flashtools in wine...
Click to expand...
Click to collapse
Thanks, but I don't think wine have usb support.
ambrosiosanchez said:
Yes, that was a must.
To keep the USB connection you have to add it as a filter in the settings tab:
Without starting the virtual machine, connect the phone and go to settings > usb, select to add a filter and select the phone. I think that should work for PC Companion. If you plan to update with seus the usb device is a different one, so you should put the phone in flash mode and add the filter for the corresponding device. After the update, the name of the devices will change again, so you need to add new filters again.
Btw, I wasn't able to root through Virtualbox using Superoneclickroot but I think it was because I didn't stop PC Companion properly...
Click to expand...
Click to collapse
How did you root the phone then?
mr_cos said:
Thanks, but I don't think wine have usb support.
Click to expand...
Click to collapse
I think it has some very primitive support, but certainly I wouldn't go that way...
Ben.Hahlen said:
How did you root the phone then?
Click to expand...
Click to collapse
This morning I had acces to a computer with windows, and I tried to root using Superoneclickroot and I ended up having the same problem as with Virtualbox (the program was running but it was stuck at a loop), but this time I tried Ctrl+Alt+Del > Manage tasks > Finish PcComapnion, and it automatically rooted. I think If I had done the same before It would have worked...
rooting the phone with linux works like a charm... you need the sdk from h t t p : / / developer.android.com/sdk/index.html (sorry i can't post correct links)... i haven't tried flashing it yet because i'm waiting for the official update in switzerland
munzli said:
rooting the phone with linux works like a charm... you need the sdk from h t t p : / / developer.android.com/sdk/index.html (sorry i can't post correct links)... i haven't tried flashing it yet because i'm waiting for the official update in switzerland
Click to expand...
Click to collapse
I guess you are talking android 1.6 for the rooting from linux with android sdk tools (adb?)
mr_cos said:
I guess you are talking android 1.6 for the rooting from linux with android sdk tools (adb?)
Click to expand...
Click to collapse
exactly... as soon as i have 2.1 i'll post what method i used
This is driving me crazy. I am also trying to install the 2.1 update with virtual box (non-free 3.2.10) on Mini Pro.
I am unable to get a proper USB connection to the device although it shows in the filters settings when I boot the VM it remains greyed out.
Can anybody else report success?
Sony Ericsson deserve a big slap for this.
Update: Sorry to solve my own problem, but isn't this so often the way after you ask for help:
I had to add my user to the vboxusers group, after which the usb connection worked fine.
munzli said:
exactly... as soon as i have 2.1 i'll post what method i used
Click to expand...
Click to collapse
adb works great in Linux, both for 1.6 and 2.1, but the problem is there are no flashing tools available to update.
As for rooting the phone, the program I used in 2.1 (superoneclick) seems to be a gui for some batch process in adb, hence maybe reproducing all this steps in adbshell (pushing the necesasary files, running rageagaintshecage, getting the mountpath...) one could root the phone the same way...
It looks like the superoneclick author will add linux support in the next release.
forum.xda-developers.com/showthread.php?t=803682
to bad the USBFlash.dll is from sony ericsson. we'll never know what the library does.
but i just played through the game of updating using a virtualbox windows machine... works like a charm. wrote down the simple steps to get it done here: h t t p : / / munz.li/?p=110
munzli said:
but i just played through the game of updating using a virtualbox windows machine... works like a charm. wrote down the simple steps to get it done here: h t t p : / / munz.li/?p=110
Click to expand...
Click to collapse
Excellent howto, good work
mr_cos said:
It looks like the superoneclick author will add linux support in the next release.
forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Good, I hadn't seen that before. And well, looks like it's already supported. I just installed it,
you have to run the .exe file through mono. I tried and looks like working correctly, it detects the phone... but mine is already rooted so I'm not sure...
http://forum.xda-developers.com/showpost.php?p=8699742&postcount=537
I think I've made a huge mistake.
I just wiped my device in TWRP because the last CM Nightly I installed was acting up.
I went into TWRP, wiped and factory reset. I then rebooted and went into TWRP again.
I wanted to install CM 9.1, which I copied onto my 64GB SanDisk Ultra, and I was thinking to just flash it from the external sd.
I read somewhere on xda that I needed to maybe use a smaller SD card and have the format in FAT32, which I did, but TWRP still does not recognize them.
I am currently stuck with TWRP v2.3.1.0, no way to flash a new rom from a blank internal memory or an external memory.
I tried updating SDK and the most updated drivers for the device through the Device Manager and use "adb push" or "adb sideload" but the device is not recognized.
Can someone give me some kind of suggestion to solve this situation.
I’d suggest using a linux install to do the adb stuff if you’re not doing so already, no need for crazy windows drivers to see a connected device.
Sent from my EPAD using xda app-developers app
squidlr said:
I’d suggest using a linux install to do the adb stuff if you’re not doing so already, no need for crazy windows drivers to see a connected device.
Sent from my EPAD using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
Can you elaborate a bit on what a linux install is? My PC has W8 on...
kgal said:
Thanks for the reply.
Can you elaborate a bit on what a linux install is? My PC has W8 on...
Click to expand...
Click to collapse
Windows 8 is a bugger to get drivers working properly.
Try and use a windows 7 machine or a friends laptop or try the following instructions.
Windows 8 Instructions
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Ubuntu is a linux based Operating System, and can be used to do most things Windows 8 does, sometimes worse, sometimes better. So in this case, it's less trouble to connect an android device to a linux OS such as Ubuntu, as it can recognize a telephone without having to install drivers.
If you want to give it a go, you can install Ubuntu alongside Windows 8.
http://www.makeuseof.com/tag/tired-of-windows-8-how-to-dual-boot-windows-ubuntu/
And then install Fastboot and ADB:
http://putokaz.wordpress.com/2012/08/29/install-adb-and-fastboot-android-tools-in-ubuntu-via-ppa/
But, I'd stick to Windows and follow the advice of Flumpster if you're not too confident installing a second operating system.
I can and have knowledge of installing another OS to run alongside Windows.
I use VirtualBox to run Mac OSX and Android. Can I run Linux on VirtualBox and do the process through that?
I am not quite sure what I should do after disabling Driver Signature Enforcement on Windows 8...
Yes, you can install Linux in a virtual machine - give it a try. If the device is still not recognized via OS running in the virtual machine, you can then always install to your hard disk and try that route.
The other option is to run Ubuntu as a live cd eg from the disk in memory (not install) and do it that way. I first unlocked and rooted my mobile this way. I can give more info on this if you like.
jamesthedisciple said:
The other option is to run Ubuntu as a live cd eg from the disk in memory (not install) and do it that way. I first unlocked and rooted my mobile this way. I can give more info on this if you like.
Click to expand...
Click to collapse
I think I'll give a multi-boot option a try. I've been wanting to install a different OS anyway since upgrading to Windows 8. Now I just have incentive.
kgal said:
I think I'll give a multi-boot option a try. I've been wanting to install a different OS anyway since upgrading to Windows 8. Now I just have incentive.
Click to expand...
Click to collapse
Just a quick thought after re-reading your first post, I'd try a smaller sd card (16 or 32GB). I have heard of the larger faster cards giving some people problems.
Solved!
After trying to install Linux using Ubuntu 13.04 and getting more errors (something with the UEFI vs Legacy Boot installation), I decided to retry and find the original Windows drivers for the TF201.
I found one through Softpedia, downloaded it, used the "Have Disk" option when installing the yielded "Transformer" device in the Device Manager and sideloading the new CM 10.1 Nightly onto it.
Works like a charm!
Thanks everyone for the support!
My idea is to install the Remix OS on a USB stick or a SD card, so i can use it on PC and on my Tablet.
Is that possible? Or are the versions very different?
My Tablet is the Chuwi HI8 with dual os, but i want a thrid OS, which could be booted by USB oder SD Card.
I tried a little, but can you tell me how to start from USB oder SD Card? Is it only possible to start from BIOS or is there any other solution?
Or is it even possible to boot from Chuwi HI8 tablet on sd card? I know that there is OTG function, but i dont know if it is possible to boot from SD card.
The same on PC, do i have to start from BIOS or are there settings to from a operating system like Windows 10?
I'm on teclast x98 plus. Would also like to know thanks!
Sent from my SM-N920C using Tapatalk
manuelbvb said:
My idea is to install the Remix OS on a USB stick or a SD card, so i can use it on PC and on my Tablet.
Is that possible? Or are the versions very different?
My Tablet is the Chuwi HI8 with dual os, but i want a thrid OS, which could be booted by USB oder SD Card.
I tried a little, but can you tell me how to start from USB oder SD Card? Is it only possible to start from BIOS or is there any other solution?
Or is it even possible to boot from Chuwi HI8 tablet on sd card? I know that there is OTG function, but i dont know if it is possible to boot from SD card.
The same on PC, do i have to start from BIOS or are there settings to from a operating system like Windows 10?
Click to expand...
Click to collapse
Two ways, 1. You can add an entry to windows bootloader
2. Use EasyUEFI, which you can use to change the boot order like you would in BIOS/UEFI.
Booting from sdcard woukd be conditional on the device; from usb should be fine. My i7 stylus for example won't boot from sdcard.
All that being said the hi8 is baytrail right? I think support and drivers for baytrail isn't 100% with Androidx86/RemixOS
HypoTurtle said:
Two ways, 1. You can add an entry to windows bootloader
2. Use EasyUEFI, which you can use to change the boot order like you would in BIOS/UEFI.
Booting from sdcard woukd be conditional on the device; from usb should be fine. My i7 stylus for example won't boot from sdcard.
All that being said the hi8 is baytrail right? I think support and drivers for baytrail isn't 100% with Androidx86/RemixOS
Click to expand...
Click to collapse
Ok thank you, and how to add an entry to windows bootloader?
i am not so familiar with BIOS settings.
So i can use the same Remix Os on tablet and on PC? I only have to install it on the USB?
And because my tablet is 32bit i have to use the 32bit version of Remix OS right?
manuelbvb said:
Ok thank you, and how to add an entry to windows bootloader?
i am not so familiar with BIOS settings.
So i can use the same Remix Os on tablet and on PC? I only have to install it on the USB?
And because my tablet is 32bit i have to use the 32bit version of Remix OS right?
Click to expand...
Click to collapse
Personally it's easier just using EasyUefi especially with a usb install, and yea 1 usb should work on both, but what hardware works will depend on support for it...
Ok thanks, what does it mean EasyUefi? It is the 64bit version right?
Does the 64bit version work on a 32bit Tablet?
manuelbvb said:
Ok thanks, what does it mean EasyUefi? It is the 64bit version right?
Does the 64bit version work on a 32bit Tablet?
Click to expand...
Click to collapse
EasyUEFI it's a windows exe to change boot order etc. so you don't have to go into bios.
Ok thank you, i will try
but can i take the 64bit version on my 32bit tablet?
My problem:
So i have a 64 Bit PC but a 32 Bit Tablet. But i want to use the Stick with Remix os on both. so which should i take? The 32bit or?
And can i use easyUEFI with the 32bit version too?
Ok, i cant install EasyUEFI on my Windows PC. It gives an error.
So what are my options than?
And should i take 64bit or 32bit? See previous post
manuelbvb said:
Ok, i cant install EasyUEFI on my Windows PC. It gives an error.
So what are my options than?
And should i take 64bit or 32bit? See previous post
Click to expand...
Click to collapse
32bit should work on both. I guess your PC is using legacy bios; so EasyBCD might be what you need. But I don't know too much about legacy bios.
Yes you are right. it is a legacy bios.
But i switched the boot options, so it will boot from usb at first. So perfect for me. If USB is in it will boot Remix OS, if not, Windows.
Thank you very much.
Another question about Remix OS. Does it have a automatic update function?
manuelbvb said:
Yes you are right. it is a legacy bios.
But i switched the boot options, so it will boot from usb at first. So perfect for me. If USB is in it will boot Remix OS, if not, Windows.
Thank you very much.
Another question about Remix OS. Does it have a automatic update function?
Click to expand...
Click to collapse
Yes there's an OTA update that works as long as you don't alter system.img, initrd.img, ramdisk.img and kernel.
I dont know if you know anything about Chuwi HI8, but du you know how to boot from USB?
I was in the BIOS Menu but i could not find how to boot from USB.
manuelbvb said:
I dont know if you know anything about Chuwi HI8, but du you know how to boot from USB?
I was in the BIOS Menu but i could not find how to boot from USB.
Click to expand...
Click to collapse
Try EasyUefi on that; I have a vi10 -- I think they're similar.
Should i install it on Windows on Tablet? And then i get the settings or how to try EasyUefi?
"
manuelbvb said:
Should i install it on Windows on Tablet? And then i get the settings or how to try EasyUefi?
Click to expand...
Click to collapse
Yes. Install in Windows. I'll have a look at vi10 uefi/bios as well
Ok once it has worked, but when i open the program easyuefi again, the boot options are the same as in the beginning. Is there a option to save the boot settings?
manuelbvb said:
Ok once it has worked, but when i open the program easyuefi again, the boot options are the same as in the beginning. Is there a option to save the boot settings?
Click to expand...
Click to collapse
I think I know what you mean...
i.e. when you remove the usb it gets taken of the list and re-added to the bottom?
I don't think UEFI keeps the device if it's removed; I had the same issue, unfortunately no real way around it.
There is a sort of workaround; but takes a bit of work. i.e. install grub onto tablet harddrive and have that as primary bootloader
Ok thank you, but than it will be the best way to do the setting every boot again. That is ok for me.
manuelbvb said:
Ok thank you, but than it will be the best way to do the setting every boot again. That is ok for me.
Click to expand...
Click to collapse
My thinking was something like copying the attached to C:/efi/... ; rebooting and checking EasyUEFI picks up the .efi's. One of which should load fine.
It should boot RemixOS if usb is installed and fallback to Windows if it isn't.
You will probably have to change the path= in grub.cfg or remove it. Depending on how your usb is setup...
AS WE ALL KNOW THAT YOGA BOOK CAME WITH WINDOWS OR ANDROID BUT NONE OF THEM CAME WITH DUALBOOTING OPTION SO HOW COULD WE BOOT BOTH OF THEM (ANDROID AND WINDWS) ON OUR DEVICE; WELL THERE IS A LOT OF DEVICES SUPPORT DUAL BOOTING LIKE CHUWI.
SO HERE IS THE TUTORIAL
http://forum.chuwi.com/thread-2254-1-1.html
SO I THINK THIS TUTORIAL FR CHUWI 10 PLUS WILL HELP US AS YOGA BOOK USERS (WIN AND ANDROID) FOR DUAL BOOTING
I DIDNT TRY IT YET, BUT IAM SURE ITS WORKING
WE NEED TO WORK TOGETHER GUYS TO MAKE THIS DREAM CAME TRUE
Good Luck. Hope you enjoy your exclusive cutting board afterwards. :fingers-crossed:
Honestly, it doesn't really help because they use a custom bios, which we don' t have and won't jave without any experienced developer around here. And if I'm not mistaken, it has been designed for dual boot even before.
Chuwi uses an AMI Bios...
Lenovo two DIFFERENT Insyde bios'es. Furthermore, it looks like the Android Version Bios is not even from Insyde...
danjac said:
Good Luck. Hope you enjoy your exclusive cutting board afterwards. :fingers-crossed:
Honestly, it doesn't really help because they use a custom bios, which we don' t have and won't jave without any experienced developer around here. And if I'm not mistaken, it has been designed for dual boot even before.
Click to expand...
Click to collapse
That's mean we need a custom bios, but how could we do that
jamespmi said:
Chuwi uses an AMI Bios...
Lenovo two DIFFERENT Insyde bios'es. Furthermore, it looks like the Android Version Bios is not even from Insyde...
Click to expand...
Click to collapse
Thank you for this Infos I didn't realize that Lenovo used an bios that locked dual booting, iam gonna try to reach Lenovo devs and tell them to make an bios that allow us to dual booting
THE MAXIMUM POWER said:
AS WE ALL KNOW THAT YOGA BOOK CAME WITH WINDOWS OR ANDROID BUT NONE OF THEM CAME WITH DUALBOOTING OPTION SO HOW COULD WE BOOT BOTH OF THEM (ANDROID AND WINDWS) ON OUR DEVICE; WELL THERE IS A LOT OF DEVICES SUPPORT DUAL BOOTING LIKE CHUWI.
SO HERE IS THE TUTORIAL
http://forum.chuwi.com/thread-2254-1-1.html
SO I THINK THIS TUTORIAL FR CHUWI 10 PLUS WILL HELP US AS YOGA BOOK USERS (WIN AND ANDROID) FOR DUAL BOOTING
I DIDNT TRY IT YET, BUT IAM SURE ITS WORKING
WE NEED TO WORK TOGETHER GUYS TO MAKE THIS DREAM CAME TRUE
Click to expand...
Click to collapse
News: I tried to booting Remix OS but it booted just one time with alot of bugs I've made a screenshot s because I've knew that will boot just ONE time, the last photo show how Remix faules at the second booting:
THE MAXIMUM POWER said:
AS WE ALL KNOW THAT YOGA BOOK CAME WITH WINDOWS OR ANDROID BUT NONE OF THEM CAME WITH DUALBOOTING OPTION SO HOW COULD WE BOOT BOTH OF THEM (ANDROID AND WINDWS) ON OUR DEVICE; WELL THERE IS A LOT OF DEVICES SUPPORT DUAL BOOTING LIKE CHUWI.
SO HERE IS THE TUTORIAL
http://forum.chuwi.com/thread-2254-1-1.html
SO I THINK THIS TUTORIAL FR CHUWI 10 PLUS WILL HELP US AS YOGA BOOK USERS (WIN AND ANDROID) FOR DUAL BOOTING
I DIDNT TRY IT YET, BUT IAM SURE ITS WORKING
WE NEED TO WORK TOGETHER GUYS TO MAKE THIS DREAM CAME TRUE
Click to expand...
Click to collapse
https://www.insyde.com/tags/dual-os-switching take a look about that
THE MAXIMUM POWER said:
https://www.insyde.com/tags/dual-os-switching take a look about that
Click to expand...
Click to collapse
Cool, but nor the Windows nor Android Bios'es are made for InsydeQ2S. Lenovo uses a custom made BIOS...
Folks, Lenovo used on purpose different bios'es. The Android Version will never understand ACPI, UEFI, Bitlock etc... it's cropped EEPROM is just not meant for it. I know it's a frustration, but it won't happen. The Windows Version will "maybe" be able to load some kind of x86 Android, but what about display, halo, wifi, anypen, wacom, dolby etc drivers?
jamespmi said:
Cool, but nor the Windows nor Android Bios'es are made for InsydeQ2S. Lenovo uses a custom made BIOS...
Folks, Lenovo used on purpose different bios'es. The Android Version will never understand ACPI, UEFI, Bitlock etc... it's cropped EEPROM is just not meant for it. I know it's a frustration, but it won't happen. The Windows Version will "maybe" be able to load some kind of x86 Android, but what about display, halo, wifi, anypen, wacom, dolby etc drivers?
Click to expand...
Click to collapse
Actually I've booted successfully Remix OS on my Xbox win version it booted successfully just one time then I wasn't be able to boot again, this problem in one hand, in the other hand as you said Halo keyboard, Wacom, Dolby, seems seems no place for them in Remix OS
jamespmi said:
Cool, but nor the Windows nor Android Bios'es are made for InsydeQ2S. Lenovo uses a custom made BIOS...
Folks, Lenovo used on purpose different bios'es. The Android Version will never understand ACPI, UEFI, Bitlock etc... it's cropped EEPROM is just not meant for it. I know it's a frustration, but it won't happen. The Windows Version will "maybe" be able to load some kind of x86 Android, but what about display, halo, wifi, anypen, wacom, dolby etc drivers?
Click to expand...
Click to collapse
i don't have device in my hands now
but i have a little hope
at least we can boot windows or android from USB/microSD
hmm
for windows version it must be easy
we can keep windows on primary disk
and install android on external drive
* :|||| then how this s**t can boot it?
hmm, we need to disable secure boot
then add grub to bcd with easybcd
* :\ android need system/boot/data/cache... !!
yep, we need to partition usb drive like official android disk
same sizes for system, cache, ...
not userdata
then we need to edit ramdisk
we need to edit fstab(and init.r2_cht_ffd.rc) to mount system and other partitions from /dev/sdb(c) [instead of /dev/block/by-name/]
* what about other partitions like keymaster?
i'm not sure it's needed but we can symlink it on init scripts
but for android version i'm not sure what i have to do
first i downloaded android firmware zip and there was file called "bootloader"
Code:
/Volumes/ExFAT 1/YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles/bootloader: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "mkfs.fat", sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 200, sectors/track 32, heads 64, sectors 204800 (volumes > 32 MB) , serial number 0x786ce839, label: "ANDROIDIA ", FAT (16 bit)
so it's fat image
and i was able to mount it
BINGO
volume label is ANDROIDIA just like what i saw in chawe boot option photos in OP guide
well on bootloader i can see \EFI\BOOT\bootx64.efi
:good: :good: :good:
now i'm sure android version yoga can also boot (any)efi file
* but who dare to touch it?
noone, we have tool called efidroid : https://forum.xda-developers.com/android/software-hacking/efidroid-t3447466
this guy can boot efi files for us
someone have to port efidroid for yoga (thats why i asked for device tree on TWRP thread)
now we need windows boot manager efi files (uefi boot partition) and windows system files to boot windows
ok, i'm not sure how to install windows on usb at this stage
but for example we can boot windows setup usb
(we need to find a way)
like install windows by virtualbox with PC on USB, then try to boot it on yoga (not sure)
or took backup of windows version and restore on USB :\
my friend wants to buy windows version (right now we have shipping problem from amazon) and i will try to install android on it
then if anyone wants to work, i hope can help
erfanoabdi said:
i don't have device in my hands now
but i have a little hope
at least we can boot windows or android from USB/microSD
Click to expand...
Click to collapse
That sounds everything so amazing and specially: Easy Peasy
And once you boot Android: Tataaa! No drivers for Screen-Rotation, Wifi, Touch, Holo etc etc...
But hey, hope dies last. Good luck
jamespmi said:
That sounds everything so amazing and specially: Easy Peasy
And once you boot Android: Tataaa! No drivers for Screen-Rotation, Wifi, Touch, Holo etc etc...
But hey, hope dies last. Good luck
Click to expand...
Click to collapse
But absulutly we have drivers
1) i want to boot stock Android
2) drivers are on kernel and kernel source is available on Lenovo site (only for custom rom purposes)
erfanoabdi said:
But absulutly we have drivers
1) i want to boot stock Android
2) drivers are on kernel and kernel source is available on Lenovo site (only for custom rom purposes)
Click to expand...
Click to collapse
Where exactly are they?
jamespmi said:
Where exactly are they?
Click to expand...
Click to collapse
https://pcsupport.lenovo.com/tr/en/products/tablets/yoga-series/yoga-book/downloads
https://pcsupport.lenovo.com/tr/en/products/TABLETS/YOGA-SERIES/YOGA-BOOK/downloads/DS118515
contains some libs and files from android source + kernel + gpt partition creation/info python script
Hi guys!
So I just got an Android YogaBook and the "bios" (actually UEFI) is a standard Intel made UEFI loaded with tons of options.
Android is loaded as any standard UEFI OS using a bootloader called KernelFlinger.
This means that we can boot Android, Linux, Windows and in theory also macOS (LOL).
I'll try to install Windows in the next few days, should not be hard (except for finding and usb adapter LOL) and will report back
P.s. I believe the Windows version uses the same UEFI but is locked in a user friendly "basic mode". This makes sense as they are supposed to be able to get into the UEFI while we're not
windserfer said:
Hi guys!
So I just got an Android YogaBook and the "bios" (actually UEFI) is a standard Intel made UEFI loaded with tons of options.
Android is loaded as any standard UEFI OS using a bootloader called KernelFlinger.
This means that we can boot Android, Linux, Windows and in theory also macOS (LOL).
I'll try to install Windows in the next few days, should not be hard (except for finding and usb adapter LOL) and will report back
P.s. I believe the Windows version uses the same UEFI but is locked in a user friendly "basic mode". This makes sense as they are supposed to be able to get into the UEFI while we're not
Click to expand...
Click to collapse
Nice! Hopefully it works out
windserfer said:
Hi guys!
So I just got an Android YogaBook and the "bios" (actually UEFI) is a standard Intel made UEFI loaded with tons of options.
Android is loaded as any standard UEFI OS using a bootloader called KernelFlinger.
This means that we can boot Android, Linux, Windows and in theory also macOS (LOL).
I'll try to install Windows in the next few days, should not be hard (except for finding and usb adapter LOL) and will report back
P.s. I believe the Windows version uses the same UEFI but is locked in a user friendly "basic mode". This makes sense as they are supposed to be able to get into the UEFI while we're not
Click to expand...
Click to collapse
Hi, any news from your project?
ox_eye said:
Hi, any news from your project?
Click to expand...
Click to collapse
Had to send back my Yoga for a screen problem and got the replacement only this evening
I hope to have time to try this weekend
windserfer said:
Had to send back my Yoga for a screen problem and got the replacement only this evening
I hope to have time to try this weekend
Click to expand...
Click to collapse
Any news? I have a working Windows To Go usb. I would love to boot my yogabook from that.
erfanoabdi said:
i don't have device in my hands now
but i have a little hope
at least we can boot windows or android from USB/microSD
hmm
for windows version it must be easy
we can keep windows on primary disk
and install android on external drive
* :|||| then how this s**t can boot it?
hmm, we need to disable secure boot
then add grub to bcd with easybcd
* :\ android need system/boot/data/cache... !!
yep, we need to partition usb drive like official android disk
same sizes for system, cache, ...
not userdata
then we need to edit ramdisk
we need to edit fstab(and init.r2_cht_ffd.rc) to mount system and other partitions from /dev/sdb(c) [instead of /dev/block/by-name/]
* what about other partitions like keymaster?
i'm not sure it's needed but we can symlink it on init scripts
but for android version i'm not sure what i have to do
first i downloaded android firmware zip and there was file called "bootloader"
Code:
/Volumes/ExFAT 1/YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles/bootloader: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "mkfs.fat", sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 200, sectors/track 32, heads 64, sectors 204800 (volumes > 32 MB) , serial number 0x786ce839, label: "ANDROIDIA ", FAT (16 bit)
so it's fat image
and i was able to mount it
BINGO
volume label is ANDROIDIA just like what i saw in chawe boot option photos in OP guide
well on bootloader i can see \EFI\BOOT\bootx64.efi
:good: :good: :good:
now i'm sure android version yoga can also boot (any)efi file
* but who dare to touch it?
noone, we have tool called efidroid : https://forum.xda-developers.com/android/software-hacking/efidroid-t3447466
this guy can boot efi files for us
someone have to port efidroid for yoga (thats why i asked for device tree on TWRP thread)
now we need windows boot manager efi files (uefi boot partition) and windows system files to boot windows
ok, i'm not sure how to install windows on usb at this stage
but for example we can boot windows setup usb
(we need to find a way)
like install windows by virtualbox with PC on USB, then try to boot it on yoga (not sure)
or took backup of windows version and restore on USB :\
my friend wants to buy windows version (right now we have shipping problem from amazon) and i will try to install android on it
then if anyone wants to work, i hope can help
Click to expand...
Click to collapse
hii, did i get it? I have the android version and I am stuck because I cannot find how to update the android or how to pass it in a stable way that the keyboard works to windows.
is have asked in many forums but didn't got anything working.
so the whole story is, I own a Windows tablet from 2015 or something. recently I tried to install android x86 on it just for fun. I installed the BlissOS 14 x86 version and it ran great only that the tablet is overheating a lot and reboots. Now I want to go back to windows but what's going on is that the tablet is not detecting the windows bootable USB drive, it is only detecting the android bootable USB drives. every time I try to boot a windows USB it goes back to bios. i tried dozens of windows bootable tools and even changed between a bunch of drives nothing is working. please guys help me, I want my windows tablet back.
Update: I'm sorry to all who brainstormed on this, I am an IDIOT. I was trying to boot 64-bit windows into the 32-bit processor. Now everything works fine, Sorry Again.
What tablet is it?
amitrahi04 said:
is have asked in many forums but didn't got anything working.
so the whole story is, I own a Windows tablet from 2015 or something. recently I tried to install android x86 on it just for fun. I installed the BlissOS 14 x86 version and it ran great only that the tablet is overheating a lot and reboots. Now I want to go back to windows but what's going on is that the tablet is not detecting the windows bootable USB drive, it is only detecting the android bootable USB drives. every time I try to boot a windows USB it goes back to bios. i tried dozens of windows bootable tools and even changed between a bunch of drives nothing is working. please guys help me, I want my windows tablet back.
Click to expand...
Click to collapse
Use Rufus software(https://rufus.ie/) to create bootable USB.
Bro,
Try Rescartux !
Burn it into a USB drive, then booting it!
Find a menu that "fix boot-stuff for windows"
Try every menu related to fixing windows Boot!
If that didnt give a Budge, U could try HirenBoot .