yashsingh1/xdaforums huggingface dataset:
[Android General] nvrpayretail:
Welcome back [MENTION=803240]gbkelly[/MENTION]. Glad you've returned.

I found the same issue with not recognizing the zip file in the root directory but had no luck figuring out why. I've since switched to using fastboot and it has worked like a champ. Absolutely no problems. Perhaps you can run a small windows partition just to be able to use fastboot - at least until a solution can be found for the not recognizing zip file in root directory issue.

On another note, [MENTION=3679859]jostrus[/MENTION] did a great job of creating a rooted 5.0.21 system for us but it's the mega download of 800 or so meg. I've been trying to create the small root zip but have hit a stone wall. Although all appears to be good with it, it always fails to load. I suspect it might be a signing issue but have tried a couple of different methods with no luck. Can you tell me what you used to sign the previous root zips?

Thanks...
[Android General] gbkelley:
[MENTION=2634745]mpgrimes[/MENTION]: no worries, mate, fastboot using [MENTION=3679859]jostrus[/MENTION] works fine even though earlier posts recommended against it. I sit corrected...:eek:

UPDATE: After looking over [MENTION=3679859]jostrus[/MENTION] it seems that fastboot for his image is OK. Since nothing I tried for 6 hours on 4.7.3 to get the system to recognize the zip file upgrade worked, I did a full system reset (data wipe) since I had a good backup anyway. That didn't help. So, I did the OTA upgrade to 5.14 and that worked. Then, I folowed [MENTION=3679859]jostrus[/MENTION] procedure to create image file and fastboot. One thing I would change in his instructions is to run his shell file as root (sudo) as most Linux users don't have root privaleges to create the /system temp mount to create the image file. Once I ran using sudo everything worked and I had an image file to fastboot.

Even though I'm now on Kubuntu, I did install VNware Player so I could run Intuit Quicken and Quickbooks (my personal and business financial apps). I was able to run fastboot in this virtual machine and even though it gave a bogus result from 'fastboot devices' (1111111) it did run fastboot flash system <filename> just fine.

I am now rooted at 5.0.21 and after doing a restore with ASUS Backup (yes it backs up apps and data even without root!) I'm now back to where I was at 4.7.3 with all my apps and settings running.

Thanks to everyone who has contributed to this thread over the past year since [MENTION=4177701]perpe[/MENTION] and I started this whole 'root' thing for the MemoPad. Hope we can get our own space here at XDA since this thread is WAAAYYY too long to sort through.

The ASUS MemoPad is worth our continued efforts as it beats an iPad up like a schoolyard bully pounding a cross-eyed nerd (yeah not politically correct but neither am I). :laugh:
[Android General] mpgrimes:
When I updated to . 21 I did a complete wipe first fastboot - w. then fastboot erase system. Then using fastboot I installed the factory image for. 21. Then rebooted back to fastboot. Downgraded to 473 bootloader and recovery then installed the rooted 21 system image with fastboot. Worked great. Then copied my titanium backup folder from pc back to tablet and restored
[Android General] jostrus:
[MENTION=5592485]gbkelley[/MENTION]: I forgot to add mention that the script should be run as root or with sudo. Thanks for pointing that out. I updated the post and changed the command to be sudo bash... with a reminder to run as root if using a distro without sudo. I make the assumption if someone is doing a manual build using all the commands that they'd be doing it as root as running them all as sudo would be a pain.

[MENTION=4771287]nvrpayretail[/MENTION]: Thanks. I've been playing around still trying to make a zip myself. Ultimately I'd rather just make something like chainfire's root's for other devices where it has a kernel and ramdisk merged together as a bootable image. For example on my Nexus 5 I can just just do a fastboot boot CF-auto_root.img and it boots up, installs root files, then reboots normal. Unfortunately the fastboot loader for the Asus ME302C doesn't support the boot command. But that doesn't mean if we figure out a way to combine a kernel and a ramdisk we can't just install it as a recovery then boot it, then reinstall the original recovery back.

I just haven't been able to find any details on how to make the boot images compatible with the ME302C. The standard mkbootimg doesn't seem to work and the tricks used for the Asus transformer prime don't work. So I'm at a loss at this point. If anyone has helpful information please do share.

