yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] coolbeans2016:
OP

CWM tethered recovery for these tablets is on first page of this thread. Factory reset first, (either through settings or in tethered recovery), then install the firmware (.191). Place Chainfire's SuperSU .zip on internal mem or sd card (tethered recovery will not recognize large sd cards like mine (64gb) flash it with tethered recovery. When you choose to boot back to system after flashing SuperSU .zip, it will prompt you to fix root, do not! Also, it will ask to update binary, with options of regular install or through recovery, you have to use regular of course, but it works.

This not only gives some fixes, tweaks to performance that I have noticed now since using it saves you from having to do three flashes. Follow the OP directions as well. After downloading the .zip, rename a copy of it to user (user.zip) so it can be found with option of installing "user.zip" in tethered recovery. Also, note, after I installed, system popped up asking to install the update .zip again after getting to desktop! Had to go delete off internal memory.

---------- Post added at 11:37 PM ---------- Previous post was at 11:33 PM ----------

Don't forget to hit the "thanks" button if this helps :) For the dev in the OP and me!
[Android Q&A, Help & Troubleshooting] kaiser2000:
Any thoughts on the below? Cheers! :)
[Android Q&A, Help & Troubleshooting] coolbeans2016:
I would not

I am no dev, the person who started this post, and contributors are mainstay people here on xda that have helped thousands of people like myself with their devices. That said, I would not delete any partitions, particularly since this device does not have a full custom recovery available. I do not believe any further support will be available from Asus after this .191 firmware I posted so you can debloat to your hearts content. But from inside KitKat, rooted, using whatever app you like. ROMToolbox, Link2SD, SD Maid, Titanium Backup.... are a few. I prefer the Asus launcher, and Asus"s apps for email and such. Asus's launcher allows you to use icon packs, and other custom creations with their launcher. Asus ZenUI, and launcher from what I have read is now useable on all android devices..... was going to try it on a samsung phone I am using right now. Hope this helps.... Using CWM tethered recovery I successfully installed the .191 firmware like I had the .172 + two OTA's previously and have seen very good performance. My tablet is very useable with its 1gb of ram. But always has been since rooting, getting updated and using Xposed, Greenify, and SD Maid Pro to clean it up, stop everything from being included on startup and freezing the included Amazon apps and internal phone apps included with KitKat (I use voip apps like Talkatone, hangouts). And since the update it has helped to fix my bluetooth issue with using Voip with bluetooth headsets. Have a great day!

zach
[Android Q&A, Help & Troubleshooting] BigBaron:
I hate to ask again, but I did a factory reset (to wipe everything so I could sell it) after successfully rooting my tablet, and now the keyboard doesn't pop up when I touch the screen!

I have tried to do bootloader by pressing vol+ and power, but nothing happens. It will only boot normally.

I'm an Android novice, so be gentle... LOL
[Android Q&A, Help & Troubleshooting] coolbeans2016:
not my thread

This is not my thread, and I am no dev. But it has gotten ghostly quit from the ones whom placed it on XDA. So, I will help anyway I can. Two questions to start with. I take it you are in the USA? (WW firmware build).... & what number at the end is your firmware at? .172, .189, .191..... ??

zach
[Android Q&A, Help & Troubleshooting] CCarson:
There's something really interesting happening over in the world of the Nexus 7 (original model). That device is notorious for its horrible performance degradation after the first year of ownership. F2FS helped somewhat, but it's still a subpar model.

But someone has come up with a series of boot scripts that tweak various system and eMMC parameters that make it a whole new machine. I know because I own one and have installed the modification.

While I've developed Android apps, I know nothing about the Android system itself. If anyone here is interested, you may want to take a look and see if some of this approach might be adapted to the ME181C. If so, it could make this an amazing device once again.

Here's the XDA thread:

http://xdaforums.com/nexus-7/orig-development/parrotmod-speed-2012-nexus-7-emmc-fix-t3300416

Here's the GitHub repo:

https://github.com/parrotgeek1/ParrotMod_Grouper

And here's the script that seems to most directly tweak the eMMC parameters:

https://github.com/parrotgeek1/ParrotMod_Grouper/blob/Universal/zip/system/su.d/01ParrotMod.sh
[Android Q&A, Help & Troubleshooting] kitsis:
Hi Folks, thanks so much for this thread. I got my K011 booting to eternal spinner last week, either by installing the microg GmsCore into /system/priv-app, or by being really lazy and typing reboot on the console before syncing and remounting /system read-only.

