yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] thelegendy:
OMG, OMG, OMG! Thanks man, it worked for me! :)
[MeMO Pad 7 General] T_I:
Thanks for the info, this totally worked for me. A warning to other owners with this tablet, don't install the .24 version of lollipop, or be very cautious. I too this version as it was the newest, but now I've reinstalled it almost 6 times just to get a 'simple' app as facebook to install.

Install teh modified version, place the unmodified version on ext. sd, so update finds it and when it wants to, let it install this one. After these steps, root if you want to and reinstall all apps. (with me the restores from the .17 apps gave some issues, but so did installing those via play store)
[MeMO Pad 7 General] dexter20082001:
Everything worked up until installing the update. It failed at installing the flash_esp_update. Now it is still stuck at the Asus logo rebooting every few minutes. Any help?
[MeMO Pad 7 General] Ruben Craveiro:
Well i Was wondering if i could do this to reinstall lollipop (i have it already) or if i could downgrade back to kitkat because lollipop simply cant make any multitasking... and im allways with only 350mb of ram free....
[MeMO Pad 7 General] Ruben Craveiro:
This Thread is about the "K013" Model not the "K01A" Model.

---------- Post added at 07:43 AM ---------- Previous post was at 07:12 AM ----------

I must say... Thank you so much i could reinstall android 5.0 to get a "fresh start" it wasnt bootlooped but it surelly did help my problems with cpu (i have messed around with it XD).
[MeMO Pad 7 General] ALBTechno:
Hey I try both versions 4.4 and 5.0 installed both but after asus logo it shows black screen and does not start i leave it about 2 hours and nothing PLZ i really need your help in my tablet i have 5.0 installed before it broken ...
[MeMO Pad 7 General] Ruwin:
Same here, black screen forever. I've used version .17 to be on the safe side, still nothing booting.
[MeMO Pad 7 General] Totty:
Need help

Hello, i had some problems with downloading apps, music etc. from market and google chrome because i removed "downloadmanager.apk" (if im right) from my system. I wanted to solve it and i put some downloadmanager.apk to system files, reboot and i get stuck on logo Asus. Ok, i tried to wipe my system using temporary twrp recovery. It wiped all my system and i cant now get even into recovery/fastboot. I get into fastboot mode once and i dont know how i did that. Sometimes i can too get to screen with "Fastboot starting..., Fastboot starting... #1, Fastboot starting... #2, Fastboot starting... #3". Guys, dont you know some solution for this? Atleast how to force my tablet (asus k013) to boot into fastboot or something like that? Thanks for every answer.
[MeMO Pad 7 General] Ruben Craveiro:
to go into fastboot u must press power vol+ and -, after that to access bootloader/droidboot, you need to have droidboot.img (u can get it from an update) and put in adb folder, then make fastboot boot droidboot.img which should make you boot to bootloader where u can load temp recovery and flash everything again, i hope i helped
[MeMO Pad 7 General] irfan5110:
help needed for ME170C

will this unbricking method work for ME170C (K017)??
[MeMO Pad 7 General] Pipecar742:
E: error executing updater binary in zip

Hello. I am grateful to all the people in the forum and collaborate. I recently took a System Recovery in my "K013". Everything was going well until, in the Setup Wizard, after configuring Wi-Fi, a message "Unfortunately, Setup Wizard has stopped" appears. I proceeded to do the mentioned here, and when you are installing update.zip from TWRP error messages appear "Unable to mount System", "Unable to mount Storage" and "E: error in executing updater zip binary". What can I do? Thanks in advance!

Sorry for my bad English, I'm from Colombia and I know very basic English.
[MeMO Pad 7 General] Totty:
Thats the problem, i dont have access to any modes like fastboot/recovery, can i somehow force the tablet to load to it?
[MeMO Pad 7 General] gdfajkldfkwfj:
Please don't mislead people if you don't know what you are talking about.

Try Vol+ and power, then release power

you were on the right track

If IntelAndroid-FBRL can detect your phone. that's good enough. Make sure your computer has adb driver installed

---------- Post added at 02:53 AM ---------- Previous post was at 02:49 AM ----------

I was unable to mount ext-sd with cwm, so I used twrp which mounted ext-sd just fine.

modified zip with updater-script first 1 or 2 lines deleted instantly fail to install in twrp and all I get is error flashing zip

