yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] daspex:
if you are on lp you could try to install a backup of lp posted i think from jearbeer somewehre in the threads for me176c/x with cwm/twrp temp recovery
[MeMO Pad 7 General] T_I:
Indeed, the temp TWRP solution worked (07-24-2015 version, option 4, T4 method), once I had Windows 10 booted (free upgrade, don't use windows on the laptop, but it was still claiming space, was useful for once) and followed this xda guide to get past the K013 vs. K013_1 issue.

However, I decided to take the newest firmware (24), but now I have issues with facebook. Not that I am a lot on there, but the sames I play on the tab want the link. FB fails to restore via titanium backup (39.xxx and 41.xx ) or clean install via play store (41.xxx). Will try a 17 install via the same method.
[MeMO Pad 7 General] daspex:
i read about this fb error other users have had same issues with googleplay,i use titanium backup just to deinstall and reinstall system-apps.to save and restore settings from apps and accounts i use the gobackup app this works in most cases for me.i use win7 ultimate the upgrade to win10 has failed i will wait a few weeks and then i'll try it again
[MeMO Pad 7 General] caiefh:
hi where i can find the cache/recoveryfolder?i cant find it...
[MeMO Pad 7 General] caiefh:
no luck , still cant update, it says no command in recovery...pls help
[MeMO Pad 7 General] jedial23:
make wipe of everything then star over. My table works without lag, it's running perfect....

Enviado desde mi K013 mediante Tapatalk
[MeMO Pad 7 General] daspex:
use the cwm/twrp temp recovery and install a clean backup by following the instructions on the cwm/twrp temp related thread
[MeMO Pad 7 General] janmatys:
Hi 2 all,

is there a way to downgrade back to 4.4.2 (4.4.4)? I have many bad experiences with LP on my ME176CX and want the previous stability back so if someone could help me I will be appreciative. Send a PM with the steps or write it here - THX.

Sincerely, Jan

PS: Btw updates NOT working for me either. "No valid installer medium found" in BootLoader... (or something like that message)
[MeMO Pad 7 General] thebulletfromhell:
No. Take it to a service center and ask nicely, the base board is on KitKat
[MeMO Pad 7 General] janmatys:
No option for me mate cause what I will tell them (please, swap my stuff with another - nonsense). But I heard/read somewhere that downgrade IS possible somehow... (think from "jerbear294" user). On the other hand it looks like Im NOT the only user with that upgrade problems??? When I tried to upgrade the device restarts itself, jump to BootLoader and write something like "no valid installer medium found" ... how its even possible to get a message like that???

Sincerely, Jan
[MeMO Pad 7 General] thebulletfromhell:
Jerbear isn't a dev as far as I know, and the Lollipop upgrade included a complete bootloader change as well as repartitioning. There is no way of downgrading, at least for now. Just brick the thing, take it to a service center and ask them not to upgrade the firmware when they install in a new board.
[MeMO Pad 7 General] therealprof:
Of course a downgrade can be done (without JTAG), it's just that no one has packaged a nice one-click solution so it requires some experience to do. Just check the ME572C thread about rooting; for some strange reason they're doing that via the huge and crazy detour over a KitKat downgrade; a similar approach (including the repartitioning) should work for the me176c as well...
[MeMO Pad 7 General] thebulletfromhell:
The ME572C also had access to important bootloader files that we do not have, as well as the raw firmware file for the factory ASUS flash tool. Exact same reason why the Zenfone first gen could go up and down freely between Jelly Bean, KitKat and Lollipop. DNX mode for this device is unlocked, but there is nothing to flash/boot
[MeMO Pad 7 General] therealprof:
I think the ifwi files should be available somewhere (if they're actually different from the ME572C ones, not sure about that), probably even from Intel themselves. The ME572C firmware is not available as a raw flash image, only the full upgrade files (same as for ME176C) which are modified by some Russian guys to include su and other SuperSu.apk (which breaks the image signature and hence requires a different approach for installation to avoid the signature check). The only thing I know is missing at the moment is the old partition map for the ME176C KitKat system.
[MeMO Pad 7 General] thebulletfromhell:
Ifwi only comes with major update that actually change how the bootloader emulator works (like Lollipop for us). The Zenfone had it for BL unlock, and the ME576C had one with a KitKat update. The ME576CL has a full ASUS Flash Tool raw firmware, which got backported to the 576C from what I can derive from google translate
[MeMO Pad 7 General] therealprof:
ifwi is short for "Integrated Firmware Image" and is actually provided by Intel as a binary blob, cf. http://download.intel.com/support/edison/sb/edison101presentationfromidfforthecommunity.pdf . This version is managed by the system so it can be upgraded and in that case needs to be part of the software update image.

From what I understand it can be used to enforce certain behaviour of the booted system, like making sure that only a Secure Boot is used (i.e. the bootloader is signed and locked). I'm not quite sure what its relation is to UEFI but it seems that even Intel SoC systems using UEFI have an IFWI but that could actually be embedded in the UEFI.

It might have but this is not used in the threads telling you how to downgrade the ME576C to KitKat. Those are (vastly simplified): downgrading the IFWI version, repartitioning the device and then use droidboot to flash a (modified for root) regular full system image as provided by ASUS. I'm not quite sure why they're downgrading to KitKat at all when the goal is to root Lollipop as the (modified) Lollipop full system image (also provided by ASUS) can be flashed using the exact same method.
[MeMO Pad 7 General] thebulletfromhell:
From what I understand, its: IFWI (lowest level) -> UEFI -> Droidboot (Fastboot emulator on intel platforms, sort of like a bootloader). KitKat skipped UEFI, or it wasn't user accessible.

IFWI - low level flashing direct to device, through the DnX mode. No signature enforcement what so ever, but it only flash/boot the bootloader. Fastboot interface.

UEFI - self explanatory

Droidboot - An emulation of the traditional android's fastboot interface. On tabs, the android boot setting inside the UEFI/BIOS config hard boot this, while the WIndows 8.1 setting look for bootx64.efi on connected devices. Signature enforcement is here

>PDF linked

That's for the Edison (intel's dev board). It could be the same as it only cares about the SOC

>Downgrade

That was the old method. Eventually they simplified it and just flashed the KitKat IFWI
[MeMO Pad 7 General] therealprof:
No, it seems that UEFI (if available) includes IFWI, if it is not available then IFWI works standalone. The ME176C always had UEFI, not sure about the ME576C though. Droidboot is a bootloader.

IFWI does not have a fastboot interface and I think it can used with signature enforcement, too.

Droidboot is a bootloader, bootx64.efi a UEFI application which usually is a bootloader.

Yes, I know. I put it in for illustration because it works exactly the same with the IFWI and DnX mode as the ME576C does.

I haven't seen this simplification yet from other/"official" sides, that's what I've been proposing for a week now. The closes thing I've seen in this direction is the recovery method for a killed bootloader someone proposed with the xFSTK Downloader in here: https://translate.googleusercontent...t=2240&usg=ALkJrhiu5nbkIOIpzNiNfDhMCvchemso-A

Actually it also works with the manual xfstk tools e.g. the Downgrade.cmd is using but the GP flags are incorrect there, should be 0xEEEEEEEE instead of 0x80000007 to fix a device hanging at the USB logo.
[MeMO Pad 7 General] thebulletfromhell:
1. Run adb reboot dnx. It'll show up on fastboot, and will only accept flashing the bootloader, and booting an image. That's the board's "bootloader" (in the sense of a smartphone. Its not terribly accurate, but its been in use since the WinMo day so I'll just go with that). It accepts anything you throw at it, but I don't have a "hacked" image to boot. Booting into a blank image soft brick it and needs a hard restart.

