yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] Alexadro:
I mean

what other plates like UEFI runs Windows x86bit.

Perhaps there is a mode legacy bios, on our plate that we could not be found .

Because I am Gabriel to add our legacy bios and 86bit

---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------

a complete tablet

Windows 8.1 with Bing

? 64bit?
[MeMO Pad 7 General] joao1996f:
Touchscreen works just fine on Linux. For Windows we need drivers.

Our touchscreen is from Goodix.
[MeMO Pad 7 General] vampirefo:
Good for you, my touch screen doesn't work on my tablet, I do have wifi working.
[MeMO Pad 7 General] Mis012:
look at http://www.techsupportalert.com/content/32-bit-and-64-bit-explained.htm for info about 32bit and 64bit. 86bit doesn't exist (but theoreticaly could) and x86bit is completely messed up.

So. In past, there was only 32bit processors. They were x86 architecture. Then, Intel started to make 64bit processors. they were x64 architecture. BUT, because of the diferrent architecture, there was no backward compatibility, so you were only able to run 64bit OS and 64bit programs and games. And even today, a lot of apps only have 32bit variant. So, in name of compatibility, Intel started to make 64bit processors with x86 architecture. They are called like x86_64 or EM64T etc. These processors are capable of running both 64bit and 32bit OS. But we have UEFI, which can be 32bit or 64bit, and 64bit UEFI can for some reason not run 32bit OS. It should theoreticaly be able to run 32bit OS, but I am not sure if the bootloader has to be 64bit or what the problem is. But, there is nothing like x86bit, and there is also nothing like x64bit. x86 and x64 are architectures. Thank you if you read entire post.

And our tablet should be capable of running 64bit windows OS.
[MeMO Pad 7 General] joao1996f:
It's capable but very slow, I tried. 3-5 minutes to boot Windows 8.1
[MeMO Pad 7 General] therealprof:
You mean IA-64. And that's not actually true. The first Itaniums had hardware support for execution of x86 software which was later replaced by much faster software emulation. I don't think there was ever any "game" compiled for Itanium (other than maybe some OSS game which happened to come with some Linux distribution).

That depends very much on the operating system. Android and Windows? Potentially. Linux and MacOS X? Definitely no; no sane developer would even think of distributing only 32bit binaries because they run slower and cannot (easily) use large amounts of memory. Heck, we actually see 32bit support being dropped from new OSses.

Again not true, x86-64 was actually invented and introduced by AMD and Intel scrambled to follow suit...

<sic/> Again... not... true.
[MeMO Pad 7 General] Alexadro:
Yes, no one argues. Let it be x32bit it does not change the matter.

The main thing that we need to do is install windose 8 or 10 (x32bit)

It is necessary to concentrate on that. It is important to decide either to fix or to transfer UEFI boot loader on another supposedly rude or refind else

I think better to cast aside the Chinese letters rather Taiwan manufacturer ASUS

this requires consolidation and a common impulse of all communities, and links people

Everything else demagogy does not make sense to focus on history and other matters

It does not matter :)
[MeMO Pad 7 General] social-design-concepts:
I've been having a hard time following this uefi discussion

What's the issue with booting Windows 32bit uefi?

So this device has the ability to disable secureboot or just has Microsoft keys loaded so it can boot a signed shim.efi?

I keep seeing that users are booting Windows or Linux but no one ever mentions disabling secureboot so that makes me think signed shim.efi?

Just need some clarification on what the issues are.
[MeMO Pad 7 General] Mis012:
I always thought 64bit Windows is better the 32bit, why would anyone want 32bit when 64bit works? I am not sure if 32bit OS will be less lagy. Of course Windows 10 may run better as they are planned to be used also in less powerful devices. Windows XP should run fine on this tablet on the other hand, but it is old and new programs may refuse to work (And Microsoft support ended, but who makes viruses for OS noone uses?) Or we can use some lightweight linux distribution. Or someone can take Intel's generic android image (UEFI bootable) And make cayenogenmod 12.1 which would use Intel's bootloader. And that should be done with no matter if Windows 10 will run smoothly or it will be laggy as hell.
[MeMO Pad 7 General] social-design-concepts:
So secureboot is able to be disabled on this device?

Intel's kernelflinger (which is nice by the way) won't load if it secureboot isn't disabled after injecting android-ia keys you could re-enable secureboot.

Though this device seems to have Microsoft keys loaded so you should be able to use andriod-ia shim.efi / mokmanger with kernelflinger.