So I have a couple of queries, I'm a seasoned unix based sysadmin, and this android bootloader stuff and lack of a way to just get in and fix it is frustrating!

1st question is - There must be a simple answer, but loading a system up from an image I download from a filesharing service is not something I would do. How is this wise? I assume it's protected somehow? But then if the whole point in loading this tethered CWM recovery is to somehow bypass the bootloader signature checking, could it not be very easy for me to have loaded malware by loading this UL-K011-WW-3.1.23.191-user.zip (Not saying it is!! just wondering what the protection mechanism is)

For information: After loading the first image, (the one from ADB.rar) I tried OTA update, was told there was one available, but of course it failed as it checks for files that are not present. Subsequently OTA won't work although I notice the asus server uses a self signed SSL cert, I wonder if maybe I can do an MITM on it and get the transaction. I will take a look when I have a moment.

Unfortunately, I didn't think to catch the update file from /cache before it was deleted.

A further information and again a query, I didn't factory reset as I didn't want to loose certain data from /data. This didn't seem to affect the recovery process, I'm wondering why you recommend a factory reset/wipe?

Many thanks!!
[Android Q&A, Help & Troubleshooting] mariosaraylian:
kitsis: Unfortunately, without any access to unlocking the Bootloader, we cannot do ANYTHING beyond a simple Rooting and using Tethered versions of Recoveries like ClockworkMod.....

I bought this Tablet because the hardware specs are excellent, cameras etc. Its really a shame that ASUS does not want to offer any sort of update on it to any newer versions of Android, or offer any sort of bootloader unlocking or SDK development....
[Android Q&A, Help & Troubleshooting] coolbeans2016:
Asus's only downside - locked bootloaders

Exactly. I found this thread after purchasing my k011, which was stuck at the WW-3.1.23.150 firmware and was not pulling any OTA's! Thanks to this discussion and available downloads (.172 & accompanying OTA's to .189), it was very useable, and with root could use some apps I like to speed it up. When the .191 update came up on my tab back in February, (like 2.8mb) I posted about it on G+ Asus Memo Pad Owners group. Due to a request, tried to find the update but could not, after 2nd try it installed and uploaded the screenshot of the .191 firmware for another k011 owner who was not getting this update offered. His back & forth with Asus tech resulted in an Asus Webstorage download being offered of the full firmware (.191) being made available by an Asus tech!!!! Soon as I got it loaded on mine, tried out, I posted in here that link to show my appreciation for the dev's keeping this tablet useable (not only with updated firmwares but the ability to get it back up & running)! With this full .191 firmware the tablet can be brought up to latest firmware with just one install using CWM tethered rcovery, and it is an improvement on battery (charging/discharging), if nothing else.

Have a great day!!!

zach
[Android Q&A, Help & Troubleshooting] coolbeans2016:
data, cache, 5.1 & up dalvik as well

It can cause performance slowdowns, other bugs if not performed.
[Android Q&A, Help & Troubleshooting] Minh Nhân:
Why they install windows boot from sd card? Gpu intel hd availd driver
[Android Q&A, Help & Troubleshooting] ricforte:
Hi. Why do i get "no valid installer media" message and have no install from sd card option in my droidboot?

Thks
[Android Q&A, Help & Troubleshooting] coolbeans2016:
issues I'm aware of

The tethered recovery will only work with sd cards of 4gb and smaller. Pretty sure its 4gb, could be 6, but yeah, has to be small. I just put the firmware on internal, if you have room.

Post back if this fixes problem or not. Are you using the .191 I put link up to? Have not checked since putting the link up if its still available.

zach

bout to reload it myself today, get it all cleaned up again......
[Android Q&A, Help & Troubleshooting] ricforte:
Thks in advance. Will try it tonight and let you know. I'm using 2 or 4gb microSD but get the message all the time. Maybe it works in internal memory. Fingers crossed.
[Android Q&A, Help & Troubleshooting] coolbeans2016:
thoughts

did not think to ask, mention, anything in regards to instructions, or hints..... no dev here, but you have made sure your device is WW build? And is not the "Rockchip" chipset, right? These are the only two items I'm aware of that would make it a 'no-go'.....