2. Droidboot runs on top of UEFI, and it boots Android, as well as emulate the function of a traditional android bootloader (including fastboot). Its a bootloader in the traditional sense. Whatever gets flashed here get written onto the mainboard through the capsule (included in major firmware updates). Signature verification is here. Its not a traditional UEFI bootloader, but it seems to be built into UEFI. In the "BIOS" setting, there is two mode: Windows 8.1 and Android. Windows 8.1 search for bootx64.efi on connected devices, while Android load straight into Droidboot

Needed to clarify that. Calling the flash interface the bootloader isn't really correct, but that came from way back in XDA's windows mobile day, and I'm not sure what else to call it.

The downgrade script's TLDR is:

1. Flash KitKat IFWI (and associated files)

2. Flash partition table/nuke existing partitions

3. Flash recovery and fastboot again.

Before after flashing the old IFWI, they had to flash the entire KitKat package. Now, it just flash the bare minimum to run TWRP and flash the pre-rooted firmware.

TL;DR for all of this:

Intel Android tabs are just Intel Atom boards with some trickery in the UEFI to chainload Android seamlessly and emulate the typical functions of an Android bootloader
[MeMO Pad 7 General] therealprof:
I think you have most of your information right but there're a few mixups. IIRC the ME176C uses UEFI to boot Android (or Windows) while the ME576C seems to use a different approach without UEFI (at least the usual tricks to get into UEFI do not work there and there don't seem to be any UEFI references). This also means that the flashing process is vastly different, on the ME576C one can get directly into DnX mode and use tools like Intels xfstk downloader to flash an IFWI and control the boot while on the ME176C the IFWI is included in the UEFI and as far as I know the only way to do an upgrade is to replace the whole UEFI.

