yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] social-design-concepts:
i personally recommend these adb drivers https://software.intel.com/android/articles/intel-usb-driver-for-android-devices , twrp backs up fat32 partitions as compressed zips not images totally forgot about that.

I know what the issue is : [MENTION=5479482]jerbear294[/MENTION] check efibootmgr -v it looks like your still using the method off adding the the insecure efilinux-usr.efi into the Intel/ folder and then adding the boot entry and then changing the boot order with efibootmgr which was the way i originally had you test. unfortunately that way isn't shareable because boot entries are persistent only on the device they were set.

I made the changes to the ESP.img this should be correct. View attachment ME176C.ESP.twrp.zip
[MeMO Pad 7 General] vampirefo:
Good morning

LMAO all the work was for nothing I guess, SDC uploaded a completely different esp.img try it and see if you get positive results.

Looks like difference between sdc version and andjerbear294 version is efilinux-user.efi has been added to sdc version, this account for size difference.
[MeMO Pad 7 General] Ruben Craveiro:
it works jts howsing the intel logo now
[MeMO Pad 7 General] vampirefo:
Yes, I am sure efilinux-user.efi made a difference, you also install twrp?
[MeMO Pad 7 General] Ruben Craveiro:
the recovery.img was right so i didnt needed to dd the "new one".
[MeMO Pad 7 General] jerbear294:
I didn't think of that until after I went to bed :S

Well, at least it works now.
[MeMO Pad 7 General] social-design-concepts:
It's [MENTION=5479482]jerbear294[/MENTION] image still i just made the needed changes, the esp.img was still configured from back in the testing days. Intel/efilinux-user.efi was actually the insecure bootloader i just moved it to BOOT/bootx64.efi so users wouldn't need to manually add / configure the boot order with efibootmgr. It's a simple derp and really my fault i should of been more available to him in assisting making it go live.
[MeMO Pad 7 General] vampirefo:
No big deal, it works now (verified by Ruben Craveiro) , that is the goal.
[MeMO Pad 7 General] jerbear294:
Updated my earlier post with [MENTION=4821597]social-design-concepts[/MENTION]'s fixed images.
[MeMO Pad 7 General] :
[MENTION=5479482]jerbear294[/MENTION] [MENTION=6427704]Ruben Craveiro[/MENTION] can we get tutorial for flashing it and backing the ESP properly? I've read 5 pages and I kinda get it but do not want to brick; Can you make a tutorial thread/post for flashing TWRP?
[MeMO Pad 7 General] Ruben Craveiro:
Tutorial for backing up ESP and Recovery and flash new recovery and ESP:

Backup Original ESP and Recovery

1- Load temp twrp

2- Press Backup, untoggle everything and toggle ESP and recovery and if u want to change the backups name you can also do it.

Flashing new ESP and recovery:

Without PC:

1- Install android terminal emulator

2- download ESP and Recovery .img files and place them in root of internal storage

3- Open android terminal emulator

4- write su, for shell supersu access, then do "dd if=/sdcard/ESP.img of=/dev/block/by-name/ESP and ESP partition will be flashed, now for the recovery partition you just need to make " dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery and then its flashed.
[MeMO Pad 7 General] :
[MENTION=6427704]Ruben Craveiro[/MENTION]

Do we backup it via TWRP since jerbear said it can't backup it correctly?
[MeMO Pad 7 General] social-design-concepts:
It backs up correctly just not as an image TWRP backs up fat32 partitions as zip files not images. I'm going to reach out to the twrp team to see what can to be done to make ESP/ partitions backup as raw images instead, it might be as simple as a flag set in fstab or actually needing to modify twrp source I hope to have it worked out by the time I go live with twrp 3 next week.
[MeMO Pad 7 General] MKKLR21:
I created my backup using dd in Android Terminal Emulator.

su

dd if=/dev/block/by-name/ESP of=/path/to/backup/folder/stock_ESP.img

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

reboot

