yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] dexter20082001:
I can confirm that USB keyboards, mice, flash drives, and Ethernet adapters work. The adapter needs to be android/Linux compatible and it isn't support directly. It can be manually configure in a terminal or just use an app from the play store called Ethernet.

Sent from my Rooted Asus MeMo Pad 7 176CX
[MeMO Pad 7 General] salekojot:
But no usb 3g modems support. I use PPP widget and no success with Huawei e220.

Is this only for me or Gravitybox not working on our device?
[MeMO Pad 7 General] jerbear294:
You don't need OTG to use a PS3 controller. The app Sixaxis Controller will pair it via Bluetooth.
[MeMO Pad 7 General] jerbear294:
Gravitybox is intended for pure aosp ROMs and as such it will not work or be unpredictable on manufacturer-tweaked roms.
[MeMO Pad 7 General] dusty8:
Official adb driver and new kernel code is available on ASUS support page!
[MeMO Pad 7 General] plopingo:
PS3 controller working perfect in OTG ;)
[MeMO Pad 7 General] nogarder:
Its posible use knock on in our asus me176??
[MeMO Pad 7 General] salekojot:
It depends on kernel. You can buy case for our tablet with magnet cover. You can buy this on online store for 9$ with free delivery. I had one and it is very easy to use.

On my MeMO I disable lockscreen, no need for it.

When open front cover MeMO is started, when close front cover, it goes to sleep.
[MeMO Pad 7 General] nogarder:
I mean the doble tap , as lg G2 knock on.
[MeMO Pad 7 General] plopingo:
sixaxis controller driver stop all the time in bluetouth its why I have asked the question, no problem at all in OTG now :)

---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------

I will try on my side with "huawei e1756" and "option icon 225"

feedback soon
[MeMO Pad 7 General] social-design-concepts:
Sorry not full uefi iafw / osip-gpt unless Asus releases an update that makes the device full uefi there is really nothing that can be done not aware of any one that has found an unlock for these devices.
[MeMO Pad 7 General] Omicron2:
Aw hell :/ anyways, thanks for your time guys, guess I'm stuck with a expensive slow ass paperweight
[MeMO Pad 7 General] Penguineh:
I just worked up the courage to flash the unlocked bootloader (Edit: Insecure Bootloader :)), wow, everyone working on it, you guys have done an amazing job :)

Just curious, (I do have my boot order changed, so restoring from usb is no problem, I just wouldn't rely on it as my tablet is one of those with motherboard issues), I have 4 files generated from a simple AOSP build, system.img, ramdisk.img, userdata.img and cache.img... Would any of these overwrite the ESP or Recovery partition, effectively nuking the bootloader on my device? Don't I have to merge system.img and ramdisk.img to create boot.img which is then flashed to the system partition?
[MeMO Pad 7 General] social-design-concepts:
Well first i don't want people to get confused about what this is, by definition this isn't a bootloader unlock; i don't what anybody to think that some kind of master hackery had to be done or any type of real exploitation was needed to get around signature verification or anything like that. this is possible because the devices uefi firmware is unlocked (secure boot is disabled) the only thing we are really exploiting is the fact that most Antel Android device manufactures have implemented the bootloader in an insecure manor allowing it to be replaced as long as it is signed in the format the uefi expects. So really the proper term for this is an insecure bootloader.

I'm going to send [MENTION=5479482]jerbear294[/MENTION] another build and if it works as expected i'll forward to you as well, it's basically the same build but i cleaned up the source some more and simplified the combo key handling so that the changes made from the official intel version are as minimal as possible. I would like to have it ran a few day by only a couple of users to ensure that there are no issues that would prevent this from being used daily and then i'll push the source to github and post a build and installer for everyone else.
[MeMO Pad 7 General] phonephreak32:
Awesome!
[MeMO Pad 7 General] jerbear294:
[MENTION=7057426]Penguineh[/MENTION] how's the ROM coming? I can't wait to get off of ZenUI.
[MeMO Pad 7 General] Penguineh:
Me too! No, I really haven't done any "compiling" as such over the past day or two (I have been very busy), but I have been identifying more blobs. The required blobs certainly include the /system/vendor folder on the stock rom, plus some other random places.. This has been a great help actually:

https://github.com/thuutin/android_device_asus_a500cg (For the ASUS Zenfone 5)

Setting up a device build tree also has it's challenges!!
[MeMO Pad 7 General] spookmeister101:
Keep it up, you guys are awesome!
[MeMO Pad 7 General] Opensystem:
Just dropping in to say a big thanks to everyone working on the bootloader/roms for this device, obviously it's huge to the community :). Got mine a couple days ago and knowing about the locked bootloader I never expected more than root. Once these last few kinks are ironed out I suspect this will be the best tab for the money for a long while (paid $65 U.S.D. for mine used on Amazon, doesn't get much better than that!)