This method has the benefit of not requiring an update for every rom upgrade. So long as you don't need new binaries for root you can just keep using the same root image to do it over and over.
[Android General] gbkelley:
nvrpay: Since we have moved on with new rooting methods, I removed my working folder and can't remember the signing app I used. You can send [MENTION=4177701]perpe[/MENTION] a message and she can tell you what app she uses to sign the zip file. I know you have to use tehe test keys when generating.
[Android General] nvrpayretail:
Yeah, I've been in touch with [MENTION=4177701]perpe[/MENTION]. She provided some input regarding the directions to create the zip but I haven't heard anything back from her in awhile wrt the signing issue. Maybe she's on holiday.
[Android General] nvrpayretail:
[MENTION=803240]GBK[/MENTION]elly: [MENTION=4177701]perpe[/MENTION] was finally able to get back to me. She found one error that I made creating the zip so hopefully that will fix the problem. She also provided the signing app and test keys she uses so if Zipsigner doesn't work I'll try hers and hopefully get this resolved once and for all. I'll post my results.

[MENTION=3679859]jostrus[/MENTION]: [MENTION=4177701]perpe[/MENTION] also suggested a solution for a generic rooting tool. She hasn't tested it and I haven't had time to look into it yet, but if you have time you can try searching for zenfone root apk. This is a root app for the new Asus Zenfones and the new x86 based MeMO Pads. Definitely seems to be worth a shot.

Kudos and many, many thanks to [MENTION=4177701]perpe[/MENTION].
[Android General] mpgrimes:
Zenfone is easy to find. I'll try it out when I get a chance unless someone beats me to it
[Android General] jostrus:
I found the aforementioned zenfone root apk. 3 versions actually. 1 on Google Drive which blatantly stated it had a virus! So yeah I didn't get that one. Another on Drive and then a 3rd labeled as 1.2r (found 2 copies on different sources of this one). A quick browse of the apk contents makes me think it runs some sort of compiled binary to hack root. Probably to exploit some bug in the kernel. I'm only making an assumption as I haven't decompiled the apk. Doing so to review the smali or java code can be rather time consuming and I don't have much to spend right now. At quick glance there are some shell scripts which mount mmcblk0p9 to /system. On the ME302C the /system is mmcblk0p8. Running this apk on the ME302C would be very dangerous without first decompiling and reviewing all the scripts to make sure they're written properly.

I would be interested in the process for making the update zip. My attempts have all been to take one of the previous ones: tried 5.0.12-faked 5011, 5.0.17-faked 5016, and 5.0.20-faked 5019. Starting with those bases

