yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] daspex:
as i know some of us can make this upgrade on so different way's and sometimes it works and sometimes it does'nt.i think it's a kind of mainboard missarchitecture or using different chipsets or something like this by the asus manufacturers.some of us took it to the warranty and got it back sometimes with the lp installed and sometimes with kitkat .i'm not a dev./coder but if you want to know how the update is managing the bootloader or compare things like this you should talk to thebulletfromhell

regards

---------- Post added at 01:39 AM ---------- Previous post was at 01:30 AM ----------

@bromisco

hi!

thank's for the short reply and clearly explanation,so i don't have to go deeper inside of this stuff,couse i don't use xp.
[MeMO Pad 7 General] HenryLeonheart:
I have the same problem as muzsielod. As I remember from a long time ago, I think I deleted the "show_progress(0.750000, 0);" after having the K013_1 error. Is there any way to fix it?
[MeMO Pad 7 General] sidane12:
I have the same problen, and I deleted "show_progress(0.750000, 0);" too. :crying::crying::crying:
[MeMO Pad 7 General] Mis012:
EFI variables

OK, so I have got my tablet repaired, mainboard change. I set up english languege, went to settings and updated. I left the tablet for some time and when I came back, I couldn't believe - I was on lollipop. I checked the version, it vas the latest build. I looked on the new bootloader. I factory reseted the tablet to use the lollipop feature and restore google saved data to it, and set my native language.

I copied rEFInd to ESP, making photos for a how-to guide. Then I used efibootmgr (the one social-design-concepts posted) to add it to boot order. Well, when I wrote it the right way for this device (and ten times bad before) it had zeeo output. I thought hooray.

BUT - I wrote efibootmgr, it showed the same list as before. I wrote efibootmgr -v and I have got a really weird output ( but maybe not that unusual ). Haven't tried -v before, but it looks like it was like this all the time.

The I "discovered" the problem. Any efibootmgt command which should change something (for example timeout set) did absolutely nothing. So please do you have any other method how to add boot entry, disable secure boot etc., without powered hub?

I wanted to try to replace some of the efi files in ESP with refind, but wouldn't the secure boot refuse to boot up?
[MeMO Pad 7 General] social-design-concepts:
After reading the commits for efibootmgr I noticed I noticed that there is a build flag that needs to be set when using 64bit efi firmware I'll build another version the one I posted earlier was for 32bit firmware it's probably the issue.
[MeMO Pad 7 General] Mis012:
Wow thanks a lot, working efibootmgr is essential when I cannot enter UEFI setup (maybe I really need powered hub). In refind, there will be no problem with keyboard not working. Or setting timeout other than zero could let me boot in that "aptio setup utility"
[MeMO Pad 7 General] lambdadroid:
If you've got the latest update from ASUS then the device shouldn't even use Secure Boot for UEFI. On my device Secure Boot is already disabled, without me doing anything. You will probably not be able to boot something else without modifying something in the UEFI setup if you don't have a powered hub - at the end it might be actually easier to get one?
[MeMO Pad 7 General] Mis012:
I don't think so, efibootmgr is so powerful tool when it comes to boot entries. The bootloader says secure boot enabled, but it may be that asus only want's us to think so, but he don't want/can really use it for some reason (thankfully)

And even with powered hub (which may be expensive/may not solve the problem) it is eisier to use efibootmgr. But once I will get it up and running, I will make a guide how anyone of you (with OR without usb keyboard/otg cable) run for example chrome os in dual boot (as a lightweight flash enabled browser)
[MeMO Pad 7 General] lambdadroid:
The bootloader is not the same as UEFI. The bootloader DOES use Secure Boot, but UEFI does not. Simply said, if you replace the bootloader ASUS installed by default with something like kernelflinger or similar that can be easily unlocked you could install custom ROMs etc. If you have a USB keyboard and a powered otg hub it's easy to boot something custom, simply plug it in, press F2 and modify the boot order - if you go to the Boot settings you will also see that Secure Boot is disabled in UEFI. I paid like 10€ for my powered OTG hub, it was well worth it and works just fine to get into the UEFI setup.
[MeMO Pad 7 General] Mis012:
I was the one who first came up with using another bootloader to solve the problem. BUT, that the bootloader is locked, doesn't mean it has secure boot ( but it behaves like that) becouse secure boot is UEFI feauture. But thanks for the info. If you want, you can experiment and find some efi bootloader which will work with our tablet, and spread the info to developers so they can make us something like cyanogenmod 12.1.

