yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] social-design-concepts:
that sounds like your not actually extracting the compressed file but trying to run it from inside the compressed file.
[MeMO Pad 7 General] russy23:
Ive definately extracted the files, placed them in the root of the tablet, i just cant do it, maybe im not telling it to look in the right place, i do the backup bit ok, just not the installation
[MeMO Pad 7 General] jerbear294:
What command are you running?
[MeMO Pad 7 General] russy23:
my instructions are this, via pc..device regonised

dd if=/sdcard/ESP.img of=/dev/block/by-name/ESP

dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
[MeMO Pad 7 General] social-design-concepts:
sorry i confused you with the user who was having problems rooting their tab
[MeMO Pad 7 General] Mis012:
The /sdcard/ is not root of anything. I would also recommend using /dev/block/mmcblk0p3 for ESP and dev/block/mmcblk0p5 for recovery insteas of by-name
[MeMO Pad 7 General] russy23:
sorry but im still a noob, so if i placed the files on my tablet, no folder, i believe in the root of the device, what would the instructions be..cheers
[MeMO Pad 7 General] Mis012:
Use root browser to look around, it uses root, and you will see. The root is /

Did it say like no such file or directory: ESP.img or No such file or directory: /dev/..
[MeMO Pad 7 General] russy23:
root@K013_1:/ # dd if=/sdcard/ESP.img of=/dev/block/by-name/ESP

dd if=/sdcard/recovery.img of=/dev/block/by-name/recoverydd if=/sdcard/ESP.img of=/dev/block/by-name/ESP

dd: /sdcard/ESP.img: No such file or directory

Thats what i get, i cant move the files to the root, rw protected or something, but this is the right location for the files, also tried your recommended change to de v block bit but doesnt help, i must be doing something stupid and obvious but i just cant see it
[MeMO Pad 7 General] Mis012:
As you should already see, there is no ESP.img in /sdcard/ so it is somewhere else. Isn't it actually at /Removable/MicroSD ? /sdcard/ is a folder in /data/ partition just symlinked, so it is still internal storage.
[MeMO Pad 7 General] russy23:
thankyou so much, i have now done it, i placed the files on the removable sdcard and put in what you said, worked straight away, thankyou..

looking forward to a custom rom now
[MeMO Pad 7 General] Opensystem:
You and I both. Anyone else needing help rooting, I have a thread in general that explains how to get root and xposed running :)

Ps jerbear, you're amazing thanks for your hard work
[MeMO Pad 7 General] tertill:
I followed your steps.

Everything works except the recovery.. I get "Error" and a dead droid when trying to load the recovery.

Is it possible that the recovery isn't compatible with my tablet?

Info from the Fastboot screen:

PROCUCT_NAME - K013_1

VARIANT - K013

HW_VERSION - PR

BOOTLOADER VERSION - WW_K013-12.10.1.36-20151230

IFWI VERSION - 107.05

SERIAL NUMBER - 0123456789012345678

SECURE_BOOT - yes
[MeMO Pad 7 General] coolbeans2016:
Any word on bootloader with Asus Memo Pad 8 181c? Still KitKat 4.4.2 (WW-3.1.23.189) but just received an OTA that is 2.8mb.... could it be lollipop upgrade? its a dlpkgfile update....??

---------- Post added at 09:40 PM ---------- Previous post was at 09:29 PM ----------

After you get Xposed on, don't forget to check on module to fix memory leak!
[MeMO Pad 7 General] jerbear294:
2.8mb? Doubt it's Lollipop.

Rather, it's probably the "debug version" of KitKat that was leaked recently, but made public. (.203)

Unfortunately, because the ME181C doesn't use a UEFI, this method will not work.
[MeMO Pad 7 General] social-design-concepts:
[MENTION=5479482]jerbear294[/MENTION] [MENTION=2472806]vampirefo[/MENTION]

