yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] jerbear294:
Get back into droidboot mode (Volume Up + Power or Volume Down + Power depending on how far you got into the update) and hit "Reboot" or "Normal Boot" depending on how far you got into the update. This should take you into the ROM.
[MeMO Pad 7 General] Lightn1ng:
Did it work? If not, flash the initial ROM and use fastboot to flash the old boot.img
[MeMO Pad 7 General] Lightn1ng:
Do you have access to DROIDBOOT (power up + power)? If not, then, sorry to tell you, you're hardbricked.
[MeMO Pad 7 General] zapz:
Hey everyone, after trying to update to Lollipop from 4.4.2 and the update failed, I want to downgrade to .182 and flash one by one, as it says in this post. But I've never used ADB, so I don't know too much about it. I installed Minimal ADB and Fastboot and I downloaded the Naked Drivers, which have no executable file. What exactly do I do with those Naked Drivers? Can I use Minimal ADB to flash the ROMs without it? Minimal ADB recognizes my tablet when I type "adb devices". I asked about this in another thread too, but silly me, it's better to ask in the one that has a topic dedicated strictly to this.
[MeMO Pad 7 General] MysticRhythms87:
This might be the answer to my problem...last week I was prompted to install the Lollipop update. It failed, and now I'm stuck on .198 with the system telling me it's up to date whenever I try to check for updates...despite the fact that they officially released .199, .201 and now Lollipop.

I'm backing up my apps/settings to my microSD card. I'll proceed with a factory reset, root again, and go for broke with the manual updates. Wish me luck!

(feel free to let me know if anything I said I was doing is wrong or will lead to problems)
[MeMO Pad 7 General] Bifi991989:
no way to fix the brick .....

my Pad say on recoverymenu:

Finding update package ...

Opening update package ...

E: failed to moun /dev/block/mmcblk1p1 on /sdcard (no such file or directory)

E: failed to map file

SD Installation abortet.

I install the LP-update.zip on ADB and get an error:

Finding update package ...

Opening update package ...

Verifying update package ...

E: failed to verify whole-file signature

E: signature verification failed

Installation abored

I install the LP-update.zip with CWM and get an error:

status 7

I modifigt the updaterscript, deactivate the vertification and get an error:

status 6

I install the backup fromCWM and get an error:

android_secure.img not found

Hello ASUS , now I have an error for you .

I bought the ASUS ME173 with MTK and the support was verry poor. So I bought the ME176 a half year later (So far 260 euro for these 2 devices).

My recognize is i dont buy any Tab from Asus again . Even your great support page. I find it very good that your firmware-support isnt available.

If I could flash the latest full LP firmware I would not have this problem .

With the very best thanks to ASUS

If none of you great people still has an idea , I'll be able to use it in the kitchen, but i dont want to do that.

But I wait for a method to downgrade or fix. Thanks again to the developers and members from germany
[MeMO Pad 7 General] jedial23:
I got lollipop in my MeMOpad without problems... yeah! Now, install superuser!
[MeMO Pad 7 General] PeterParker:
Asus ME176C/CX

Download original Firmware from here:

ASUS memo pad 7 me176CX

http://dlcdnet.asus.com/pub/ASUS/Ee...user.zip?_ga=1.172245093.778525891.1431034338

ASUS memo pad 7 me176C

http://dlcdnet.asus.com/pub/ASUS/Ee...user.zip?_ga=1.138610805.778525891.1431034338

And everything ok, just copy zip file to SDcard and unplug the cable, and follow the step from tablet.

or try to copy to sdCard and enter recovery.

PS: Only apply to same SKU update, Example: WW->WW
[MeMO Pad 7 General] tonyhtsun:
Hi, I have upgrade to LP via OTA. Everything seems fine but why the three buttons at the bottom still using the old style icon?

I thought LP is using the triangle, circle and square for those three buttons like my nexus 5.

Can anyone post a photo of the upgraded me176c? Cheers!
[MeMO Pad 7 General] jerbear294:
Those are ASUS's custom buttons (I personally hate them)

You can used an Xposed module called Android L Navigation Bar or something like that that will change the buttons.
[MeMO Pad 7 General] Lightn1ng:
SoftKeyZ (paid) also works.
[MeMO Pad 7 General] Mono0521:
Is lollipop 5.0.1 a big change from lollipop 5.0?
[MeMO Pad 7 General] Lightn1ng:
Enable USB Debugging in Developer Options, then plug it in. Don't worry about the drivers. (Do adb devices to test).

---------- Post added at 12:32 PM ---------- Previous post was at 12:32 PM ----------