Still don't understand the issue with booting 32bit windows efi unless the issue is the boot option in the efi firmware is hardcoded to look for microsoft bootx64.efi in the 1st partition of the selected boot device. if that's the case you should be able to use edibootmgr to add the boot entry for bootia32.efi.

I was working on a PC the other day that the efi was like this it looked for bootx64 from the chosen boot device on partition 1 if it didn't find it it wouldn't boot I'd have to either drop to efi shell and manually call it or bootx64 and then add the boot entry.
[MeMO Pad 7 General] Mis012:
If someone already booted Ubuntu, then it has to be disablable. I don't think this tablet has windows keys preloaded, there is no logical reason WHY. On the other hand, it has some weird option if you want to boot Windows or android (while there are no windows), maybe Asus wants to give us option to boot Windws 10 when it will be complete, so the UEFI is prepared for it. My tablet should be back from servis soon (someone said it should take about five days) So I can experiment, documentate and make that dual boot tutorial. And ESP is not partition number one on our device, as you can read in partition.something inside lollipop firmware.zip from asus site.
[MeMO Pad 7 General] social-design-concepts:
Official Ubuntu x64 has a Microsoft signed uefi bootloader, Redhat also has a Microsoft signed bootloader, and there are several others, but having the option to boot Android or Windows is why I suspect the Microsoft Keys are loaded.

You're correct ESP is partition 2, I was only quoting efibootmgr default setting wich is /dev/sda partition 1 uefi firmware would use the ESP defined GUID to look for \EFI\Boot\ and then fall back to selected disk partition 1 if no GPT defined ESP exist.

Regardless android and windows being selectable boot options probably means that the .efi app name is hardcoded into the firmware.
[MeMO Pad 7 General] TalhaGirgen9:
İ Got A Update From ASUS... Hell YEAH:D

Bootloader And Bios Updated With Same Version. İ Think Bootloader Unlock:D Or Not:(

FW Version İs: 12.10.1.24

Edit: All Bloatware (Like CleanMaster) Was Removed :)
[MeMO Pad 7 General] jerbear294:
Try the zenfone 2 bootloader unlock method! This could be good news!

