yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] social-design-concepts:
I credited you for the cwm build, but I feel ya i see the tethered method all over the net and very few credit me for the original exploit and launcher. It doesn't really bother me when they don't credit me it's infuriating though when they take the credit as if it was their own.
[MeMO Pad 7 General] Mis012:
No, I am referring to https://01.org/android-ia/downloads/android-4.2.2r1-ia3

And UEFI has some specifications so there must be possibisity to install UEFI designed OSes, which are made according to the same specifications. And one of things UEFI has to support legacy mode, so you can boot BIOS designed systems.
[MeMO Pad 7 General] therealprof:
There're Lollipop versions though it seems that with the advent of MinnowBoard MAX they've repurposed their distribution to be MinnowBoard MAX only. The release notes of the above URL read "Added support for MinnowBoard MAX platform" which kind of suggests that move.

It must be able to run find and run EFI binaries according to the specification. UEFI does not really care what those binaries do, typically they're bootloaders to load an OS. However nothing says that either bootloader or OS have to run universally on any system you attempt to run it on. In fact there's always at the very least an CPU architecture dependency as can be seen by the UEFI 32bit/64bit mismatch.

I don't think that is true but I don't have the time to look it up right now. As far as I know legacy mode is an option, not a must.
[MeMO Pad 7 General] Mis012:
There're Lollipop versions though it seems that with the advent of MinnowBoard MAX they've repurposed their distribution to be MinnowBoard MAX only. The release notes of the above URL read "Added support for MinnowBoard MAX platform" which kind of suggests that move.

> That would be bad, June 11 2013 doesn't look like recent build :(

It must be able to run find and run EFI binaries according to the specification. UEFI does not really care what those binaries do, typically they're bootloaders to load an OS. However nothing says that either bootloader or OS have to run universally on any system you attempt to run it on. In fact there's always at the very least an CPU architecture dependency as can be seen by the UEFI 32bit/64bit mismatch.

> I think that if you wnt to use UEFI to boot your OS, you have to let it check for hardware, and hardware which runs UEFI should be again under some conditions to work with OS desined for UEFI. That's how it is with x86 machines with UEFI from my point of view. And someone has actually ran Windows on this device. And the architecture is x86_64, so it supports both 32bit and 64bit, and as we have 64bit UEFI, we should be able to run both 32bit and 64bit Windows

I don't think that is true but I don't have the time to look it up right now. As far as I know legacy mode is an option, not a must.

> I am not 100% sure but I really think I have read somewhere that legacy mode support is a requirement.
[MeMO Pad 7 General] therealprof:
Not necessarily. The universality you're implying really does not exist, the OS not only needs to fit the architecture but also bring the necessary drivers for the platform. Usually Android images are custom built to include exactly the drivers needed for the target, so if you're using a non-fitting image it might boot, if you're lucky it will even display something but usually that's where usability ends.

The fact that Windows can run on that device has nothing to do with UEFI. To use UEFI the device vendor needs to include drivers needed to use the relevant hardware (flash drivers, hardware initialisation, ...) so the device is capable of locating and running the UEFI binaries on the hardware and that's really about it.

While the CPU is 64bit it does not necessarily mean that the UEFI is also 64bit. Most of those tables are actually running a 32bit UEFI which can cause a lot of pain because some stunts are needed to create a UEFI binary which will then run a 64bit OS. That's also the main reason why many Windows tables are running the 32bit version of Windows 8.1 instead of 64bit!
[MeMO Pad 7 General] spookmeister101:
Just got off a chat with Asus customer support, and asked for a unlocked bootloader. She said that they aren't releasing one "yet" .

Maybe there's hope. :D
[MeMO Pad 7 General] Mis012:
Wow, you got some info from them :)

Maybe you can ask what is causing the lollipop update failure and if it can be updated somehow?
[MeMO Pad 7 General] daspex:
At first thanks again to Mis012 for the .201 Backup i got it now,thanks to slayeralive for his cwm and thanks social-design-concept for his twrp, without you i would have to send my device to warranty.Tryed to upgrade to lollipop again after the backup of .201 but .....nothing.thebulletfromhell told me that the LP bricks the asus "bootloader os" and as result as i tried to make a factory reset the asus "recovery" told me that there ist no filesystem at all.....that´s a kind of strange to me.