Also on the ME576C the booting process seems to be different and I haven't seen anyone replace recovery mode with TWRP (unlike on the ME176C) yet and the whole rooting trick seems to rely on a replaced droidboot which removes the signature check to allow flashing of any full Android system image; well, likely the only reason for the complicated KitKat downgrade was to circumvent the version check which does not allow an upgrade to the same software version again...
[MeMO Pad 7 General] pcantare:
Hello everybody, I've got the following error:

I:Install package /data/update.zip

update_package path=/data/update.zip

Finding update package...

I:Update location: /data/update.zip

Opening update package...

sysutil: Unable to open '/data/update.zip': Permission denied

E:failed to map file

E:Install of /data/update.zip failed with status 2

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

Installation aborted.

E:Delete /data/update.zip failed (Permission denied)

I:Saving locale "en_GB"

Any idea?

Thanks

Paolo
[MeMO Pad 7 General] thebulletfromhell:
There is a possibility the ME576C might have used a similar system to our KitKat, loading Droidboot straight from IFWI skipping UEFI, but its a bit unlikely, as their Lollipop also needed a repartition (to accommodate for the new /efi partition possibly. Check the partition.tbl file inside the update archive)
[MeMO Pad 7 General] therealprof:
It's hard to say what the partitions are used for as there're a quite a lot (19) but none of them is called EFI. Also the image itself does not contain anything with the name efi in it but it does contains a lot of other images and an ifwi update.
[MeMO Pad 7 General] thebulletfromhell:
In a traditional EFI system, there is a 200mb boot partition containing all necessary files (bootmgr for Windows, Grub, etc...). Anything like that?

Also, if it has an ifwi update (and a capsule.bin, or just capsule) then there should be UEFI.

From the ME176C's partition.tbl:

add -b 292904 -s 67584 -t efi -u C12A7328-F81F-11D2-BA4B-00A0C93EC93B -l ESP -T 0 -P 0 /dev/block/mmcblk0

The ESP partition is the EFI boot partition
[MeMO Pad 7 General] therealprof:
No, boot is a 32M partition on flash and here are the images contained in the system image:

10748632 Mär 22 2011 boot.img

13486808 Mär 22 2011 droidboot.img

16770 Mär 22 2011 file_contexts

798579 Mär 22 2011 ifwi.zip

2351 Mär 22 2011 modem_nvm.zip

2399 Mär 22 2011 partition.tbl

18191594 Mär 22 2011 radio.img

11473624 Mär 22 2011 recovery.img

58584 Mär 22 2011 splashscreen.img

No, that's what I've been telling you the whole time, IFWI is completely independent from UEFI and I have the suspicion that an Atom SoC which uses UEFI might even have it embedded rather than a separate flash area.

inflating: bom-token_77.141.bin

inflating: dnx_osr.bin

extracting: version

inflating: ifwi_77.141.bin

inflating: dnx_fwr.bin

There's no partition of type efi in the table, only data.
[MeMO Pad 7 General] thebulletfromhell:
Boot partition - linux terminology, referring to a partition that is traditionally used to store kernel, initrd, and stage 2 of Grub (or syslinux/LILO if you used that)

Boot = Kernel location in an android device

ESP = EFI System Partition. Modern equivalent of a Boot partition, also used by other UEFI compliant operating systems.

Open up partition.tbl, look for ESP. If it exist, there is UEFI.
[MeMO Pad 7 General] therealprof:
That's exactly what I said: it does not exist.
[MeMO Pad 7 General] thebulletfromhell:
You said >There's no partition of type efi in the table, only data.
[MeMO Pad 7 General] therealprof:
Yes, that's what I said. Let me clarify then: There's neither a partition of type efi in the table NOR a partition named ESP.
[MeMO Pad 7 General] grdina:
Need help. :)

Hi all,

I am trying to update from ww_k013-12.10.17 to ww-12.10.1.24 and I am encountering this error

Finding update package

Opening update package