Bug fixes, better battery, etc.

---------- Post added at 12:33 PM ---------- Previous post was at 12:32 PM ----------

Can you tell me if there is a second Lollipop OTA?
[MeMO Pad 7 General] Mono0521:
I just download it off the Asus website. I have not tried to installed it yet. I put it on my sdcard and my tablet does nothing. Not sure what I'm doing wrong.
[MeMO Pad 7 General] Lightn1ng:
Are you familiar with using a temporary CWM session?
[MeMO Pad 7 General] Mono0521:
Yes that's how I was able to root Lollipop 5.0
[MeMO Pad 7 General] Lightn1ng:
Use that to flash the new ota
[MeMO Pad 7 General] Lightn1ng:
I would hold off from taking the 5.0.1 update, the website says they added the following bloat:

50+ Games/Asus support/Auto-star Manager/Backup/TripAdvisor(stub)/Clean Master/Live Wallpaper-MyOcean/Live Wallpaper-MyWater/Live Wallpaper-DayScene/Supernote/Webstorage/Kindle/Remotelink

Yeah... insane amount of crap there.

Of course, you could root and debloat it. I'll probably be making a ROM which debloats it once BestBuy ships back my tablet after repairing it...
[MeMO Pad 7 General] j3cool:
I tried to flash using temp cwm and I get a status 7 error. Said "This package is for K013 devices; this is a K013_1". What did I do wrong?
[MeMO Pad 7 General] Lightn1ng:
What model is your device?

Try turning off signature verification. (Or try temp TWRP beta from here: https://www.androidfilehost.com/?fid=23991606952614221)
[MeMO Pad 7 General] j3cool:
I checked Setting>About and in my build.prop and it says K013. No where do I see anything about K013_1. I tried turning off verification and got the same result.
[MeMO Pad 7 General] Lightn1ng:
I meant is it ME176CX or ME176C

Both are K013

I will be making a debloated 5.0.1 ROM once I get my tablet repaired from bestbuy
[MeMO Pad 7 General] j3cool:
Sorry. I have me176cx.
[MeMO Pad 7 General] Lightn1ng:
You using the 182 ROM (not OTA!)?

What version was the tablet on before the f*** up?
[MeMO Pad 7 General] j3cool:
I was on 201 and had the lollipop OTA fail so I used the guide here to drop back to 182 and followed the process all the way to the lollipop 5.0 available from the first post. Was wanting to go to 5.0.1 but keeps getting that strange error.
[MeMO Pad 7 General] Lightn1ng:
I had this problem. Try using the temporary TWRP instead of the temp cwm, downloadable from here:

https://www.androidfilehost.com/?fid=23991606952614221
[MeMO Pad 7 General] bonogv:
is there chance to downgrade back to kitkat and could someone tell me a guide .. ?! :)
[MeMO Pad 7 General] Lightn1ng:
Unfortunately,

---------- Post added at 09:59 PM ---------- Previous post was at 09:44 PM ----------

Might want to add the 5.0.1 update to the OP

http://dlcdnet.asus.com/pub/ASUS/Ee...ser.zip?_ga=1.110401797.1810943694.1429574486
[MeMO Pad 7 General] Maeke.fr:
I also have a me176cx and i have the same error AFTER 5.0 ota, so i'm stuck with the bugs right now. BTW i tried with the twrp recovery, so no good either.
[MeMO Pad 7 General] j3cool:
I tried twrp as well. Same error. Anyone smarter than me have any idea how to fix this? Please.
[MeMO Pad 7 General] T_I:
Ok, got myself a challenge. Tried everything, including a factory wipe, but installing UL-K013-WW-3.2.23.182-user.zip via sideload fails. Downloading the stock firmware via the support.asus.com link in 1st post shows only http://www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=83838 as available firmware. I was able to sideload that version, but it failes on /tmp/update.zip, although this version should be a complete firmware.

Finding update package...

Opening update package...

Installing update package...

E: Error in /tmp/update.zip

(Status 0)

E: fota_return_code 409

Installation aborted.

Now it hangs on the ASUS logo during boot.

How can I clear the device completely and do a clean install of the available firmware (not an update)

Edit: Ok, found fix in topic http://xdaforums.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049. WW version is to large for sideload, need CN version...
[MeMO Pad 7 General] bravesoul:
We know. That's why that thread exists.
[MeMO Pad 7 General] T_I:
Ok, got myself another challenge. Finally got 5.0 installed, however, I'm unable to enter the google account. Each check fails, password is 100% ok. (checked with several other devices) It just looks like it's not checked correctly against google and thus marked as incorrect. Time to see if I can root the device or one way or the other reinstall play services.