still alot of work left but . . .
[MeMO Pad 7 General] AlexOnFire94:
Great work sdc! What are the stuff that need more work? Do you think all tablet functionality will be kept with CyanogenMod? GPS, bluetooth etc.
[MeMO Pad 7 General] social-design-concepts:
I need to clean up my baytrail / intel_base device tree some more to start it's a mess there are somethings in it i don't think are needed and things that still have to be added, i'll work on this today so i can have a build to work off of that is more complete.

I hope to keep as much functionality as possible. Audio, Bluetooth, GPS and Camera don't work yet, WiFi has crashed a couple of times, but hopefully can have an alpha build for users to test by the weekend.
[MeMO Pad 7 General] jerbear294:
Personally, I'd be happy if you can just get audio working for the alpha. I rarely use bluetooth and camera, and I don't think I've ever used the GPS.
[MeMO Pad 7 General] Opensystem:
Agreed this is awesome ty so much!
[MeMO Pad 7 General] spookmeister101:
Fantastic work guys! You rule:)
[MeMO Pad 7 General] russy23:
+1 as long as theres sound and wifi to play games and youtube, id be as happy as a pig in sh.....you know
[MeMO Pad 7 General] social-design-concepts:
Well I'm sure you know already but you'll see it before it's actually available, easier to work with a few people at first.
[MeMO Pad 7 General] jerbear294:
Yeah, I figured that.
[MeMO Pad 7 General] AlexOnFire94:
Why can't I use official builds from Asus when using the unlocked bootloader? From what I understood, unlocked meant I could install any ROM. This might be a question for sdc since he made it.
[MeMO Pad 7 General] social-design-concepts:
Because the official KK build for your device wasn't full efi you could always modify the official build
[MeMO Pad 7 General] Mis012:
The actual problem is that before lollipop, the kernels were 32bit. [MENTION=4821597]social-design-concepts[/MENTION] said the bootloader may not work with 32-bit kernels. Also the kitkat rom was running on top of something as different as UEFI is, just not so familiar becouse of not being computer firmware standard. There might be some things relying on it which were needed for the system to start up. But having UEFI, there is no way I regret the update.
[MeMO Pad 7 General] thebulletfromhell:
This is why calling it an unlocked bootloader is a bad idea....

This is an unsigned bootloader, that won't check the kernel/recovery/etc...'s signature upon boot, allowing the installation of a permanent custom recovery, and later on custom ROM.

When upgrading from KitKat to Lollipop, the partition table is rewritten, and the bootloader (+ associated partitions) are written directly to offsets rather than abstract droiboot/fastboot/etc.. (which the bootloader translate to the offset its on), which mean the location of it changed between releases, which is why you can't just downgrade to KitKat. Downgrade is possible, as the warranty centre has a manufacturing flash tool package to do so, even when the device doesn't boot from a bricked bootloader flash. Now just hope some Russian/Chinese anon can get their hand on it
[MeMO Pad 7 General] Mis012:
What about me?

---------- Post added at 09:30 PM ---------- Previous post was at 09:19 PM ----------

You don't seem to get the UEFI thing? Only kernel+ramdisk and /system are needed to boot up. And the state without UEFI where the tablet was with kitkat was WITHOUT UEFI so no custom bootloader etc. And nobody wants that (I hope)

AND bricked bootloader means nothing with UEFI. I recommend you the link in my signature, it's nice.
[MeMO Pad 7 General] social-design-concepts:
Sorry didn't mean to exclude you, once i confirmed that there are not any issues with making it boot on the ME176 I'll be adding a couple of more people,

so i'm actually going to try a cm-13 build tonight, so we'll see.
[MeMO Pad 7 General] jerbear294:
CM13... I'm liking the sound of that.
[MeMO Pad 7 General] thebulletfromhell:
>ou don't seem to get the UEFI thing? Only kernel+ramdisk and /system are needed to boot up. And the state without UEFI where the tablet was with kitkat was WITHOUT UEFI so no custom bootloader etc. And nobody wants that (I hope)

