Related
Anyone using CM10.1 managed to use DriveDroid? I'm trying to boot Ubuntu but Windows just say that I need to format the driver, I don't know if it's a CM related, MTP or my issue :cyclops:
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Don't look at what Windows thinks of the disk. Windows doesn't recognize the structure of the disk, so it suggests to format it.
What does matter is whether your bios recognizes the disk as bootable. The structure of the disk is usually not the problem if you downloaded the image from DriveDroid: it is the same as anyone else downloading the image. If booting from your phone does not work it usually has something to do with timing/the software on your phone (ROM/kernel). If you indeed can't boot from your phone, I'd suggest to do the following:
Go to preferences of DriveDroid.
Turn off UMS and turn it back on again.
Reboot your phone.
See whether that helps. It worked for some people, but it doesn't have a 100% successrate.
hipgnose said:
Anyone using CM10.1 managed to use DriveDroid? I'm trying to boot Ubuntu but Windows just say that I need to format the driver, I don't know if it's a CM related, MTP or my issue :cyclops:
Click to expand...
Click to collapse
Same here. Really disappointing it doesn't work. I can't tell you how often I thought about boot an image from my phone. In fact, I think I posted the question on XDA a few years ago.
Hey guys, developer here. A few things that might help:
The ISOs that are in DriveDroids downloadlist are all hybrid. This means they are specially crafted to be compatible with USB as well as CD. This is great, because at the moment Android devices only correctly emulate USB drives.
When selecting such an image, Windows will show it as an USB disk. However, Windows does not recognize the format that is used on the disk, because it's hybrid. Therefore Windows suggests to format the disk with a filesystem that Windows recognizes (FAT or NTFS). Do not do this, it'll just blank out the image, which isn't what you want.
Bioses however should be able to recognize the USB disk as a bootable one.
The USB-disk emulation is what in Android is called UMS (USB Mass Storage). On oldish devices this was used to share the SDcard with the PC. DriveDroid uses the same mechanism, but not on the SDcard, but on files (ISO/IMG). Downside is that this mode isn't by default enabled on modern devices, so you usually have to switch from MTP (the system in use to share SDcard in modern devices) to UMS. Such an option is available in DriveDroids menu. However on some devices this switch does not work correctly atm. I have no idea why, but from others I have heard that you can make the option work on these devices. You'll have to rapidly switch the UMS option on and off and end with UMS being on. It *should* popup on your PC when you have a USB cable plugged in. For others it helped to reboot the phone too, but I'm not too sure why this works.
Hopefully that helps solve the problems.
FrozenCow said:
You'll have to rapidly switch the UMS option on and off and end with UMS being on. It *should* popup on your PC when you have a USB cable plugged in.
Click to expand...
Click to collapse
Funny you suggested this. Last night while trying to make it work (thinking the image didn't download correctly the first time), I did the same thing.
jdgiotta said:
Funny you suggested this. Last night while trying to make it work (thinking the image didn't download correctly the first time), I did the same thing.
Click to expand...
Click to collapse
Oh were you also one of the people who send me a support email about this by any chance? I learned about this from those.
In any case, good to hear another confirmation on the method. It's weird, since I'm not too sure why this works yet (it just enables and disables UMS on my device), but I'll put something in the next version to emulate the same behavior.
FrozenCow said:
Oh were you also one of the people who send me a support email about this by any chance? I learned about this from those.
In any case, good to hear another confirmation on the method. It's weird, since I'm not too sure why this works yet (it just enables and disables UMS on my device), but I'll put something in the next version to emulate the same behavior.
Click to expand...
Click to collapse
No, I didn't send the report. I tried it on a whim, but didn't it work.
Hi everyone,
Unless someone has any idea, I've given up on this. I have tried every version of the installations for an old HP Pavillion PC (32bit). I either get the OS not being detected, blinking light of doom, infinite search for the OS, splash screen of doom and I'm sure more that I don't recall.
I even tried installing it using the INSTALL=1 DEBUG= to install it on a drive all by itself, but it only detects the USB slots and not the hard drive! I've already provided feedback to the Jide team that I'd like to see a true LiveCD to hard drive installation process like every version of Windows and the Linux distros where you can just boot to a stick and either run it in a guest mode with option to install or just an installer process that can install it to a clean drive.
Of all the systems (64 bit and 32 bit / laptops vs desktops), I can get it running from one stick consistently. I'd rather install it a drive and be done that way. Hopefully a future version will do it simply.
This might be a long stretch, but you might check and see if the disk is still reading as "active". I've tried installing Remix OS on a flash drive using their Windows tool via Windows 10, but noticed the USB drive would just disappear. Going to Disk Management/Partition Manager shows the USB drive as inactive, and works no problem when it's active again when I restart the system. If you're using the entire hard drive, try using a tool like GParted Live CD/USB and see if your disk drive is active.
Ya, I've tried that too because initially that did happen and I figured once I solved it that would sort the problem out but no dice.
BladeMaverick said:
This might be a long stretch, but you might check and see if the disk is still reading as "active". I've tried installing Remix OS on a flash drive using their Windows tool via Windows 10, but noticed the USB drive would just disappear. Going to Disk Management/Partition Manager shows the USB drive as inactive, and works no problem when it's active again when I restart the system. If you're using the entire hard drive, try using a tool like GParted Live CD/USB and see if your disk drive is active.
Click to expand...
Click to collapse
this is one way I can revive my Acer Aspire One AOA110 with 8GB SSD. up for interest and attention
I have here a P3-1Ghz with 512 megabytes of RAM on an Asus CUSI-M (SiS630M) motherboard in a compact case. I thought I'd try running RemixOS on it, under the rationale that Android should be friendlier to old PC hardware than any other modern system because plenty of ultramobile devices it runs on have about the same power as old PC hardware.
The CD-ROM drive is a slim unit that's unfortunately quite dead, and I don't have any of my old IDE optical drives handy; plus the computer only has USB1.1 (from which it can't boot without Plop Bootmanager and even that's sketchy) and I don't have any USB2 PCI cards, so it requires some creative ways to get a live system running. My idea is to either put the OS on the drive from my main computer and then transfer it across, or get the system on another drive, plug it in the secondary IDE channel, boot it and install to the primary drive from there.
I plugged the drive into my win10 box with a IDE-to-USB2 converter and ran the Windows installer program; it did its thing, but when I transfer the drive to the PIII it doesn't boot - it just stays there at the BIOS screen forever, as if there was no bootloader on the hard disk (I understand the installer, which seems derived from UNetBootin, should have put one there). This happens both with FAT32 and NTFS.
So I tried dd'ing the image to the hard drive directly in Linux. That at least got me to the bootloader, but when I try to boot (in guest mode) it complains about Intel Powerclamp not working and some other process being incompatible with the CPU. Then it reboots.
I then tried using Rufus to write the image to the hard disk, and that caused a cleaner attempt - no complaints and it goes straight to "looking for Android-x86 on /dev/sda1, found"... and then reboots.
Notably my idea seems to work otherwise - I can boot any Linux live by Rufus-ing it to one of the two drives, and if I put the live on the second drive I can then boot it, run the installer and install it on the first; by way of an experiment I installed Mint like this and it booted to a desktop just fine (if slowly).
I'm wondering if I'm doing something wrong with the image files, or if I'm just trying to install it on an excessively ancient and unsupported computer - which would be too bad, really, as it seems an ideal solution to revive slow hardware.
Edit: another attempt. I used my main box to create a RemixOS USB drive, then rebooted the main box to verify that it works, and sure enough RemixOS booted fine from the thumbdrive. I then used Linux to dd the thumbdrive directly on the IDE hard drive and plugged that in the P3. This works - it boots to the bootloader, acts as if it wants to boot (even formats the data partition if I select resident mode), then - again - resets.
Why is the damn thing resetting on boot and how do I stop it? Argh!
Fallingwater said:
I have here a P3-1Ghz with 512 megabytes of RAM on an Asus CUSI-M (SiS630M) motherboard in a compact case. I thought I'd try running RemixOS on it, under the rationale that Android should be friendlier to old PC hardware than any other modern system because plenty of ultramobile devices it runs on *have* about the same power of old PC hardware.
The CD-ROM drive is a slim unit that's unfortunately quite dead, and I don't have any of my old IDE optical drives handy; plus the computer only has USB1.1 (from which it can't boot without Plop Bootmanager and even that's sketchy) and I don't have any USB2 PCI cards, so it requires some creative ways to get a live system running. My idea is to either put the OS on the drive from my main computer and then transfer it across, or get the system on another drive, plug it in the secondary IDE channel, boot it and install to the primary drive from there.
I plugged the drive into my win10 box with a IDE-to-USB2 converter and ran the Windows installer program; it did its thing, but when I transfer the drive to the PIII it doesn't boot - it just stays there at the BIOS screen forever, as if there was no bootloader on the hard disk (I understand the installer, which seems derived from UNetBootin, should have put one there). This happens both with FAT32 and NTFS.
So I tried dd'ing the image to the hard drive directly in Linux. That at least got me to the bootloader, but when I try to boot (in guest mode) it complains about Intel Powerclamp not working and some other process being incompatible with the CPU. Then it reboots.
I then tried using Rufus to write the image to the hard disk, and that caused a cleaner attempt - no complaints and it goes straight to "looking for Android-x86 on /dev/sda1, found"... and then reboots.
Notably my idea seems to work otherwise - I can boot any Linux live by Rufus-ing it to one of the two drives, and if I put the live on the second drive I can then boot it, run the installer and install it on the first; by way of an experiment I installed Mint like this and it booted to a desktop just fine (if slowly).
I'm wondering if I'm doing something wrong with the image files, or if I'm just trying to install it on an excessively ancient and unsupported computer - which would be too bad, really, as it seems an ideal solution to revive slow hardware.
Edit: another attempt. I used my main box to create a RemixOS USB drive, then rebooted the main box to verify that it works, and sure enough RemixOS booted fine from the thumbdrive. I then used Linux to dd the thumbdrive directly on the IDE hard drive and plugged that in the P3. This works - it boots to the bootloader, acts as if it wants to boot (even formats the data partition if I select resident mode), then - again - resets.
Why is the damn thing resetting on boot and how do I stop it? Argh!
Click to expand...
Click to collapse
Try flashing it to another hard drive, insert both drives into the computer, and and at the grub menu press alt, and add "install=1 debug=" (without the quotes of course, and debug should have no character whatsoever afer the equals.
After installing from the second hard drive to the first, turn off the computer, remove the second hard drive, and boot up the conputer.
I hope this works for you.
Good question... I have an pentium 4 3.0 ghz 64 bit cpu, 4 gig mem and an sata ssd, that runs on Linux mint. Can i install Remix Android 6 without Windows or is Windows recommended if i will to install Remix Android 6
Flemischguy said:
Good question... I have an pentium 4 3.0 ghz 64 bit cpu, 4 gig mem and an sata ssd, that runs on Linux mint. Can i install Remix Android 6 without Windows or is Windows recommended if i will to install Remix Android 6
Click to expand...
Click to collapse
No need for windows, however it makes things easier for flashing it on the flash drive.
My recommendation, though, is to use the flash drive as an installer: according to what I had written above, install Remix OS to a hard drive from the flash drive.
I did what you suggested. The system is now installed on the second hard drive, but the computer still resets when attempting to boot. However, by selecting debug boot in grub it tells me a bit more info about the crash - which it didn't when I just did "debug=" in the live, for whatever reason.
Does this tell you anything?
Fallingwater said:
I did what you suggested. The system is now installed on the second hard drive, but the computer still resets when attempting to boot. However, by selecting debug boot in grub it tells me a bit more info about the crash - which it didn't when I just did "debug=" in the live, for whatever reason.
Does this tell you anything?
Click to expand...
Click to collapse
Not much, unfortunately.
However, perhaps a BIOS update will help.
It's already updated to the newest revision.
In case others come across this problem: apparently it's not caused by the CPU, but by an unsupported video adapter. This computer has a disgusting old integrated SiS something-or-other video chipset, so that doesn't surprise me. I might try again if I ever find a PCI video adapter that'll fit the case.
Fallingwater said:
In case others come across this problem: apparently it's not caused by the CPU, but by an unsupported video adapter. This computer has a disgusting old integrated SiS something-or-other video chipset, so that doesn't surprise me. I might try again if I ever find a PCI video adapter that'll fit the case.
Click to expand...
Click to collapse
Alright, I hope it'll work then.
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.
Hello. I'm a happy (?!) user of Win 10 Pro x64 since few days.
I want to connect my RN4X Snapdragon to PC, using usb on my pc's motherboard.
However, despite setting option, that I'll listed below, my phone is still not recognisable as useful stuff.
Without changing anything on my phone since my last flashing topics (Feb and March this year), I was fully able to connect easily to pc with win7 x64. I also was able to connect (using Xiaomi's cable, cheap replacement does not seem to work) phone to win 8.1 x64, where only the basic adb fastboot were installed. But, I cannot do the same on newest Windows.
I've done:
1. Installing minimal adb and fastboot 1.4.3. for all users (I'm the only one account here, but not sure if that's matter)
2. Having programming option enabled, usb debugging enabled and all that good stuff.
3. All four elements on that list - https://************/how-to-fix-mtp-devices-not-connecting-on-windows-10/
4. I've tried to install it as adb interface, installing it manually, installing it by using *.cat files from xiaomi_usb_driver archive, that contain that kind of stuff for newer windowses (it's from this side, if I remember it right - https://www.xiaomiusbdrivers.com/2018/02/download-xiaomi-usb-driver-2018-for_4.html)
5. Almost all stuf from here - https://www.jihosoft.com/android-tips/windows-10-cannot-recognize-android.html. Because I do not have Samsung, Odin mode is not an issue
6. I've tried to install my Redmi 4X as MTP device. However, my phone during each connection to PC started himself in charging mode (I can change it). Even changing it doesn't changing anything, though.
7. Editing the bulid.prop, adding there few lines describing how the phone should behave. I've saved it, but my original version of bulid.prop does not have anything in there about types of connection. I don't remember it word by word, but I've could check in history if anyone will find it interesting.
Drivers for usb 3.1 are pre-installed with mine version of win10 (I cannot install drivers given on my motherboard's dvd attached, system says that I'm currently having them).
When I try to install it manually via device manager, on the first time it says, that is other device, identifed briefly as MTP. However, installing it either as Android ADB interface, fastboot interface or third option does not give me anything. What's worse, even when I've pick windows/INF as my source of drivers for this device, it does not list on "lemme pick ddevice type" MTP type devices. I'm using win 10 in polish, so it might be that I'm blind or does NOT understand translate.
What else could I do? I can of course use wife's laptop with 8.1, usb sticks or other stuff, but I would like to have it sorted out.
Does otg still works to your device?
whatpigs said:
Does otg still works to your device?
Click to expand...
Click to collapse
Not sure. How to check it? We use to have 16GB OTG to USB2.0 (other end was micro usb B), but we must have put it somewhere during moving out to new flat, cause I cannot find it now.
gonna bump it, cause there's not any clue yet.
Same here.