yashsingh1/xdaforums huggingface dataset:
[Android General] gbkelley:
Update 1-21-14: Root for 5-0-11 available - go to pg 17 for details, pg 20 for new and improved method. Having said this, there are no real benefits to Android 4.3 over 4.2, so I recommend staying with 4-7-3.

Yes, folks after two days of trial and error I finally was able to build a system image file (from the US OTA update files) that you install via fastboot.

Install Instructions:

First, BACKUP! Use ASUS App Backup for installed Apps (and their data) and I also use My Backup to backup personal and system settings info. Once rooted, use My Backup Root (or keep using ASUS App Backup for Apps and My Backup (non-root) for everything else. Always Backup to your External SDcard as a Factory Reset (should you need to do one) or if you have to or accidently run 'fastboot erase userdata' will erase your internal SDcard.

Second, Charge your Battery - make sure you do any flashing with a good charge, battery going low during this process can do 'bad things'...

Linux Users Note: I'm using Ubuntu and fastboot will not recognize the MemoPad. Still trying to resolve this, the latest Windoze version of fastboot works.

Download ME302C-US-Root.img.gz from MediaFire (see below)

Install the Minimal ADB-Fastboot into a folder (google this you're on your own)

Install the ASUS USB Drivers (google this you're on your own)

Place the image file in the adb/fastboot folder (do not decompress, install as is)

Run these fastboot commands:

fastboot devices (make sure your MemoPad is connected)

fastboot erase cache

fastboot erase system

fastboot flash system ME302C-US-Root.img.gz

Reboot from MemoPad recovery menu

Install from Market:

SuperSU v1.86 Chainfire (required for all other apps to work)

Root Checker (run it to confirm you have root)

You are now rooted

Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to enhance that by installing BusyBox from the Market and use Safe Install method to add new links to the ones already set for toolbox (explained in busybox).

Enjoy your Rooted MemoPad!

Download the image file from here:

http://support.mediafire.com/download/avhe9zizn7z0t5w/ME302C-US-Root.img.gz

If the flash fails or doesn't root, you can just go back to the original OTA update by downloading it from ASUS and running:

fastboot erase cache

fastboot erase system

fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip

Don't post questions about installing/using fastboot or USB drivers, it's been covered ad-nauseum here and other places - google is your friend. If you have the LTE model (ME302KL), that has a locked bootloader and requires the unlock utility available on the ASUS website before you run fastboot.

Thanks goes out to djsven for getting this idea started, then getting it done himself in Germany using the German distro from ASUS. I ended up having to extract the su binary he had as the three I tried from different downloads didn't work. Not sure where he got it but it's a winner!
[Android General] Turbojugend:
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.
[Android General] tdamocles:
+1
[Android General] Turbojugend:
Why not use Mega? Seems to always work and have great speed.
[Android General] tdamocles:
It is rooted...thank you.
[Android General] gbkelley:
I tried RapidShare and it was crap. MediaFire was next on my list and that worked so I used it. May try Mega if there are problems with folks getting the file from MediaFire, we'll see...
[Android General] notten:
Worked for me. Updated to 4.7.3 and is rooted.

Tried in Linux and could not get fastboot to recognize device.

Tried in Windows Server 2012 with this driver:

http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices

Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.

-notten
[Android General] gbkelley:
Try this:

http://xdaforums.com/showthread.php?t=537508

or this...

http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
[Android General] notten:
Hey, thanks, but neither of those has anything I haven't tried. I'm using the latest SDK and running fastboot as root so it's not the perms. I read on some Intel forum that someone else is having trouble getting it to work in Linux also.

Any luck with iptables? I don't think the kernel for this tablet comes with iptables enabled. I tried a few methods of getting it installed (DroidWall, iptables (beta) from marketplace). If I screw up the kernel on this, will flashing over it with the system image you upped revert it?

-notten
[Android General] Turbojugend:
Thanks a lot for all of this gbkelley. Cheers!!
[Android General] gbkelley:
No my image is the /system folder only. Kernel is in boot.ini. The OTA update zip should fix it though as it has boot.ini
[Android General] tdamocles:
Xposed framework works great. Gravity box and app settings work great. Thanks for root.
[Android General] FirefighterRQ:
Links if you don't want to google it

Minimal ADB and Fastboot

How to install USB drivers
[Android General] Turbojugend:
Hide battery work for you?
[Android General] Duyo:
Got Root, Thanks so much.
[Android General] Turbojugend:
gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?
[Android General] notten:
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.

-notten

EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15

Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.
[Android General] Turbojugend:
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version
[Android General] notten:
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.
[Android General] Turbojugend:
Ok cool, I just don't want to be stuck with something that will have nothing going for it. I really like the tablet, but if it was going to be dead on XDA I would exchange it for the Sony Xperia Z Tablet. Both fit my needs for what I use it for.
[Android General] gbkelley:
My method for 4-7-3 was to add su binary to /system then convert updater-script to shell script to set owner and perms. I created img file with: make_ext4fs -l 1344M -a system ME302C-US-Root.img system/

I followed the same procedure for our 5-0-11 but now realize the /system folder is a bit larger so I have just made img file with: make_ext4fs -l 1516M -a system ME302C-US-Root.img system/ (larger image file)

I have caniswesley ready to test as soon as it uploads to MediaFire, he will report back if successful.

If not, I will read your new method with translator. Thanks. I would PM you but I think it's educational for others to see what goes into creating these roots.
[Android General] perpe:
Adding su to /system/xbin isn't enough with 4.3. You also need to add the su binary as daemonsu to /system/xbin and as .su to /system/bin/.ext

Additionally you need to change the /system/etc/install-recovery.sh

The new method is much easier. You only need to create a fake update zip with the su binary and flash it with the stock recovery :D

If you want I can write a little how to, should be better for the futur. I can maintain the WW version you the US one.
[Android General] gbkelley:
I just read your translated procedure, downloaded your .zip file and had a look. This is MUCH easier! I like this very much! I don't see anything (except for the build.prop file) that's different between WW and US. If you have time to make one, we would all appreciate it. I will use your new method going forward. Much smaller file to upload/download and simply elegant! Very Nice! :good:

I put your .zip file into my work folder. I have modified build.prop in /system to show version 12. I see the updater-script sets perms so I don't have to.
[Android General] perpe:
Yeah, it' pretty simple :D

For the US sku you have to change these files(from my zip):

rename the original US install-recovery.sh to install-recovery-2.sh and replace my /system/etc/install-recovery-2.sh with it

Copy the file /META-INF/com/android/metadata from the original 5.0.11 update to the same directory in my zip and open it.

You have to change the version number in the post-build line and the date and also the post-timestamp line with a timestamp bigger the original one.

If you aren't a linux user, you can get the current timestamp from pages like http://www.unixtimestamp.com/index.php

And place a copy of the original build.prop into the /system folder open it and edit ro.build.date.utc and ro.build.fingerprint to match your changes from the metadata file.

Delete the files in the /META-INF folder, but not the com directory and it's content.

Pack it and sign it with the test keys ;)

Name it like your US Sku update file, but with a bigger version number (the same like in metadata)

Keep a copy of the original build.prop, you have to replace the modified with original one after the root process, reboot afterwards.

That's it.

Take care of these 2 points:

- I don't know if the automated update sends the logs to ASUS after the update process, so it's better to root with WiFi disabled. Delete the log files in /cache/recovery after the rooting and before you turn on WiFi again.

- If you use SuperSu Pro with OTA survival on, disable it and start SuperSu once after you rooted and before you replace the build.prop. With OTA survival on, it stucks at first reboot with the original build.prop.

Edit: maybe you can flash my WW zip, if you do this and it works for you, then you have to replace the build.prop with the us one and also the install-recovery-2.sh with your original install-recovery.sh (don't forget the -2 at the end of the file name)
[Android General] caniswesley:
Hoping you'll have a chance to do this soon (ASAP), as currently my Tablet is nonfunctional for my general purposes (can't recover without root access since use Titanium Backup). :good:
[Android General] camandiisdad:
You could always re flash the 4.7.3 rooted and just not update couldn't you?
[Android General] caniswesley:
Once you upgrade to 5.0.11, I have found no way to downgrade. I think there must be a new bootloader or something like that (I'm still somewhat at the beginning of my Android literacy) that does not recognize the older versions, or specifically keeps you locked into 4.3+
[Android General] camandiisdad:
You have to downgrade fastboot. If you look at earlier post it will tell you. You have to use the me302c 4.7.3 us ota-zip file. I had the ww 5.0.9 and i went back to the non rooted 4.7.3 then upgraded to the 5.0.11
[Android General] caniswesley:
All due respect, sir -- but I did downgrade fastboot to 4.7.3, allowing me to utilize fastboot again. I then tried flashing back to the OTA from the Asus support page. But my tablet wouldn't recognize images older than 5.0.11. It just wouldn't recognize older images. However, that is not important. I have worked with [MENTION=5592485]gbkelley[/MENTION] as a test subject, and he with [MENTION=4177701]perpe[/MENTION] 's help, has created a 4.3 (5.0.11) rooting method. I am running 5.0.11 rooted. I will leave it to him (all due credit to him and perpe) to post the files necessary and instructions. I do not wish to take away from their due. :)
[Android General] perpe:
[MENTION=5242387]caniswesley[/MENTION]

If you want or need to downgrade or install the current version from scratch, then you need to downgrade the recovery also.

This is the ww recovery.img for 4.7.3 it allows you to flash a older versions. But I don't know if you can flash US version with this recovery.

(please, start reading here if you need the us recovery)

With a rooted device there is another way to flash the current or an older version. You have to copy the update file into /cache, it's a good idea to rename it to dlpkgfile

in adb shell you have to enter the following line (as su)

echo '--update_package=/cache/dlpkgfile' >> /cache/recovery/command

(edit: if it gives a error like file doesn't exist, then the recovery directory is missing, create it with "mkdir /cache/recovery")

and after you logged out from the device

adb reboot recovery

I know, this is not much useful for you, because you only want to root. Only for reference, if someone search for it.

I wrote a lot about this kind of things and the Memo Pad at our German board.

By the way, nice to read that root works. Thank you for testing :)
[Android General] caniswesley:
Thank you, [MENTION=4177701]perpe[/MENTION]! I know for a fact that both [MENTION=5592485]gbkelley[/MENTION] and I appreciate your knowledge and association. The work you folks in Germany are doing is outstanding. I, for one, also just happen to love the idea that we as an international community can cross borders and barriers without any animosity. It's absolutely glorious. Between you and [MENTION=5592485]gbkelley[/MENTION], the 302C is that much more of an accessible device. If I had any say, I'd tell Asus to hire you as independent contractors ;).
[Android General] perpe:
[MENTION=5592485]gbkelley[/MENTION]

Greate written.

One note: on step 3. set the file permissions for /system/build.prop to 644 (-rw-r--r--) after replacing it. If you forget this, it will stuck on boot.

(and her not him ;))
[Android General] caniswesley:
Confirmed. My system froze because I forgot to set these permissions. Have to reflash to a clean OTA and then re-root. Practice makes perfect! Thanks for the heads up, [MENTION=4177701]perpe[/MENTION]. Wish I'd known sooner, though! Not your fault. I'll send you a dozen imaginary [MENTION=4945452]->---[/MENTION]
[Android General] misterpat1975:
US Version works great! Thank You!

---------- Post added at 03:58 PM ---------- Previous post was at 03:51 PM ----------

I did the same thing. I fastbooted the root update zip and i was back up and running.

fastboot flash update US_ME302C-V5.0.12-0-ota-user.zip
[Android General] caniswesley:
So I tried to set up the Xposed framework on 5.0.11 Rooted (Android 4.3), and the system (as previously mentioned in an earlier post somewhere) hangs indefinitely. I had to reflash to a the OTA and then re-root to undo the damage. I don't recommend using Xposed, currently. I'm searching the web for a fix, and it does appear that this has been a bit of a nuisance for us x86 pioneers, but hopefully the Xposed folks will get there acts together and start supporting the wondrous x86 better.
[Android General] sabetta:
I am rooted running 4.7.3. running fine. I used titanium backup to delete a bunch of apps, still running fine. Got the ota update, I did a batch backup of everything, factory reset, tried to install ota update and it failed! So now I dont know what to do next! here's where I'm at, after factory reset all my titanium backups are gone, I reinstalled root checker and I'm still rooted, tried reinstalling titanium, nothing no back ups. I have a factory reset 4.7.3 that won't update and is still rooted? Any suggestions would be greatly appreciated I would like to update and try the root again.
[Android General] caniswesley:
1. Personally, I always install an external microSDHC card if possible in any Android device. Since the 302C can hold up to a 64GB one, I have one inserted there. I use the external card for my Titanium Backup Files. I've never lost any data.

2. I believe in order to be able to update OTA, you have to first UNroot. I did this by first downloading the US_4.7.3 OTA from the support page (I have included the link to make it easier for you).

3. I found it easier (personally) to download and flash the 5.0.11 OTA from Asus and flash it using fastboot

4. Follow [MENTION=5592485]gbkelley[/MENTION]'s above post on how to root for 5.0.11. Be sure to have a root-enabled File Explorer beforehand, as well as the SuperSu. You don't want to have Wifi active until the very end.

5. Be sure to move the build.prop to the root /system folder following update using [MENTION=5592485]gbkelley[/MENTION]'s file above.

6. Be absolutely sure to change the permissions on the build.prop (after moving it and overwriting the old one) to 664.

7. Delete all files in the /cache/recovery

8. Don't install Xposed framework. To my knowledge it is not currently working with the 5.0.11 update.

9. Thank [MENTION=4177701]perpe[/MENTION] and [MENTION=5592485]gbkelley[/MENTION] whenever possible :good:
[Android General] gbkelley:
First, not sure why OTA update won't install on a Factory Reset rooted 4-7-3, many others have had success, but prudent to fastboot install 4-7-3 unrooted update then the 5-0-11 update to guarantee success.

You must backup before Factory Reset - it's like doing fastboot erase /data and fastboot erase /userdata as it wipes the internal SDcard also.

You must Factory Reset then do the OTA update, then the rooted update, then restore back to 'normal' (whatever that is)

If you use a Backup app that only backs up to the internal SDcard, you're basically screwed unless you manually copy the backup file/folder to the Ext SD after the backup then manually copy it from Ext SD back to internal to do a restore (PITA). ASUS App Backup will create a file in the ASUS folder on Internal SDcard and if Ext SD is present will do a failsafe copy to root of Ext SD. If your Backup App doesn't allow backup to Ext SD FIND ANOTHER APP! I use My Backup Root, works great, YMMV. And I don't think ASUS App Backup will backup Contacts and Calendar, etc. Someone please correct me if I'm wrong (that's why I use My Backup Root).
[Android General] mingkee:
Here is the summary of the procedure for updating rooted 4.7.3 to 5.0.11 and root:

Prerequisite:

Both 4.7.3 (for unrooting) and 5.0.11 (for ROM update) ROMs from Asus support site.

7Zip for unpacking .rar files from Asus

Root patch

(US) http://support.mediafire.com/download/1v42nl58n7gmq6x/root-us-5011.zip

(WW) http://www.android-hilfe.de/attachm...fhd-10-ab-android-4-3-me302c-root-v5.0.11.zip

ADB installed with X86 Android adb driver installed from Intel

A 32GB micro SD

USB debugging enabled

Steps:

1. Backup all your apps and settings with your favorite app, or use Asus app backup and backup

to memory card (NOT INTERNAL MEMORY!!!)

.

2. Connect your pad to computer. Make sure it has at least 60% charge because the whole procedure takes about an hour.

3. Unroot with original Asus ROM. Locate adb.exe and copy the location. Move the 4.7.3 ROM downloaded from Asus, and move it to where adb.exe is.

4. Open command prompt. With Windows 7 or older, Windows -> run, enter cmd; with Windows 8, call out the right side bar and enter cmd on search, and enter the following commands:

cd\
cd (paste the adb.exe location)
adb reboot bootloader
fastboot flash update (the zip file name of 4.7.3 ROM)

Do not close command yet. Delete the 4.7.3 ROM or move it elsewhere

5. Factory reset the unit at the bootloader. You will be at the initial startup screen. You can do some initial setup from there.

6. Enable USB debug again. (Setting -> about device -> hit build number few times until it says "you're a developer now".

Go to Developers Settings and check enable USB debugging.

7. Move the 5.0.11 ROM downloaded from Asus to where adb.exe is.

8. Enter the following commands:

adb reboot bootloader
fastboot flash update (the zip file name of 5.0.11 ROM)

9. Restore the app and setup Wi-Fi, download and update the apps if necessary. Make sure you download SuperSU if you do not have it restored.

10. Disable Wi-Fi.

11. Unpack the root patch, put the unpacked .zip file and build.prop onto the memory card.

12. Put the memory card in the unit and you should see an update notification. If not, restart the unit.

13. Use root-enabled file explorer (I use Root Explorer) and go to cache/recovery and delete everything; put the modified build.prop from the root patch into /system (it's highly recommended to move the original file elsewhere first) and change the permission to:

rw-r--r--

14. Restart the unit and it's rooted.

All credits go to those who developed the root patch and provided the methods. I only share what I did according to what I read here.
[Android General] emcee99:
I killed it

Failed trying to root with V4.7.3

Was 5.0.11 when I started. Downloaded 4.7.3 from ASUS then:

fastboot erase cache

fastboot erase system

fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip

Started OK:

ERASE COMPLETE.

RECEIVE DATA...

/data available size: 26348 MB, file size 733 MB

FLASH update...

OTA-UPTATE...

Then got following errors

E:unable to rename file /cache/update.zip: Cross-device linkE:Unable to write file: /cache/update.zip

E;Unable to write file: /cache/update.zip

E:update flash failed!

FLASH FAILED!

RESULT: FAIL(flash_cmds error!)

Help?
[Android General] mingkee:
You cannot go back to 4.7.3 from 5.x without flashing bootloader first.

Now you don't have to flash back to 4.7.3 to gain root. You just need patch for 5.0.11
[Android General] emcee99:
Thanks for the response mingkee.

Tried to go back to 5.0.11

Got same errors:

E:unable to rename file /cache/update.zip: Cross-device linkE:Unable to write file: /cache/update.zip

E;Unable to write file: /cache/update.zip

E:update flash failed

I'm stuck
[Android General] caniswesley:
Hi [MENTION=5686955]emcee99[/MENTION]. You need to downgrade fastboot first, before trying to flash a new image using fastboot. Every and any time you upgrade or re-flash 5.0.11 OTA, it upgrades flashboot to a copy that no longer allows user flashing using flash boot. But if you downgrade using this flash image and instructions from [MENTION=5592485]gbkelley[/MENTION]'s post, you will then be able to use fastboot again.
[Android General] emcee99:
flashed the recovery473.zip from android-hilfe.de/attachments/asus-memo-pad-fhd-10-me302c-forum/274021d1389098943-update-auf-5-0-9-4-3-fehlgeschlagen-brick-recovery473.zip

That worked but when finished it rebooted and stayed on the "ASUS In Search of Incredible" screen.

Then rebooted to bootloader and tried to flash 5.0.11 again.

Same errors as before.