yashsingh1/xdaforums huggingface dataset:
[Android General] perpe:
[MENTION=5686955]emcee99[/MENTION]

Flashing the recovery isn't enough, you also need to downgrade the fastboot.img to 4.7.3, afterward you need flash the 5.0.11 update.

Your problem is that you erased the system partition with "fastboot erase system" this is a very bad idea. The 5.0.11 Fastboot and recovery can only flash updates, that are newer then the installed one.

Downgradeing fastboot is a dangerous thing, if something goes wrong it can brick your device.

My suggestion is:

Flash the rooted system image for the ww version, you can download it at http://goo.gl/v6ETyE

This gives you a working, rooted system, but it isn't the us version. Read this post http://xdaforums.com/showthread.php?p=49704751#190 to flash the us version, follow the rooted way(works only for 4.3 versions, if you want to go back to 4.2.2 you need to downgrade the recovery). This is the secures way to get your system working again.

Afterwards you can root your 5.0.11 us version with the new method.
[Android General] gbkelley:
[MENTION=5686955]emcee99[/MENTION]:

Thought I'd jump in and join the party!

First, take a deep breath - hold - let it out slowly, eyes closed...now...

Delete all the crap you've been playing with and let's start over...

Download fastboot-4-7-3 (see my post previous page) and fastboot flash fastboot fastboot.img

Now you have the older fastboot and can do whatever you want

Download ASUS 4-7-3 update and follow instructions on page 1 for rooting, only you are reloading

unrooted

ASUS update file instead

Now you have unrooted 4-7-3 (remember that?)...

OK, we are back to pretty much out of the box so you have two options:

If you want a rooted 4-7-3, follow instructions on orig post Page 1

If you want rooted 5-0-11:

Download ASUS 5-0-11 update

Since you are now 4-7-3 unrooted, just fastboot install 5-0-11

Now go to page 20 and follow post #2 to install root for 5-0-11

Take your time, reboot after each update.

It seems more complicated than it actually is.

Device needs to see things in a certain order or it gets 'unhappy' :crying:
[Android General] Cerberus_:
Mine has been crying for 3 days.
[Android General] emcee99:
IT LIVES!

Here's what worked:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices

Medfield4CE8AABF fastboot

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache

erasing 'cache'...

OKAY [ 3.339s]

finished. total time: 3.340s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system

erasing 'system'...

OKAY [ 4.050s]

finished. total time: 4.052s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system sys5011.gz

sending 'system' (817975 KB)...

OKAY [ 53.802s]

writing 'system'...

OKAY [ 53.285s]

finished. total time: 107.090s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash update US_ME302C-

V4.7.3-0-ota-user.zip

sending 'update' (750956 KB)...

OKAY [ 49.549s]

writing 'update'...

OKAY [ 3.220s]

finished. total time: 52.772s

C:\Program Files (x86)\Minimal ADB and Fastboot>

And after all this - it says Build Number JSS15Q.WW_epad-V5.0.11-20140113. I flashed 4.7.3?

WTF? 5.0.11 is still in there after all that? AND IT's Rooted? I'm completely confused. But the damn thing works again so that's enough for today.

Thanks perpe and gbkelley for the suggestions
[Android General] caniswesley:
[MENTION=5592485]gbkelley[/MENTION] and [MENTION=4177701]perpe[/MENTION] make the 302C a truly awesome tablet with their rooting efforts. :)
[Android General] danbjorklund:
I finally decided tonight to upgrade to 5.0.11 and I found out you really don't need to restore your tablet back to stock 4.7.3

All I did was:

1) backup my data and apps just in case.

2) adb shell

3) su

4) mount -o remount,rw -t ext4 /dev/block/mmcblk0p8 /system

5) rm /system/xbin/su

6) exit

7) adb reboot bootloader

8) fastboot flash update US_ME302C-V5.0.11-0-ota-user.zip

then I followed gbkelly's instructions here
[Android General] justforvexter:
unrooted 5.0.11

Hi everyone,

I'm fairly new to the Android world and I'm trying to undestand the procedures (and all the related tools and things as well).

My situation is: I bought a 302c and never cared about rooting. I never cared about fastboot, sdk and such.

The device has notified the official OTA upgrades since I bought it and I have allowed every upgrade.

Now build number is WW_epad-V5.0.11.