I have had a look inside my windows 8.1 professional version and it can only be used for x64 architecture,i tried already to install it to 32bit devices but it doesen´t worked but windows did not say anything about it.As i already said i´m no coder/dev but i will contact microsoft and ask them if the prof.-version of win 8.1 will support or have drivers to run the me176c couse it has a intel chipset,well see.If i get a reaction from them i´ll post it here.

BTW maybe it helps,here are the asus and bloatware apps i removed from the .201-system:

emusic,galerie,googleplaybooks,googleplaygames,googleplaykiosk,googleplaymovies,google+,Contacts,myasus,playto,remotelink,sharelink,mirror,webstoragewhat´snext

chrome,dlnaservice,dmclient,drive

no issues so far.....when they come i´ll report it here.
[MeMO Pad 7 General] Mis012:
No problem, I am sometimes searching the internet and I had luck that I have found that Russian forum. The processor is 64 bit with x86 architecture. And as the file in efi system partition is named BOOT/bootx64.efi , I think it means the UEFI is 64 bit too.
[MeMO Pad 7 General] Mis012:
You cannot think about this device like about other android devices. By getting UEFI it is as much capable of running other OSes as any UEFI computer with some random hardware, just because if the conventions. Look at this article: http://www.reddit.com/r/cyanogenmod/comments/1kxxi6/eli5_why_does_every_device_needs_its_own_custom/

and x86 thing in comments
[MeMO Pad 7 General] :
Anyone else getting terrible game performance on Lollipop or just terrible performance all round?

Many games I've played either crash or play slowly. Seriously regret updating to 5.0, ASUS have done a terrible job, to me it's just a big buggy mess of an update. Thankfully I've got another tablet as this is just pure hell, random reboots, lots of bugs, slow performance, bloated ROM. How could they get it so wrong.

Annoyingly, Move to SD Card is broken/buggy, many apps seem to move back to internal storage (May happen after a reboot?).

Hopefully they are hard at work on a bug fix release, it seriously needs one.

If you are still on KitKat, seriously, save your time/sanity & DON'T UPDATE to 5.0 (Unless you have another tablet to use, as this one will drive you mad with it's bugs & you'll want to throw it out the window in frustration).
[MeMO Pad 7 General] therealprof:
I know, that's exactly what I'm saying! However UEFI does not change the fact that the OS must be capable of running on device, the only thing that UEFI makes universal is the locating and starting of a bootloader.
[MeMO Pad 7 General] Mis012:
But UEFI supported system knows how to work with UEFI supported device, or not?

What's the difference between this device and some XY coputer with UEFI, which can run any UEFI designed OS???
[MeMO Pad 7 General] therealprof:
UEFI runs a bootloader and the bootloader starts the OS. So the bootloader needs to be UEFI compliant, not the OS -- pretty simple.

The OS more or less doesn't care whether the device is bootstrapped by a custom bootloader directly executed from NAND flash (as most embedded systems used to and still do) or a PC compatible BIOS, EFI or UEFI. Some OS are aware how they're started and allow some level of access or even control over the bootstraping mechanism but in essence the OS couldn't care less how it is started.

Back to your question: Yes, it should be possible (unless secure boot is involved) to boot any UEFI compliant bootloader and thus boot any OS. However the OS still must support the hardware and in the case of Android the drivers and configuration contained in an image usually only work on a very specific configuration. In case of Windows you'll either need a preconfigured system image with the right drivers or you'll have to install it yourself from scratch (which might be somewhat tricky given the lack of connections).
[MeMO Pad 7 General] zapz:
Ok so after I kept having problems on 5.0 with the descreased performance,clock sync (these 2 seem to be related) and the freezes + restarts, i decided to take the tablet back to the warranty center. After 1 week,(yesterday) I got it back, with OS back to 4.4.2 version .161 ....I updated it to .201.

Then came the big question: to try 5.0 again or not. "Eh,it can't go wrong 2 times,right?" I said to myself...and oh,how wrong I was.

I updated it to 5.0 using OTA,everything went fine..i tested some apps and games everything was fine...but around 10 pm i wanted to play a game and that's when i saw that descreased performance problem (most noticeable in games,they run smooth but in slow motion) and clock sync problems are back...this time restart and factory reset aren't helping with anything.

Any idea of what I should do to fix it? If I can't solve it, I'll take it back to warranty to get 4.4.2 again and I'll stick with that one,but first I wanna try fixing this.