And again, it hurts me that you are explaining me something I wrote here a month ago.
[MeMO Pad 7 General] lambdadroid:
As I said, the bootloader is locked and that's most likely what they call Secure Boot in their bootloader. I doubt it is related to UEFI in any way, they've just used the same name for a similar feature in their Android bootloader.

Tried that already, stuff like the generic Android image or kernelflinger from the newer images generally boot up fine (into the bootloader) but will fail after that. We would probably either reconfigure it or simply compile our own to properly configure it for our device. I'm not experienced enough with this I'm afraid.

I am fully aware of this and just trying to clear things up. UEFI's Secure Boot is disabled and that's something you didn't appear to be sure about in your previous posts so I was clearing that up. Not trying to hurt you. Sorry if I did.
[MeMO Pad 7 General] jedial23:
could someone send me the google store APK for Intel architecture? I've a wrong installation.
[MeMO Pad 7 General] Mis012:
Just search on google, but I think there are better ways to repair wrong installation.
[MeMO Pad 7 General] social-design-concepts:
32bit and 63bit View attachment efibootmgr.zip
[MeMO Pad 7 General] Mis012:
Thanks a lot, now works like a charm.
[MeMO Pad 7 General] Mis012:
Tutorial

So after a month since realizing I wont to make it, the first part of dual boot tutorial: http://xdaforums.com/memo-pad-7/help/how-to-dual-boot-me176cx-part-1-t3183437
[MeMO Pad 7 General] jedial23:
Hi, mis012 I did, but it's difficult to me find correct thread. Where you from? Speak Spanish?

---------- Post added at 09:58 ---------- Previous post was at 09:45 ----------

Hi, sorry... http://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096
[MeMO Pad 7 General] lambdadroid:
Do you perhaps know how to properly build kernelflinger for our device? I've been trying to boot the Android-IA's kernelflinger build (from the minnowboard image) on the device. First it boots fine into the bootloader but will then

a) complain that Secure Boot is disabled in UEFI (it's possible to skip this warning, so no big problem)

b) when trying to boot after that it will search for the boot partition with the gpt guid 49a4d17f-93a3-45c1-a0de-f50b2ebe2599 - that's the one that is also in the gpt.ini you would flash on the minnow board, so I guess our device's partitions have simply other guids and it can't find the boot partition and