I'm super excited at the prospect of marshmallow custom roms. My only regret is having updated from stock 4.4.2 without making nandroids for y'all. Although pretty soon I doubt anyone will want them :)
[MeMO Pad 7 General] jerbear294:
Forewarning- Lollipop is a mess.

The first couple updates gradually slowed down. The initial Lollipop upgrade had a clock drift issue occasionally, not unlike the reported clock drift bug that seems to be in Android 6.0 on some devices.

The latest update fixed performance at the cost of horrendous battery drain. Not even Xposed has been able to fix it for me.

ZenUI doesn't do the tablet any favors either. The memory management is terrible, and even with a lot of bloatware removed I still constantly find apps that run in the background crashing. In fact that's the main reason I can't wait for the Marshmallow ROM. Seriously, applications running on phones with 512MB of RAM on Lollipop crash less than on this tablet.

Lollipop is nice enough for me to still use, and I've gotten used to turning off my tablet when I don't need it to circumvent the battery drain. You got your tablet at the right time; Those problems can be dealt with for a few weeks, it's worth it for some AOSP Marshmallow goodness.
[MeMO Pad 7 General] Opensystem:
Agreed, ram management (or lack thereof) is one of the key reasons for me wanting an alternative to stock. Battery drain, in my limited experience thus far, isn't horribly bad...but from reading through this forum, I understand that these models tend to run stronger at first and gradually settle into a slump after a couple weeks, so I'm taking everything with a grain of salt so far. I was debating holding off on root, but from what I can tell it seems fairly easy and safe using http://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096

Not to mention thanks to folks like yourself I doubt I'll need any more ota updates from Asus. Not like I need xposed haha. Thanks again for the work you're doing on the insecure bootloader, let me know if I can help in any way
[MeMO Pad 7 General] jerbear294:
Xposed works on the latest update, an update for Xposed was released that fixes it.

And yeah, the root's pretty easy to install. Not as easy as it was on KitKat (download a special version of RootZenfone, install it, click "root", wait a few seconds, reboot, done) but still easy enough. Just download that recovery, download SuperSU's recovery flashable zip, use the following settings: TWRP HDPI portrait, T4 (or CWM T4 if you prefer but TWRP's grown on me a lot), flash the zip file, done.

Battery drain will probably happen in a couple weeks. Mine's horrendous- 8 percent an hour is unacceptable.
[MeMO Pad 7 General] Mis012:
But no lollipop is no UEFI, and no UEFI means no freedom and no fun.
[MeMO Pad 7 General] phonephreak32:
I am still on 4.4.2. Do you need a backup?
[MeMO Pad 7 General] jerbear294:
True, the reason all of this is possible is because of the UEFI.
[MeMO Pad 7 General] Opensystem:
I appreciate it, but I do not at least at this time. Someone else may though, I posted that because I had noticed a few requests in previous pages :)

---------- Post added at 02:35 PM ---------- Previous post was at 02:11 PM ----------

Just an update for anyone hesitant about rooting: I can report following these instructions I'm now successfully rooted without difficulty of any kind. Super easy. Thank you, jerbear294

Edit: I'm a little hesitant to flash xposed, given the possible repercussions of doing it incorrectly. Can someone on the .33 lollipop tell me if this is the current correct procedure?

1. Flash xposed-v78-sdk23-x86.zip in twrp temp recovery

2. Run XposedInstaller_3.0_alpha4.apk

3. Profit??

Thanks guys, I love xda :)
[MeMO Pad 7 General] Ruben Craveiro:
After aosp buodl what about starting building a port of ressurection remix? Or cyanogenmod
[MeMO Pad 7 General] Opensystem:
Just made a backup and attempted to flash xposed-v78-sdk23-x86.zip via temp recovery, and the installation failed. Device booted up normally, so there's that at least. Can anyone confirm that this is in fact the correct .zip file? First hiccup I've encountered, so this thread is doing something right! Thanks in advance
[MeMO Pad 7 General] jerbear294:
Sdk23 is for Marshmallow, the one you want is sdk21 which is for 5.0.x
[MeMO Pad 7 General] Opensystem:
Lol duh, I gotta stop messing with this on no sleep. Thanks though, up and running perfectly now. Finally feels like an Android!!
[MeMO Pad 7 General] DudeyGeezer:
Ive been wading through google and threads on here, I have the latest lolipop installed, its a M176CX, Can I root, and if so, can someone PLEASE point me to the instructions. Cheers guys.
[MeMO Pad 7 General] Opensystem:
Just did this myself, was pretty easy. Download