AND bricked bootloader means nothing with UEFI. I recommend you the link in my signature, it's nice.

.....

What part of that post didn't you get? The original poster asked if the custom bootloader could let him downgrade, and I gave him an answer why. And considering the amount of craps you've put out over the course of the other thread, saying that is terribly ironic. Skimming article that people already skimmed on the detail does not make you an instant expert on the topic.

Everything run on top of DNX mode, which is the Intel SOC flash mode. UEFI, or the previous bootloader firmware used on KitKat simply boots upon that. That's why ASUS warranty could freely move between KitKat and Lollipop, because the MFT writes the package directly from DNX, ignoring whatever the hell is going on top. ASUS's Kitkat doesn't work after upgrading to Lollipop because it wasn't built to chainload from UEFI, and a downgrade is not possible because the firmware package does not have the offsets where the bootloader has to be flashed to.
[MeMO Pad 7 General] Mis012:
Please don't be rude. DNX flash mode is just a flash mode. It's Intel's way for updating UEFI. The UEFI is the firmware. It's not running on top of anything, the same as UEFI on laptop.
[MeMO Pad 7 General] russy23:
How did the cm13 build go
[MeMO Pad 7 General] idoetzchen:
Great work! Cant wait anymore for a custom rom

Yesterday i seen this thread and im so lucky!

Question: Is there an early rom available just to test, because i cant wait?
[MeMO Pad 7 General] jerbear294:
Not yet, unfortunately- [MENTION=4821597]social-design-concepts[/MENTION] hasn't even sent me the super-early build yet :p

I believe he said that once he's verified with me and a couple others that it boots properly, he'll open up the alpha to more people.
[MeMO Pad 7 General] social-design-concepts:
No one has a build yet, had a little less time than expected, going to binge debug / build tmrw night.
[MeMO Pad 7 General] tertill:
Can't wait myself. I have 3 of these for my kids.. and the big issue ist the space.. So with Android 6.0 I'll get the change to use the microsd as internal.

I'll deffo donate u some when u have a stable working build! :) That would save me from buying 3 new tablets...

Off topic: Can anyone explain why it needs 400 mb free space to download a 20 mb game? :P

(I've tried foldermount, Link2sd and App2sd on them.. It all gives different problems, some apps works and some apps wont even start..)
[MeMO Pad 7 General] social-design-concepts:
so do i continue debugging cm-12.1 this evening or do i make the leap and start fixing cm-13?
[MeMO Pad 7 General] AlexOnFire94:
Depends which one will need less patching to be stable and fully functional (Audio, GPS, etc). Any ideas?

Does CM13 boot right now?
[MeMO Pad 7 General] Mis012:
The fastest to get wifi+sound alpha, or any build I can test. What about TWRP 3.0 with self-compiled kernel? The 6.0 multiwindow seems promising, but not much practical use I think. I would also like some nice kernel feautures like framebuffer console or hid device - it's right there just not enabled :/
[MeMO Pad 7 General] jerbear294:
Depends, I think.

CM13 is mature enough that it's usable, but you've made more progress with 12.1, to the point that we're almost in alpha.

If you think it's worth the extra time tinkering with 13, then I'd do that. Otherwise I'd continue with 12.1
[MeMO Pad 7 General] tertill:
I vote for CM13, because it's android 6.0 and I use it on my phone and I really like it.
[MeMO Pad 7 General] :
But if one rom is 80% done and the other is 30%, it is a logical thing to finish one and then adapt the other. Besides, it is his time and his effort, if he feels like it he will do it, I don't like the idea of telling him what to do, after all he is the only one who's willing to make a rom.
[MeMO Pad 7 General] thebulletfromhell:
Just FYI, the combined storage function is literally dog****. Google didn't think about how even the fastest microSD card is only at best half at fast at the internal NAND.
[MeMO Pad 7 General] csamolot:
At this point I'd take anything over zenui and the memory leaks
[MeMO Pad 7 General] :
Get xposed with fixed memory leaks app, I have around 400 MB free ram every time I pick the device up, the only downside iz zenui's memory managment - it won't use more than 600MB of ram for some reason.

try with xposed obb2sd module, I found that forcing apps to install on external storage sometimes reboots the tablet, but on the internal it's fine, so I usually download to internal and move it to sd with link2sd and then move the obb manually, the only downside is that some games don't work even with moved obb like hearthstone, but some do like (I think) Real Racing 3.
[MeMO Pad 7 General] fosco_:
Unlocking process worked perfect in my .33 firmware, thank you guys.

Will try these CM builds as soon as they are ready :)
[MeMO Pad 7 General] social-design-concepts:
we'll resolved a couple of things last night on cm-12.1 but audio is still making me bang my head against the wall, so i have cm-13.0 building for fugu ( nexus player ) to fill up ccache so that rebuilds wont take so long when working on porting over to cm-13.0 figure if i'm going to have to bang my head against the wall it might as well be on android-6 off to run some errands.
[MeMO Pad 7 General] Opensystem:
Cm anything usable quickly gets my vote. 12.1 would be fine. Audio and WiFi and then blam zenui goes to the curb.