Having read the post by gbkelly (by the way, many thanks), I was convinced to trying rooting my device because of the simplicity of the procedure (no fastboot, no drivers and so on).

I got the WW version of the "fake update", and followed the instructions. Sent the file to the root of my sd card, got the flashing icon in the notification area, started the upgrade. The tablet actually switched to recovery mode, and started the upgrade but stopped almost immediately displaying "error!"

It Rebooted and showed something like "the upgrade went wrong for unknown reasons, reverting back to previous version".

What did I do wrong? Did I skip a crucial step?

Sorry if my bad knowledge of android made my description above being incomplete or unclear. Maybe things that are important and needed in the case are not so obvious to me at the moment.

I'd really apprecciate a helping hand

Thank everyone
[Android General] perpe:
You have to put the fake update into the internal storage.

If you put it into your real MicroSD, then this error occures.
[Android General] justforvexter:
Thanks perpe, I'll give it a try and let everyone know.

EDIT:

Before starting, I'd like to solve a different problem. The second part of the procedure clearly tells us as to do some "clean up" steps after installing the fake update. In order to do so, a root file explorer (such as root exploer for instance),is needed and it is said that also SuperSU is needed.

Problem is: at the moment I'm not rooted, and don't have such tools installed. So, when am I supposed to install them? Before the fake update? Or will I be able to install them Immediately after the fake update?

Thank everyone
[Android General] gbkelley:
That's a very good 'catch-22' question.

If you are currently unrooted and don't have these files, install them

before

the root update so they are available for cleanup before switching on WiFi again.
[Android General] grpdave:
How do you flash the bootloader

I have same exact proble tried everything here still fail each time I try to flash the 4.7.3. You said the bootloader needs to be flashed, exactly how does one get that done?

Many thanks
[Android General] sabetta:
Just wanted to say thanks for all the hard work you guys do trying to help everyone out with this device! After almost killing mine a couple pages back, I'm happy to say I got it updated to the rooted 5-0-11!! Thanks to all your hard work!! Keep it up guys maybe someday we can get our own forum and some dev going on! New ROMs would be nice! Until then thanks to gbkelley, perpe, caniswesley and evryone else putting in their own time helping everybody out!

---------- Post added at 11:38 AM ---------- Previous post was at 11:23 AM ----------

Bootloader flash is on page 16 towards the bottom. From gbkelly.
[Android General] gbkelley:
It's called fastboot, go to the big install post pg 20 #2 and step #8, download that zip file and 'fastboot flash fastboot fastboot.img'
[Android General] grpdave:
I followed steps

Thanks for your fast response! These are the steps I followed.

I did an OTA to 5.* latest version from asus support page then flashed the system_4_6_2_root.img and got soft bricked. I have followed all the instruction here and I still get the "E: unable to rename file: / cache / update.zip: Cross-device link" error. All assistance is highly appreciated just got this device two days ago

---------- Post added at 06:33 PM ---------- Previous post was at 06:28 PM ----------

adb reboot bootloader does not work for me says "error: device not found"
[Android General] emcee99:
That's exactly what happened to me (E: unable to rename file......). See my post #209 for what worked for me. Note that this was after I did the 'fastboot flash fastboot fastboot.img' discussed in step #8 of gbkelley's post #192. Also note that the sys5011.gz file I refer to came from the link provided by perpe in his post #206.
[Android General] danbjorklund:
Maybe 4.3 isn't for me.

After updating to 4.3 and using the table I went today to do some writing and the Bluetooth keyboard bug that others have experienced on different devices is there. I could pair my keyboard but the tablet wouldn't receive any input from the keyboard. I spent all day trying the workarounds and fixes and nothing helped. So I had to go back to 4.2.2

So a warning for others who use Bluetooth keyboards and haven't upgraded yet, you might want to wait. Also if anyone has upgraded and their keyboard does work I'd love to know what brand and model it is so that I may get one that'll actually work with the ME302C
[Android General] justforvexter:
I just want to say a big THANK YOU for the help I got here. My Tablet is now rooted.

Just a note about root explorer. I couldn't get it to start. Don't know if this is because of the intel architecture or simply an unlucky feature of my own tablet. It could be a pain because after rooting you have to do the necessary cleaning procedure and get the correct attributes for build.prop file.

So, before the fake update I searched for a different file explorer and found that "root browser" worked.

Then started the procedure as described and advised here and everything went fine.