P.S: I didn't even get to test it and see if it still freezes and restarts,can't do it because of this performance problem,trying to solve it first.
[MeMO Pad 7 General] Mis012:
I wold love to have lollipop, becouse of the UEFI thing etc., but if you want kitkat, everyone will say you cannot get it. Even with root. In theory, you can go to UEFI and instlall intel generic x86 android, which is basicaly pure android for x86 UEFI devices, but if you will not find out how to install it on sdcard or new partition or so, you will never get asus's android back. And latest intel's android is 4.4.2, buid from 2013. But on the other hand, the bootloader included in this relase should not be locked, so someone could make cyanogenmod 5.0 which would be generic for all x86 UEFI devices :)
[MeMO Pad 7 General] zapz:
As I said above, when I took it to warranty, it was 5.0 ....when they gave it back,it was 4.4.2 ...so it IS possible. And I upgraded it back to 5.0 only to have problems again...that's why if I can't find a solution,I'll take it back for them to reinstall Kitkat and I'll stick with it.
[MeMO Pad 7 General] Mis012:
Lollipop slowness solution?

Ok, it looks like you have to turn off power managment in settings, that is what causes the slowdown.

And wipe cache for clock promblem disappearance.

Please! Noone knows how can I get lollipop?
[MeMO Pad 7 General] AzOzA:
OH MEN i hope I can see your post earlier :( thats explain why temp recovery doesnt work :silly:

Did you open your pad connect with hard drive wipe and roll back with commands/programs? and you needed the OS, IFWI, BIOS files so its impossible at the moment for us, but its possible for ASUS.

---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------

What you mean?
[MeMO Pad 7 General] Mis012:
I mean I am stuck on kitkat so I do not have UEFI. The lollipop update somehow fails to change bootloader etc.

Looks like I will have to send it for motherboard replacement and wait for a whole week.
[MeMO Pad 7 General] AzOzA:
I got it. same here I will send it to RMA next week. and this time I will stay in KK, only update to 5.1 version 5.0 unstable for every device.
[MeMO Pad 7 General] profee:
Has someone figured out what causes slowdowns? Did someone manage to fix it?
[MeMO Pad 7 General] Alexadro:
The people who figured out how to translate UEFI to legacy status ? what would have appeared in UEFI x32

Our options can be used for translation into UEFI x32 GRUB or rEFIt ?
[MeMO Pad 7 General] Mis012:
Is it that hard to read some pages backward or just look for new posts daily? Does anyone really do it?

And an answer: I gave a possible fix about two post upwards..
[MeMO Pad 7 General] Alexadro:
The people who figured out how to translate UEFI to legacy status ? what would have appeared in UEFI x32

Is it possible to use for translation ( in UEFI x32) or rEFIt GRUB ?
[MeMO Pad 7 General] profee:
Sorry, dude. I saw you are still on 4.4 so I thought you were just speculating.

I have done twrp and cwm backups prior to updating to lollipop, so if anyone needs them, I can upload.

Edit: you were right. I froze power saver, rebooted, and it's running great now.. Thanks!
[MeMO Pad 7 General] vampirefo:
Can some post a pic of bootloader, I want to see if pic states the bootloader is locked, here is a pic of my ares 8 bootloader, the bootloader is not locked, as you can see it has ? instead of yes or no.
[MeMO Pad 7 General] profee:
Can't take a picture, but I just checked. It says 'secure boot: yes'. I guess that's all you wanted to know.
[MeMO Pad 7 General] vampirefo:
Correct, thanks.
[MeMO Pad 7 General] Mis012:
Don't want to go into details, but please read something about secure boot, idealy in this great article: https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/
[MeMO Pad 7 General] vampirefo:
Thanks, I am just looking at options to boot my tablet, it sees ubuntu and loads grub given me choice to boot live, problem I have no hub, need keyboard to enter choice.

I read somewhere me176cx tablet booted windows, I am sure mine would also, just can't find a windows iso.

Anything for the link.
[MeMO Pad 7 General] Mis012:
Don't think "finding a windows iso" is legal, but I read about program which can make bootable live usb from your current Windows installation, and you can always search this thread, the guide should work almost the same way. I would make a nice tutorial even before this guy, but I cannot actually find out what exactly to do as I am still stuck on kitkat :(

It looks like that letting ASUS change the motherboard is all I can do :(
[MeMO Pad 7 General] Alexadro:
In UEFI in the Advanced section on (lpss&scc Devices mode) next

Look for in a top setting os selection Windows 8 - android) switch

If you select windows then reboot the tablet and see (not loaded booth Android) as if anything but windows is not installed

Now connect the keyboard, press F2 on it and to boot UEFI.

That is what apparently goes to load Windows Android Ubauntu and other H. unlocking the Bootloader is not necessary (I think so)

In General who switched don't be put off by pressing (power) on the keyboard and F2 we get back into the BIOS and return all the values back.

In General can unlock the bootloader is not necessary ?
[MeMO Pad 7 General] vampirefo:
Finding the windows OS was easy, but it's 32bit while my tablet boots 64bit, so not going to work. Sidenote I did go to walmart and buy a $6 hub, I had to know if this $78 ares 8 tablet could boot a full 64bit Linux, well in fact it can, I got it to boot Fedora-Live-Workstation-x86_64-22-3.iso. In desktop mode really slow.

So a powered hub would be needed for speed or usability, anyway just needed to know if this tablet could boot a Linux distro.

Hopefully you can get your tablet repaired.

Edit update, just now booted into Ubuntu 15.4, it's faster than Fedora on this tablet, no wifi cause, this tablet uses realtek wifi and bluetooth I doubt any distro via default includes the wifi for this tablet.
[MeMO Pad 7 General] Mis012:
seems weird to me, if you have 64bit UEFI on x86_64 tablet, it should boot both 32bit and 64bit windows? And you can always give Windows 10 technical preview a try, it should have 64bit version ;)