Make sure to let us know if you need testers/ anything at all
[MeMO Pad 7 General] jerbear294:
So you're scrapping 12.1 and moving onto 13?
[MeMO Pad 7 General] social-design-concepts:
No just needed to clear my head before i built cm-12.1 again, I just wanted to have a base time on how long a build from clobber takes on cm-13.0,

cm-12.1 cleared ccache 2 hours 45 minutes - after building with ccache 45 minutes

cm-13.0 cleared ccache 1 hour 54 minutes - after building with ccache 55 minutes

so a with fresh build i only need to wait a hour.

so now it's off to determine what proprietary blobs are actually common across all baytrail tablets so we can use the ones from a 5.1 device on cm-12.1 or from a 6.0 device on cm-13
[MeMO Pad 7 General] RandyJB:
Just a quick Thank You to you Jer and you Concepts for this!! I have just rooted my K013 and it stands ready to have a ROM installed. Curerntly backing up my boot files using the ADB shell, and just enjoying learning. You have a 47yy controls engineer ready to become a pupil again.
[MeMO Pad 7 General] tertill:
Well. I'm not telling him what to do. I did just answer his question with what I want the most for this tablet.. I thought he was asking us an open question.. Maybe I was wrong?

[MENTION=4821597]social-design-concepts[/MENTION] I appreciate your work on this.

Yeah.. I know. But some more loading time for the games is ok for my kids.. As long as they don't get the "Not enough space" error.. This tabletis really great except the storage.
[MeMO Pad 7 General] thebulletfromhell:
Its not just the loading speed, the whole shebang will lag hard. I've used two devices with this kind of config in the past (HTC Tytn 2, to free up the NAND space for a bigger /system partition, and Samsung Captivate which has the /data/ partition locked up due to a hardware bug, and needed a replacement on the sdcard), and its a visible performance drop. It will lag like a 600mhz 192mb device on ICS
[MeMO Pad 7 General] jerbear294:
So it'll have the same performance as ZenUI.

Got it.
[MeMO Pad 7 General] Opensystem:
Lulz
[MeMO Pad 7 General] russy23:
Might need to reinstall android..anything to test out before putting .36 back on
[MeMO Pad 7 General] JarrelStudios:
you cant have a folder with the name "recoverystuff" in the root directory

it would be /storage/sdcard0/recoverystuff

that would be on the internal storage of the tablet
[MeMO Pad 7 General] MojUk:
Thanks to all who have contributed to this! Carried out root then insecure bootloader last night on my Daughter's 176cx..ready for custom roms! Will chuck some beer funds once we have rom. Keep up the good fight!
[MeMO Pad 7 General] russy23:
I can't see us getting a custom Rom to be honest, devs start projects then get another device that's better and stop developing, it's not having a dig at anyone it's just the way it is..
[MeMO Pad 7 General] jerbear294:
That's why [MENTION=4821597]social-design-concepts[/MENTION] is doing his CM12.1/13 work. Like his TWRP, it's going to be universal for as many Intel tablets as he can make it compatible for.
[MeMO Pad 7 General] T_I:
Wow, great, I've been waiting for this a while. Maybe I'm crazy enough to try a cm12(.1) compile...
[MeMO Pad 7 General] :
Another one, also with .36.