c) as far as I can say it has no USB fastboot support inbuilt (at least it isn't working for me), probably because all the tutorials for the minnowboard are actually using fastboot over the ethernet which isn't working on the tablet because the device has only WLAN which is obviously not supported.

Any ideas? The whole Android build environment is really confusing for me so I'm not sure if I could somehow build it differently to fix these issues.
[MeMO Pad 7 General] social-design-concepts:
I'll build one tonight with GUID's used on the consumer tablets thanks for confirming the error I suspected u were seeing
[MeMO Pad 7 General] social-design-concepts:
yes

80868086-8086-8086-8086-000000000100 BOOT

80868086-8086-8086-8086-000000000101 RECOVERY

80868086-8086-8086-8086-000000000102 FASTBOOT

80868086-8086-8086-8086-000000000004 MISC "I have to double check this one if it is consistent across devices"

these 4 are the important ones that need to be changed
[MeMO Pad 7 General] ymDroid:
Guys....

Kind of need some help here.

I own a Nexus 7 and Memo 7.

Since my daughter uses the Memo 90% of the time, I figured I don't need root or anything special. Especially since she solely uses YouTube kids and Sprout TV.

So rather than go through a series of updates to get to Lollipop, I unrooted with ZenFone and did a factory resest.

So the tablet is stock now. In an attempt to expedite the Lollipop update, I attempted to boot into recovery mode just like I do with my Nexus to wipe the CACHE but it pops up to a the Android with the red triangle and the words NO COMMAND.

When I boot into Fastboot, there a series of commands, and the says AWAITING COMMAND. Selecting Recovery Modo through here also boots me to the Android with the red triangle.

Funny thing is that once I'm in here, any attempts to power off and power back on takes me back to the red triangle.

To fix this, I insert an SD Card, let fast boot come up, and give a bunch of errors blah, blah, blah...CANT read blah blah from SD Card.

I remove the SD Card and select REBOOT and the it will boot up normally.

So....what the deal with the recovery on this tablet.

Where's the good old Android recovery with factory reset, wipe cache, etc...that my Nexus has.

Did having root ZenFone on this table screw up my recovery?
[MeMO Pad 7 General] lambdadroid:
Did you have any chance compiling it yet? No worries if not, I don't mind waiting.
[MeMO Pad 7 General] social-design-concepts:
No sorry I spent my Friday installing internet for my daughters grandma and Saturday fixing my phone its on my agenda for today but at this time I need to get my coffee in. Did the hardware keys work on the prebuilt version from android-ia
[MeMO Pad 7 General] lambdadroid:
Where do I need to change that?
[MeMO Pad 7 General] ymDroid:
No one having issues with stock recovery?

Regular Android recovery working for everyone?
[MeMO Pad 7 General] chuy409:
Has anything happened since I left? Last thing I remember was lollipop being released.
[MeMO Pad 7 General] lambdadroid:
I managed compiling a proper build now that has the correct guids, however it does still seem to have problems with booting. Basically I can't see much except that it will fail and something with Invalid argument will be printed for a short moment. The droidboot ASUS installed does probably boot slightly different than kernelflinger.
[MeMO Pad 7 General] grävling:
Hello. I have just purchased an Asus Memo Pad HD 7 K013(ME 176CX). It has android version 4.4.2 (kitkat) build number ww-3.2.23.201

I downloaded RootZenPhone here http://d-h.st/1MK, moved it to my SD card, moved the SD card to the K013, and used the installer that comes with the tablet to install the apk. I followed the instructions here: http://xdaforums.com/showpost.php?p=55229933&postcount=22 but, alas, it did not give me root, but only put me into the annoying demo mode, which you have to factory reset to remove. I tried this 3 times, and I have since read that RootZenPhone does not work with KitKat, so though it is still possible that I am repeatedly doing something wrong, I think that I just have the wrong rooting method. Has somebody got this to work with build 201?

Should I be trying with the method here? http://xdaforums.com/android/genera...-4-4-2-100-t2947092/post56904125#post56904125 or doing something else?

Suggestions welcome,

Grävling
[MeMO Pad 7 General] chuy409:
Hmm. Did you buy the Memo pad 7 or memo pad HD 7? The one with the HD is an older version than the memo pad without the "hd". But you listed the correct model number which the old one is ME173X. hmm i also had the annoying demo mode thing. Jesus christ it was so long ago that this happen but i remember bypassing the demo mode. Hopefully someone here can help you.
[MeMO Pad 7 General] grävling:
Here, at any rate, other things besides the ME173 are called the HD, but indeed on the box it doesn't say HD, just Asus Memo Pad 7. I own one of the ME173X as well, and Framaroot rooted this one just fine. But Framaroot doesn't work here, unsurprisingly. The demo mode isn't the problem -- the problem is the lack of root.

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

I found a more recent version of the rooter, RootZenFone-1.4.6r.apk and tried that, still no joy.

---------- Post added at 11:01 AM ---------- Previous post was at 10:43 AM ----------

Asus is also giving me the option to move to Lollipop 12.10.1.24

I wonder if this is a better place to start rooting from?
[MeMO Pad 7 General] groovychap:
I've got a problem.

I've been holding off installing the most recent update, but I've just downloaded it by accident after pressing the wrong button in the status bar.

It now says that the file has been downloaded and 'tap to update your system'.

The problem is that I'm rooted and have the Xposed framework installed, so attempting to install the update is likely to end badly.

What should I do now?
[MeMO Pad 7 General] grävling:
............. I found a different RootZenFone-1-4.6.r.pk _here_

http://onhax.net/root-unroot-asus-zenfone/

And I tried it. According to the web page I should have been prompted for whether I wanted to install SuperSu (by Chainfire) or Superuser (by Koushik Dutta). This did not happen to me -- but the tablet is now rooted with SuperSu.

Happy Happy Joy Joy :laugh:
[MeMO Pad 7 General] grävling:
problem with ota

I installed the Pro version of Titanium backup, and then froze CMClient.apk and DMClient.apk . This makes the messages about

the OTAs that you don't want to install by mistake go away. Should you ever want to get an ASUS OTA you can just defrost them. Freezing them is under backups, and I think you need the pro version of TB to get this ability. Probably there are other ways to freeze apps, but this is how I always do it.
[MeMO Pad 7 General] daspex:
and did you do the update and get the lp?
[MeMO Pad 7 General] PhantomSS:
I have the same problem, I only can go through fastboot mode :crying:
[MeMO Pad 7 General] daspex:
read the unbrick section!!!!?
[MeMO Pad 7 General] portenaert:
Hi,

My ME176 is on kitkat .201 and Root.

If i update on Lollipop, i lose the root?

thank
[MeMO Pad 7 General] MKKLR21:
You probably will lose root access through upgrading. But you can gain root access on lollipop with this method: www.ibtimes.co.uk/how-root-zenfone-5-android-5-0-lollipop-v3-23-40-52-one-click-tool-1505424
[MeMO Pad 7 General] portenaert:
Thank you MKKLR21.

Nobody has tried this method?
[MeMO Pad 7 General] dog121:
I've used this method it works fine
[MeMO Pad 7 General] Alexadro:
Hello forum users ! Tell please !

Whether it is possible to overwrite the UEFI?

The problem during installation Ubauntu or Windows,

mode Windows installation got the battery . It was decided to charge the tablet but was able to windows connected to the battery power supply. After this has been switched to UEFI in the state of Android and charged to the end

Result:

Do not install Ubauntu. Shipping only windows.

Install Flash card is only displayed at the end of the Boot section not keep it there just installed android .

The question I want to reset the UEFI

Yet I think that it is possible from a damaged tablet - for USB hub There provd connected to the tablet plus to plus or minus to minus USB but there was OTG but maybe it did not help and the voltage of the battery has passed through the plate and erased part of the UEFI
[MeMO Pad 7 General] portenaert:
With Lollipop Version: V 12.10.1.24 :confused:

Thank
[MeMO Pad 7 General] dog121:
Yep ...
[MeMO Pad 7 General] portenaert:
Thank you dog121.

But I think staying on Kitkat......

I do not think lollipop will bring me much
[MeMO Pad 7 General] dog121:
Yep lollipoop was a disappointment... On the tablet on my phone different mater altogether..
[MeMO Pad 7 General] jerbear294:
Lollipop is actually quite nice after you put Xposed on it and put the Fix Lollipop Memory Leak Xposed module on it, plus it's more customizable than KitKat. If you don't care about that, then yeah, stay on KK.
[MeMO Pad 7 General] ardicli2000:
Is there a compatible xposed for me176c?

If yes, could you please provide the link for xposed and the lollipop memory leak module?
[MeMO Pad 7 General] kacpeur:
So, my K013 keeps driving me crazy. I got lollipop (rooted) with the xposed fix memory patch, but the battery keeps draining like hell. After two days of not using and keeping the device on, it goes from 100 to 0 percent.

My build version is 12.10.1.17-20150505: has anyone updated to the recent update and did you still have root? Or has even anyone managed to go back to stock kitkat? Should I follow the unbrick method?

cheers!
[MeMO Pad 7 General] ardicli2000:
Updating to 10.1.24 will resolve most of your problems. Previous lollipop build is very problematic.

Plus, dont activate battery save mode. IT causes performance problems. Instead use no frills cpu, greenify, etc to lower your battery consumption.
[MeMO Pad 7 General] kacpeur:
What about root? Does the update delete it?
[MeMO Pad 7 General] jerbear294:
Yep, but you can easily reroot the update.

The official Xposed for Lollipop is compatible since it now supports x86, but I haven't tested it. I've been using Shacalaka's Zenfone 2 Xposed build.
[MeMO Pad 7 General] maxwellshammer:
A quick line for anyone wanting to root Asus Memo Pad 7 me176cx with Android Lollipop.

It's pretty straightforward - google HTCMania root lollipop - although the translated pages do make a couple of small errors (in the Linux method anyway) so check the original source.
[MeMO Pad 7 General] iamflip:
can anyone help me on how to root asus memo pad 7 me176c k013 android lollipop version? i can't find on how to root this tablet with ease, there are many confusing guide.. thanks in advance :)
[MeMO Pad 7 General] Alexnb:
No, download from OTA

I do not think that people use the same apps to discharge the battery :)