And as for the repair, I am 15 years old, it'n not going to be easy..
[MeMO Pad 7 General] tonzky24:
Games are running on slow motion too, but smooth, had to wipe cache every now and then to get the fps back. How do we fix this?
[MeMO Pad 7 General] profee:
Turn off power saver, or even better freeze it. That helped me.
[MeMO Pad 7 General] Alexadro:
Try to run x32 bit operating systems be used Grove or rEFInd
[MeMO Pad 7 General] Mis012:
Turn off battery saver mode in settings ;)
[MeMO Pad 7 General] LNDRG:
hi, im having the same problem with bluetooth..it sounds like slower and freezeing. How do you solved it ?

EDIT: I did a full wipe and now it works grate.
[MeMO Pad 7 General] enims:
mount -o rw,remount /factory then do getprop ro.isn > /factory/asuskey
[MeMO Pad 7 General] tonzky24:
Anyone tried playing implosion? Most of the texts are missing
[MeMO Pad 7 General] Mis012:
Hey all! If anyone is interested in making custom rom for this great tablet, take intel's generic android image as a base instead of asus' android with locked bootloader. We have UEFI after all :)
[MeMO Pad 7 General] jerbear294:
I'm aware of that, and it confused me the first time I played the game since I didn't see anything past the menu. I eventually figured out where the start button would be and muscle-memory'd chapter locations and such.

Rayark said they'd release a hot fix but that apparently hasn't happened yet.

Hmm... That could work, but how would Intel's generic image unlock the bootloader? Does it just flash a generic one that's unlocked and UEFI compatible?
[MeMO Pad 7 General] Mis012:
It doesn't unlock bootloader, it uses it's own. The problem is it has some bugs, and looks like discontinued project. On the other hand, cyanogenmod 12.1 or so could be edited according to this and we would have generic cyanogenmode for a all x86-64 UEFI devices. And that would be amazing!
[MeMO Pad 7 General] uramis:
Manual Update .182 -> .191

Hi, almost just got back my memo pad from being serviced and I has really old builds so I decided to update it. Up until .182 I was able to update it OTA, however downloading the .191 file was stuck at 99%, so I decided to restart the device. However, when I try to click the "Check for update" button, nothing happens, that's why I tried to do it manually. I binge-backread from some October last year, so that I can find the .191 files and how to install them. During trying to manually install, I rebooted to recovery, but I get an error message "No command" with the android bot open and the red exclamation mark picture. I think I don't have any recovery installed. Also, my device is not rooted, and would prefer that it stay unrooted for now.

Any ideas? Maybe something I missed during my backread?
[MeMO Pad 7 General] Alexadro:
But what if you unlock the boot UEFI , you can select Windows and loader Andrtoid as there was , he was no longer hanging out ?

Choosing to UEFI Windows and there is no loader Android it disappears
[MeMO Pad 7 General] spookmeister101:
I was actually quite curious about this. I've been trying to get up to speed on UEFI, and I certainly don't claim to have knowledge about it yet. But I suppose there would be driver issues and such that would have to be figured out. It looks like they have it up to 4.4 now, but they're working on 5.1 at http://www.android-x86.org/