Edit: Ok, this is even weirder, I can create a new account, but I can't add my existing account to the device.
[MeMO Pad 7 General] T_I:
Could you post an howto for the rooting process? I've installed LP, but have issues with the rooting. All FB reports are ADB-ONLINE and after that all actions result in Access is denied. I just can't figure out which mode the tablet should be in, running as usual, fastboot or recovery. Have this issue with 01-17, 05-16 and 06-03, all T levels and all twrp/cwm modes... I'm must missing a simple step. (possibly the correct driver, I'm on Windows for the first time on 20 years)

Ok, found another rooting method here and this method gives the same issues as RF, adb commands are accepted, fastboot commands are totally ignored. Is there a way to get fastboot enabled via usb?
[MeMO Pad 7 General] T_I:
Finally, LP5.0 and rooted

Ok, after loads of troubles I managed to upgrade the 201 version to LP in my ME176CX. First I managed to brick my tablet, so I needed to unbrick it.

After having a workable tablet again, I've installed the latest version available at ASUS (url from 1st post in this thread)

When I installed this version, I noticed google login failed. After registering a new account with a dumbed down password, I used the same password for my original account. This worked. Rooting however didn't work. I was unable to root the device with the FB method. On Windows no response at all, on Linux (Debian stretch) the tablet reacted to adb, but ignored fastboot. (Both from android-tools package) As I was playing with the idea to build my own theme, I followed this guide to setup the development environment. Trying the adb and fastboot from this environment, resulted in a response from fastboot, but not on adb.

Using the method found here I edited the Root.sh script to use the correct binaries (adb from Debian, fastboot from the development tree) and was able to root the tablet.

Ok, so in steps for the upgrade + rooting from a Debian Stretch server...

Check if you really want the upgrade

Read this list, the text above and all erferred guides at least twice