Just thought to throw that out there, not aware of your experience in these matters, just there are two tablets with complete different chipsets, and this thread is for the North America build.....
[Android Q&A, Help & Troubleshooting] ricforte:
Well, as attachement i provide you a snapshot of the information that appears in droidboot. For the posts i've read the version i have is compatible. I can flash .img file from fastboot and i think i can solve my problem if i could get .img of system and boot as the ones you provide in ADB.rar

Is there any chance to get .img for the official firmware?

Thks.
[Android Q&A, Help & Troubleshooting] ricforte:
I followed this directions from remmylee's post, but i only could get to point 4. If only i could get my hands to a system.img and boot.img of the current updated firmware i would be very apreciated :)

1. https://cloud.mail.ru/public/2b47381cb37c/ADB.rar - This contains adb and fastboot if you don't already have them installed. This also contains the system image that we're going to use temporarily to get this thing restored.

2. Hook it up to your computer and load up Fastboot on the tablet (Volume+ and Power while booting. Let go of power after the logo shows up).

3. Flash the System image ( fastboot flash system system.img) followed by the boot image (fastboot flash boot boot.img)

4. Reboot.

5. https://www.androidfilehost.com/?fid=95857557620392052 - Next, we're going to use a temp version of CWM-Recovery to reinstall firmware. Enable USB debugging, run launcher.bat, type "ACCEPT" and choose T3.

6. You'll auto reboot into CWM-Recovery. Grab the official firmware from the Asus site and install the zip from SD. Once complete, you'll need to reroot the device most likely. If you have a SuperSU zip, install it after you've restored the system.

You're done. This also opens us up for just about anything. Go play with your system. As long as you don't mess up your boot loader, this should save you.
[Android Q&A, Help & Troubleshooting] coolbeans2016:
splain lucy

I will apologize in advance..... is this post directed at me?

You are using a K011 that is not North America firmware?

You need a system.img and boot.img from a NA device?

I could ask other questions, but if this is even close, can we start with these!?!?!?!?!

zach (natural blonde)

:cool:
[Android Q&A, Help & Troubleshooting] ricforte:
Answer to coolbeans2016

Yes. The post is for you. Sorry but i'm not very good with "reply", "quote", etc.

My K011 is from Germany. Prosieben version. I think that is not a problem as the tablet received the ROM mentioned above on point 1 and it worked fine.

The only problem is that i can't get to update with the right firmware.

The files provided in point 1 was just to recover the tablet from a wrong installation and seems that is only a "demo" firmware.

With that in mind i need a system.img and a boot.img from a WW device.

I provide you a snapshot that i took from my droidboot with the product code.

Not sure is this help.

Thks.
[Android Q&A, Help & Troubleshooting] coolbeans2016:
Okay, you are in luck, kinda, sorta.....maybe! I just happen, as mentioned, to be cleaning up, backing up all of this tablet, getting ready to clean install the .191 firmware probably for the last time. Other words, I will have an Asus Memo Pad 8 181c K011 with a clean install before root (for a short period of time)! I have never pulled a system.img or boot.img file before, so if you are ready, capable of giving me instructions as to how to accomplish this, you will be in possesion of what you need!

Please, its 1:20am here as of now, respond as quickly as you can, I will want to continue on reloading everything after the clean install.

zach

---------- Post added at 01:20 AM ---------- Previous post was at 01:18 AM ----------

how to pull a system.img of any kind off this device.............

type up instructions, will oblige you the files....

:cool: zach
[Android Q&A, Help & Troubleshooting] ricforte:
Ooops. That is the problem. I don't know how to do it.
[Android Q&A, Help & Troubleshooting] coolbeans2016:
nap (not a problem)

Thats cool.... I just have to go read a thread on here, get directions. Right now, 36 hours with no shut-eye, gotta go crash a bit. As soon as I have them pulled will request how you would like to receive them.

Adios

zach
[Android Q&A, Help & Troubleshooting] ricforte:
Ok thks a lot
[Android Q&A, Help & Troubleshooting] coolbeans2016:
rise n' shine...........