dd if=/dev/block/by-name/recovery of=/path/to/backup/folder/stock_recovery.img

dd if=/path/to/image/folder/recovery.img of=/dev/block/by-name/recovery

Worked like a charm.
[MeMO Pad 7 General] jerbear294:
That's what you do, yep. Those instructions will flash and back up the recovery and ESP as an img. The reboot's not necessary, by the way.

EDIT: I've once again edited my earlier post. It now has clear DD instructions.
[MeMO Pad 7 General] :
A huge thanks to [MENTION=4821597]social-design-concepts[/MENTION] [MENTION=6427704]Ruben Craveiro[/MENTION] [MENTION=5479482]jerbear294[/MENTION] [MENTION=2472806]vampirefo[/MENTION] for the tutorial, the .img and all and all help about our tablet, you guys are awesome :D
[MeMO Pad 7 General] social-design-concepts:
It might be best now to simply start a new thread.
[MeMO Pad 7 General] jerbear294:
I'm planning to do that but haven't gotten around to it

---------- Post added at 01:20 PM ---------- Previous post was at 01:03 PM ----------

I've made a thread for the insecure bootloader and TWRP.

http://xdaforums.com/memo-pad-7/general/asus-me176c-cx-unlock-bootloader-t3315603
[MeMO Pad 7 General] russy23:
Is all this leading to a custom rom??
[MeMO Pad 7 General] jerbear294:
Yep, with the insecure bootloader we can now flash a custom ROM

[MENTION=7057426]Penguineh[/MENTION]'s had access to the insecure bootloader for a while, and has been attempting to get AOSP Marshmallow to run, but there hasn't been much success from what I know. [MENTION=4821597]social-design-concepts[/MENTION] is also working on Cyanogenmod 12.1 (I believe)

I'll take either of those over ZenUI any day.
[MeMO Pad 7 General] russy23:
Arhhh ok, i ccouldnt get my head round all the talk, hehe..hopefully a custom rom will be developed, i guess a tablet rom is easier than a phone rom??or not
[MeMO Pad 7 General] Ruben Craveiro:
its the same except the drivers you need for mobile signal...
[MeMO Pad 7 General] brackenhill_mob:
Really noob question but will this insecure bootloader work on other Intel units? I've used [MENTION=2472806]vampirefo[/MENTION] Linux temp recovery successfully on my Hudl2 and Asus Zenpad S8.0. Would be good if I can use this on the Asus! TIA
[MeMO Pad 7 General] russy23:
Just noticed something today..ultra power saving mode makes this really nippy
[MeMO Pad 7 General] Mis012:
It's efi application, so you need UEFI with secure boot disabled.
[MeMO Pad 7 General] social-design-concepts:
the device has to be 64bit full uefi in order to use the insecure bootloader i would be happy to work with you in testing and trying to address any issues if it's at all possible.
[MeMO Pad 7 General] brackenhill_mob:
Happy to help. How do I tell if my Asus (model P01M) has 64bit uefi?
[MeMO Pad 7 General] social-design-concepts:
CM-12.1 and Android-M
[MeMO Pad 7 General] jerbear294:
The tablet needs an ESP partition.

Do you see one when you hit Backup in TWRP? If so, you have a UEFI.
[MeMO Pad 7 General] Opensystem:
Any rom with ram management would be amazing, I'm pretty happy with this thing lately
[MeMO Pad 7 General] jerbear294:
It could be worse...

I got the "privilege" to briefly use my cousin's Allwinner A13 today. That was fun[emoji14]

