yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] pachulo:
Well, I might be missing something, because I'm running Lollipop and I'm not seeing the EFI partitions:

root@K017:/ # ls -l /dev/block/by-name/
lrwxrwxrwx root root 2018-01-27 18:49 ADF -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-01-27 18:49 cache -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-01-27 18:49 config -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-01-27 18:49 data -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-01-27 18:49 factory -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-01-27 18:49 firmware -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-01-27 18:49 gauge -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-01-27 18:49 panic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-01-27 18:49 reserved -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-01-27 18:49 system -> /dev/block/mmcblk0p9

The tablet is the K017 model and I have installed the latest ASUS update: LRX21V.WW_MeMO_Pad-12.8.1.41-20151112

and I have used this method to install root: https://xdaforums.com/memo-pad-7/general/asus-memo-7-me176cx-root-method-t3581213

Isn't my tablet compatible with this method?
[MeMO Pad 7 General] joo young yoon:
doesn't work.

I did as you told me to.

But it doesn't work.

If you type a command,

No such file or directory

come out

What is wrong?

Could you show me the pictures by phase?
[MeMO Pad 7 General] Ruben Craveiro:
of course its not.. this is for ME176C/CX or aka K013, K016 is a different model, and im not even sure if it even uses UEFI
[MeMO Pad 7 General] joo young yoon:
no work

Microsoft Windows [Version 10.0.16299.192]

(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>adb shell

shell@K013_1:/ $ su

v/block/by-name/ESP of=/path/to/unzipped/zip/stock_ESP.img <

dd: /path/to/unzipped/zip/stock_ESP.img: No such file or directory

dev/block/by-name/recovery of=/path/to/unzipped/zip/stock_recovery.img <

dd: /path/to/unzipped/zip/stock_recovery.img: No such file or directory

path/to/unzipped/zip/ESP.img of=/dev/block/by-name/ESP <

dd: /path/to/unzipped/zip/ESP.img: No such file or directory

path/to/unzipped/zip/recovery.img of=/dev/block/by-name/recovery <

dd: /path/to/unzipped/zip/recovery.img: No such file or directory

1|root@K013_1:/ #
[MeMO Pad 7 General] Ruben Craveiro:
You shouldnt have been doing anything to the tablet if you cant even see that you need to add the directory on the path and not just copy paste...
[MeMO Pad 7 General] joo young yoon:
Thank you for your answer. Please answer me once more

I am a beginner and don't know well.

I can see pictures or articles on the web.

Be just like

Please let me know which input I need to add.
[MeMO Pad 7 General] Ruben Craveiro:
the path for the file.. the directory you stored the file.. you dont just copy paste.. you need to chabge the path for something like C:/Users/Ruben/Reciveryfileinhere.img <-- this is just an example, you need to repalce the path with 'Your' path
[MeMO Pad 7 General] joo young yoon:
thank you

Thank you for your answer.

I saw your writing

I succeeded.

I didn't realize anything so simple.

Thank you very very very much
[MeMO Pad 7 General] gmgo:
TF103C will work with this bootloader ?

Hello,

I'm new here, I'm wondering if this unsecured bootloader will work on Asus TF103C (K010) that has similar hardware.

I have updated it to Lollipop, so I see ESP partition with bootx64.efi

root@K010:/ # ls -la /esp/EFI/BOOT/

-rwxrwxrwx root root 2057216 2015-12-25 19:04 bootx64.efi

root@K010:/ # ls -la /esp/EFI/Intel/

drwxrwxrwx root root 2015-12-25 19:04 Data

-rwxrwxrwx root root 2057216 2015-12-25 19:04 efilinux.efi

-rwxrwxrwx root root 72192 2015-12-25 19:04 warmdump.efi

I'm looking into this as there's no bootloader unlock app like other Asus devices like Zenfone 2.

Thanks

Regards
[MeMO Pad 7 General] lambdadroid:
This might work yes, looking at the kernel and the tablet it looks very similar to the ME176C. Is the temp recovery session working on your device? https://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (Trigger T4 works on the ME176C)

Note that the recovery image in this thread is likely NOT going to work properly on your tablet. It might boot, but you'll likely need a few kernel changes to have it working properly.

Also, could you send me the output of "dmesg" (the kernel log) in a root shell? Would be interesting to know how similar the devices really are...
[MeMO Pad 7 General] gmgo:
I don't see the option to attach a file when replying, I read I should reach 5 posts to have the option, I'm going to post some other stuff :)
[MeMO Pad 7 General] lambdadroid:
Alternatively, try something like https://pastebin.com and copy the link here.
[MeMO Pad 7 General] algarues:
Hello,