Okay, nice little nap. Thank you for the ADB/FASTBOOT. I did not have it on this laptop, new Dell, and seems to be working fine. The CWM Tethered Recovery from the OP is no longer working for me though...... :(

Guess Windows 10 nitched that one in the bud. The ADB/FASTBOOT though should let me do what your needing, under ADB commands it plainly states how to "pull" (copy) a file so let me go see if I can screw up this device real quick, lol! :silly:

brb
[Android Q&A, Help & Troubleshooting] coolbeans2016:
o'tay

Message me in here, PM me .... have boot.img & system.img. I will PM you the link after getting uploaded to cloud.
[Android Q&A, Help & Troubleshooting] coolbeans2016:
still working on it

I have found the .191 WW I posted is just an update, not complete firmware. I have gotten the tab load up through to .191 again and it is functioning really well. No hang times like it had when refreshing screen after closing something. I am still working on that system.img and boot.img pull, sorry........ getting back to it today. I need to know how to do this, the ones I thought I had are not right. Soon as I accomplish this will post in here.
[Android Q&A, Help & Troubleshooting] coolbeans2016:
mount points

lrwxrwxrwx root root 2016-07-27 19:24 ADF -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2016-07-27 19:24 APD -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2016-07-27 19:24 FWUP -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2016-07-27 19:24 cache -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2016-07-27 19:24 config -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2016-07-27 19:24 data -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2016-07-27 19:24 factory -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2016-07-27 19:24 misc -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2016-07-27 19:24 panic -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2016-07-27 19:24 reserved -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2016-07-27 19:24 system -> /dev/block/mmcblk0p10

This is where I'm at, as soon as I figure out the mount points, will be able to do the system.img/boot.img pulls

really has been frustrating, but learning alot I needed to as well.......

zach
[Android Q&A, Help & Troubleshooting] miniuser123:
KSM

In order to gain some ram, KSM (kernel same-page merging) can be turned on a rooted device. In terminal emulator type:

su
echo 1 > /sys/kernel/mm/ksm/run

After 10-15 minutes of intense usage about 150-200 MB ram is freed by KSM on my tablet. The total memory usage of system_server and systemui processes (the main memory wasters on this poor tablet) is down to about 90 MBs from 170 MBs. I don't know yet how persistent this gain will be, I only tested it for a few hours. After this the tablet can hold 2 Chrome tabs and Youtube in memory at the same time (wow!:))

The setting is not persistent over reboot!!

Memory gains can be checked by typing

su
dumpsys meminfo

Unfortunately zram (another memory saving method) cannot be turned on, because it was not compiled into the kernel. I compiled a kernel module, but it cannot be insmod-ed because the r*t*rded asus devs turned on module signiture verificaton.
[Android Q&A, Help & Troubleshooting] coolbeans2016:
Is this why when I'm trying ls -al /dev/block/platform/dw_mmec/by-name on mount points I get "Permission Denied"?

I noticed when browsing to dev/platform there is not any folder but "Intel". 1/2 of the os listings are missing under the tablet, other 1/2 are in this folder within this area.........

I'm def a newb, so..... may have not stated this in a way that is correct, that you understand, since I don't lol :p

---------- Post added at 12:42 PM ---------- Previous post was at 12:30 PM ----------

Is this why when I'm trying ls -al /dev/block/platform/dw_mmec/by-name on mount points I get "Permission Denied"?

I noticed when browsing to dev/platform there is not any folder but "Intel". 1/2 of the os listings are missing under the tablet, other 1/2 are in this folder within this area.........

I'm def a newb, so..... may have not stated this in a way that is correct, that you understand, since I don't lol :p

I am updated to the WW-" " " " " " " " .191, and have been trying to get a adb pull, or dd of the system.img & boot.img without ever having done this before. The amount of time/reading put in is alot, with no success so far........ any hints, info, point in the right direction would be greatly appreciated!

zach
[Android Q&A, Help & Troubleshooting] ricforte:
Problem solved

Hi. I've get in touch with the guys at Asus Repair Service from Spain and they were superb. They sent me all the files i need to get the tablet running sharp. And is a simple procedure. Just downloaded the software, usb debugging, connect to computer and execute a batch file and just wait. In the end voilá. All running good.

Thks anyway for the effort.

If you want i'll send you the link they provided.

Thks
[Android Q&A, Help & Troubleshooting] coolbeans2016:
:p:good:

Please, at your earliest convenience!!!!!!!!!!!

Grazie!!!!

zach
[Android Q&A, Help & Troubleshooting] coolbeans2016:
links

Could you please message me the links. I found a new command "du" and it definitely shows where this tablet is covered up with encryption. Permission denied all through the file system. I will be stuck with this tablet for awhile longer and trying to learn all I can about making my own flashable backups from a device system & any help is greatly appreciated!

zach
[Android Q&A, Help & Troubleshooting] klemen241:
dude, you are a life saver, i was gettting error all the time, untill i named folder user.zip ..... Thank you
[Android Q&A, Help & Troubleshooting] cdma2k:
Hi, could you send me the link? thanks!:)
[Android Q&A, Help & Troubleshooting] Firefighting_74:
Share files, please!
[Android Q&A, Help & Troubleshooting] cdma2k:
You are right about that the battery performance is much improved after upgrading to 191 and a factory reset, thx:)