now I am trying twrp to flash official zip, it worked until executing update binary. modem mismatch
[MeMO Pad 7 General] bedman77:
For the people with black screen after flashing the rom try to mount system in TWRP and then flash.
[MeMO Pad 7 General] FrutasX:
Hello,

install update.zip without erros but then when reboot stuck in logo asus and then reboot and is stuck again....always doing this!!!

any help?

thanks
[MeMO Pad 7 General] whitefang0925:
ANY HELP?

i tried this but still no luck ... the update from the sd installs successfully but still stuck on bootloop...

the only option that works on bootmode is power off ... normal boot, recovery mode restart bootloader doesnt work :rolleyes:
[MeMO Pad 7 General] gijsmans:
Worked for me, great! Easy and straightforward fix. Thanks!
[MeMO Pad 7 General] claudiomarcelo:
You are a genius!!!!

Thank you very much!!!
[MeMO Pad 7 General] Vítor Guimarães:
Many thanks, my friend. It worked just fine. :good:
[MeMO Pad 7 General] CORP002HU:
Hi, i tryed to fix my tab. I read and do it. But when i type t4 in the cmd it write in the screen : device status unknow. The tab is loading a droid and a loadig bar, but do nothing. It like freezing. Can you help me_?
[MeMO Pad 7 General] osprey220:
I've been stuck in a boot loop as well. Anyone else who previously had this issue find a way to resolve it?
[MeMO Pad 7 General] cikaybe:
After a while after starting "Installing Update..." i get

"flash_capsule failed"

"E:Error in /external_sd/update.zip"

"(Status 7)"

"Installation aborted."

Any ideas?

---------- Post added at 06:16 PM ---------- Previous post was at 05:53 PM ----------

If i retry to update I get the message:

"mount: failed to mount /dev/block/by-name/system at system: Device or resource busy

---------- Post added at 06:59 PM ---------- Previous post was at 06:16 PM ----------

Now stuck in loop.
[MeMO Pad 7 General] RichardCooper:
Hi,

Unfortunately, didn't worked for me. I did wall the steps.

The tablet was bricked after a asus oficial update, but i successfully installed LineageOS, but the camera doesn't work, so i cant use skype. Now im trying to go back to the original firmware, Lineage OS 14 whit no success.

Now im stuck to the Intel logo, the only way that im able to go to recovery mode is by fastboot mode, then IntelAndroid-FBRL-05-16-2015-PTR Bat file to install the firmware, but after the installation and clean the Devarik cache says, No operation system Installed. I restart and get stuck on the INTEL logo, even after 20 min.

What im doing wrong? Any one can help me?
[MeMO Pad 7 General] m_okuyucu:
Mod edit - translated by https://translate.google.com/:

Hello, give me my asus k013 me176 model device, I cannot enter the fastboot and recovery menus, can you help me?

********************************

Merhaba, asus k013 me176 model cihazım ver, fastboot ve recovery menülerine giremiyorum,yardımcı olurmusunuz
[MeMO Pad 7 General] Pullback205:
Same problem. After successful installation of Lollipop file with modified script, it stuck in Asus Logo rebooting loop.

I tried everything of tipps and tricks what i could found on this side. Nothing works.

I can´t understand, on some devices it works, but it looks like most don´t work to upgrade to 5.0.

Also the trick with nandroid backup with TWRP didn´t work, but i think i get not the right backup to swap.

Is there someone could make an backup of his 5.0 Version over TRWP for helping?
[MeMO Pad 7 General] Totty:
check my thread i made, i had alot of issues updating to lollipop aswell, the same bootloop like you have, i spent several hours trying to figure it out, so you dont have to.

i did make a thread (as i already said above), that includes every single step to make a lollipop update succesful

https://xdaforums.com/t/me176c-cx-kitkat-and-lollipop-ota-update-guide-troubleshooting.4533621/

EDIT: Also, TWRP backup of 5.0 wont work, cause you need to update the bootloader, so this way is dead end

+if youre stuck at bootlop after 5.0 update, you can reflash the original KK first WW version of the ROM, 182 it was i believe
[MeMO Pad 7 General] Pullback205:
Thanks for your replay. I tried your way several times with different files (V. 17, V. 36). When i try to copy the update.zip (with modified script) to the root of my devices ( with app "root explorer"), it started to copy some seconds, freezed minutes, then reboot system, two and three times and then restart to the old running system (4.4.2). Nothing happend. How can i copy the update file to the root without freezing and restarting system automatically. I think the copy process was not finished, but the device starting to reboot.
[MeMO Pad 7 General] Totty:
As i said, please check out the thread i made, its made very clear in the thread what to do exactly.