Deleted the META-INF/* leaving the com folder and sub contents.

modify META-INF/com/android/metadata to more appropriately identify as an "update" to the current running rom.

update META-INF/com/google/android with current binaries from the Asus Full rom OTA zip (the 800mb one)

copy build.prop from Asus full rom OTA zip to system/build.prop and system/build-1.prop

edit system/build.prop to match changes in META-INF/com/android/metadata

re-zip using normal compression with winrar (my zip app of choice)

use zipsigner with "testkeys" option not "auto-testkeys" (tried both with failure)

place zip on microSD card

eject and re-insert microSD then try to update.

FAIL miserably.

Does that sound about right? If you've got any alternative suggestions or what me to pop quick tests of something here let me know.

---------- Post added at 05:52 PM ---------- Previous post was at 05:41 PM ----------

Ok after some more brief looking there is even more things that make me cringe at the idea of running the apk on the tablet.

The internal scripts mount a path /APD from mmcblk0p7. We don't have a /APD on the ME302C. mmcblk0p7 is unmounted.

also mounts /ADF from mmcblk0p8. mmcblk0p8 is our /system on ME302C

as previously mentionted the scripts mount mmcblk0p9 as /system. mmcblk0p9 is our data partition

I'm not really sure I want to continue looking at this any further.
[Android General] caniswesley:
RIP Asus 302C

Sadly, my 302C died on me today. One minute it was working just fine, and then the screen froze. I powered it off, and could not get it to respond again. I let it charge a few hours, with no success. I tried to boot into download mode or recovery, with no success. Finally, in desperation I removed the back and unplugged the battery. Re-plugged the battery and still could get no response. I searched and found my receipt. Sadly my warranty has passed... so I think I'm out of luck. It's been fun. Now I guess I will just have to suffer without a beautiful 10" Android tablet :'(. Thanks to everyone in this post while it lasted. Best of luck with our beloved FHD 10.
[Android General] jostrus:
So sorry to hear about that. Same thing happened to my Galaxy s3 a few months back. Was cheaper and easier to replace it than fix. Got me a nexus 5. I would say that you could pick up a nexus 10 tablet or even some other 10 that aren't too expensive as a replacement.
[Android General] nvrpayretail:
I've got good news and bad news.

Bad news first: I finally got my update zip signed correctly and got it to apply. However, this put my memo pad into a really ugly reboot. So I've still got a way to go before I can create my own update file.

Good news: [MENTION=4177701]perpe[/MENTION] graciously took pity on me and created a root update zip for us. All credit and apprecitation goes to her.

As always, no warranty is given or implied. Use at your own risk:

http://www.4shared.com/zip/J0wCvvhkce/US_ME302C-V5022-0-ota-user.html

As a reminder, to apply this root file:

1. Install ota 5.0.21 by your preferred method

2. Boot into bootloader

3. fastboot flash update US_ME302C-V5.0.22-0-ota-user.zip

4. Enjoy
[Android General] perpe:
[MENTION=5242387]caniswesley[/MENTION]

Do you use a Windows or a Linux PC?

The Memo Pad FHD charges with booted recovery. You can connect it to your PC and try to boot it with "adb reboot". On Windows you need special drivers for this (I can upload them, if needed), on Linux you have to start ADB with root rights.

This could work, if it shows the battery symbol when it is connected with PC/charger.
[Android General] caniswesley:
Thank you, [MENTION=4177701]perpe[/MENTION], for your reply. You've always been amazing member of the xda community and the ASUS 302 C development. Unfortunately there's not even a charge icon showing up when the power is completely off. The device is, from my rather thorough examination, completely dead. No idea what happened. There were no signs of burnout. I tried ADB and fastboot, as well as finding any other signs of connection to a computer (I have both Linux and Windows machines at my disposal). All I can say is that I really appreciate all that you and everyone else in this thread has done over the course of the time I've owned this device. I shall miss it, and the development of the 302C -- but I have a tendency not to ever re-purchase the same item twice. So, hopefully I'll have the honor of interacting with you at a later time on another device. :)
[Android General] perpe:
I quite agree with you. The touchscreen of my Nexus 7 (1. gen) died last month. Just after the warranty. It's a shame with these ASUS devices. ASUS shipped a lot of MeMO PAD FHD with faulty memory chips. My tablet is a replacement, sent back the first one.

Development for this device is also very hard. The boot and recovery images are signed and we can't flash own images. I'm working on CyanogenMod 11. Maybe I will release a preview in the next weeks.

Now, most of the work is done and I'm thinking about buying a Dell Venue x86 based Android Tablet. Dell provides development firmware, this means one can flash an own boot and recovery image (but lose the warrenty). Would be nice to have one, just only for ROM porting. Sadly, only Dell Venue 7 is avaible in Germany. I will wait for the new announced super slim Dell Venue 8 7000. Maybe I can grab one.

Many thanks for your compliments and I hope a new tablets brings you more joy.
[Android General] mhaaland:
Found this is anyone still needs it.

patchroot_for_v5.0.21_us.zip

http*://cloud.mail.ru/public/db1749885080/Asus%20ME302C/Firmwares/_Alternative/

*=s
[Android General] enriquejones666:
So, I'm curious. Were you able to compare perpe's zip with your's and figure out what you were doing wrong?
[Android General] nvrpayretail:
Got sidetracked and haven't gotten to it yet. Will be happy to post when I have some news.
[Android General] fhmail:
Strange Error on Update

Hi guys. I have read multiple times through the forum but cannot solve this error I'm getting when trying to flash. "E:zib memory/data/corruption error failed: File exists" Does anyone have an idea how to fix this. I tried wiping with fastboot but that made things worse because the update won't take and now it wont boot as well! Would really appreciate any help you can give. I am thinking it might be a permissions problem or maybe I have to delete some files but I am not too familiar with that since I am using the boot screen. I am using the US version and also tried to downgrade but no luck - always get the same error. Thanks!
[Android General] jostrus:
Sorry for such a late response. For some reason I never got an alert to a new post.

I wanted to clarify some things first.

You said you were trying to flash an update. A root update or a full rom update?

You said you tried wiping with fastboot. Wiping what exactly? system? cache? data? fastboot itself?
[Android General] fhmail:
Hi jostrus, no worries

I was trying to do a full ROM update by auto update when I got the error referenced above. I then tried fasboot to wipe system, cache, and data. However, every attempt to flash resulted in same error and since I wiped system it would not boot. I gave up and exchanged it for a new one. I would like to hear though from anyone who has seen this error and what it might mean before I attempt root on this tablet again.

Regards.
[Android General] jostrus:
Well I've never had that error myself. Although I've never tried to flash an update via fastboot either. My understanding is that it requires the fastboot and recovery images from 4.7.3. I'm always afraid of flashing old images to devices after them being upgraded as sometimes they don't work properly. Thank Samsung for screwing their users over like that. But in any case, for future reference, using fastboot to flash a raw partition image (like the .gz I posted Here on post 521) should work unless there is something wrong with the flash memory. The only reason I can think of getting an error is if the zip was in fact corrupted when it tried to verify it. Yet another reason I stick with partition images instead of the damn update zips. I do realize there is proper uses for the updates and what not but for some reason my tablet has just gone bonkers. I can no longer load the recovery it always just says failed even with legitimate updates.
[Android General] Clementk:
Can you help.

is there any chance you can maybe show how to flash with fastboot ? i am on the v21 US update now in the past i have just used the update.zip on SDcard way and with my phone i just use the clockworks. i have never used fastboot and i really don't know how :P. is it as simple as just downloading fastboot and then just runing CMD and just just useing the command "fastboot flash Update.zip" ?

---------- Post added at 06:01 AM ---------- Previous post was at 05:40 AM ----------

am i missing something i downloaded fastboot and then i booted into the bootloader and the bootload says fastboot cmd watting... and on my CMD it says waiting for device ?

---------- Post added at 06:11 AM ---------- Previous post was at 06:01 AM ----------

hey can you maybe just help me ? i installed fastboot / adb on my windows and i boot my tablet into bootloader and it says fastboot is waitting and then on my desktop it also says waiting for device i did look if there is drivers for the asus USB but dod not find any.

i got it fixed had to download intel tablet drivers .. then i have to use the fastboot flash update update.zip
[Android General] gbkelley:
Silent C: the method you refer to for rooting the phone is an exploit for an ARM processor, the ME302C here is an Intel processor. I tried all of the 'batch root' methods out there before cooking my own system image. Sometimes there is no 'easy' way at first.
[Android General] gbkelley:
Do you have an FHD 10 or the LTE version? The LTE has a locked bootloader and requires the unlock utility available at ASUS.
[Android General] manuzes:
I have the me302kl. That utility is available on asus website? to do the unlock?
[Android General] caniswesley:
Whoops! My bad. Got too excited. Sorry about that, guys. Just ignore me (for the memo-ent) ;)
[Android General] Turbojugend:
So what's next for this tablet do you think? Will it get it's own form on XDA? Will people start developing on a non Tegra device?
[Android General] gbkelley:
I think we have to 'petition' the folks here at XDA to get them to add the MemoPad to the device list to get it's own forum space. If they get enough requests, they'll consider it popular enough to comply (or so I assume). There is a thread here to post your request.

Some folks in Germany are already playing with the Kernel so I think development is now taking off and we may see some interesting 'developments' in the near future.

Sometimes these things are an organic 'start from a small seed' process and instead of waiting for the big developer types finding time to look into it, you see things being created by lowly users (like myself) and it then takes on a life of it's own. We are now seeing that for the MemoPad, so be patient, there is more to come I'm sure.

The MemoPad is a great Android device. Well designed, relatively inexpensive (compared to others), and the Intel Atom is not bad performance wise (regardless of what some armchair experts have to say). I did a lot of research before buying mine and I'm now 'all in' on helping to make it a success in the greater Android community.
[Android General] Turbojugend:
If you had your choice of keeping this Asus tablet or getting a Sony Xperia Z Tablet right now, which would you choose?
[Android General] gbkelley:
Turbojugend: I believe the last sentence in my last post answers your question. I just got my MemoPad like three weeks ago.
[Android General] Turbojugend:
Ok, I'll stick with it, I love the tablet, I just want to make sure it gets some love in the dev world at some point hehehe. Thanks for everything, I'll be keeping my eye out.
[Android General] miked2332:
LTE version

sorry if this is wrong place to post but i have lte version unlocked bootloader using the asus link and used this to root (newbie can't post link) got framaroot app from jellydroid website (confirmed on android hilife if anyone needs a second opinion) it will install su i installed busybox seems to work fine will update if there's issues
[Android General] tstack77:
C:\fastbootadb\fastboot flash system ME302C-US-Root.img.gz

error: cannot load 'ME302C-US-Root.img.gz': No error

I've downloaded twice with the same result. Can someone confirm the file hash since MediaFire chooses not to?

CFA3F26F67669752624DA964F0684656

Thanks
[Android General] gbkelley:
tstack77: That is the correct MD5 hash from this end (generated by onlinemd5.com)

Are you sure you have the 302C and not the LTE? LTE locked bootloaded would cause this error...
[Android General] tstack77:
Yes, I'm sure. And now to compound the issue I think that the battery level might now be too low to flash the ota. Is there anyway to check the battery level once the system is erased?
[Android General] gbkelley:
tstack77: I'm pretty sure the USB will provide enough power to run the tab but not enough to charge it, so you should be good to go with a reflash.
[Android General] tstack77:
Thanks for the thought but I wasn't clear enough before. I did try to flash the US and WW OTA's but they sent back the same:

error: cannot load 'US_ME302C-V4.7.3-0-ota-user.zip': No error

I think that the problem has been that my battery has been too low since the beginning, and that is why I am not getting any error beyond 'cannot load' for any attempted flash. I unfortunately do not know how to test this since there is no battery display in the bootloader. Plus I do not know if the tablet is charging when powered off since the icon display shows a static image of 0% battery, even when it gets disconnected. (Picture attached)

I do not know what else to try here. This is a Christmas gift for my wife and she will not be very pleased if my habit bricks her gift :)
[Android General] gbkelley:
Usually if you press power button for 5-6 seconds with that b&w battery icon (and pluggen into charger) you get the colored animated battery and it should charge in about an hour and a half to two hours.

Try pressing power till device completely shuts down, then plug in charger. See if the tab responds to the charger - if so, then try to press power again for animated battery.

I left out 'check for full battery before beginning' in instructions as I assumed that was a given since the OTA update dialog reminds you to check battery level. :o

Good luck with this, hope you don't have to resort to ordering a replacement and shipping overnite for the Mrs.

She will like her prezzie once this is sorted out...
[Android General] Droidman61:
Thank you so much, you ROCK!
[Android General] gbkelley:
Apps List for MemoPad

Productivity:

Pocket Money - been using this since my Palm Treo and iPhone 2G ages ago. Great personal finance app, imports Quicken QIF. Also have it now on my Samsung Galaxy Centura. Have abandoned Quicken on desktop, use this on the Tablet now. $5 but worth it.

Kingsoft Office 5.8 - Word and Excel documents

aWallet Passwords - store encrypted passwords

Equalizer Player - great tunes

Dish Anywhere - Live TV or DVR recorded shows from Hopper with Sling anywhere you have WiFi

ClipNote - stores clipboard entries for future pasting

BookmarkFolder v3.0.1 - import your bookmarks in HTML, complete organized folders, etc. auto launches your browser (Firefox BETA)

+DGT GTD Tasks - best task manager on the planet

OK Timer - three separate up/down timers

K-@ Mail - great email app, K9 doesn't download from Market, says incompatible with MemoPad so tried this one and it's even better

Firefox BETA

Utilities:

Battery Doctor - with some tweaking of the settings, full deep sleep and zero battery usage overnite.

WiFinder - good WiFi locator

WiFiKeyboard - type from your PC

FTPServer - transfer files between devices using ES File Manager (as client) or an FTP Client on PC

Switch Controls Full - loaded this and caused Tablet to stay awake and never deep sleep, uninstalled for now, no response from developer. Works fine on the Centura

Deep Sleep Info - to verify you're going into deep sleep (good for finding rogue apps)

Quick Boot - button to power off, reboot, reboot to bootloader so you don't have to power off/on (saves the physical button)

Screen Off and Lock - tap to lock (if lock screen disabled immediately sleeps) (saves the physical button)

Rooted utilities in previous post in this thread.

Some apps for phone but run in portrait mode and auto-zoom and look great on the FHD
[Android General] Turbojugend:
Quickboot is a nice app too, allowing you to reboot into any mode with the tap on the menu.