But, yes, I have restored, not all my apps
[MeMO Pad 7 General] Hag77:
Yea that's what I meant. Perhaps your factory restore just temporarily fixed the discharge problem until you load that one problem app back on.. Who knows which one it is.. I've used many "battery saver" type apps that attempt to tell me which app is the problem one, but it never seems to work out when I try to uninstall, or it's one that I need.. It's one of my biggest problems with android actually, had similar problems on my HTC DNA. My ipad and iphone have great standby battery, but I just needed another cheap e-reader/browser. I really like this tablet overall, but the standby battery problems suck- hope I can get it figured out- or maybe install a custom rom w/ better performance at some point.
[MeMO Pad 7 General] zapz:
I had this problem too, but it seems that keeping Wi-Fi on permanently (on the second power saver option or with the power saver off) temporarily solves the problem. I'm still testing it though. With my Wi-Fi off, I get the battery standby problem and in around 8 hours, the battery drops like 20-30%. With the Wi-Fi on, it drops less (2-4% around the same time span). It should be even lower, but it's probably because the Wi-Fi is always connected (the deep sleep problem actually dissapears, Android OS doesn't keep the tablet awake anymore, but the Wi-Fi still eats some battery since it's always on). The problem came back once (while actually having Wi-Fi on), but after doing a restart, the problem dissapeared again. But yeah, even like this, the problem is still there and unless I always keep Wi-Fi on, it comes back.