http://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096

And the latest supersu .zip 2.46

https://download.chainfire.eu/696/supersu/

Install the temp recovery to your computer, connect the tablet, make sure you enable adb on it in developer mode. Once connected, run the exe in the .zip from the temp recovery. Choose: TWRP HDPI portrait, T4 (thanks jerbear294!). Your device will boot into twrp recovery. Now navigate to the supersu.zip on your tablet, and install, and you should be good to go :)

Again, thanks to jerbear294 for walking me through this. Glad to pay it forward

Side note: if you want xposed up and running, just go over the last couple pages in this thread. Directions are all there. Also you might want to take the opportunity to make a backup first using temp twrp when you first boot into recovery, just in case, although you probably won't need it it never hurts :). Good luck!
[MeMO Pad 7 General] DudeyGeezer:
thank you, your m176cx was definitely on the latest lollipop update from asus when you did this?
[MeMO Pad 7 General] phonephreak32:
How do you enable adb? Is that just enabling usb debugging?
[MeMO Pad 7 General] Opensystem:
Yes, yes it was, .33

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

Exactly
[MeMO Pad 7 General] DudeyGeezer:
Fan dabbie dozy!

Thanks dude :)
[MeMO Pad 7 General] DudeyGeezer:
Hi, thanks for all of your help, Is it best to backup via the temp recovery or will something like titanium backup work with this once rooted?
[MeMO Pad 7 General] Opensystem:
So far both have worked fine, depends on what kind of backup you're looking for I guess. I personally like to have one full twrp backup on my computer saved just in case I need to load it on an sd card and restore in the event something goes haywire. Temp recovery worked just like normal recovery..which is to say, great. Awesome developers on here
[MeMO Pad 7 General] jerbear294:
It's even better once you've got TWRP permanently installed on the thing. I'm not too worried about anything going south anymore since I don't even need a computer to access TWRP.

Seems basic, but it is such an accomplishment on this tablet.
[MeMO Pad 7 General] phonephreak32:
Would someone make a video of the backup and rooting process for a noob? :)
[MeMO Pad 7 General] Opensystem:
I have faith in you

---------- Post added at 10:33 PM ---------- Previous post was at 10:28 PM ----------

I unfortunately don't have the hardware to do so. Tbh, the instructions are really basic...if you're still uncomfortable with them, and you're afraid to cause problems for your device, I'd recommend not bothering. Most day to day users don't even need root, and without custom Rom access as of yet there's less of a pressing need than there otherwise would be.

If you're determined to take a leap of faith and no one can post a video, I would read the last maybe ten pages of this forum to familiarize yourself a bit more with comments on the process. I also made a separate post in general with a quick tutorial, but it's only slightly more in-depth than my earlier post here
[MeMO Pad 7 General] DudeyGeezer:
once rooted, is getting perma TWRP an easy process? Ive rooted and flashed custom roms etc on many devices but its been quite some time since and I think I'm probably just over thinking the process.

Im thinking once rooted there should be no reason that a perma custom recovery couldnt be flashed right?
[MeMO Pad 7 General] Ruben Craveiro:
For custom images to actually be installed in this case the recovery.img you need unlocked bootloader.. So if u have root u still need the ublocked bootloader to flash the img
[MeMO Pad 7 General] Ruben Craveiro:
I would like to have it. Thanks.
[MeMO Pad 7 General] daspex:
https://yadi.sk/d/63tXpfZzepTa6

