[Q] How to root Asus Memo Pad 7 (me572c) 2014 version

[pWEN]

is there anyway to put the Google Nexus tablet OS onto my memo pad 7? this OS seems to be somewhat slow, especially when typing.

No, there isn't.

 

[nrthunderman]

So, I searched through the thread and did a bit of research on the internet, and it seems like the answer to this question is no, but I may as well ask for a concise breakdown: has there been a reliable way to root Lollipop without reverting to an older version of Android?

 

[pWEN]

So, I searched through the thread and did a bit of research on the internet, and it seems like the answer to this question is no, but I may as well ask for a concise breakdown: has there been a reliable way to root Lollipop without reverting to an older version of Android?

Sadly not. I wish Asus would let us unlock the damn bootloader, would really open up more possibilities.

 

[kanagawaben]

Help! Downgrade failed and tablet seems to be bricked (only get "intel inside" logo). If I connect it after combi pressing buttons, it shows as moorefield device but if I try to run the downgrade program again it crashes with message "xfstk-dldr-solo has stopped working" @xda-log or anyone any ideas?

Edit: found post a couple of pages back with possible solution. Will try to follow that post.

 

[kanagawaben]

Indeed, reinstalled win7x32 on my trustworthy eee-pad as Win10 was a bit too much anyway for a screen with 800x600

I am struggling because I have no machine to throw windows 7 on (and no copy of windows 7 even if I did). I see in the notes that it says it is supported on ubuntu, so maybe I can make a bootable ubuntu usb stick and use that.

Update: can't work out how could do it on linux because can't find intel drivers, tried a win 7 virtualbox machine but couldn't do it that way either. Think I'm screwed.

 

[pWEN]

I am struggling because I have no machine to throw windows 7 on (and no copy of windows 7 even if I did). I see in the notes that it says it is supported on ubuntu, so maybe I can make a bootable ubuntu usb stick and use that.

Update: can't work out how could do it on linux because can't find intel drivers, tried a win 7 virtualbox machine but couldn't do it that way either. Think I'm screwed.

You might be able to run Win7 off a flash drive. There are websites that have things that start with a "T" and rhymes with "warrants" where you can get a copy of Win 7, possibly even already optimized for running on a flash drive.

 

[kanagawaben]

Thanks, but I was able to do it in Win 10. Phew! There's a guide for brick recovery over in the Zenfone 2 general page of XDA, which explains how to install the intel soc driver correctly and has a more recent version of the xFSTK downloader tool. Combining that guide with the instructions @pvansoest gave two pages back was ab!e to restore bootloader and get stock firmware installed. Anyway, I'm staying on the latest stock unrooted firmware from now on - done with using dodgy tools and instructions sketchily translated from Russian. Shame ASUS don't seem willing to give us an unlock - this tab would be so sweet running CM13.

 

[mrredcon2]

Xposed won't install!

I'm having trouble getting Xposed to run on my ME572C. Everytime I run the script, I get stuck at the ASUS boot screen with the circle. Help? (I've already recovered from it.)

 

[imwithid]

Sadly not. I wish Asus would let us unlock the damn bootloader, would really open up more possibilities.

Does anyone know what kind of bootloader Asus uses? Why are bootloaders so difficult to crack?

 

[kanagawaben]

Does anyone know what kind of bootloader Asus uses? Why are bootloaders so difficult to crack?

I don't know, but it is strange and annoying that they provide unlock tools for some products (e.g. zenfones) but not others, like this tablet. It's getting old in the scheme of things, they have a whole newer line (the zenpads), and it doesn't seem likely that they will provide any further updates for the memo pad, so no earthly reason for them not to give us an unlock. Would be great to have CM12.1 or 13 on this tablet.

 

[imwithid]

I don't know, but it is strange and annoying that they provide unlock tools for some products (e.g. zenfones) but not others, like this tablet. It's getting old in the scheme of things, they have a whole newer line (the zenpads), and it doesn't seem likely that they will provide any further updates for the memo pad, so no earthly reason for them not to give us an unlock. Would be great to have CM12.1 or 13 on this tablet.

My ME572C just bit the dust (likely the digitizer, no longer responding - sent for RMA). I've contacted ASUS and took the opportunity to forward my request that a boot unlock be released (likely, this will be ignored, but I gave it a shot). On the feedback page, I reiterated this request letting them know that I have bought two of these, two ME176X tablets and I still have my TF700T (unlocked and running OMNI 5.1 - the tablet works great almost four years later! Albeit a bit slow).

If a boot unlock is not offered, I'll be moving away from ASUS (or else choose more carefully when buying a tablet).

 

[kanagawaben]

My ME572C just bit the dust (likely the digitizer, no longer responding - sent for RMA). I've contacted ASUS and took the opportunity to forward my request that a boot unlock be released (likely, this will be ignored, but I gave it a shot). On the feedback page, I reiterated this request letting them know that I have bought two of these, two ME176X tablets and I still have my TF700T (unlocked and running OMNI 5.1 - the tablet works great almost four years later! Albeit a bit slow).

