Hi,
for testing purposses (a lot of devices) i am looking for a method to get the full android version of differen devices (different manufacturer, modells and major android releases).
i would be interested in get it in a text form or worst case as one screenshot (or more if necessary). The screenshot should be done with the device itself.
The information should land on my pc (win 7) where will be further processed. This should be done via WLAN or USB
The method should be manufacturer and modell independent, best case would be also platform independent (works also for iPhone, Windows Phone, Blackberry)
i know, the easiest way would be to take a picture with a second device and copy the picture via USB, but this is not the expected method. The focus should be on the text information. Is there any app that can do this?
thank you!
r.amse.s said:
Hi,
for testing purposses (a lot of devices) i am looking for a method to get the full android version of differen devices (different manufacturer, modells and major android releases).
i would be interested in get it in a text form or worst case as one screenshot (or more if necessary). The screenshot should be done with the device itself.
The information should land on my pc (win 7) where will be further processed. This should be done via WLAN or USB
The method should be manufacturer and modell independent, best case would be also platform independent (works also for iPhone, Windows Phone, Blackberry)
i know, the easiest way would be to take a picture with a second device and copy the picture via USB, but this is not the expected method. The focus should be on the text information. Is there any app that can do this?
thank you!
Click to expand...
Click to collapse
Have you tried mobileuncle from play store and send to your pc via WLAN (wifi file transfer via ftp) also from PS.
md mat said:
Have you tried mobileuncle from play store and send to your pc via WLAN (wifi file transfer via ftp) also from PS.
Click to expand...
Click to collapse
MobileUncle only works on MTK devices. If you're running a Qualcomm or X86 device it's not going to work.
popthosegaskets said:
MobileUncle only works on MTK devices. If you're running a Qualcomm or X86 device it's not going to work.
Click to expand...
Click to collapse
right, so i am still looking
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.
Can anyone see what I'm doing wrong here, I've been trying to get this working for a couple of days now...
I've installed File Manager + on the X96 and given it access to the attached USB drives. One drive is a 256gig stick and the other is a 4tb WD HD.
I've installed Cute FTP on the PC.
I launch FM+ on the X96 and start it's ftp and given it root access.
On the PC, Cute see's the X96 but only the internal storage not the attached drives? Both attached drives are attached at boot.
Am I using the wrong app on the box?
Can anyone suggest how I get the PC to see the attached drives?
Thanks.
steve1221 said:
Can anyone see what I'm doing wrong here, I've been trying to get this working for a couple of days now...
I've installed File Manager + on the X96 and given it access to the attached USB drives. One drive is a 256gig stick and the other is a 4tb WD HD.
I've installed Cute FTP on the PC.
I launch FM+ on the X96 and start it's ftp and given it root access.
On the PC, Cute see's the X96 but only the internal storage not the attached drives? Both attached drives are attached at boot.
Am I using the wrong app on the box?
Can anyone suggest how I get the PC to see the attached drives?
Thanks.
Click to expand...
Click to collapse
Trying this app X-plore File Manager
, it's the one I used to go to my Drive and on my PCs and the like, it's great and easy to use.
Sealowed said:
Trying this app X-plore File Manager
, it's the one I used to go to my Drive and on my PCs and the like, it's great and easy to use.
Click to expand...
Click to collapse
Many thanks, that works very well.
Wifi share works like a dream, but I can't seem to connect to with an ftp client? It's not a problem, but would you happen to know why?
steve1221 said:
Many thanks, that works very well.
Wifi share works like a dream, but I can't seem to connect to with an ftp client? It's not a problem, but would you happen to know why?
Click to expand...
Click to collapse
Sorry, but I don't use it, I couldn't answer you.
Sealowed said:
Sorry, but I don't use it, I couldn't answer you.
Click to expand...
Click to collapse
No worries, I can live without it. Thanks again for the suggestion, it's solved so many problems
aloha
can i install it?
by odin3?
are there chromeOSflex files?
md5
& other files to inject to the device with odin3?
i dont mind losing some device features
such as cams & mics...
Yapersia said:
aloha
can i install it?
by odin3?
are there chromeOSflex files?
md5
& other files to inject to the device with odin3?
i dont mind losing some device features
such as cams & mics...
Click to expand...
Click to collapse
Chrome os flex does not support arm processors currently, though you can run it emulated.
It is not open source so you can't compile it for arm
is there steps on how to do this?
Also
My Windows 10 cant detect the galaxy tab n8000
Even though the device start charging power from the usb when connecting it…
Installed Samsung usb drive
But still no detention…
Yapersia said:
is there steps on how to do this?
Also
My Windows 10 cant detect the galaxy tab n8000
Even though the device start charging power from the usb when connecting it…
Installed Samsung usb drive
But still no detention…
Click to expand...
Click to collapse
you can emulate x86 architecture in the limbo frontend for qemu. it's on f-droid. make sure you are not using a power only cable (cheapo chinese ones usually are)
Maybe some info in the Chromebook forum:
Google announces Chrome OS Flex: Easily turn your PC or Mac into a Chromebook
FYI, https://www.androidauthority.com/chrome-os-flex-3108653/
forum.xda-developers.com
Chromebooks
For discussion of Google Chromebooks (software and hardware hacking)
forum.xda-developers.com
$cronos_ said:
you can emulate x86 architecture in the limbo frontend for qemu. it's on f-droid. make sure you are not using a power only cable (cheapo chinese ones usually are)
Click to expand...
Click to collapse
Yes thank you
That was also a big problem im stuck on
Didn’t thought that the cable could be for power only
$cronos_ said:
you can emulate x86 architecture in the limbo frontend for qemu. it's on f-droid. make sure you are not using a power only cable (cheapo chinese ones usually are)
Click to expand...
Click to collapse
ya doesn't read
even trying fancy looking cable
even different PCsss
still only charge .. but no detection...