I am in lollipop and rooted.

I followed the instructions from the first post and the files are copied correctly into /dev/block/by-name/

However, when I reboot, I always get the Asus logo.

I also tried the volume down + power at startup, but i get the Asus recovery.

Any suggestions?

Should I mount rw rootfs before giving dd?

after reboot both EFP and recovery disappear from /dev/block/by-name

Thank you
[MeMO Pad 7 General] villo88:
Hello,

I've installed the recovery but the touch isn't responding.

Any ideas, please help!
[MeMO Pad 7 General] gmgo:
I finally got some time to look into, I did progresses, digging in existing info on this forum and the one on 4pda.ru .

I'm able to go into UEFI setup, and from there start a boot from an USB storage, it just goes in a black screen status, however I saw for the first time a Linux kernel booting :) , not the embedded android one.

This is working for me on TF103C, updated to Lollipop and rooted with the Zenfone apk.

adb shell

su

mount -t efivarfs efivarfs /sys/firmware/efi/efivars

printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c

reboot

I use an USB OTG hub where I connect the keyboard and the USB storage, I press ESC just after reboot, and I get the UEFI setup page, where I can change the settings and save, and also choose the USB boot device.

So currently I can play with these options, I will not need to look into changing boot loader for now.

I will try android-x86 lineage os and see what happens, who knows when, free time for these experiments is not much.

Regards

---------- Post added at 23:18 ---------- Previous post was at 23:13 ----------

Adding a correction, as printf is not found on my system, I used echo instead.
[MeMO Pad 7 General] lambdadroid:
Cool! Let me know if you manage to boot Android x86. If you do, it might be possible to port my LineageOS ROM to your device with a few minor changes. It works similar to Android x86, but is more optimized for Baytrail tablets and can be installed as regular ROM (without re-partitioning your internal storage etc).

Also, if you do manage to get another Linux distribution to boot, me176c-boot might be helpful to you since it allows dual-booting the preinstalled Android and another Linux distribution.
[MeMO Pad 7 General] gmgo:
Yes I tested system rescue CD, both older 4.5.4 and newer 5.2.2 and android-x86 lineageos 14.1, in all cases the issue is my USB OTG hub gets disconnected and powered off, so I lose the keyboard and storage connection.

LineageOS shows the animated graphic logo, but doesn't reach the point when the logo completes.

I'm searching for specific baytrail kernel options to resolve the usb disconnect issue, Lollipop kernel ones are these

<5>[ 0.000000] Linux version 3.10.20-x86_64_byt-00002-g61e2b17 (android@Capricornus) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Dec 25 18:53:37 CST 2015

<6>[ 0.000000] Command line: loglevel=0 androidboot.bootmedia=sdcard androidboot.hardware=tf103c watchdog.watchdog_thresh=60 androidboot.spid=xxxx:xxxx:xxxx:xxxx:xxxx:xxxx androidboot.serialno=01234567890123456789 oops=panic panic=40 vmalloc=172M debug_locks=0 bootboost=1 vga=current i915.modeset=1 drm.vblankoffdelay=1 acpi_backlight=vendor i915.mipi_panel_id=7 androidboot.mode=main