Not even Hayai Launcher could make that thing perform. (totally recommend Hayai btw, it's small enough to stay in the RAM, and the only redraws it does are occasionally reloading icons)

The thing made ZenUI's memory management look godlike.
[MeMO Pad 7 General] :
I have been freezing and stopping services and one thing I can't understand, the tablet never went above 600 MB ram, never, not once, I tried to multitask and to open up something and hell forced it to stay in memory but it never stayed there. For instance open up firefox and xda labs and lets say a reddit app and firefox gets deleted from memory when I can see that the tablet has more than 200MB free/usable ram. From the advertised 1GB of ram to 862MB that the tablet reports to the usable 600MB(maybe); The memory management is non-existant.
[MeMO Pad 7 General] vampirefo:
The ares8 suffers from similar problems, my guess these tablets are all similar. The ares8 runs Android 5, has a memory leak, xposed helps some but tablet still has drag time.

The fix for this tablet was flashing 5.1 rom from and Intel device, I708Q, probably same rom would work on this tablet.

If so your problems would be gone, the volume on the rom is very low, no camera, but everything else works great on ares8.
[MeMO Pad 7 General] Opensystem:
Thanks for the advice, the volume for me is a selling point though. It's a surprisingly good media tab

We're starting I dare saw to look close to cm 12.1, I'll be waiting and hoping
[MeMO Pad 7 General] brackenhill_mob:
and there's my problem. TWRP loads but doesn't respond to any button press. I've tried several different builds and always get the same result. I rooted using cwm. Any idea how I get around this?
[MeMO Pad 7 General] vampirefo:
Load TWRP, then adb pull /etc

Now look in the files all can be opened via test editor and see if esp is listed.

If you have esp it will be listed.

Or just try in normal boot, not in twrp,

adb shell

ls /dev/block/by-name/
[MeMO Pad 7 General] jerbear294:
I might try it, if the volume is also low on here then I'll just pull out Viper4Android and rectify that.
[MeMO Pad 7 General] :
I deleted Iceservice.apk , MXMusic.apk, Audioservice.apk and the service of the audioservice apk - the sound is clear, its low but its clear, as for viper4android I couldn't get it to work for some reason.
[MeMO Pad 7 General] vampirefo:
I use head set, sound is clear through that, but through speaker I have to almost put tablet to my head to hear.

I use head set on most devices anyway, so doesn't matter to me, but just wanted people to know sound is low on rom, so they don't think something is wrong with their device
[MeMO Pad 7 General] social-design-concepts:
I was going to look at that devices rom but wasn't able to find a download for that devices firmware.
[MeMO Pad 7 General] vampirefo:
There isn't one, I was giving the complete firmware though.
[MeMO Pad 7 General] Opensystem:
Yeah I'm not too keen on the idea of flashing another devices firmware on this one, baytrail or no
[MeMO Pad 7 General] brackenhill_mob:
no esp partition listed in fstab. Bummer :(
[MeMO Pad 7 General] Opensystem:
Help me out guys, is a rom custom firmware designed specifically for a device or am I wrong and it's just some other device firmware that somehow just works on something else? Because I'm honestly confused and I could use clarification after this
[MeMO Pad 7 General] brackenhill_mob:
Tried both methods with same result. I won't be trying this bootloader! Pity as this Zenpad S 8.0 is a really nice tablet.

Thanks for your help and guidance [MENTION=2472806]vampirefo[/MENTION] - keep on rocking ;)
[MeMO Pad 7 General] jerbear294:
Well, you're half right.

While it is true that typically ROMs don't work cross-device, this case is special. If you look at less-expensive devices like Allwinner or Mediatek-powered devices, you'll see that they can all use the same ROM after some patches. This is similar.

Odds are [MENTION=4821597]social-design-concepts[/MENTION] is doing something similar- taking a base ROM and making some device-specific patches.
[MeMO Pad 7 General] Opensystem:
That makes sense, I probably should have just been clearer from the start. Thank you for helping to clear it up :)
[MeMO Pad 7 General] TMSurfer:
Is there a way to flash kitkat stock rom with the bootloader unlocked?

Have lolipop
[MeMO Pad 7 General] social-design-concepts:
Actually I'm working from source not patching another devices rom, my hope is to get the IRDA kernel source working so, we can use android-m blobs from an IRDA device but not intending to use the full ROM from another device.