this is a clean backup of the .201 kk system...thanks again to [MENTION=6013061]Mis012[/MENTION]
[MeMO Pad 7 General] Ruben Craveiro:
i can install all partitions except the boot partition it allways fails.. im on android 5.0 WW.33
[MeMO Pad 7 General] Opensystem:
I've read it's impossible to go backwards from lollipop to kitkat unless the bootloader is unlocked without a jtag, although I've personally never tried it. Might be waiting a little longer until that gets sorted unfortunately
[MeMO Pad 7 General] Ruben Craveiro:
nevermind the stuff i said before.. now im testing android x86 in 4.4.4 r3, kinda weird, and it uses almost no ram, its so smooth but no wifi :<
[MeMO Pad 7 General] ardicli2000:
That seems good news and looks promisin. When wifi is fixed, will everyone be able to install it??
[MeMO Pad 7 General] jerbear294:
Won't matter pretty soon, [MENTION=7057426]Penguineh[/MENTION] is working on an AOSP 6.0 ROM and [MENTION=4821597]social-design-concepts[/MENTION] briefly mentioned the idea of making a universal AOSP ROM for Baytrail devices
[MeMO Pad 7 General] Opensystem:
Just out of curiosity, what's you're idle ram usage? That's the one thing that bothers me right now, even after debloating and greenify, apps are constantly kicked from memory
[MeMO Pad 7 General] ardicli2000:
Looks even more promising :))
[MeMO Pad 7 General] profee:
You can't solve that issue with greenify on this thing, because memory menagement is awful. No matter how much bloat you remove, multitasking with memory heavy apps like chrome or games won't be possible untill we install AOSP.
[MeMO Pad 7 General] jerbear294:
Speaking of...

[MENTION=7057426]Penguineh[/MENTION] STATUS REPORT! :P

Also, is your ROM 6.0 or 6.0.1? 6.0.1 would be nice, it would basically turn this tablet into the Nexus 7 2014 that never was. The hardware is capable, but the software is weak.
[MeMO Pad 7 General] profee:
There are rumors thet google is working on nexus 7 2016. That would be sooo nice.
[MeMO Pad 7 General] Mis012:
This tablet is x86_64 with UEFI that is already better than Nexus.
[MeMO Pad 7 General] DudeyGeezer:
I can't quite work out from previous comments if the boot loader on this can be unlocked to install perma custom recovery, has someone actually done this on the latest .33? If so how?

Any custom Roms for this would be greatfully accepted :)
[MeMO Pad 7 General] jerbear294:
True, but right now it doesn't feel very Nexus-like with CrapUI.

[MENTION=4821597]social-design-concepts[/MENTION] is working on an insecure bootloader that can be installed and allows for permanent recoveries and custom ROMs. I'm testing it now; I successfully have permanent TWRP on my tablet.
[MeMO Pad 7 General] TalhaGirgen9:
What a great news! i cant wait for aosp roms. asus's zen ui is really sucks :p
[MeMO Pad 7 General] Uninen:
Anybody have any insight to the matter that will we ever get official 5.1.1 or 6.0/6.0.1?
[MeMO Pad 7 General] Opensystem:
Asus has a history of abandoning products when a newer version is out, but then again my girlfriend has the 170 model and we're both on android 5.0, so I imagine they'll roll out at least 5.1 in the next few months. Marshmallow is maybe pushing it.. but hopefully we'll have more devs move to this once the insecure boot loader is out. It really is a capable device, nothing else is close at this price point. I'm more optimistic that we'll be on custom developed 6.0 before we ever see it from Asus
[MeMO Pad 7 General] jerbear294:
Odds are, never. Not that it matters, we won't need official 5.1 or 6.0 soon enough.

If we do get something it'll most likely be 5.1 and not 6.0.
[MeMO Pad 7 General] DudeyGeezer:
Nice one.... Don't be shy... Lol..