I notice I can now attach files, so I added dmesg_lollipop_boot.txt.bz2 with TF103C Lollipop kernel boot messages.
[MeMO Pad 7 General] gmgo:
I tested that temp recovery session, it starts with T4 but as you say it's only leading to a black screen status.

I actually used not the one prepared to be launched from Windows, but the equivalent to be launched from Linux.
[MeMO Pad 7 General] lambdadroid:
I see. The USB setup on these tablets is usually somewhat complicated and (afaik) not fully supported by the upstream kernel. Main problem is usually that they decided to hard-code certain I/O ports, instead of providing this information from the BIOS/ACPI resources.

With the ME176C I'm somewhat lucky: If the (powered!) USB OTG hub is connected on boot, it stays working. Otherwise OTG isn't working yet. I'm working on it, but it's still a bit of work.

I think you won't find any kernel option for this, either something is completely different for your device, or it just needs to be set to host mode to have USB working. There is no option for this directly in the kernel, though.

Thanks for the kernel log. With a few changes, I think my LineageOS ROM for the ME176C could work quite well on your device. This is what I've noticed so far:

Usually, battery/charger drivers are custom in these devices and take significant time to port. However, your device seems to use the same driver/battery combination as in the ME176C, so assuming they work I've already done this.

WiFi, USB, Bluetooth and Accelerometer look similar as well, so might be pretty easy to get them working.

Sound and Touchscreen look different, might be difficult or not (hard to tell before)

However, not going to lie, it would probably take quite a bit of time to get most things working.

If you want, you can do further tests and see how much you can working. I can send you a reduced build of my TWRP recovery port that may boot on your tablet. However, to boot it you'd already need an unlocked bootloader. Before you touch your bootloader, be sure you have access to Fastboot and DNX mode (on the ME176C this is triggered by pressing Volume Up + Volume Down + Power while booting; it then displays "Fastboot starting..." on the screen.
[MeMO Pad 7 General] gmgo:
Back on this after some time, as you said, powered hub helps, I connected a power supply and now it is stable, without specific kernel options, let's see how long the linux booted system can stay up, as instance if a complete mmcblk0 internal device dump can be completed.

While booting android-x86 cm-14.1 doesn't progress more than animated logo, 8.1 rc1 was reaching setup wizard step, so I'm looking into this one.

As a note, also Fedora 28 Xfce live can boot, while Gnome one hangs at desktop showing, it seems 1GB memory is the limit.

Actually android-x86 8.1 rc1 skipping setup wizard can boot, but it's very slow, likely doing lot of initial settings, hopefully it can be improved.
[MeMO Pad 7 General] lambdadroid:
Nice. The USB interface is rather slow on these tablets, which is probably the main reason why android-x86 is so slow. It should improve should you decide to replace your main Android installation at some point. (If you want to go ahead with this, my offer with the TWRP recovery build still stands...)
[MeMO Pad 7 General] gmgo:
Yes, thinking to USB slowness, as I noticed android-x86 was also searching for its partition on the external SD card, I added the 8.1 rc1 partition also there, so I booted from USB key, but it actually started using partition on external SD card, it seemed a little better, but still slow and lot of not responding processes notifications.

As the session with this 8.1 rc1 lasted like 3 hours, see attached screenshot TF103C_android-x86_8.1.rc1.jpg , I was expecting the battery to go low (the indicator shows as connected to power supply, no %) instead when rebooting to Lollipop I see basically the same charge as when I booted it with 8.1 rc1 .

I don't think it's the case the tablet really gets power from powered USB hub, this low battery usage may be apparent, or maybe the 8.1 rc1 system slowness is related to CPU set to very low working clock frequency, I'm going to start another session to check this, trying also to connect to network, hopefully the same USB to ethernet adapter which works on Lollipop will work also on 8.1 rc1 , as I don't think it supports TF103C wireless adapter.