Again many many thanks to all those clever guys.
[Android General] shaky_bootins:
also rooted

Mine is also rooted now. Very nice. I flashed it with fastboot, as I couldnt get the pad to recognize the update on the internal sdcard, and on the external sd i didnt work. So fastboot flash update ww_me302c-v5.0.12-0-ota-user.zip, and it was basically ok. Great work!
[Android General] Droidman61:
Permissions

How do you change the permissions? Sorry a newb.
[Android General] misterpat1975:
I used ES File Explorer with root options enabled.
[Android General] Droidman61:
Hey New Jersey, I am from Trenton. Thanks for the help.
[Android General] Cerberus_:
I just wanted to know if abybody else had noti d that when performing the 5.0.11 OTA Update on a completely untouched and unmodified OEM 4.7.3 4.2.2 the update rebooted with the progression meter just beyond 50%? The reason I is this: the IFWI8 Version reported by fastboot on my unit has never changes yet there appears to be a newer version in the ifwi.zip In the OTA.

---------- Post added at 05:23 AM ---------- Previous post was at 05:09 AM ----------

I
[Android General] ozzii:
Hi,

Sorry for asking but this is my first tablet and I don't want to do something wrong or else my wife will kill me :p

I'm under the 'official' 5.0.11 (so no root).

Is all the procedure under the page 20 ok for me?

Where I can find the 'ADB with X86 Android adb driver'?

Again sorry, but I'm a n00b :fingers-crossed:
[Android General] joytofender:
I'm Rooted! Thank You!

I followed the instructions from post #192 and I was able to root with no issues.

Big thanks to [MENTION=4177701]perpe[/MENTION] and [MENTION=5592485]gbkelley[/MENTION] for your hard work and sharing it with us.
[Android General] gbkelley:
Yes follow the pg 20 procedure. You do not need ADB just use the internal SDcard process.

If you run Windoze and want to downgrade fastboot (at some point in the future), google 'Minimal ADB Fastboot' to download the install and google 'Android Intel USB Driver' for the bootloader/fastboot driver.
[Android General] ozzii:
Thanks for the explanation.

I will do the procedure and use the internal SD.

I am under Win and I will surely downgrade the fastboot. So I will google the things and install it.

Thanks again :good: :laugh:
[Android General] coolwazza:
ROOTED!!!

Many thanks, I also have rooted straight from US 5.0.11 (unrooted) to rooted image using fastboot method (had to flash fastboot 4.7.3 first). Had lots of trouble changing permission on boot.prop and replacing file, had to use ADB shell command, mount /system as rw then make the changes. Root Explorer was opening and crashing like other suggested but eventually I got it to work properly and not crash anymore. Install BusyBox to /system/bin , SU, all good!

Thanks again for your hard work! Main reason why I wanted to root was to run ad-away (not available on the market) and get rid of all the advertisement, also I like to add that you can easily install APP OPS X with no issues (Xpertia framework not needed), you can make application permission changes no problem.
[Android General] perpe:
Please, be careful with downgrading fastboot and recovery. This can brick your device. Do it only as a last resort.

If you device boots and you have root, then use the rooted way described in this posting http://xdaforums.com/showpost.php?p=49704751&postcount=190

If you device doesn't boot, then flash a prerooted system.img with fastboot. (make sure that system image version matches to your installed version) and follow the same procedure as above, if you want to downgrade/unroot.
[Android General] ozzii:
I have another n00b question:

If I root my official 5.0.11 with the procedure from the page 20 will I lose all my settings/installed apps :confused:

I think (hope) that will be my last question :p
[Android General] wakata:
xposed framework doesn't work with 5.0.11 right? :c
[Android General] joytofender:
No. You should be fine.

---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------

No. You should be fine.
[Android General] ozzii:
Thanks a lot. Now I can do it :cowboy:
[Android General] clown_6:
Thank you!!

I want to start by saying thank you all for the wonderful work on this!

Also, now that the work has been done for root, and all that jazz, is there going to be anyone interested in custom roms/ kernals? Like is there any devs getting behind it, or is it still to early to tell?
[Android General] vuger22:
I have install ww5.0.9, but when i try to upgrade to ww5.0.11, it say error. I do not understand why?
[Android General] clown_6:
Do you have root?

