***5.0 Brick Solution*** Asus Memo Pad 7 ME176CX

Search This thread

Pullback205

Member
Jan 15, 2023
16
0
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.
 

Attachments

  • 182_full_rom.PNG
    182_full_rom.PNG
    34.2 KB · Views: 4

KrakmanCz

Senior Member
Nov 8, 2015
58
23
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.
 
Last edited:

Pullback205

Member
Jan 15, 2023
16
0
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.
 

Attachments

  • release 203.jpg
    release 203.jpg
    39.5 KB · Views: 6

KrakmanCz

Senior Member
Nov 8, 2015
58
23
.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.
 

Pullback205

Member
Jan 15, 2023
16
0
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?
 

KrakmanCz

Senior Member
Nov 8, 2015
58
23
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.
 

Pullback205

Member
Jan 15, 2023
16
0
I have spent more than 30 hours to read and try everything, several times and different variants, unfortunately without success.
I wanted to use the Memo Pad as a display for a video doorbell, but I need android 5.0 so that I can run the necessary apps.
 

KrakmanCz

Senior Member
Nov 8, 2015
58
23
I have spent more than 30 hours to read and try everything, several times and different variants, unfortunately without success.
I wanted to use the Memo Pad as a display for a video doorbell, but I need android 5.0 so that I can run the necessary apps.
I know my answer sounds really basic, but if your device is not supported by the app, have you tried searching for an .apk version of it? Like APKmirror does these kind of things, for example, or you could theoretically install it on a different device and then move the .apk file. Or, maybe its just an actual requirement to have, some apps are just making up uncompability for lower android versions, cause of the security risks - bank apps, google pay, etc.
 

Pullback205

Member
Jan 15, 2023
16
0
All the apps i need don´t work on this Android Version. I tried with apk files an dso on.
I will sell the Asus.
I ordered a Lenovo Tab M7, Andorid 9 installed.
 

KrakmanCz

Senior Member
Nov 8, 2015
58
23
All the apps i need don´t work on this Android Version. I tried with apk files an dso on.
I will sell the Asus.
I ordered a Lenovo Tab M7, Andorid 9 installed.
I bought mine brand new for roughly 250 euros back then in 2015, it was good device back then, but now, not really. I had to get a motherboard replacement - i bought the whole device described as "non-working" for roughyl 20 euros. I believe it will be hard to get more than 50 euros for your device even if its decent condition.

Few years ago i purchased Mi Pad 4 which was really good device for its price - aroundish 250 euros including tax+import fees.
There are many good tablets these days, for affordable prices, but if your only usage will be the doorbell, i dont think it really matters.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    For the people out there who for some reason had there devices bricked when updating to lollipop. Whenever I was going to flash the WW_5.0_ME176C/X update I would get this error. "This package is for "K013" devices; this is a "K013_1"." I was bricked for a week because of a random device "name change?" Well here are the steps I took to make a flashable lollipop that wouldnt brick me. What you are doing here is telling the script that does the update that it does not need to verify your tablet model since it is wrong anyways.

    Step 1: Download 7-zip. Download Notepad++. Download the TEMP CWM. Install the first two and hold onto the TEMP CWM for later. (Links Below)

    https://notepad-plus-plus.org/download/v6.7.9.html
    http://www.7-zip.org/download.html
    http://forum.xda-developers.com/showpost.php?p=60770086&postcount=352

    Step 2: Download the latest update from asus on your device's page (UL-K013-WW-12.10.1.17_KK.zip in my case). Extract the download into a new folder. If there is another .zip inside the new folder just make another folder and extract it once more.

    Step 3: In the folder you extracted the .zip to, navigate to \META-INF\com\google\android. Open updater-script in Notepad++. Delete lines 1 and 2 and Save.

    Step 4: Go back to the extracted folder and select all of the files in the folder. Right click and choose "Add to archive..." Make sure the "Archive format:" is "zip" and the "Compression level" is set to "Normal". Name it update.zip

    Step 5: Put update.zip in the root of your micro sd card. Insert your micro sd into your tablet.

    Step 6: "Open IntelAndroid-FBRL-05-16-2015-PTR" and the folder inside that. Open "launcher.bat".

    Step 7: Power off the tablet. Hold the Volume-Down key in, while holding the Volume-Down press and hold the Power button until the screen says Asus, release the Power button at this point. You should be in recovery. Plug your tablet into your pc.

    Step 8: In the cmd window that popped up from the "launcher.bat" type "ACCEPT" and when the next prompt appears type "T4".

    Step 9: Wait until the cwm recovery fully loads and go to "Install a zip..." then go to "choose zip from external sdcard". When installing it may look like it froze, LEAVE IT BE! It is actually installing.

    Step 10: You may get an error about /system not wanting to mount, ignore this and reboot your device, let it go and it will boot into lollipop. (Give your tablet 15mins to boot)

    After a week of hurting my tablet and my tablet hurting my feelings I figured out this workaround, let me know if it worked for you! Enjoy 5.0!!! :D
    1
    OMGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG OMGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG MY TABLET WORKSSSSSSSSSSSSSSS AGAINNNNNNNNNNNNNNNNNNN 1000000000000000000000000000000000000 THANKS MANNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN RESPECTTTTTTTTTTTTTTTTTTT :good:
    1
    No, I was having a 791mb archive...
    Ok new attempt: 791MB but with compression set on normal, not on store (i'm french so my 7-zip is in french).
    1
    tried this and verified it works. was waiting for someone to find out what the "K013_1" error in the firmware was.
    1
    Hi.
    my device 176cx. lollipop 5.0. Only run at black screen (fastboot and adb)

    1. update.zip delete first 2 line. ok.
    2. update.zip goto microsd card. ok.
    3. open fastbboot menu.
    4. start launcher.bat.

    error:


    ***********************************************************************
    FASTBOOT TETHERED RECOVERY LAUNCHER 05-16-2015-PTR
    ***********************************************************************

    =======================================================================

    DEVICE STATUS: FASTBOOT-ONLINE

    DEVICE INFORMATION: Baytrail024D1F20 fastboot

    =======================================================================

    copy needed files to our device
    sending '/tmp/recovery.zip' (3477 KB)...
    FAILED (data transfer failure (Unknown error))
    finished. total time: 5.131s
    sending '/tmp/recovery.launcher' (400 KB)...
    FAILED (command write failed (No such device or address))
    finished. total time: 0.022s
    we need to stop logcat before replacing it
    ...
    FAILED (command write failed (Unknown error))
    finished. total time: 5.010s
    sending '/system/bin/logcat' (178 KB)...
    FAILED (command write failed (No such device or address))
    finished. total time: 0.017s

    issue fastboot oem "stop_partitioning" command to start cwm recovery:
    ...