About the update, dont forget there are some requirements to have before you can go to Lollipop.

- having latest .201 Kitkat update installed

- using Lollipop update file with "KK" in the name (on website can be seen as Kitkat to Lollipop file aswell)

Also, i did put the update file to LP on sdcard / internal memory, you dont need to put it in /data/... in the root of your device, you just put it in the root folder of sdcard or internal memory, reboot device and then a notification should pop up in notification bar.
[MeMO Pad 7 General] Pullback205:
That´s what i wrote. On the attach files last message, you can see that i have .201 KK Update.

I put the file (WW KK) on internal memory in root folder, not in /data. There are no notification popup. Because it is starting to reboot while it is copying zip file to the root of internal memory.

Everything is working: root, bootloader, recovery, superuser, twrp, backup and restore with twrp.
[MeMO Pad 7 General] Totty:
Is it starting to reboot, when youre trying to copy the files?

If thats the case, then maybe check your storage or reinstalling the original ROM and then going up to 201 might help.
[MeMO Pad 7 General] Pullback205:
I started again from .182 to .191, .198, .199 and .201. At last took the Asus LL File in root of MicroSD > nothing happened. Same in root of internal store, reboot before copying ended. Same problem as before.

I think I have to accept that it just doesn't work on my device.
[MeMO Pad 7 General] Totty:
Can you describe what exactly happens when you try to install the LL update?

When does it start rebooting?
[MeMO Pad 7 General] Pullback205:
ok, one mistake i made is that i tried to copy the file in the real rooted path of the internal memory, not in the simple base of memory.

Another error and important note: DON´T RENAME THE FILE, NOT ONLY ONE LETTER.

I renamed, read in other threads, in "update.zip". If i use the original name from Asus download, it comes the notification that an update file was found.

It sounds good at first, but unfortunately the installation did not work.

With original file the installation works till the system reboot after this. It stucks in the typical Asus Logo boot loop.

With modified script, the installation started only a short step then an error droid is coming and booted back in last running system with a notification the update didn´t worked.

Ok, looks a little bit better, but the file with modified script does not seem to be the right way for my device.

You can find the log-files here > log-files K013
[MeMO Pad 7 General] Totty:
Now, when it bootloops, the only way to restore the system is to reinstall the KK rom back through Temp CWM. You can either restore the .182 and go back up to .201 or any TWRP backup of the 201 should work aswell. I did also try the service .203 firmware to restore the system and it was fine. Any of the backups and service firmware you can find on 4pda. Regarding the service firmware, it is flashed through Intel Flash tool.

Now, back to the point.

I do believe, it doesnt matter if you flash .17 or .36 or .24 LP from KK, i did .17 first and it worked. You could try that aswell.

What exactly are you modifying in the updater script? Can you send a photo? You should just DELETE the first 2 lines using text editor, repacking the zip with normal compression level and then flash it the way you just did.

When i had trouble updating, i used OTA verifier, it was an app, that you selected the file in, it checked the updater script and compared it to your build properties and told you what was wrong.

For me, the error was having 2x build.prop

K013 and K013_1

K013_1 is used when the device updates to LP, so the script knows youre on LP

I did delete the K013_1 one, checked once again with OTA verifier and then flashed.
[MeMO Pad 7 General] Pullback205:
I made a backup of my .201 system with TWRP, works perfect to restore.

I tried both update files 17 and 36.

Attach script file show the lines i deleted.

The app "OTA Verifier" shows in original update file .36 problem with the first line. I deleted and tried again, but error droid as result.

On the OTA Verification Results, there is Device: k013_1, same like your error?
[MeMO Pad 7 General] Totty:
the APP says your device is K013_1, thats bad, check your build.prop , if there are 2 files, delete the K013_1.prop (cant remember the exact name)

after fixing that K013_1 build prop issue you should be able to use the updater script thats not modified

and yes, its the same error as i had, i fixed it by searching for the build.prop and i saw 2 files, ones of them was a regular build.prop and the other ones was named somewhat K013_1 build prop, i deleted the K013_1 named one and installed the update without issues.