That is truly fantastic news, just need someone to work on the hudl 2 now (that would make all my xmas's and birthdays)
[MeMO Pad 7 General] social-design-concepts:
The tethered recovery worked on that device? Wanna test the insecure bootloader / twrp recovery modifier?
[MeMO Pad 7 General] DudeyGeezer:
Pretty sure that for those that updated their hudl 2 to the latest lollipop that it's now locked down so tight that nothing can be done.

Wish I'd never updated it.

I'm happy to try anything though,

Now the hudl 2 file system is encrypted, there is no way to root it, they've also broken the previously open SD card access and locked that off too. Literally killing a device that has the exact same specs as the ME176CX but has 2GB of ram instead of 1! Oh and an 8.2" full HD screen!

:( sad times.
[MeMO Pad 7 General] Mis012:
I think they have the real secure boot enabled so that is the first problem. Sadly UEFI specs doesn't require secure-boot to be disable-able. But there are still things to try, like powered OTG f2 spamming or looking into efivars.
[MeMO Pad 7 General] jerbear294:
Try accessing fastboot mode. For us it's volume down + power. If neither that nor volume up + power works enable usb debugging and type

adb reboot fastboot

into your computer's command prompt or download a terminal emulator on your Hudl and run

reboot fastboot

Once you're in fastboot mode try http://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096. It's a tethered recovery that works on the majority of Intel Bay Trail devices. It appears Intel patched the exploit in Clover Trail, so stay away from Intel tablets in the future unless another exploit is found.

It will give you an option of ClockWorkMod or TWRP. Personally I recommend TWRP HDPI Portrait.

It's got four methods of "attack": - T1, T2, T3 and T4. Try all four of them, if none of them work nothing can be done. Most likely T4 will do it as it's more universal, but try all four just to be safe.

If it succeeds you should boot into TWRP. If that can be done, the insecure bootloader might work too, but the bootloader will only work if the Hudl 2 uses a UEFI and has disabled secure boot. Look for an ESP partition under the Backup menu of TWRP. If it's there, you have UEFI. If it's not there there's another way to check.

If you have UEFI the next step is to make sure secure boot is disabled. Shut down your tablet and get a USB OTG cable and a USB hub that uses external power (OTG power seems to be flaky on our tablet so we use a powered hub, even if it's not the case on the Hudl 2 it's good practice).

Plug the OTG cable into the tablet, the USB hub into the OTG cable, plug in the USB hub to the power source, then plug in a USB keyboard to the hub. After that, power on your tablet and mash F2 on the keyboard, and with luck you'll boot into a screen that looks like a computer BIOS.

Once there navigate the menus with the keyboard until you find an option called Secure Boot. If it's disabled, you should be good. Otherwise, try disabling it, and if it can't be disabled, you're out of luck.
[MeMO Pad 7 General] DudeyGeezer:
My kids have just gone to bed so I will have a play right now :)

---------- Post added at 11:59 PM ---------- Previous post was at 11:23 PM ----------

Encountered a few issues so far, not sure if it's drivers or something but with usb debugging on, adb devices showed as:

C:\adb>adb devices

List of devices attached

101214PE5039928 device

i used the "adb reboot fastboot" command and it rebooted into this:

[IMG="screen pic"]http://s16.postimg.org/wfhtjbz11/IMG_4530.jpg[/IMG]

loaded the installer but I get the "UNKNOWN / UNKNOWN" device status and information.

checked my drivers but im not sure what it should be showing as, it said android phone at first, ive changed drivers to:

android adb interface

android bootloader interface

android composite adb interface

and refreshed the tool each time but it still says UNKNOWN,

not sure what to do next, i found this thread and it seems people have tried this approach before:click me
[MeMO Pad 7 General] fosco_:
This is not an ME176cx
[MeMO Pad 7 General] DudeyGeezer:
that is correct, check a few posts back, someone is helping me with a HUDL 2 using the same method they've managed to get perma twrp recovery on a ME176CX
[MeMO Pad 7 General] social-design-concepts:
The hudl 2 requires the device I'd to be passed with the fastboot command let me do some digging I believe I have a version of the launcher that allows setting the device id.
[MeMO Pad 7 General] jerbear294:
A Christmas Day release would be fantastic! The only problem is if someone comes along trying to flash it without the bootloader installed, it's going to be a bad Christmas for them... When the ROM's first build is public I'd make a new topic for it, link it here, and mention in the OP that the insecure bootloader must be installed (and preferably permanent TWRP installed but I guess it's not necessarily mandatory)

Put those vendor/device trees up on GitHub once the ROM is publicly released. That would make porting other ROMs a breeze. I might attempt CM13 once it's more stable... speaking of, how crazy would it be if we somehow get this device officially supported for CM?

Does the ROM contain a custom kernel or is it stock so far? Also, is it 6.0 or 6.0.1? I don't think I got answered on that one.

In other news, the Zenfone 2 Laser just got a bootloader unlock... I would be really salty about that were it not for [MENTION=4821597]social-design-concepts[/MENTION]'s insecure bootloader; we don't necessarily need an official bootloader unlock at this point and I don't really care if we never get one.
[MeMO Pad 7 General] Opensystem:
That's some good news there!
[MeMO Pad 7 General] Penguineh:
It's Android 6.0! No, I figured that with a major version change I better figure out how to get a fresh kernel to compile. Here's hoping the insecure bootloader knows how to boot it!
[MeMO Pad 7 General] Opensystem:
No rush, but when someone has time would they please link me the insecure bootloader process? I looked back a little bit, but I wasn't able to find anything. Starting to sound more and more important :). Thanks guys