Rooted, TWRP'd & bootloader replaced in under 10 minutes*, thanks to people like [MENTION=4821597]social-design-concepts[/MENTION] and his outstanding work for the community.

And an extra thanks to the "helpdesk", [MENTION=5479482]jerbear294[/MENTION] & [MENTION=5260988]Opensystem[/MENTION] for providing tools and lots of useful information. ;)

*I copy-pasted most of the Terminal path commands with Pushbullet, look what technology did to me, lazy and pathetic! ^^
[MeMO Pad 7 General] jerbear294:
"helpdesk" lol

That's what Recognized Contributors are for, right? :)
[MeMO Pad 7 General] cr0n_dist0rti0n:
Can't find "by-name" folder in /dev/block/

Am I missing something? But I cannot find either of these files:

/dev/block/by-name/ESP

/dev/block/by-name/recovery

There is no "by-name" folder in /dev/block/.

The device is rooted. I know the terminal pretty well with Linux, FreeBSD, and OSX but this is my first time messing around with an Android. I have:

Model: K013

Android Version: 4.4.2

Build number: WW-3.2.23.191
[MeMO Pad 7 General] jerbear294:
That's strange :S

This is probably obvious, but I'm trying to eliminate every factor: Does the file manager you're using have root access? I use Solid Explorer but there are plenty of free root browsers out there.
[MeMO Pad 7 General] social-design-concepts:
This devices didn't become uefi until android-5 so it can't use this bootloader.
[MeMO Pad 7 General] cr0n_dist0rti0n:
Well that is disappointing...

So is there a way to get my unit to android-5? If not where are some good resources on bootload hacking to get TWRP to work?

Thanks.

---------- Post added at 09:07 AM ---------- Previous post was at 08:58 AM ----------

Always good to check. Well initially I rooted Terminal Emulator and was working my way through that, which was super frustrating until ditched the stock keyboard which kept changing "ls" into "p.s." and "cd" into god knows what...

In addition to not finding it through rooted Terminal Emulator I used "ES File Explorer" and "Root Browser". I can get to /dev/block/ fine with everything but no "by-name".

I will check out "Solid Explorer". Thanks!
[MeMO Pad 7 General] lambdadroid:
[MENTION=5479482]jerbear294[/MENTION] [MENTION=4821597]social-design-concepts[/MENTION]

Great work! It's good to finally see a working version of a replaced bootloader. One obstacle removed towards a clean ROM as alternative for all these ASUS trash apps.

[MENTION=4821597]social-design-concepts[/MENTION]

Mind if I ask what the current state on the CM ROM is? I'd love to help testing it, I'd like to get rid of this ugly UI and ASUS apps as soon as possible. :)
[MeMO Pad 7 General] jerbear294:
He's now collaborating with Recognized Developer [MENTION=4329876]Olivier[/MENTION] who was also working on CM for Baytrail devices.

Last I checked he had finished his "generic" baytrail source that will make porting Baytrail devices over a breeze. Not too long now :)
[MeMO Pad 7 General] bryandroid98:
Worked perfectly with your instructions. Used ADB on the tablet. :D:D