Is the UEFI intact?
[MeMO Pad 7 General] social-design-concepts:
Did you capture the ota?
[MeMO Pad 7 General] TalhaGirgen9:
Zf2 Using Another Way Calling SplashScreen İ Dont Try İt Because Of Hard Brick Risk :(

---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------

İ Cant. İ Have Not Root.

Sorry For My Bad English
[MeMO Pad 7 General] jerbear294:
I'm capturing the OTA as we speak. I will upload it to AndroidFileHost when I've got it.
[MeMO Pad 7 General] Mis012:
Helo, we do not need bootloader unlock. It should be possible to run android using another bootloader. Or we will not focus on ASUS' lollipop, an we can use something like https://aur.archlinux.org/packages/android-x86-system-image-22/ and eventualy make a custom rom out of it, maybe with better and more device-specific drivers. And if the update didn't change BIOS, we can backup whole emmc (mmcblk0) and recover it using live linux usb, if there will be a need for.
[MeMO Pad 7 General] groovychap:
Is it safe to install the update if you're rooted and running Xposed?
[MeMO Pad 7 General] social-design-concepts:
Zenfone actually calls a firmware that was added to the last ota under /system/etc/firmware/if.bin then changes the splashscreen.img to mark the device as unlock this is why the bootloader remains unlocked after flashing the stock splashscreen back.

Being uefi there is no need to use that method of flashing an unlock firmware but Asus could use a similar method to expose additional functions in droidboot that are not accessible as fastboot oem commands.

The zenfone2 bootloader unlock is just that droidboot looks for that file the serial number gets echoed to then if it sees it initiates the bootloader upgrade to unlock the device.

In theory Asus could do something similar to have droidboot set OEMLock efivar or even possibly SecureBoot efivar to disabled
[MeMO Pad 7 General] jerbear294:
OTA captured!

https://www.androidfilehost.com/?fid=24052804347775459

I have yet to update my tablet. Is everything going as planned? Root intact?
[MeMO Pad 7 General] vampirefo:
Root would be disabled by install-recovery.sh.p
[MeMO Pad 7 General] Mis012:
Has anyone tried using efibootmgr? It should be able to disable secure boot.
[MeMO Pad 7 General] pgabor29:
Is it 5.0.2? What does it update?
[MeMO Pad 7 General] jerbear294:
Seems to be a bug fix. I haven't applied the update so I wouldn't know for sure.
[MeMO Pad 7 General] stoffel010170:
Official update from ASUS is available, now.
[MeMO Pad 7 General] pgabor29:
Can someone help me with rooting my asus me176cx (with all updates, incl. today's). I'm interested in a reversible rooting. Is this possible with latest updates? I've read 2-3 relevant threads but those methods doesn't seem to work now. I've tried the latest RZF method but it failed. Can someone please explain to me how to do it? Noob freandly please! Thy!
[MeMO Pad 7 General] AndrewRBX:
I tried to apply the new update, but it failed.

Update succesfully downloaded, tablet reboots automatically,

but when the "updating system screen" shows up,

I get the "dead droid screen".

Luckily nothing else happened, I got into recovery from that "dead droid screen" by

pressing POWER+VOLUMEUP, I chose Reboot and Lollipop restarted normally,

with a pop-up notification telling me that the update couldn't be installed succesfully.

I'm pretty sure this is related to my old post here:

http://xdaforums.com/memo-pad-7/general/asus-memo-7-me176cx-t2814046/post61242866#post61242866

Maybe they screwed up with the name of this device.
[MeMO Pad 7 General] sutekh137:
Same here. Though, not sure why, VOL+-POWER no longer works to get me out of the dead droid screen. I just held down Power until the system rebooted, and it came back in 5.0 with the error you mention.

And now System Update does not find anything new to install.

I am rooted (and still am) and do have some apps frozen, most notable the "Power Saver" (really does make a world of difference -- I was up for a week with no app crashes or slowdowns). So, perhaps being rooted or having some apps frozen causes this to not work. Will have to wait and see if we can flash it, I guess. I am really pretty much fine with 5.0, as, like I said, once I froze Power Saver things work fine and memory does not seem to be an issue.

Thanks,

sutekh137
[MeMO Pad 7 General] profee:
I have 50+ apps frozen, so i probably won't even try to update. It's good as it is, and this update is probably solving issues with performance and time which i don't have now.
[MeMO Pad 7 General] AndrewRBX:
First of all, I totally agree about the "Power Saver"... I disabled it too, and the Tablet worked better than ever! :good:

But I also have to tell you that I already tried to update with no frozen apps, just like I did in the past (and every update worked fine for me, no problems at all), and it didn't work... that's why I'm pretty sure this is their fault, not ours.

I still remain sure that they screwed up with the name of this device (K013 and K013_1), so when the tablet checks if the update is the right one for itself, the update procedure stops.
[MeMO Pad 7 General] jerbear294:
The new process for getting out of the dead Droid screen is volume down and power. ASUS changed it in their new bootloader.

---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------

RootZenfone was patched a while ago. Look up "Intel temporary ClockWorkMod" and flash root with that using the guide in that thread. Use the public trial release, and when asked use trigger 4.
[MeMO Pad 7 General] profee:
I don't believe it's that simple. In the past, some updates worked for me, and some didn't. Noone on Serbian forum reported update errors except me, and we probably have same models from the same batch.
[MeMO Pad 7 General] vampirefo:
The update contains a bios firmware update, I would think this update is important, else there wouldn't be any bios modification.
[MeMO Pad 7 General] jerbear294:
ASUS must MD5 the whole system. That way when we root or get Xposed on here the MD5 changes.

Temporary ClockWorkMod/TWRP can probably install the updates after messing with the updater-script

---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------

Either it's a critical UEFI update or ASUS is preparing to unlock the bootloader.
[MeMO Pad 7 General] social-design-concepts:
The efi update probably fixes the clock or patches the access to the uefi / windows option would be my guess.

This is the latest tether recovery launcher :

http://xdaforums.com/showthread.php?p=61861507

It has the latest twrp and finally proper fstab generation for twrp so now you should be able to backup fastboot.img recovery.img the esp partition as well as the option to back the system partition as an image. Its not in the OP yet its been a work week from hell.
[MeMO Pad 7 General] pgabor29:
Non of these worked for me but thx.

CWM: when I type accept, nothing happens.
[MeMO Pad 7 General] profee:
Are you gonna try it that way?

Edit: In the log it says: "script stopped: install-recovery.ch contains unexpected contents", so i guess you're right about tomporary recoveries.
[MeMO Pad 7 General] jerbear294:
Probably not. This update wipes root from what I know, and until we can verify what that UEFI and bootloader updates contain I'm not going to try it.
[MeMO Pad 7 General] social-design-concepts:
Did you extract the 7z file and post screen shots of the cmd prompt so I can see where it is failing
[MeMO Pad 7 General] :
Updating now...

Hopefully this fixes power saver interfering with clock & making games slow, move to SD (apps randomly move back to device storage) & random reboots (One can only hope! :D)

Oh an also the pre-installed apps that can be removed reinstalling after a restart.
[MeMO Pad 7 General] spookmeister101:
Just tried to update mine -- by accident, hit the wrong button -- and it failed LOL 'course it was rooted, and xposed framework installed, so no surprise there.
[MeMO Pad 7 General] Alexadro:
Cheers Hello dear social-design-concepts

I tried as much dokrichatsya you. But why do not you meet

About Secure boot

So Sekyure boot off and was always off. There is Disable.

And you do not have this tablet memo pad 7 (me176cx) ?

What can I say, our uefi 2.3 pi 1.2

like this here on this. The differences are not significant

http://www.youtube.com/watch?v=2bpAE8RaVAo

Torments so that programmers do not have specialists in UEFI It is not downloading

for some unknown reason did not work UEFI x32 bit

As if it is not present at all. I wrote to the China and they mentioned UEFI and said that you can boot (Windows x64) about (windowse x32) did not mention anything at all.

This I wrote in support Táiwān. And Chen is useless Ghawar zero sense

Chinese Ghawar we do not owe anything only for android

Да Táiwān like better support

---------- Post added at 08:47 PM ---------- Previous post was at 08:34 PM ----------

As if they did not at all blocked or removed from our eyes, I am very afraid that this can make asus

---------- Post added at 08:57 PM ---------- Previous post was at 08:47 PM ----------

Because windows 32 really less windose 64. Windovs 64 did not have a 1 GB - ramm is very small and windose 64 hangs and working very hard and informed.

For windose 64 you will not find drivers for tablets and we also need to ASUS
[MeMO Pad 7 General] joao1996f:
It's true. A lot of drivers are missing.
[MeMO Pad 7 General] Mis012:
OK than, I will try to boot Windows 32bit as soon as my tablet will be back from servis.
[MeMO Pad 7 General] joao1996f:
I can't boot windows 32 bit, only 64 bit. 32 bit isn't recognized by UEFI.
[MeMO Pad 7 General] Karvenry:
Update failed

Can anyone else help me on how to install the update. I got a message that the update failed and now I can't see an option to download or update
[MeMO Pad 7 General] un4saken:
no command

Hello,

I just bought ME176c. Not rooted yet. I try to go into boot menu "Power button & (+) button" then i select "Recovery".

After i select "recovery" there is a dead android image saying "no command" and nothing else. Why i can't go into the recovery mode?
[MeMO Pad 7 General] zapz:
All of them are like that I guess, same thing happened to me as well. But I guess you have the access denied? I tried all the button combos I could think of and no menu showed up (heard that in some cases there are specific button combos to make the menu appear).
[MeMO Pad 7 General] profee:
Vol up ÷ vol down combo will do what you need.
[MeMO Pad 7 General] un4saken:
You mean press vol down and vol up buttons at the same time?

edit: Pressing in the middle of the volume button worked! Recovery menu showed up! Thank you!!!
[MeMO Pad 7 General] zapz:
Well damn, tried every combo except that one xD Good to know, thanks!
[MeMO Pad 7 General] joeyisdamanya:
How?

There are a bunch of suggestions for rooting, but none seem to work. Could you please tell us which post you followed?
[MeMO Pad 7 General] nogarder:
i just root my me176cx with Rootzenfon 1.4.4

It seem all works correctly¡

Thanks
[MeMO Pad 7 General] bravesoul:
You can try to answer me if there's a way to do a clockworkmod recovery yet. I need one desperatly.

Kind of soft bricked my Tablet and now Im trying to push the update rom or even the original rom through adb and fastboot commands but nothing seems to work. See this post: http://xdaforums.com/showpost.php?p=55288003&postcount=214 for more info.

Anything you can help, I'd appreciate. :good:
[MeMO Pad 7 General] dexter20082001:
What exactly can you get into with your tablet? Also, what fastboot or adb commands can you use? pictures would be helpful
[MeMO Pad 7 General] bravesoul:
Check this post photos:

http://xdaforums.com/showpost.php?p=55288003&postcount=214&nocache=1&z=7535526903811842
[MeMO Pad 7 General] dexter20082001:
Well your recovery is working as it was intended. Have you tried deleting the cache and then doing a factory reset?
[MeMO Pad 7 General] nogarder:
How can enter into recovery?

I cant do it, only see Logo Asus 10 seg and then shut down
[MeMO Pad 7 General] Hag77:
Haven't messed around with root yet- but I might if it it helps with standby battery.. Anyone w/ root deleted apps that helped? I swear it seems like the battery drains faster when I'm not using it than when I am! Last night went to sleep with 100%, woke up and it was about 87%. I really don't have that much installed since my primary usage for this thing is kindle reading and web browsing.
[MeMO Pad 7 General] bravesoul:
Good lord I've tried everything but VooDoo! :laugh:

The recovery seems to work and I have tried to wipe factory and then wipe cache but I need the commands for the reset..

My recovery isn't showing anything like a reset.
[MeMO Pad 7 General] nogarder:
I have that problem when i use a microsd.

I dont know the explication.
[MeMO Pad 7 General] dexter20082001:
I know this sounds needless but make sure it is on the charger. Turn it off. Once off. hold the power and vol+ button for about 5 seconds and then release the powerbutton. continue holding the vol+. Once you see droidboot scroll down to recovery using the volume buttons and select recovery using the power button. Once it restarts you should see a dead droid with "No command" under it. press both volume keys and then you should see your recovery options

---------- Post added at 04:37 PM ---------- Previous post was at 04:26 PM ----------

the wipe data/factory reset option is the reset. if that isn't working then we need to try to using the update from asus. Make sure to redownload it so that there is no chance your previous one was corrupted.
[MeMO Pad 7 General] nogarder:
Woks perfectly ¡ Thanks ¡

There are more keys combinations??
[MeMO Pad 7 General] Alexnb:
Helped me a full system restore via Boot Recovery

Night consumption decreased from 15-25% to 2%

Asus MeMO 7 (me176cx) v161, root
[MeMO Pad 7 General] nogarder:
its possible do a nandroid backup now or i must wait having a new recovery? Thanks
[MeMO Pad 7 General] Hag77:
Did you have to d/l the factory image from website? Also- is it possible that this just helped because it deleted any apps that may have been causing drain? Did you put all the same apps back on and it continued to have better stand by battery?
[MeMO Pad 7 General] vampirefo:
Same on my nextbook booting only 64 bit Linux, I don't have windows so can't try to boot it.
[MeMO Pad 7 General] Mis012:
If I said I will try it, I will try it. Maybe some other way then you.
[MeMO Pad 7 General] mvrana:
+1 to that. What's the procedure to update rooted?
[MeMO Pad 7 General] vampirefo:
Have not see anyone that has applied update post. If it were me I would return to stock rom then apply update.
[MeMO Pad 7 General] social-design-concepts:
I have this issue on a few PC I configure at work the selected boot device from with in the uefi firmware will only boot x64 uefi but will boot 32bit uefi if I manually add a boot entry for it.
[MeMO Pad 7 General] Alexadro:
If you add manually will be 32 bet?

And as for that much more?
[MeMO Pad 7 General] vampirefo:
I haven't tried, but perhaps a multi boot usb would work, bootimg 64bit is a must, once in grub perhaps can load 32bit, from another partition on usb drive.
[MeMO Pad 7 General] social-design-concepts:
Hmm I'll look into it this evening it's odd cause the three Intel devices I have Dell Venue 3730, Iview 700i, and my Lenovo TAB S8-50F all work with fine with CWM and TWRP is it just CWM not working or TWRP too if you wouldn't mind checking , I like to know if it launches twrp so I know if something I changed in the launcher broke support for this device.
[MeMO Pad 7 General] lambdadroid:
I just tried with twrp_hdpi_portrait.zip and twrp_mdpi_portrait.zip (was that correct?) and it's basically the same as with the CWM recovery, it's sending everything fine but it will just stay in the bootloader screen with "RESULT: OKAY" - it doesn't boot into the recovery.

(bootloader) Start partitioning

OKAY [ 0.068s]
finished. total time: 0.068s
target reported max download size of 536870912 bytes
sending '/tmp/recovery.zip' (6827 KB)...
OKAY [ 0.367s]
writing '/tmp/recovery.zip'...
OKAY [ 0.049s]
finished. total time: 0.416s
target reported max download size of 536870912 bytes
sending '/tmp/recovery.launcher' (817 KB)...
OKAY [ 0.072s]
writing '/tmp/recovery.launcher'...
OKAY [ 0.043s]
finished. total time: 0.115s
target reported max download size of 536870912 bytes
sending '/system/bin/logcat' (425 KB)...
OKAY [ 0.054s]
writing '/system/bin/logcat'...
OKAY [ 0.042s]
finished. total time: 0.096s
...
(bootloader) Stop partitioning

OKAY [ 0.044s]
finished. total time: 0.044s
[MeMO Pad 7 General] vampirefo:
Your commands appear to be wrong, if using Linux you can use my Linux version.