Oh and also, I called Asus 2 weeks back regarding this problem, but they didn't help with anything, such experts, wow. They said that the battery being eaten like that is something normal. I couldn't believe it.
[MeMO Pad 7 General] Alexnb:
I think the problem arose after the 161 upgrade, not after installing the apps.

I will add the apps one by one and look at the results ;)
[MeMO Pad 7 General] bravesoul:
No joy. It stops at 95% then shows the error message. Could I have a corrupt ROM?
[MeMO Pad 7 General] zapz:
Has anyone tried to un-root the device? Wondering if it works, in case I'll ever need the warranty back after I'll root the tablet.
[MeMO Pad 7 General] dexter20082001:
That is a possibility. Give a new download a try.

Sent from my Rooted Asus MeMo Pad 7 176CX

---------- Post added at 03:45 AM ---------- Previous post was at 03:40 AM ----------

Does anyone know how we would go about getting an actual thread/section on here? It would make it better for developers and users to find this info and even be aware of its existence.

Sent from my Rooted Asus MeMo Pad 7 176CX
[MeMO Pad 7 General] jerbear294:
Unfortunately not likely. My main dev tablet has tons of work in it but still no forum.
[MeMO Pad 7 General] Alexnb:
Try using SuperSU unroot function
[MeMO Pad 7 General] groovychap:
Would it be safe to attempt to install Viper4Android on this device?
[MeMO Pad 7 General] zapz:
Will that also delete the tablet data? Or only remove root?
[MeMO Pad 7 General] pjim:
No luck on a recovery? Do you need different files?
[MeMO Pad 7 General] Alexnb:
Remove root
[MeMO Pad 7 General] gd6noob:
root-zenfone-142r

Works perfectly on my ME176C... installed titanium backup and un-installed a bunch of asus bloatware...

Now just need a custom rom...
[MeMO Pad 7 General] nogarder:
I just found a method to use when the application icon disappears and can not run.

Only for ROOT.

Once this happens, we must re-install the application, and look for the newly installed apk in mnt / asec folder

We copy the APK from there, and paste with a different name in the /data/ app / folder.

The name should be the same as the folder where the files are installed obb, and we must add "-1".

Reboot the tablet and we should appear with the apk icon and should work correctly.
[MeMO Pad 7 General] boyan_bg:
I have e me176cx 16gb, and after root with zenfon everything was OK. Also I try to make external SD card available for write to programs using solution with edit of platform.xml and adding media_rw as described on net.

After this i have a very bad problem. Just rebooted device and i have permanent crash on all applications. Also I dont have content on internal or external SD card and I can't fix this at all.

I try factory reset from android but same after that, also from recovery i made clear cache and factory reset - same.

I try to adb sideload latest firmware from asus web site for this SCU (WW) but when sideloaded tablet gives me error that checksum doesnt mach and cant update.

Also I adb push rootbrowser, because after reset i lost everything but SU was present because was installed as system app. So after push rootbrowser and mount /system as RW, I manual enter all platform.xml to its default state, but no luck after reboot :(

Strange is that, I formated external sd card and when put on device, its mounts but I not see. But when I read in my card reader on pc there is "lost+found" and "android" folders, and its been mounted anyway but not visible.

Does anyone knows how to reflash flash entire rom on this device or any other solution on this problem?

I have a working fastboot and adb.

Regards!
[MeMO Pad 7 General] ICavalera:
We know that don't have a big community with this device.

Why don't you just make root, then delete the bloatware and then... We get a "costum" rom.

I use nova launcher, deleted all the apps don't need and the tablet gets more faster and smooth. Don't have any trouble so far.

In my opinion, let's get this simple, guys.
[MeMO Pad 7 General] jerbear294:
Because we need a custom recovery to flash the custom rom.

I'm still working on that.