I have 2 M builds I flop between working on AOSP and CM-13 and only working with CM-12.1 for lollipop. I flop between the three when I hit a snag to clear my train of thought.
[MeMO Pad 7 General] LenAsh:
Thread cleaned - keep it cordial and on-topic please folks.
[MeMO Pad 7 General] dog121:
Can someone tell me wtf this means EFI Linux error [ start_boot_logic:498] no valid target found. Fallbacking to MDS .... this is what i get when booting into the new recovery after about 2 mins..then tablet just reboots..can someone tell me what size esp and recovery .img size they have after extracting the zips..I have 33MB ESP and 18.75MB recovery the only thing I can think of is the files haven't extracted correctly...
[MeMO Pad 7 General] social-design-concepts:
What command are you issue the falling back to MOS error suggest an invalid boot target specified in the BCB, but fall back to MOS should boot to android.
[MeMO Pad 7 General] dog121:
Yep its booting back to the os no problems there.. but this message I'm getting when I go into recovery I get the Intel logo then it boots to the recovery page I select recovery and then the tablet says booting recovery then 2 mins later this message appears...what is the actual size of the recovery file .IMG of the new recovery
[MeMO Pad 7 General] Mis012:
The recovery has to be 16GB as that is the size of partition. Not that it won't be unsolvable but as for me the recovery works and didn't complain about being bigger than the partition.

P.S English is not my native language but shouldn't it be falling back rather than fallbacking? It sounds weird :/
[MeMO Pad 7 General] Ruben Craveiro:
i think there is but you need to change the zip to not flash esp partition or recovery, im gonnq try that now
[MeMO Pad 7 General] dog121:
Yep you're Right... But what I'm after is some one to tell me what was the size of the recovery file. IMG after it was extracted from the original zip file was I have extracted it twice now 16 mb&18.75mb this is the twrp recovery file...
[MeMO Pad 7 General] social-design-concepts:
Well because its a raw dd of the recovery partition it should be the same size of the recovery partition on the device. Sorry not near the download best answer I can give you.
[MeMO Pad 7 General] dog121:
Thanks I must have got a corrupted recovery file when I extracted the zip to Get the two .IMG files the first one came out at 18.75mb which gives me the error so I've extracted it again this time I've got 16mb so I'll try this one in terminal ..

Sorted the 16mb file worked :)

Thanks for all you're hard work on getting this recovery and the bootloader override half of this wouldn't be possible if it wasn't for u and jerbear 294
[MeMO Pad 7 General] MKKLR21:
I suggest using 7-zip.org. Never had a problem with that.
[MeMO Pad 7 General] dog121:
Yep I was doing it in house so was using ROM tool box.. not at a PC but sorted now it was defiantly while the file was extracted...
[MeMO Pad 7 General] Opensystem:
Yes, huge thanks to social design and jerbear :)
[MeMO Pad 7 General] HampTheToker:
If using your device to extract a zip, I suggest using Root Explorer. I've never had a problem with corrupted files while using Root Explorer.
[MeMO Pad 7 General] jerbear294:
Rom Toolbox IS Root Explorer :P

Rom Toolbox has a bunch of JRummy's tools packed into it.
[MeMO Pad 7 General] HampTheToker:
JRummy = Speed Software??

I thought they were different developers.
[MeMO Pad 7 General] Mis012:
you need boot partition and files from system partition.
[MeMO Pad 7 General] smsalom:
how so? those items are already included inside the zip, i mean, i'm not able to flash this because of the updated script, something is missing... TRWP rejects flashing it
[MeMO Pad 7 General] Mis012:
You may need to format system partition first
[MeMO Pad 7 General] smsalom:
i'll give a try

PD: It shoot me this error: E:Error executing updater binary in zip
[MeMO Pad 7 General] Ruben Craveiro:
i did the same and well it didnt work it gives error on updater script and cancels

---------- Post added at 06:15 PM ---------- Previous post was at 06:15 PM ----------

same to me...
[MeMO Pad 7 General] social-design-concepts:
the device is full uefi / gpt and not osip / gpt after updating to lollipop.