If so, I'm pretty sure you have to instal the stock asus firmware before you can update.
[Android General] compccs:
ok so i think i did the same thing by forgetting to change the permissions... so anyway to reflash the clean ota without downgrading the fastboot since it can lead to bricking? i tried the reflash command for the rooting zip but that didnt work... i tried downloading the official update and rename it to asus_bundle.zip so i can use the sd download function in droidboot... that didnt work either... any solutions??
[Android General] kashaf.syed.iqbal:
awesome thank you
[Android General] compccs:
i think i need this prerooted img.... how do i go about making one or does someone have a link to one?
[Android General] clown_6:
You have to download it from the asus website.
[Android General] compccs:
i thought those would be unrooted images... right?

and their site is like a maze but ill see what i can find...
[Android General] vuger22:
I dont have root.
[Android General] perpe:
You can find a prerooted system.img for 5.0.11 at http://goo.gl/v6ETyE but this is the WW version. You can switch back to your desired SKU with flashing the official update like described and then root it again, if you want to have root.
[Android General] clown_6:
Ah, I misread the original question. I thought you see looking for a unrooted image.
[Android General] kayateia:
First of all, a giant thank you to everyone who's worked on this. :D

I have my MeMO rooted on 5.0.11, and that's working great. I had a question about alternate su apps though.

I've been working on setting up my Linux-on-Android chroot for it, and I'm not having as much luck there. It seems that while the MeMO's 4.3 does not enable SE Linux at all (getenforce returns "Disabled"), it does have some extra enforcement of the standard Android permissions. Namely, you can do this:

- adb in, ping something and it works

- su, ping something and it works

- su back to shell user, ping something and it fails.

All network access fails with permission denied on socket() once you su, so I am assuming this has something to do with SuperSU's su daemon breaking the chain of command.

So! All that babble aside :), I am wondering if anyone has tried using SuperUser instead, and if that borked, I'm wondering if re-installing the root by the fake OTA method would work. I think it should, but it has me a little gun-shy. I have my Linux-on-Android chroot working, but everything has to run as root. /yuck :eek:
[Android General] perpe:
[MENTION=4955721]kayateia[/MENTION]

Which busybox do you use?

There is only one busybox in the play store that supports x86, it' Busybox X.

Other busyboxes are ARM only. Because of the ARM emulation the appelts link to houdini and not to the busybox.

There is also a preinstallied stock busybox, but it misses most of the applets.