I understand the best way is to go replacing the main android on internal storage, but I'm not familiar with the process, I'm more familiar with linux, then I'm trying to use external SD card for the purpose, leaving Lollipop unchanged.

It may happen I will just break also original Lollipop system at the end :) so I'll need to look into the re-flash process at that point.

Other TF103C_android-x86_8.1.rc1_upd.jpg screenshot is about initial android update 8.1 rc1 is doing, extra slowness about it.
[MeMO Pad 7 General] lambdadroid:
It's somewhat hard to tell what it is doing without charging driver. I once managed to drain my battery to absolutely zero so it didn't actually boot properly into the charger screen anymore. That was fun to fix. However, with the charger driver now working for me, I can actually see that it actually does charge a little bit from the powered USB hub. Maybe yours does the same.

Can you post a dmesg copy of Android-x86? I might be able to suggest something to get WiFi working.
[MeMO Pad 7 General] gmgo:
Here attached find dmesg.tf103c.andx86_8.1rc1.zip , I notice you need to capture it quickly as otherwise initial part gets lost as lot of messages are appending when the system is running, you see in there a 2nd USB storage sdb is connected, more than sda used to boot the system, which is a vfat partition mounted read write by the system, so good to dump dmesg to it.

So it seems the battery charger driver in this android-x86 8.1 rc1 is allowing charge from OTG usb port while it is used for data too, I tested also the USB to ethernet adapter and it worked as expected.
[MeMO Pad 7 General] lambdadroid:
Weird, it seems like the WiFi chip in your tablet is indeed not supported. (See the related brcmfmac lines)
[MeMO Pad 7 General] gmgo:
Well, it should be, but not configured properly by default

/lib/firmware/brcm/brcmfmac43340-sdio.txt

in 8.1 rc1, I read this should come from

/sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113

but I do not have this one on TF103C, however I can find on Lollipop

/etc/firmware/bcmdhd_aob.cal_4334x_b0

which seems the same info, so I'm going to merge and see what happens, I noticed the same problem also on Fedora 28, brcmfmac43340-sdio.txt needs to be added with proper info for the TF103C.
[MeMO Pad 7 General] lambdadroid:
Maybe it's only not supported on the Android kernel, because the kernel log you sent me says:

[ 8.613787] brcmfmac: brcmf_fw_map_chip_to_name: Unknown chipid 43341 [2]

But yeah, all that was necessary on my device to make WiFi work was to place the NVRAM file at the correct path. On the stock ROM of the ME176C it was at /system/etc/nvram.txt, but the file you posted above looks like the correct one too.
[MeMO Pad 7 General] gmgo:
I got WiFi working on Fedora 28, just using that nvram file renamed as expected, so I was able to install a minimal server system on the external 64GB sdcard, booting the netinstall image from USB storage, then adding the nvram file and reloading the brcmfmac module.

Than as the TF103C BIOS is not supporting booting from external sdcard, I needed another USB storage where to copy efi partition and other needed boot data only, so I can boot from this one and start the system on sdcard partition, then I can unmount the boot USB storage. As this is basically first time I setup an efi only system, it is not all correct for sure, however it works at the end.

Then on the fedora system I installed the android-x86 8.1 rc1 rpm package, so updating the USB storage to boot from with android needed kernel and initrd, I can boot also android-x86 in the same way as fedora.

At this point I tried to add the same nvram file to android-x86 system.sfs , but the error above is still the same, maybe there's some other configuration for brcmfmac module that is in Fedora 28 but not in android-x86, the support in the kernel should be in for all 4.x ones.

Looking at how the installed android-x86 works, it's visibly faster than the live image booted without installing, I use kernel parameters

intel_idle.max_cstate=1 as suggested for baytrail

SETUPWIZARD=0 this one to skip setup wizard
[MeMO Pad 7 General] lambdadroid:
It seems like it was added in Linux 4.10, that Android kernel is still on 4.9: https://github.com/torvalds/linux/commit/dc630dc5c753ccba97ce174f9c2894f802f9bd93
[MeMO Pad 7 General] gmgo:
Got it, maybe newer releases after rc1 will include 4.17, as it is mentioned as work in progress there.