Just waiting for CM ROM o something like that. :victory:
[MeMO Pad 7 General] trekminal:
I tried to follow these steps, but there is no "/dev/block/by-name/" directory in my rooted tablet (ME176CX). Is this method only valid for LP? :crying:
[MeMO Pad 7 General] jerbear294:
Yes, this only works on Lollipop.
[MeMO Pad 7 General] SyCoREAPER:
I have a question which is related but off-topic, can I or you me PM?
[MeMO Pad 7 General] Mis012:
you should probably start a thread with the question in Q&A
[MeMO Pad 7 General] SyCoREAPER:
And why would I do that when I want to talk to this specific developer directly?
[MeMO Pad 7 General] jerbear294:
PM if you want, but I'd prefer that you state the question here so others can view and learn from it.
[MeMO Pad 7 General] arif.celik56:
Do you think you share it?
[MeMO Pad 7 General] Koskee:
Digging up old(er) thread here, but what options do I have if (I was stupid) and was on LP version .17 when I flashed in the new bootloader? I'm unsure how to go about getting the device to .36, and since switching to LP from KK, my device seems to be overheating pretty hard on big file operations. Which I'm assuming was one of the improvements in the latter builds, but even if it wasn't, I would like to get to .36 somehow. The update instructions that accompanied the file (listed on the asus canada website) are pretty vague to begin with, which doesn't help.

I've tried dd'ing the stock ESP/recovery back where they came from, but then when I went to reboot I was suddenly cautioned that I had no OS installed (and had bad experiences with that particular warning before, on other devices) so I backpedalled to where I started with modified BL to double check what you guys figure might be best idea here? Read this thread and a couple others with no relevant info i could find...

Side note, my entire /system partition was unmountable following this, the only way i managed to restore it (lucky guess) was by attempting to flash the asus supplied firmware update (.** -> .36, LP to LP, the first one in the list) which i had downloaded from their site previously. It failed obviously, and appeared frozen for probably about 2-3 minutes saying it was "flashing," but eventually some assert in the update binary caused it to kick out with /system access intact. I have got this to work for me on two separate occasions, just in case anyone ends up in the same dilemma.

Thanks, Any help is much appreciated.
[MeMO Pad 7 General] jerbear294:
That's strange, flashing the stock ESP/recovery *should* be all you need to do. I don't think the ESP changed across updates.
[MeMO Pad 7 General] Koskee:
I'll admit that I'm not certain that it doesn't work, all I do know is that after I attempted it, TWRP was suddenly unable to mount /system, and was giving me warnings about rebooting because it figured I didn't have any OS installed. This spooked me a bit because the dd was reverting to stock recovery, which I figured would really limit my means of recovering should the system partition remain unmountable when I tried to reboot,since TWRP would no longer be installed. And that's where all of my backups and things were. Didn't want to lose everything so I chickened out and retreated in favour of consulting with someone before proceeding.

Apparently though, something happened which has me entirely surprised: I'm now on .36, even though flashing the Asus update failed. It took rebooting the device probably 8 times (the dumb optimizing app thing times out and turns off the device multiple times), and then I had to reflash supersu and xposed, but my software info page happily reports being .36, and some subtle changes seem to have been made. I mean, i'm glad but.. that somehow seemed way too easy. :eek:
[MeMO Pad 7 General] UntouchedWagons:
Am I in over my head?

How would I know if this will work with my tablet? It's a MemoPad 7 but it's a K01A running Android 4.4.2.

Thanks
[MeMO Pad 7 General] jerbear294:
Unfortunately this will not work on your K01A.

The unlock was made possible by the Android 5.0 update replacing the bootloader on the tablet with a UEFI- essentially, the 5.0+ K013 devices boot similar to most modern PC's. The idea behind the unlock exploit is that we can make the UEFI not load ASUS's default locked bootloader, but instead a generic unlocked one.

The K01A has no such mechanism, so it's not possible to trick the unlocked bootloader in to running.
[MeMO Pad 7 General] UntouchedWagons:
Aww that's really disappointing. I guess I'll need to keep looking for a new tablet.
[MeMO Pad 7 General] marcothien:
Root
[MeMO Pad 7 General] jerbear294:
OP updated with a TWRP 3.0 image!
[MeMO Pad 7 General] Firefighting_74:
Hello! Is there twrp 3.0 for our plane-table?