I wouldn't know where to begin though being a newb :silly:
[MeMO Pad 7 General] social-design-concepts:
That's not Intel's that project is about running android on traditional desktop and laptop PC hardware.

you want to look at android-ia or even better the windriver Intel bsp for the mobile device platform

android-ia is Intel's opensource departments official android source.

windriver and other Intel bsp is more for device manufactures and has a lot more closed source parts but requires you to agree to an NDA to download.

Experienced people curious about modifying uefi vars should look at

http://github.com/android-ia/platfo...oot/blob/release/android-5.1.0_r1-ia0/aboot.c
[MeMO Pad 7 General] spookmeister101:
LOL, well there you go. I did say I don't have any knowledge. Thanks for the heads up. I'll head over to those sites.
[MeMO Pad 7 General] Mis012:
You have to boot it from usb. I am going to make a tutorial on how to dual boot windows and android but I have to let asus service give me lollipop > UEFI because I don't wan't my guide to be only theoretical and I want to make pictures during the process. It's not as easy as it looks to make a way to the store and say them something to point them to send it for RMA. I will try to ask parents about it right now, not having UEFI is actualy frustrating..
[MeMO Pad 7 General] Alexadro:
We have a device of 16 GB of memory is very small why dual boot is awful

It is better to do so would people chose Windows or android to whom it is necessary , and each downloaded what you need it :)
[MeMO Pad 7 General] Mis012:
I will try it first, then I will see if it can work. Of course a 64GB sdcard with good r/w speed would be better for storing windows, but they're pretty expensive

Edit: found this card it should be a bit faster than usb 2.0 devices

http://www.ebay.com/itm/Samsung-Mic...075?pt=LH_DefaultDomain_0&hash=item1c40bcf6db
[MeMO Pad 7 General] Mis012:
I can only recommend this great article: https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/

This is where almost all of my UEFI knowlenge goes from.
[MeMO Pad 7 General] spookmeister101:
I actually did read that article, and it helped a lot, but I'll probably have to read it a few more times before it sinks in lol.
[MeMO Pad 7 General] Alexadro:
UEFI is possible to update the site with INTEL

maybe he and our lack of our UEFI update

But you can only update the UEFI obchno on your computer and on a laptop or tablet, you can get a bricks

And therefore I need a specialist

http://www.youtube.com/watch?v=pxeJI5WYdJU
[MeMO Pad 7 General] Mis012:
UEFI has to be specific for every device, and ASUS will not share UEFI for this tablet publicly. Or do we just need the capsule.bin?
[MeMO Pad 7 General] joao1996f:
Can´t boot

I did it and now I can´t boot, only enter in Fastboot.

EDIT: I used a new USB HUB.

I boot UBUNTU from USB!!!
[MeMO Pad 7 General] jerbear294:
So you were able to boot Ubuntu via USB, but can no longer access Android?
[MeMO Pad 7 General] joao1996f:
Now I can boot to Android because I can change that option inside UEFI.
[MeMO Pad 7 General] Alexadro:
do not worry everything is fine .

This is because of - the fact that there is nothing found

No windows ubantu or other systems to meet the need for UEFI

But we can immediately get to the UEFI clicking on the start and press F2 on the keyboard ie as well as on computer persoonalnom

And we do not interfere with the boot loader Androida prove that treovalos

Ie boot androd 's not hanging out

---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------

Ie we just go in there and change the UEFI Windows to Android and get back to android

---------- Post added at 01:27 PM ---------- Previous post was at 01:19 PM ----------

I think asus he receives information and technology from Intel so I think if there is a good specialist UEFI he can help us in addition UEFI 32bit or 86bit digit
[MeMO Pad 7 General] joao1996f:
Running Windows 8.1 N on this tablet via USB using Windows to GO!!!

Very slow!
[MeMO Pad 7 General] Mis012:
Our processor is x86 architecture 64bit. Our UEFI is 64bit. 86bit doesn't exist. Read something about that.
[MeMO Pad 7 General] vampirefo:
Lubuntu should run just fine on tablet, it's light weight.
[MeMO Pad 7 General] joao1996f:
Xubuntu it's Ok.

---------- Post added at 04:28 PM ---------- Previous post was at 04:23 PM ----------

I´m running Windows 8.1 N from an old USB external disk, so it doesn´t help.

My Asus only has 8GB. Even if I delete Android partitions I can´t put Windows inside.

SD Card isn´t recognized.
[MeMO Pad 7 General] olegaslav:
Technology WIMBoot Windows takes ~4-5 GB