If a boot unlock is not offered, I'll be moving away from ASUS (or else choose more carefully when buying a tablet).

As you say, it's likely to be ignored, but thanks for trying.

When you say it was no longer responding, do you mean the touch panel was no longer responding? I've found mine occasionally does that, but booting into recovery and wiping the cache fixes the problem.

 

[imwithid]

As you say, it's likely to be ignored, but thanks for trying.

When you say it was no longer responding, do you mean the touch panel was no longer responding? I've found mine occasionally does that, but booting into recovery and wiping the cache fixes the problem.

Even after a factory wipe, it did not resolve the problem. If anything, it has gotten worse. Worse yet, the RMA was rejected because the receipt did not have a company logo on it (but had the name, store number, address, etc.).

I have tried going into recovery mode but get an error.

I hate to say it, but I think I'm done with ASUS.

 

[pvansoest]

Even after a factory wipe, it did not resolve the problem. If anything, it has gotten worse. Worse yet, the RMA was rejected because the receipt did not have a company logo on it (but had the name, store number, address, etc.).

I have tried going into recovery mode but get an error.

I hate to say it, but I think I'm done with ASUS.

In an earlier thread I've explained a bit about recovering the tablet with some external tools. Might help to restore your tablet with the original rom. Good luck!

 

[ndluan29]

Issue "Error!!! FWR_DnX DONT EXIST,EXIT!"

hello,
my me572cl is at 12.14.1.23. i prepared everything following post#637. but it faced issue like quechua1 had mentioned "Error!!! FWR_DnX DONT EXIST,EXIT!" when running downgrade.cmd. should i use downgrade-2.cmd or downgrade-3.cmd included in the packet too?
thank you.

 

[pWEN]

hello,
my me572cl is at 12.14.1.23. i prepared everything following post#637. but it faced issue like quechua1 had mentioned "Error!!! FWR_DnX DONT EXIST,EXIT!" when running downgrade.cmd. should i use downgrade-2.cmd or downgrade-3.cmd included in the packet too?
thank you.

If you're not on a Windows 7 computer, you're going to have a bad time. That procedure does not work reliably on Windows 8 or 10.

Otherwise, make sure Moorefield Device shows up in Device Manager like it says in the instructions. If not, your issue is likely related to that. I believe the downgrade.cmd runs downgrade-2 and -3 on its own, but maybe not, so you can try it.

There's probably a newer, maybe even better, way of doing things now, as those instructions are pretty old. Unfortunately, the guy who was hooking us up abandoned this thread once things stopped working reliably. If you go to the 4pda forums, you can find the latest dev threads there, but you'll have to translate them from Russian.

 

[kanagawaben]

If you're not on a Windows 7 computer, you're going to have a bad time. That procedure does not work reliably on Windows 8 or 10.

Otherwise, make sure Moorefield Device shows up in Device Manager like it says in the instructions. If not, your issue is likely related to that. I believe the downgrade.cmd runs downgrade-2 and -3 on its own, but maybe not, so you can try it.

There's probably a newer, maybe even better, way of doing things now, as those instructions are pretty old. Unfortunately, the guy who was hooking us up abandoned this thread once things stopped working reliably. If you go to the 4pda forums, you can find the latest dev threads there, but you'll have to translate them from Russian.

See my post #887 on the previous page - there's more up-to-date win10 compatible stuff available over on the Zenfone 2 page's brick recovery guide. I managed to get it done by combining the files and instructions there with the stuff on this thread.

 

[pWEN]

See my post #887 on the previous page - there's more up-to-date win10 compatible stuff available over on the Zenfone 2 page's brick recovery guide. I managed to get it done by combining the files and instructions there with the stuff on this thread.

I looked around the Zenfone 2 area and wasn't sure if I found the thread you mentioned. Is it this one? [Guide] Un-brick both (Soft/Hard) bricked Zenfone 2 ze550ml/ze551ml.

Can you provide detailed instructions for the process you followed? If the work's already been done and was successful, it would be very helpful for everyone here.

 

[therealprof]

There's probably a newer, maybe even better, way of doing things now, as those instructions are pretty old. Unfortunately, the guy who was hooking us up abandoned this thread once things stopped working reliably. If you go to the 4pda forums, you can find the latest dev threads there, but you'll have to translate them from Russian.

The whole approach of flashing an old lowlevel firmware so you can boot a broken bootloader which allows to flash unsigned images only to flash such an image from an untrusted Russian source just to gain root access is completely bogus anyhow. There's most likely a much simpler way but some people seem to like it very dirty...

 

[pWEN]

The whole approach of flashing an old lowlevel firmware so you can boot a broken bootloader which allows to flash unsigned images only to flash such an image from an untrusted Russian source just to gain root access is completely bogus anyhow. There's most likely a much simpler way but some people seem to like it very dirty...

Currently it's the ONLY way.