Any good reason to root it?
[Android Q&A, Help & Troubleshooting] migge65:
I have the same tablet , Asus MeMo Pad 8 - Pro 7 Entertainment Pad

Which method did you use to root it?
[Android Q&A, Help & Troubleshooting] Firefighting_74:
http://xdaforums.com/memo-pad-7/development/1-16-2015-asus-memo-pad-me176cx-t3004526
[Android Q&A, Help & Troubleshooting] migge65:
Thanks, but are you sure?, this method seams to be for the memo pad 7 and I have the memo pad 8
[Android Q&A, Help & Troubleshooting] Firefighting_74:
Must work, tablets identical, except for the size of screen
[Android Q&A, Help & Troubleshooting] coolbeans2016:
a few

SD Maid PRO

Xposed

Greenify Pro

SD Maid Pro keeps any android device clean, no left behind files, and straightens out what Android never got around to.

Xposed, of course, you will need the sd card storage module, rotation force module so you can get landscape out of all apps,

greenify uses Xposed for its pro module, etc....

Greenify, when setup right with its Xposed module between this making sure all apps snooze without breaking links and sd maid pro allowing you to under all apps (system as well), and stop everything from starting up on boot, battery life just keeps going & going.

I seriously thought the battery was experiencing an end of life with performance about 6 months back until I got it loaded up and with root killed E-V-E-R-Y-T-H-I-N-G from starting on boot (except greenify, xposed, communication apps), and greenified everything including system apps. I can just press the power button to black the screen (prefer using the 'hibernat & lock' shortcut greenify can create), at 98%, 6-8 hours later I can pick it up to use, and it will still be at 96%-97%!!!

So, up to you about root, these are a couple of the main things I do......

:cool:

---------- Post added at 02:33 AM ---------- Previous post was at 02:25 AM ----------

http://xdaforums.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965

There is a part in this thread on going to a different firmware before returning to the WW build in order to downgrade and get back up in OTA's to the desired one (lollipop is out), and it is also a way to unbrick.........

Not sure if link provided is the same, just thought you would need to see this.

zach:cool:

ps if your own an 8, it is for the 7, but in reference, this cwm tethered recovery in this thread quit working for me, the same creator has another thread with a multi TWRP/CWM tethered recovery using the same options that did still boot mine. You can start with installing the .172 after a factory reset, booting into tethered getting in cwm (T3), and wiping it there as well before installing .172, then just do the ota's to .189, follow up with the .191 (.191 is not a full firmware like I previously thought) and you will get as good as this little tablet gets!!!!!!!

link for TWRP/CWM tethered recovery I had to switch to but still use CWM and options:

http://xdaforums.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
[Android Q&A, Help & Troubleshooting] cdma2k:
Thanks, the reason why I want to root is to raise the battery power efficiency as mentioned by you, my Lenovo Tab2 consumes 1% for 8 hours idle while Asus Memo 6% for 8 hours idle. I am excite when I hear your story and would like to reproduce it

I did the following

•	Download SuperSU.zip.

•	Copy SuperSU.zip to the root of SD card.

•	Enable USB debugging on tablet.

•	Run Launcher.bat.

•	Type ACCEPT.

•	Choose option T3.

•	Then Asus reboot automatically with the following options as shown in the attached pic

o	Reboot droidboot

o	Reboot

o	Recovery

o	Power off​

•	What is the next? which option I should choose? I picked "Recovery" last night, almost bricked Memo showing little green with "No Command"​