You really want to go trough al this hassle? (I've been at it for more then 16 hours) Then continue.

Install development environment as described in this guide

Download 5.0 full package from ASUS

Download all files from this guide and unpack as indicated

Edit the ZenFoneRootKit_20150528/Root.sh file so the BINARY variables point to the correct version with absolute path and remove the ./ in front of the call of theze variables:

Make a back-up (I used Titanium Backup) and store it on your external SD

Unbrick and use downloaded latest version for the final step (or the upgrade steps in the 1st post of this thread)

Root the tabled following this guide with the modified Root.sh

Restore all private apps + data.

When you have Titan Backup or something simular, freeze all bloatware. (Don't delete, it'll be checked on an upgrade)
[MeMO Pad 7 General] therealprof:
Sounds far too complicated. I downloaded the IntelAndroid-FBRL-06-03-2015-PTR2.7z from http://xdaforums.com/showpost.php?p=61148802&postcount=443, unpacked it and just issued the commands from the launcher.bat (there's a bug in there BTW, method 5 will not work) manually.

Should be as simple as (Don't forget to put SuperSU on the device before):

1. adb reboot-bootloader

2. fastboot flash /tmp/recovery.zip FB_RecoveryLauncher/twrp_mdpi_portrait.zip

3. fastboot flash /tmp/recovery.launcher FB_RecoveryLauncher/recovery.launcher

4. fastboot oem start_partitioning

5. fastboot flash /system/bin/logcat FB_RecoveryLauncher/recovery.trigger.new

6. fastboot oem stop_partitioning
[MeMO Pad 7 General] T_I:
Did the same

Should be and when you're lucky or at least not terribly unlucky, it works.

In my Windows environment, the device totally ignored all commands, including adb.

Then I switched to Debian and tried the upgrade by hand. (commands are the same in Windows/Linux, that helped)

And here the process failed completely for me.

I had no response what-so-ever on the fastboot commands and with a sh*tload of trouble I managed to get my tablet alive and even upgraded. Yeah, it's way to complicated, but nothing less worked for me. (I'm glad it took me only 24 hours to get the tablet back in running order instead of it being a very expensive paper-weight)

My post was intended for people that killed their tablet in the process of the upgrade and are not yet at the point they're stuck in the new boot-loader. Unlike all previous upgrades, this one will get you stuck when you're unlucky. (I at least haven't managed to sideload the CN .182 version after I arrived at the 5.0 bootloader) I am messaging with a user who stranded at the 5.0 boot-loader and now has a bricked device. He can boot ino fastboot, but it's dead when he tries a normal or recovery boot. (when someone has tips to get the tablet back up, let me or applerulez1 know. I'd say, at the moment it's dead, complete clean install is an option.

BTW I noticed my normal password at google didn't work, as it was to complicated. A new account with a very crappy password would let me into the Google store. I used that password for my original account to get the app store to update all apps that were in the image. After this I managed to change my password back to something I trust (complex enough) and due to the upgrades accepted by Google .

This upgrade is a lot trickier... (and after I fixed the tablet I've decided never to buy Android hardware again that's not CM supported. I want to know I can install TWRP or CWM and fix the tablet when I start messing with it. (I'll start messing with it, I want to know how stuff works)
[MeMO Pad 7 General] therealprof:
I'm sorry but isn't the main reason to buy this tablet exactly that it's a cheap ass version of an Android tablet with a name brand behind it? If money is not so relevant there're much better tablets to buy (even from Asus like the ME572C). And I wanted something that just works I'd rather pay a bit more and get something not Android...
[MeMO Pad 7 General] T_I:
For me, no. My main reason was that it's a cheap ass version with good hardware specs. The brand is irrellevant for me, as all brands dump loads of bloatware on their products.

I prefer good hardware with loads of bloatware I can kick of. To bad I'm limited to freezing the bloatware, but that's good enough for this tablet. As soon as it dies, I'll go hunting for a tablet with good alternative rom support. Did the same for my phone and loving every minute of it. (Didn't expect to do much on the tablet, with a good phone)

Then I'm stuck with Apple or WIndows. Both unescapable vendor lock-in, Android is at least kinda escapable. (And I don't want to pay more for my tablet then for my daily driver) I'm in the position I can spend time to make a good tablet perfect, I can't/don't want to spend the cash on not having to.
[MeMO Pad 7 General] therealprof:
The hardware is not really that great. And all Intel based tablets are subsidised by Intel which is guess is also the main reason why they're all completely locked down so no one can install any custom OS.

Problem is: Those are either cheap (Chinese noname brands with cheesy to non-existing support powered by Chinese chipsets which have partially really horrible driver support) or really expensive...

Good for you. I wasted so much time making my tablets (ME176C and ME572C) halfway(!) workable that it would have been cheaper for me to buy two iPads and work all those hours instead. Luckily I can justify having to spent time on Android for my day job so someone else pays for the wasted time.
[MeMO Pad 7 General] un4saken:
I'm getting this error while trying to update from 182 to 191. Can you help me please? I'm doing the exacts steps from the first post.

"Couldn't read image boot

Error in /data/update.zip

(Status 7)

fota_return_code 409

Install of /data/update.zip failed with status 1

Installation aborted"

edit:

Also if i try to install the full lollipop firmware from temp CWM, it gives result [/system], and it bootloops.

I'm currently in .182 firmware.

Any advices?
[MeMO Pad 7 General] Lightn1ng:
Hello, I am on OTA 182. Trying to update to OTA 191, it says "error reading image boot, error 7."
[MeMO Pad 7 General] thebulletfromhell:
Open up the OTA(s), remove the cluster of lines that check and flash boot.img/fastboot.img from the updater script. You'll have to do this for every OTA from 191 to 201.
[MeMO Pad 7 General] muzsielod:
I don't recommend upgrading to LP

I don't recommend upgrading your tablet to Lollipop.

I encountering a lots of problems after upgrading. The time on the tablet is changing randomly... the apps are freezing and automatically shooting down, there are several unnecessary application that are using the RAM memory, which even so you uninstall them. after the first restart, you'll getting them back... I'm very disappointed and sorrily can go back to KitKat any-more. There is still no rooting available, so you can't uninstall even some of the useless pre-installed apps...

I hope there will be some more updates that will make the tablet usable with LP, but until that, is hardly usable...
[MeMO Pad 7 General] jerbear294:
You've been misinformed, mate.

The time is an issue, yes. However, there is an app called ClockSync that fixes it.

If you can install xposed (which you can, just look up Xposed for zenfone 2) you can install "Fix Lollipop Memory Leak" which patches up Google's mistakes.

Titanium Backup can freeze the bloatware.

"But wait!" I hear you say. "All that needs root!" Yes it does.

I managed to get the tablet rooted less than a day after the OTA rolled out. By now you've probably heard of the Temporary ClockWorkMod. On your tablet, download a flashable zip for SuperSU. On a computer download the Public Trial release in that thread and choose trigger 4 in fastboot mode. It'll boot you to ClockWorkMod. After that navigate to where you downloaded SuperSU and flash it, and you'll be rooted.
[MeMO Pad 7 General] Lightn1ng:
Seems to have worked for OTA 191! Still working on modding the rest.

I also needed to remove the assert_prop lines for SystemUI, because I used SoftKeyZ to mod my nav buttons.
[MeMO Pad 7 General] Lightn1ng:
This has worked for every KitKat OTA, and I am able to run build 201! Thanks!

However, now when i flash 5.0 Lollipop, it reboots and just... sits there. At the "ASUS - IN SEARCH OF INCREDIBLE (powered by android) screen. Any ideas?
[MeMO Pad 7 General] muzsielod:
Hi, thx for your advice, but I don't get this part, what is Public Trial and how should I acces fast boot mode, could you be more specific.

The RAM optimiser and the time sync worked well. Thx again.
[MeMO Pad 7 General] thebulletfromhell:
You can't flash lollipop, as that require a full repartition + droidboot + kernel flash. Your device is in a semi bricked state, where you can't flash anything other than /system and /data (hence OTA failing on boot/fastboot). Take it to warranty, or just stay on KitKat
[MeMO Pad 7 General] Lightn1ng:
Why isn't there an OTA from 201 to Lollipop?
[MeMO Pad 7 General] ThisIsSpartah:
Have problem that stock rom is getting error toasts - systemui has stopped and gapps has stopped. So I can't do anything with tablet.

I have downloaded official Asus 5.0.1 update but it's impossible to flash it, because when I boot to recovery it says "installing system update" and after 2 seconds - "error" and boots in normal mode.

Device is rooted.
[MeMO Pad 7 General] daspex:
Don´t know how to make it work with the Lollipop

Hi,

since one Week i tried to make my me176c work with the new Lollipop and read nearly every thread but none of the described

ways ist working for me.First i flashed all OTA´s via cwm temp recovery until i reached the .201 ota.After that i flashed the lollipop rom from page 1 of this thread

after factory reset and wiping cache-partition the lollipop installation results in a bootloop.So i have downgraded to .182 and after that i could not reinstall the

other ota´s.I was waiting a few day´s and read the Forums again to figure out if someone has found a solution wich fits to my problem.I found the thread with

the advice to delete some checklines in the update-scripts but this doesn´t works for me.Now i´am going to download the Intel Flashtool and maybe give it a try.

But iám a little bit afraid to use this tool cause it could make real damage to my device when using it in a wrong way.Iám no developer and my infomations of this

kind of stuff ist not as big as it should be for this kind of operation.So before i go into this i would like to know how the lollipop for the asus device is built.

Has it the option to change the designs or will the xposed theme manager work on it.If not i have no reason to change my os to it then this .182 is working well

and the xposed stuff is working.The theme manager does not affect the homescreens but all the icons and other stuff and my free system memory is nearly always

by 360 MB so that´s enough to me for using my app´s.So if i can´t get a solution here i´ll be waiting until someone unlocked the bootloader and we get custom roms

for this device.BTW i don´t know why but my kernel and bootloader are still .201 but my rom is .182 but all is working incl. wifi bluetooth tethering etc.

Finaly i want to thank all of you nice guy´s for figuring out all the things i could read in this thread.
[MeMO Pad 7 General] thebulletfromhell:
There is. It bricks the same way the full 5.0 update bricks - kernel and fastboot are locked.

I just took mine to warranty
[MeMO Pad 7 General] Lightn1ng:
Then what? I just traded mine for a Nexus 7. It's $165 now.
[MeMO Pad 7 General] thebulletfromhell:
No, like I gave up and just took mine to warranty.
[MeMO Pad 7 General] Kaizerender:
HI, newbie here.

I tried all the steps in updating OTAs and failed..

I also tried updating through cwm and failed

Lastly, I failed the update through adb sideload and gave me this error

Finding update package...

Opening update package...

Verifying update package..

Installing update..

Verifying current system...

Verifying boot image...

Couldn't read image boot

E:Error in /tmp/update.zip

(Status 7)

E: fota_return_code 409

Installation aborted

Got it fixed.. but the problem now is it goes in a bootloop when the update for lollipop 5.0 finishes .. and now im stuck at .201
[MeMO Pad 7 General] thebulletfromhell:
Take it to warranty
[MeMO Pad 7 General] daspex:
fastboot

Hi

Like i already said i'm not a developer but i read the bootloader can be unlocked with the fastboot command fastboot oem unlock.Can't we use this command to unlock the bl of our device?.Please can somebody explain it to me?
[MeMO Pad 7 General] fran1563:
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:

"FastBoot Starting...

FastBoot Starting...#1

FastBoot Starting...#2

FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.

MAN IM GOING TO CRY, I'm from a country when buy this it's too expensive.