In the meantime, I can improve the fedora install, I did it too much minimal :) it can connect to wired network when the adapter is used, it would be nice to have it connecting also to wifi.
[MeMO Pad 7 General] sgcko7:
For all of you guys this is working only for LP!!! Firtst download official firmware and upgrade to LP and then run all those commands.

For those looking for root have a look here >>> https://xdaforums.com/memo-pad-7/general/asus-memo-7-me176cx-root-method-t3581213

Happy flashing!
[MeMO Pad 7 General] victoria042982:
KitKat

How do I upgrade to Lollipop?
[MeMO Pad 7 General] Ruben Craveiro:
its not "his" bootloader its social design concept's bootloader
[MeMO Pad 7 General] social-design-concepts:
how about it's the communities bootloader, it's actually official intel source, all i did is fix the make files / build tools so i could actually build it from source, and a small change taken from android-ia kernelflinger to fix the combo key detection. [MENTION=5479482]jerbear294[/MENTION] is owed alot of credit for risking his device during debugging.
[MeMO Pad 7 General] Opensystem:
Worked like a charm, thanks
[MeMO Pad 7 General] spookmeister101:
Worked perfectly for me. Thanks a lot you guys :)
[MeMO Pad 7 General] Ruben Craveiro:
can you explain to me how to edit the kernel from asus support and add support for otg and charge and then compile? thanks
[MeMO Pad 7 General] social-design-concepts:
I'm looking into it as this is a feature I like myself, if my daughter goes to sleep sooner than later I'm going to finish overlaying the K011 / K013 kernel sources and get them up on git, I've been working on creating as close to a complete commit history as possible.
[MeMO Pad 7 General] Ruben Craveiro:
okay thanks
[MeMO Pad 7 General] Opensystem:
Hey I'd recommend a fix permissions afterwards, some errors I was getting got resolved that way
[MeMO Pad 7 General] jerbear294:
From what I know that error means the tablet rebooted and the UEFI doesn't know why.
[MeMO Pad 7 General] dog121:
Thanks got it sorted was a problem with the recovery. IMG whilst it was extracted ..twrp is working well now great work....
[MeMO Pad 7 General] dms76:
Another success story here with .36!
[MeMO Pad 7 General] Saarge:
Hi here's what i got:

So, what do i do now?
[MeMO Pad 7 General] Opensystem:
Have you tried putting the file on the internal drive and dd'ing it over?
[MeMO Pad 7 General] social-design-concepts:
You have to be rooted "$" "#"
[MeMO Pad 7 General] Saarge:
I am.

---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------

of course
[MeMO Pad 7 General] Mis012:
Your su binary didn't make you root - you have still user@android - unless you rewrote it instead of copy/paste and made a mistake? Other thing may be that ESP is mounted? Or try if=/dev/block/mmcblk0p3

Also if you're using stock dd not busybox one, it may function differently.
[MeMO Pad 7 General] Saarge:
Well basically i didn't know what terminal emulator to install (several choices) so which one should i use?
[MeMO Pad 7 General] Mis012:
The one made by Jack Palevich
[MeMO Pad 7 General] Saarge:
Testing the result.

intel logo checked.

recovery checked.

Successssss!
[MeMO Pad 7 General] AlexOnFire94:
Hello,

Is there any news about custom ROMs for the ME176C ? (CyanogenMod or AOSP) since TWRP should be able to boot custom ROMs now.

Thanks a lot
[MeMO Pad 7 General] jerbear294:
[MENTION=7057426]Penguineh[/MENTION] is working on AOSP 6.0.