the invalidate_os("boot"); / restore_os("boot"); doesn't apply to full uefi devices try removing those lines.

and don't forget to use something like notepad++ if your on windows as notepad will screw up the line endings.
[MeMO Pad 7 General] Ruben Craveiro:
i was able to install a few times the 182 zip but couldnt boot (because of locked bootloader) i think im gonna see if i still got that file with the right script
[MeMO Pad 7 General] smsalom:
Nice, lets see then :good:
[MeMO Pad 7 General] social-design-concepts:
The old boot.img format might not be compatible and I can't recall if the bootloader supports mix mode ie ( 32bit kernel on 64bit uefi ) more than likely u'll have to make a custom boot.img with the lollipop kernel and modules and the reset of the ramdisk from kk
[MeMO Pad 7 General] Ruben Craveiro:
can u make that? i have no idea of how... EDIT: i deleted boot.img just to see if it would flash and changed updater script aswell and didnt flashed...
[MeMO Pad 7 General] thebulletfromhell:
I got my tab back from warranty with a .203 KitKat that they flashed down from lollipop while I was waiting (it also prevents the lollipop software update notification, as well as containing a bunch of debug tools). So unless there is some OEM Intel tool that bypass the bootloader and write straight to NAND, I'm guessing this might be a kitkat build on UEFI.
[MeMO Pad 7 General] Ruben Craveiro:
thats great, make a nandroid backup and share it with us :3
[MeMO Pad 7 General] social-design-concepts:
I'm curious about the debugging tools like to see the backup too.
[MeMO Pad 7 General] thebulletfromhell:
My upload speed is terrible, so I'll have to take my laptop to a public wifi sometime this week. Its mostly sensor debugging stuffs in Chinese, but I haven't had a poke around yet. The neither KitKat nor LP's button combo works though, KK's combo brought it into DNX mode instead.

EDIT:ADB reboot bootloader works. Its droidboot, so seems like we'll need a leak of the KitKat image and the flashing tools used.
[MeMO Pad 7 General] daspex:
Hi,

i thought this could be usefull for making a LP custom rom couse it's for x86 x64 PC install? http://getintopc.com/mobile/android/android-lollipop-5-1-x86-iso-free-download/

i tried to boot it with bochs emu but it don‘t booted because the kernel supports no cmov function bu i don‘t know if the issue meant the bochs kernel or the devices one.

on pc it works.
[MeMO Pad 7 General] dms76:
I had previously deleted system apps with .24 and knew I'd have troubles updating in the future. So I wanted to provide the steps I took to update .36 and unlock the boot loader.

Hopefully this might help someone having issues upgrading

1. Factory reset .24

2. using temp root, reinstalled .24 that had a modified updater script

3. downloaded the .36 file from http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip (Provide in post http://xdaforums.com/showpost.php?p=65318694&postcount=3790)

4. Rooted .36 with method found at http://www.asuszenfoneblog.com/2015/06/how-to-root-asus-zenfone-5-lollipop.html

5. Unlocked boot loader using method from http://xdaforums.com/memo-pad-7/general/asus-me176c-cx-unlock-bootloader-t3315603.

Credit goes to contributors in their respective posts
[MeMO Pad 7 General] Mis012:
Not an unlock, rather replacement
[MeMO Pad 7 General] ardicli2000:
You are not doing anything wrong. The problem is not with the script but with the binary. If you check the folder where the script file is located you will see that there is a binary file there. Binary should include some other codes to validate either integrity of lines or sthng related with bootloader etc. It's Asus binary. Coded and should be decoded first.

If you check the binary file of super su you will see that you can read and edit it. But it is not the same with asus binary.
[MeMO Pad 7 General] social-design-concepts:
that is why i always refer to it as an insecure bootloader . . .
[MeMO Pad 7 General] Ruben Craveiro:
would it work if i make my would flashable zip (without asus updater binary)? (using android kitchen my own meta-inf and working folder etc) im gonna try it
[MeMO Pad 7 General] Mis012:
[/COLOR]

I can't see why it would help, the problem is most likely caused by some change between commands used in binary between kitkat and lollipop.

EDIT: maybe, just try it ;)