Also, do you have any xposed/uninstalled or frozen apps on your TWRP restored backup?
[MeMO Pad 7 General] Pullback205:
/Root > system > "x.prop" see Attach files

I tried several combinations:

Deleted "build.K013_1.prop" , reboot, frozed in Asus boot logo, restore necessary. Don´t work!

Deleted "build.prop", reboot, restart normal. OK!

Install update file with unmodified script > Asus boot loop > restore necessary

Install update with modified script > error droid
[MeMO Pad 7 General] Totty:
Try doing factory reset, restore your .201 backup, check the build.props, you should have only one, if you have 2, then in through CWM delete system,data,cache and install fresh .182,... up to .201 again, root using the zenfone app and BACKUP it without any other modifications.

This backup should be better than the one youre using at the moment.

OR

Restore your current .201 backup, check build.props and delete the K013_1 one, DONT REBOOT after deleting the build.prop and install the LP update.

(if the update notification doesnt show up, connect your tablet to PC, enable MTP and then disconnect the tablet, the notification should show up)

OR

Delete first 2 lines in updater-script, repack the LP update, put it in root of internal storage

THEN

Restore your current .201 backup, check build.props and delete the K013_1 one, DONT REBOOT after deleting the build.prop and install the LP update.

(if the update notification doesnt show up, connect your tablet to PC, enable MTP and then disconnect the tablet, the notification should show up)

I would try the second/middle option above first of all, then try the other ones.

Also, theoretically, you could also try editing the build.K013_1.prop

line

ro.product.device=K013_1

to

ro.product.device=K013

and then install the update and see if it works

Im pretty sure like 99% the build.K013_1.prop is preventing you from update, cause the updater-script thinks your device is already on LP, but its not

after installing the update, you could theoretically view the recovery log aswell, its located in /cache/recovery

there are several files, you can copy them to your computer and check whats going on with the update more precisely

if your device is not booting up after the update, you can still get the log file through temp TWRP and in the advanced option theres a File Manager that allows you to view these files, you can simply copy them to the sdcard/otg or internal memory and copy them to your PC
[MeMO Pad 7 General] Pullback205:
I started again from the beginning, but nothing is working, boot loop or error droid.

Everything you wrote don´t work on my device.

Maybe it was just a coincidence with the build.K013_1.prop on your device and it is normal 2 of prop builds.

Do you have a comparative device to check?

In the log files (update with modified script) are some infos, but i couldn´t found some help in the internet.

E:signature verification failed

I:Installation aborted(E_UPDATE_BAD_PARAMSE).

Installation aborted(E_UPDATE_BAD_PARAMSE).

E:Install of /sdcard/UL-K013-WW-12.10.1.17_KK-user.zip failed with status 2

I:Recovery fail file /cache/recovery/recoveryfail created

Installation aborted.

E:Installation failed with status 2

Link with log files at #50
[MeMO Pad 7 General] Totty:
My K013 is on 5.0 right now and it has only 1 build.prop, the device name is K013.

I sent a request to access the google drive files you provided, its private apparently.

I think, if you try to update to LP and it fails, the second build.prop file gets created.

I believe, youre still trying to install the update through the stock method, right? Youre not trying to install it through TWRP or CWM, or?

You could also check my other thread i made, when i was seeking help like you do right now, might help somehow.

ME176 LOLLIPOP UPDATE

Maybe youre missing out on something, if i remember correctly, i had error status 2 aswell and my solution with deleting the second build.prop worked.

Theoretically you could also try installing the update with the temp recovery methods, but im not sure if thats going to help, personally i dont think so.

Did you check, if the second build.prop is only in your backup, or if its still there, even after you do completely clean flash?

You could also try a file that i created for you, with the modified update script

KK.36

I dont really know, how to proceed now, the second build.prop and deleting the first two lines in the updater-script were all my tricks up my sleeve, i dont really have any other options to give you.

I can give you an advice thats going to save some time. When i was trying to update to LP, flashing all the files over and over, i always waited for the system to boot up after the update (obviously always going to bootloop anyways).

The normal process goes like this - recovery, installing up to 70%, device reboots, goes into bootloader mode, black screen with white text on top of it, it starts actually booting after roughly 15 mins.

So, if you try to update to LP and your device reboot and it starts booting right up - asus, intel logo, its already going into bootloop.