If you installed a busyboox from the play store, look into /system/xbin, with ls -l you can see, if the applets link to busybox or to houdini. If they link to houdini (or was it libhoudini?) you have to uninstall busybox and clean up that xbin directory (busybox uninstallers will fail, you have to do it manually. Afterwards install busybox x and try it again.

You can also try Debian Kit I haven't test it with 4.3, but it worked very well on 4.2.2
[Android General] kayateia:
Thanks for the Busybox info! I actually hadn't installed one explicitly. There's one in /system/bin that I was using by prepending busybox to everything. :silly: Unfortunately I still get the same networking issues in my chroot.

In case you're curious, rather than using a pre-rolled one, I've built up a new chroot from an Arch bootstrap package. I did previously that for ARM, and it worked out pretty nicely. (ARM support on Ubuntu was lacking at the time, and that's what I was using before.) So it's possible I did something broken in my chroot still, though it works fine on an Arch (non-Android) host. I didn't root on the Android 4.2 version, so I'm not sure if it would've worked. I've been tempted to try downgrading and trying again. It makes me really nervous to run things like web browsers as root in my chroot (the only way it works right now).

I'll check out the Debian kit and see if it works. At the least, maybe they are doing something I'm missing that I can pick up on.
[Android General] gbkelley:
Keep Awake Gremlin Back

After a few days of only 5% per day battery use in sleep mode, I've now gone to 60% use in less than a day. Android OS is running Keep Awake almost 100% according to battery details in settings. A reboot didn't fix. I ran 'Wipe Delvik' in Android Tuner which reboots and now it's back to sipping battery instead of guzzling. I did notice I had a standard busybox installed, so I mounted /system/xbin r/w and deleted that busybox binary and all links to it. Installed busybox x so we'll see if the Keep Awake Gremlin reappears in a few days again. Will update with results.
[Android General] perpe:
[MENTION=4955721]kayateia[/MENTION]

If your chroot works as root, then your user may miss some group rights for internet connection. See http://xdaforums.com/showthread.php?t=2312013

A good solution for a chroot Linux is Linux Deploy, works very great on ARM. Unfortunately it doesn't support x86, but it's open source. I will try to get it working on x86, if I find the time for it.

It maybe one of the best solutions for our MeMO Pad, because it has framebuffer support. You don't need vnc/rdp, if you don't want.

[MENTION=5592485]gbkelley[/MENTION]

Busybox has nothing to do with your battery problems. There is something that prevents your device's deepsleep, maybe an updated app, a widget ...

Edit: Do you know Better Battery Stats? It's a good app for searching and finding apps, which cause wakelocks, see http://xdaforums.com/showthread.php?t=1179809
[Android General] emcee99:
Disable automatic system updates

How do I turn off automatic system updates? I can't find it under settings - about tablet or anywhere else.

Thanks.
[Android General] kayateia:
[MENTION=4177701]perpe[/MENTION]

Thank you so much! That was it. I'd forgotten to do those group adds when I set up my chroot. Networking works now.

I'm hoping when I'm all done with this to post a guide on how to build an Arch chroot somewhere. I'll check out that Linux Deploy app too; it sounds like it might be pretty useful.
[Android General] tdamocles:
Better battery stats works great. I've noticed that mine was eating extreme amounts of battery also. BBS was showing me that I was having _audio out wakelock. I turned off all sounds and now all is well.

Spoke too soon.... lt's back.
[Android General] marchions:
doesn't work for me..... after the reboot required by xposed installation, my tablet didn't boot..... i did a factory reset for solve it....

this is strange becouse xposed changelog of 2.4.1 version says: " Fixed a bootloop which mainly occured on some x86 ROMs" :confused:

I hope news about these.
[Android General] walkindude:
also doesn't work.. actually you can just flash system zip again without factory reset

not strange, 5.0.x had been released after 2.4.1, and Xposed actually worked on 4.7.x, so it's a true statement ;)
[Android General] BigDaddyJ94:
Android 4.3 Root

I recently attempted to flash a rooted system image and forgot to backup anything, and was wondering how to reinstall the OS.

Should I just do

fastboot erase cache

fastboot erase system

fastboot flash update US_ME302C-Vx.x.x-0-ota-user.zip

to bring my tablet back to life? And if so, which version should I use? I had Android V4.3 before I did anything.

Also, the format from the website only has US_ME302C_V5_0_11.rar, should I just change the extension to .zip?
[Android General] gbkelley:
BigD:

Were you rooted on 4.7.3?

Which 5.0.x did you try to update to?

If you have a rooted 5.0.x you must downgrade your fastboot in order to flash an older update file, all covered a few pages back

The OTA zip file is in the rar file, so you must unrar it first.
[Android General] BigDaddyJ94:
No, I wasn't rooted before I attempted anything. I was running on the newest update for the tablet. And I attempted to install the rooted image for 5.0.11 to no avail.

I did downgrade my fastboot, and it seemed to get me a little further, seeing as now instead of just being stuck at the Asus Logo, it now also goes to a dead Android screen and reboots a lot.
[Android General] gbkelley:
BigD:

SInce you didn't do a backup, you might as well wipe the userdata as well so try this:

fastboot erase cache

fastboot erase userdata

fastboot erase system

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

That will clear out everything and should load 4.7.3 unrooted. If you get booted back to factory you can go to pg 1 and follow the root image install process. I'm still on 4.7.3 and have no interest in going to 5.0.x
[Android General] BigDaddyJ94:
Hmmm...So I should download the 4.7.3 instead of 5.0.11? I mean, in the most recent update the only thing I noticed was improved auto-brightness...which I never use.

All right! I'll try that and let you know what happens
[Android General] BigDaddyJ94:
fastboot flash update did nothing. It seemed like it was installing, then the dead Android came up, and then it rebooted and now it is stuck at the Asus logo again.

EDIT: I tried again with the newer image (5.0.11) and it installed correctly. It seems that Asus doesn't want me to downgrade. I'm thinking about flashing to the rooted image now...

Using the method on page 20 (Using Fastboot, not the microSD - which I couldn't get to work), I was able to root.
[Android General] Valera1978:
May be exist way to downgrade US me302c to 4.7.3 from 5.0.11?

Last time check http://xdaforums.com/showpost.php?p=49704751&postcount=190 way from perpe - rooted device part - start install and then reboot with error and then I get 5.0.11 with my settings.

Look like need downgrade recovery. But recovery.img exist only for WW version, but US.