But I still don't see why you cannot just flash the partitions over with twrp (either using that zip/img switch or with dd while nothing mounted) and see what happens? Theoreticaly ;)

If that damn RAM was bigger (it's 1024MB according to Aptio Setup Utility) I could just make a ramdisk with /system already inside, but unless you have a good Idea how to make the system really small.. I may try to let it mount system from sdcard ober weekend, with twrp I have a fast starting system with all I need to get the rid of errors (I doubt thre will be any, just stuck forever in grub at "booting xy" or bootanim, the second may be too nice to happen)
[MeMO Pad 7 General] Ruben Craveiro:
i tried multiple times, didnt work i also tried withtemp cwm didnt work either but gave me the error status (255) i dont know what to do now.
[MeMO Pad 7 General] ardicli2000:
From a developer: http://xdaforums.com/showpost.php?p=35429627&postcount=2

It is still binary problem...
[MeMO Pad 7 General] Ruben Craveiro:
i forgot the meta inf folder i downloaded had a arm updater binary ... ill retry again with .36 updater binary if doesnt work ill try with original .182
[MeMO Pad 7 General] Ruben Craveiro:
I found an easy way to install xposed/update

1= install xposed framework from the link below

2= open it

3= set the package to x86 and reboot to recovery (permanent or temp)

4= on recovery, flash the package located somewhere on a folder with the name xposed in internal storage

5= reboot and done

This xposed is easier to select package and install them and it has material design

Link: https://github.com/DVDAndroid/dvdan...ks/XposedInstaller_by_dvdandroid.apk?raw=true

Thread: http://xdaforums.com/xposed/material-design-xposed-installer-t3137758
[MeMO Pad 7 General] dms76:
True however I was going off the title of the original post
[MeMO Pad 7 General] jerbear294:
I called it an "unlock" in that post to avoid confusion, since it functions exactly like an unlocked bootloader.

Most people trying to unlock this tablet wouldn't look up "replace with insecure bootloader", they'd look up "unlock bootloader"
[MeMO Pad 7 General] Ruben Craveiro:
its still hard cuz it only shows unlock petitions and not the thread you made... and also i wonder why droidboot still says secure boot is on
[MeMO Pad 7 General] jerbear294:
Thanks Google, appreciate it. :L

Seriously why isn't that up there yet
[MeMO Pad 7 General] Ruben Craveiro:
i hope someone comes up with an idea to downgrade while we wait for custom rom...
[MeMO Pad 7 General] Mis012:
It looks for some efivar if I remember well
[MeMO Pad 7 General] :
I got some backups - 3 to be exact, .33 rooted with no xposed, .33 rooted with xposed, and .36 with xposed. Would you like me to upload? But you have to tell me where are the databases stored and app data and everything, I kinda don't want everyone to have "my tablet", just the system :)
[MeMO Pad 7 General] smsalom:
I found a lite & clean version of .36 FW without Asus bloatware at 4pda.ru, it does keep custom bootloader and recovery

https://cloud.mail.ru/public/EfuY/81Nk2HGTB

Credits goes to nfs911 from 4pda.ru
[MeMO Pad 7 General] ardicli2000:
One way could be restoring a kk system and boot lmage backup. I don't know if kk will work with uefi....
[MeMO Pad 7 General] Ruben Craveiro:
just backup system partition

---------- Post added at 02:51 PM ---------- Previous post was at 02:49 PM ----------

the problem is the boot.img sdc said it was problably going to need to be changed because the kk boot.img runs on 32bit and this device is now on 64.bit, im gonna try to do that cuz i already know how to unpack/repack kernel

---------- Post added at 02:56 PM ---------- Previous post was at 02:51 PM ----------

i tried flashing boot.img of kk it didnt boot