E: failed to map file

E: Install of /data/update.zip failed with status 2

Installation aborted.

Has anyone encountered the same error?

P.S. This thread is a blessing. Thanks to everyone who contributed.
[MeMO Pad 7 General] boredfish:
Only working with ROMs, not OTAs...?

Thanks to this thread I've managed to rescue my ME176CX, first to 182 CN then to 182 WW.

However, if I try to go further, applying the OTAs (191, 198 etc.) by using the same method, I get things started (little blue line up to ~20%) and then it crashes to the dead droid (and I'm left stuck with 182).

Some say there is a zip inside the OTA zip files but there isn't, so I am uploading the correct files.

Any help greatly appreciated.
[MeMO Pad 7 General] daspex:
[MENTION=6949286]boredfish[/MENTION]

i have had the same thing and the solution was to install a clean backup of the .201 version wich has been uploaded by Mis012 somewehre i think in the unbrick thread for our device by using the cwm-temp recovery.hope that will help.

regards

---------- Post added at 10:08 PM ---------- Previous post was at 09:54 PM ----------

@grdina

just search this thread with "failed status 2 " than you have all post's wich i think should solve your problem....
[MeMO Pad 7 General] boredfish:
thanks daspex I was just reading another posts about this full 201 rom by Mis012 but I can't find the correct thread, this guy Mis012 has 100s of posts.... perhaps you can point me at where I can find the full 201 please...??

(same as searching for "failed status 2".. tons of results but no solution...!?)
[MeMO Pad 7 General] daspex:
ok i will try to find it for you just stay tuned...:)

in fact most of us have had the same problems and had to read tons of posts and for most of us it's a long time ago and it's hard to remember wich threads and postings lead to the specific solution.
[MeMO Pad 7 General] boredfish:
Thanks I just found it (searching Google!), the post is at the top here http://xdaforums.com/memo-pad-7/general/asus-memo-7-me176cx-t2814046/page223

However I don't see comments on that file, whether it's good or not, so even though I am downloading now, I am a bit hesitant to flash the tablet.. don't want to brick it again.

---------- Post added at 10:16 PM ---------- Previous post was at 09:53 PM ----------