Also, remember, as i said before, if you uninstalled any system apps, the update will always fail. The updater-script checks for your system files and if your missing something, it will fail.
[MeMO Pad 7 General] Pullback205:
Thanks for all your help. Your file isn´t working as well.

After clean installation of .182, there are 2 build props from the beginning !

I install updates with TWRP and CWM. I tried to update LL with other methods too.

I never deleted any apps. I install only root app and root explorer.

I think the solution is in the log files, but i don´t understand the meaning ot he errors.
[MeMO Pad 7 General] Totty:
I dont know if thats going to help, but i did all the OTAs on KK through CWM, you can install them in 1 session of CWM - no need to reboot after each update.

After that, the LP update i flashed the way i said before - file into the root of internal memory or sdcard, notification pops up, press that and update

(before i did delete the second build.prop ofc)

are you using any of the command files as the author suggest to in here ?

last thing i would try is flashing the service firmware located under firmware>service firmware in here at 4PDA

and then flashing the LP update once again with all 3 different methods (deleteing build.prop/modified updater-script/both at the same time)

you can flash the service firmware using this https://drive.google.com/file/d/18lW80XtH_1uP7x7dh5In-7PzisyW87PE/view?usp=sharing
[MeMO Pad 7 General] Pullback205:
Look at the update file "full rom .182" from this thread ! See attach file

Look at system file in .zip, you will find 2 build props !

No wonder why there are 2 builds after the installations.

I tried and deleted from this installation zip-file the build.K013_1.prop, with the same result as delete the build after installation. Loop or frozen.

4PDA is a russian side. i can´t read it. Please, can you send this service firmware over google drive? Thank you.
[MeMO Pad 7 General] Totty:
The service firmware is here https://disk.yandex.ru/d/7DlZtBEa3Wcsjj

I didnt want to post mirrors, cause it might be against the rules of xda, or maybe 4PDA, who knows.

Hopefully its not :D

Youre apparently using a ROM thats from the thread over here at XDA for the OTAs, i did use the one at 4PDA, i believe these are not the same, because for some reason the one youre using gave me some errors.

4PDA .182

- there is a download link, it works a bit weirdly, i have to right click it and "Save URL as.." instead of just directing me to some upload service.

I will try to download this one myself and see if there are 2 build.props

Here are the OTAs for KK aswell, here on XDA, the OTAs from XDA (Collection of ROMs) seem broken a bit, for example check the .191 - both the GDrive links, one of them is 37M other is 154M for some reason.

I recommend you to use the Chromes in-built translation tool, it always translates the site for you in decent format.

EDIT: I downloaded the .182 from 4PDA and it has the build.prop two times aswell, might be work trying to delete the K013_1.build.prop and flashing the .182 ROM, but im not sure what is it going to do with your device, its might brick it aswell, i did not test that, be careful.
[MeMO Pad 7 General] Pullback205:
ok, i found on 4pda a full release file of .203

I install this with adb launcher. Is running without error, but 2 builds.

Update to LL don´t work with it.
[MeMO Pad 7 General] Totty:
.201 is the default version to go to LP, .203 should make no difference, updater-scripts always checks for your current version, most, if not all LP updates wont install on anything else than .201

there was some .206 versions and even maybe higher aswell, but theres no need to install these, atleast from what i know

i would try the steps above, from my last post, that might help somehow.
[MeMO Pad 7 General] Pullback205:
I ´ve now tried all, really everything that was found here in the xda forum and what you have given me for tips, but it just doesn´t work.

As long as no one can analyze the errors in the script, it will not work.

Is it not possible to make a system image of your device with 5.0 and transfer it to my device, e.g. via TWRP Restore?
[MeMO Pad 7 General] Totty:
Maybe youre missing out on something, the same way like you did copy the file to the root of the system, instead of root of int. memory.

I still think, the issue is with the build.prop, you will need to mess with it a bit more, it took me several hours to find solution for myself.

And no, TWRP backup isnt going to work, because on 4.4 theres a different bootloader than on 5.0, which is why its very hard, nearly impossible to actually revert back to 4.4

Also, if you wont ever update to 5.0, dont be sad about it, the LP is slower than KK, uses more RAM.

The only thing that 5.0 brings is the bootloader, which you can use to unlock the device, meaning you could install LineageOS and even some linux/windows based systems. These are not very well optimized anyways and have quite alot of bugs, random restart and i believe windows would run terribly on our device.