[MENTION=4821597]social-design-concepts[/MENTION]'s work isn't just for this device, but he's working on CM12.1, CM13, and AOSP 6.0.
[MeMO Pad 7 General] AlexOnFire94:
Wow, that's promising! Do you know if they are close to releasing a working ROM? And any ideas, if it's gonna be Lollipop or Marhsmallow ROMs.
[MeMO Pad 7 General] jerbear294:
Not sure TBH.

CM12.1 is Lollipop 5.1, CM13 is Marshmallow, and AOSP 6.0 is Marshmallow.
[MeMO Pad 7 General] AlexOnFire94:
Well, thanks for the info.
[MeMO Pad 7 General] tizio04:
Is it possible to create modified ESP/recovery img for the ME70C model?
[MeMO Pad 7 General] jerbear294:
Only if the device is using a UEFI.
[MeMO Pad 7 General] tizio04:
mmm I can't find any information about UEFI on my device... Does this mean i am out of luck?
[MeMO Pad 7 General] jerbear294:
Yep, unfortunately.
[MeMO Pad 7 General] tizio04:
That's sad... Well thanks anyway! :good:
[MeMO Pad 7 General] jsdhornby:
Can you tell me how it got sorted? I have the same response when selecting "recovery mode."

You know what I did wrong? I left out the "stock_" before the ESP.ing and recovery.img in the first two lines of code.(not counting su as a line. So I think I ended up saving the stock files named as the new downloaded files and then just copied the stock ones back again. It's hard to describe but eventually I saved the stock files as stock_ESP etc. and installed the new files all over again. It worked beautifully. Thanks
[MeMO Pad 7 General] groovychap:
I've just installed the bootloader/recovery without any problems.
[MeMO Pad 7 General] Nexive:
I've istalled the insecure bootloader with this dd command and it works great :D

dd if=/path/to/unzipped/ESP.img of=/dev/block/by-name/ESP

Then I flashed the recovery.img with Flashify.

Both succesful!

Thank you guys!
[MeMO Pad 7 General] AlexOnFire94:
Is it possible to downgrade back to 4.4.2 using an older ROM from (https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/), after unlocking the bootloader & installing TWRP using this method?
[MeMO Pad 7 General] jerbear294:
Yes and no.

You can't use the "official" builds, but there was a leaked developer build of KitKat compatible with the UEFI introduced in Lollipop over on the main thread.
[MeMO Pad 7 General] jsdhornby:
So, with your help, jerbear, I've got TWRP installed. While waiting for a custom rom I'd like to install "xposed." But I read on htcmania (I'm not permitted to post the link-newbie with under 10 posts) that trying to install it can bootloop the me176c. I am running lollipop .36 on an me176c. Any recommendations?
[MeMO Pad 7 General] Nexive:
I've installed Xposed v80 sdk21 x86 with succes without a bootloop.

Flash the zip file in recovery (booting after that can take a while) and then install the Xposed installer apk. :)

Oh.. Always make a nandroid backup just in case. :p
[MeMO Pad 7 General] jerbear294:
I have Xposed working fine, odds are the person that said that flashed the wrong architecture or SDK type.
[MeMO Pad 7 General] jsdhornby:
Thanks to both of you. I've done the nandroid and will now install the xposed-v80-sdk21-x86.zip. Really appreciate it.
[MeMO Pad 7 General] urlyisis:
Just a few words....

I LOVE YOU GUYS!!!!!!
[MeMO Pad 7 General] russy23:
Unknown operand dd on installation, whats this mean
[MeMO Pad 7 General] cmdru1980:
Still can't find root for me176c

Thak you for this but, I can't I can't even find a way to root the ME176C. I've tried kINGO, ZENROOTFONE, SRSROOT, & INTEL ROOT. NOTHING WORKED.

ANY, suggestions?

tHANK yOU

-C

:good:
[MeMO Pad 7 General] M1chiel:
Root works with a tethered temporary recovery: http://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096
[MeMO Pad 7 General] russy23:
i keep getting no such file or directory all the time..i give up