The download is a bunch of .tar and .tar.a (?) files in a 'clockworkmod' folder..... What am I supposed to do with these...? I hoped it was some nice ME176C-WW-X_X_X.zip file :(
[MeMO Pad 7 General] daspex:
this is the link from mis012 https://translate.google.com/transl...?s=&showtopic=584225&view=findpost&p=32744050

but i coudn't download but there is another one i will search wich one worked for me

---------- Post added at 11:43 PM ---------- Previous post was at 11:31 PM ----------

this link should be the right one: https://yadi.sk/d/63tXpfZzepTa6

---------- Post added at 11:47 PM ---------- Previous post was at 11:43 PM ----------

it is a normal backup file to use with cwm it works fine in my case after instlling it you have to change the language and that's it:)

---------- Post added at 11:57 PM ---------- Previous post was at 11:47 PM ----------

ok i've had a look at the page you told me and it's the second link i told you so it'll work:)
[MeMO Pad 7 General] boredfish:
thanks, I have also downloaded ClockworkMod ROM Manager in the hope to restore the backup, however upon launch it's started with weird questions such as 'you must install a custom recovery' and then whatever i click it says 'sorry K103 is not supported' ... so I am stuck. :confused:
[MeMO Pad 7 General] daspex:
just install the zip file withh cwm tmp recovery by using the backup trigger and that's it.

---------- Post added at 12:11 AM ---------- Previous post was at 12:03 AM ----------

look at this thread http://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096 and install the cwm temp recovery and adb drivers then do what i posted above

---------- Post added at 12:50 AM ---------- Previous post was at 12:11 AM ----------

after installing the adb drivers and cwm tmp recovery you need to install a root browser for the file system to cipy the clockworkmod folder to /data/media/ of your system directory then turn on the usb debug mode in the developer section of system settings if there is no dev section you must go to the device info it's the last section in the system settings menu and click i think seven times on the last entry this will unlock the developer settings then connect your device via usb to the pc and start the launch.bat in the cwm tmp recovery folder and follow the instructions then use the bacup/restore trigger and your device will boot into cwm recovery then select restore from internal sdcard and vote the 201 backup.
[MeMO Pad 7 General] boredfish:
thanks again, this is going to be helpful to others too! (even though strangely the majority of people seem to be able to go up from the 182 rom through the OTAs without any problems...).
[MeMO Pad 7 General] daspex:
i think it has to do something with the bootloaders version or touching the system by rooting or installing xposed modules in combination with mainboard missarchitecture who knows how asus designed this devices mobo and maybe they have built in different parts or versions of electronics.i remember that i rooted my device at first than i looked at the asus support page downloaded the firmware update than i had to copy it onto the internal sdcard like the asus support operater told it to me and nothing happens at all.so i came to cwm tmp unrooted my device and could install all the ota's up to .201.

after that i made a backup of my system and tryed to install the lolipop wich results into a softbrick then i installed the 182-cn version after that the 182-ww version and then i tryed to go up to .201 again wich faild from .191 on.then i took a look on my bootloader and it still have had the version .201 though i was on .182 this leads me to the idea to install a clean backup wich was uploaded by the guy mis012 and it works.(with cwm).then i tryed to lolipop my board again with the .17 version wich failed again.i haven't tryed the .24 version yet couse i'am afraid that it won't work and i'm tired to install my backup over and over again maybe i will wait until the bootloader is unlocked and a cm12 comes up.:crying:(sorry for gramma mistakes i didn't have to write in english since 30 years:))

now i will have a last cup of tea and then i need a few ours of sleep...:)
[MeMO Pad 7 General] boredfish:
Actually my intention was to install the OTAs because I wanted Lollipop, but if you say it won't work I don't see the point of going through possible further problems (took me days and days of reading to fix the tablet which by coincidence was bricked by misbehaving with that utility you mention "Intel Fastboot Tethered").
[MeMO Pad 7 General] daspex:
[MENTION=6949286]boredfish[/MENTION]

and could you install the .201 backup with the cwm tmp recovery?
[MeMO Pad 7 General] boredfish:
Haven't tried yet, especially after you said that Lollipop was a no-go even with 201.....

I am disappointed that there isn't a way to restore the tablet just as it came from the shop, get all new updates directly from Asus etc. etc. - I am not even interested in rooting!
[MeMO Pad 7 General] daspex:
ok.but i thought you are already rooted so you could make the restore of the .201 backup or did you get unrooted by installing the .182?the .201 versio runs pretty stable.
[MeMO Pad 7 General] boredfish:
Yes right now the tablet is rooted (with the zenfone root apk so I can root/unroot with one tap). I am now going to read your instructions again (thanks) and have a better look at that cwm tmp recovery stuff.

I know already that if I manage to go to 201, I will then attempt Lollipop just like you did and get in trouble again. If instead I succeed getting Lollipop I won't be able to get further OTAs so what's the point...
[MeMO Pad 7 General] daspex:
if you succeed to get lolipop you can still get further otas but if they will work who knows.many people who are even on the .24 lp version have issues and are not satisfied with performance and stuff others are happy with it.on the other hand if you are on lp it's a little tricky to downgrade.most of the downgraders fail so far as i know.if i where you i would stay on .201 and wait for the bootloader unlock and a custom lp rom from cm if they decide or some dev to built one.
[MeMO Pad 7 General] daspex:
never mind deleted
[MeMO Pad 7 General] boredfish:
Hello daspex,

If you're still there (so sorry to bug you again and also being late, I've been travelling two days) could you please give me a quick detail on these operations you've suggested (I want to go from my current 182WW - rooted - to .201 OTA).

> installing the adb drivers and cwm tmp recovery.

DONE, notice that running adb devices shows my tablet but the command fastboot devices shows nothing.

> copy the clockworkmod folder to /data/media/ of your system directory.

The clockworkmod folder has this structure

clockworkmod > backup > 2015-02-21.15.18.13 > bunch of .tz files

which folder should I copy?? (my tablet's /data/media folder is empty at the moment)

> turn on the usb debug mode.

DONE

> start the launch.bat in the cwm tmp recovery folder by using the backup trigger.

DONE, but....

> use the backup/restore trigger

... all I see are the menus 1 to 5 from screenshot i.e. four twrp_xxxxxx options and a cwm.zip option, where is the 'backup trigger' you mention??? I don't know what to press.

Many thanks again (if you're busy leave it, I don't want to waste your time!).
[MeMO Pad 7 General] daspex:
just hit the cwm.zip trigger.you also can try the twrp triggers landscape or so but in my case only the cwm trigger leads to success.then your device boots into cwm recovery mode and from there you pick the restore backup entry.you have to copy the clockworkmod folder itself to the rootfolder of your emmc /data/media.