yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] lambdadroid:
Yes, your Linux version is working fine (and that's what I used first) - the previous public trial release used the following commands (if I read the script correctly). This is also the same your script is doing with trigger 4 from what I can tell (and is working fine for me):

fastboot flash /tmp/recovery.zip ./recovery.zip
fastboot flash /tmp/recovery.launcher ./recovery.launcher
fastboot oem start_partitioning
fastboot flash /system/bin/logcat ./recovery.trigger.new
fastboot oem stop_partitioning
[MeMO Pad 7 General] vampirefo:
Look at the order of commands yours is wrong, you are trying to start oem command before flashing recovery, not going to work.
[MeMO Pad 7 General] lambdadroid:
I took that directly from the new release of [MENTION=4821597]social-design-concepts[/MENTION], he changed this for the new release from what I can tell:

if /i %OEMTRIGGER% == "/system/bin/logcat" ( echo we need to stop logcat before replacing it)
:: See here, this is before the stuff is flashed
if /i %OEMTRIGGER% == "/system/bin/logcat" ( "%PLATFORM_TOOLS%fastboot" oem start_partitioning)

echo copy needed files to our device
"%PLATFORM_TOOLS%fastboot" flash /tmp/recovery.zip %RECOVERY%
"%PLATFORM_TOOLS%fastboot" flash /tmp/recovery.launcher %LAUNCHER%

"%PLATFORM_TOOLS%fastboot" flash %OEMTRIGGER% %TRIGGER%
echo.
echo issue fastboot oem %OEMCMD% command to start cwm recovery:
"%PLATFORM_TOOLS%fastboot" oem %OEMCMD%

Anyway, using the old order doesn't fix the issue, it is still not starting the recovery so this is at least not the only issue with the new version.
[MeMO Pad 7 General] vampirefo:
I haven't looked at sdc latest version, nothing appears to be wrong with older version, for myself I run a complete bash version.

I will look at sdc latest version when, I get time. So something in this version prevents recovery from launching, can you adb?
[MeMO Pad 7 General] lambdadroid:
What exactly do you mean with "can you adb"? adb devices doesn't show anything if that answers your question, not that experienced with Android stuff yet so not completely sure.
[MeMO Pad 7 General] vampirefo:
adb shell

adb devices

lsusb
[MeMO Pad 7 General] lambdadroid:
Here's what I got (pretty much as already said, not working):

linux@mint ~/android/IntelAndroid-FBRL-07-12-2015/linux $ ./launch.sh
target reported max download size of 536870912 bytes
sending '/tmp/recovery.zip' (3623 KB)...
OKAY [ 0.211s]
writing '/tmp/recovery.zip'...
OKAY [ 0.063s]
finished. total time: 0.274s
target reported max download size of 536870912 bytes
sending '/tmp/recovery.launcher' (817 KB)...
OKAY [ 0.073s]
writing '/tmp/recovery.launcher'...
OKAY [ 0.043s]
finished. total time: 0.115s
...
(bootloader) Start partitioning

OKAY [ 0.058s]
finished. total time: 0.058s
target reported max download size of 536870912 bytes
sending '/system/bin/logcat' (425 KB)...
OKAY [ 0.054s]
writing '/system/bin/logcat'...
OKAY [ 0.042s]
finished. total time: 0.097s
...
(bootloader) Stop partitioning

OKAY [ 0.043s]
finished. total time: 0.043s
linux@mint ~/android/IntelAndroid-FBRL-07-12-2015/linux $ adb shell
error: device not found
linux@mint ~/android/IntelAndroid-FBRL-07-12-2015/linux $ adb devices
List of devices attached

linux@mint ~/android/IntelAndroid-FBRL-07-12-2015/linux $ lsusb
...
Bus 009 Device 019: ID 0b05:7771 ASUSTek Computer, Inc.
...

launch.sh:

#!/bin/bash
fastboot flash /tmp/recovery.zip ./cwm.zip
fastboot flash /tmp/recovery.launcher ./recovery.launcher
fastboot oem start_partitioning
fastboot flash /system/bin/logcat ./recovery.trigger
fastboot oem stop_partitioning
[MeMO Pad 7 General] vampirefo:
Just tried IntelAndroid-FBRL-07-12-2015.7z via linux, it makes no attempt to load recovery (recovery.zip isn't extracted), twrp or cwm, I would recommend using older version until it's fixed.
[MeMO Pad 7 General] social-design-concepts:
[MENTION=2472806]vampirefo[/MENTION]

The order of oem start_partitioning shouldn't matter it's only used to stop logcat so it can be replaced I moved it to the top because its the proper order on how you would do if you were actually going to repartition an older devices init.rc I reviewed had a call in oem start_partitioning that mounted the root fs / as rw so that's why the order was changed. It just needs to come before replacing logcat oem stop_partitioning is what restarts logcat or partlink

[MENTION=6833678]cyandro[/MENTION]

Could you try with old trigger binary and new launcher and if the results the same try with new trigger and old launcher.
[MeMO Pad 7 General] lambdadroid:
Unfortunately I got the same problem with each of these:

Old trigger, new launcher (not starting the recovery)

New triggger, old launcher (not starting the recovery)

Old trigger, old launcher (obviously working)
[MeMO Pad 7 General] social-design-concepts:
Hmm thanks weird not sure why it works on the three I have I'll explore

Does the screen display the debug prompt and freeze or just does nothing?
[MeMO Pad 7 General] vampirefo:
Correct doesn't matter which way it's tried both the trigger and launcher causes failure., doesn't even stop droidboot, so all fastboot commands remain.
[MeMO Pad 7 General] social-design-concepts:
Thanks that's what I needed to know there is only two changes common to both binaries so should be easy to figure out which of the two it is.
[MeMO Pad 7 General] vampirefo:
They work on trigger 3 not trigger 4, your devices use trigger 3 correct?
[MeMO Pad 7 General] social-design-concepts:
The dell works with all 4 the Lenovo works with T1 T3 and T4 the iview I only use to check landscape so only test it against T3

Do the binaries delete them self when you check when it doesn't start?
[MeMO Pad 7 General] vampirefo:
No, I guess we need to get a windows guy to test it, just tried trigger 4, works on my dell, but doesn't work on my nextbook with latest binaries, so very weird.

When you test, tether my droidboot should give you same results I get.

I tried to tether dell 3830 but no go on my nextbook, going to try 7840 next.
[MeMO Pad 7 General] social-design-concepts:
Waiting on nap time then I'll explore so it a lollipop related issue that should help me figure it out

---------- Post added at 04:03 PM ---------- Previous post was at 03:56 PM ----------

You tried to tether droidboot on the dell? if so lollipop droidboot won't load on KitKat shared libs that's why I had to create a new tethered_droidboot binary so I can delete kitkat ramdisk /system/bin and /system/lib and replace them with Lollipop bin and libs
[MeMO Pad 7 General] vampirefo:
I tried to put dell on netbook, ie KitKat on lollipop.

Anyway 7840 same as my nextbook failed with new binaries. So looking for lollipop droidboot that can use new binaries.
[MeMO Pad 7 General] acadj:
Does screen on your me176cx flicker for a split second when booting up?

This flicker only happens once and only on booting up. So every time I power up the tablet it flicker for a split second. After that it works OK.

This haven't happened on KitKat.
[MeMO Pad 7 General] social-design-concepts:
My Lenovo does this if I hit the power button after disconnecting the power cord when powered off. I wonder if its similar I'll check next time I turn it on. I think off-mode charging is handled through the efi loader app where before it was handled through kernel.img (boot.img , recovery.img , fastboot.img / droidboot.img) what ever state the device was in when powered off.

Another suspect could be that the device is never really completely shutdown / off just in a really low level state and when you power on it turns off completely for a fraction of a second to reestablish the chain of trust for secure boot.
[MeMO Pad 7 General] zapz:
So, is the new update safe to install if I'm rooted? And if it can be updated like that and the root will be lost, will re-rooting be possible? Anyone tried it?
[MeMO Pad 7 General] lambdadroid:
I wasn't able to install the update when I was still rooted, had to install a clean firmware first. After the update you can just root again without any problem, though. See http://xdaforums.com/showpost.php?p=61926393&postcount=2587
[MeMO Pad 7 General] Alexadro:
so you can even ordinary (GRUB4DOS) give a simple view script

root (hd1,0)

chainloader /bootmgr

boot

He will start the boot (BootMgr ) (in XP was (NTLDR)), and he has the processor into 64-bit mode and will launch itself on Windows.
[MeMO Pad 7 General] Mis012:
32bit Windows

Okay, if you say it will not find Windows 32bit efi binary, guess why? Maybe because is searches for bootx64.efi which is obviously not present?

So, method one: rename the bootia32.efi or whatever is the exact name like, to bootx64.efi

And method two: place the bootx64 from 64bit Windows to respective folder in 32bit Windows.

It is only an Idea, it may not work. But it should not kill you if you try it }:)
[MeMO Pad 7 General] Karvenry:
I get an error when installing your Kitkat to my Lollipop ME176CX
[MeMO Pad 7 General] lambdadroid:
KitKat...? You need to have Lollipop already if you want to install the new update for Lollipop.
[MeMO Pad 7 General] Karvenry:
Ok flashed the fresh Lollipop. But the OTA update gives me an Error that it's for K013 and my unit is K013_1

please help

Got it workin. Changed the value of the unit from the script from K013 to K013_1

Didn't thought that it would work
[MeMO Pad 7 General] vampirefo:
No this is not how live USB grub works, that is old installed version of grub, will not work.

Also I won't be trying windows, will only be testing Linux.

---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------

Such stuff may work on windows computer but not on Linux, rename an apple to banana, Linux will still see its an apple. You can try all these little tricks when you get your tablet back.
[MeMO Pad 7 General] Mis012:
I was talking about UEFI, not linux. The OS doesn't matter here. As someone said, UEFI will boot 32bit Windows if you add a boot option pointing to it. But UEFI will not boot it by itself beacouse it only looks for bootx64.efi, which is not present. If you rename it, UEFI will find it and will try to launch it. In both stories, UEFI will try to launch it. In first story, it will work. We can pelemize if it will work or not and why. But if we will try it, we will know if it works or not with 100% accurancy.
[MeMO Pad 7 General] vampirefo:
Like I said you can try when you get your tablet back, will not work in my situation.

My tablet requires 64bit.
[MeMO Pad 7 General] thebulletfromhell:
Following the apple banana imagery, renaming the file is the equivalent of going to the supermarket and swapping the price tag of the apple box and the banana box.
[MeMO Pad 7 General] social-design-concepts:
In regards to the uefi loader rename it's actually talked about in a few uefi guides when the problem of a fixed loader name is used.

I say in the past month I've seen it in about 3 out of 5 documents on uefi bootloaders. Most of the times they are referring to getting Linux to load on a device looking for the windows efi bootloader naming the Linux efi bootloader to the name of the windows efi bootloader in EFI\Boot.

Take the Lenovo the \EFI\BOOT\bootia32.efi is actually a renamed copy of \EFI\Intel\efilinux.efi
[MeMO Pad 7 General] thebulletfromhell:
That is true, however in those cases the device are capable of booting the custom UEFI image, just hardlocked down through filename. Baytrail Atom only comes with a 32 bit UEFI, so it won't boot x64 EFI whatever you do.

However, grub2 compiled for 32 bit UEFI can boot an x64 kernel. For windows, you're stuck with 32 bit, not that it is a bad thing. This tablet only has a gig of RAM, and 64 bit OS uses more RAM in general. Its only ~150mb IIRC, but that's 15% of our available RAM
[MeMO Pad 7 General] Mis012:
Maybe you didn't notice, but we have 64 bit UEFI, which is capable of booting 32bit efi bianries, but does not offer them to you as boot options. And don't swap x64 with 64bit, this is why uninformed people are talking about 86 bit or x86 bit, which doesn't exist.

And 64bit Windows should work faster with our 64bit processor, however it lacks a lot of drivers and seems to be laggy.
[MeMO Pad 7 General] thebulletfromhell:
Can you provide a source on that claim? At the very least, only a few Intel Baytrail NUC are officially confirmed to have x64 EFI. In this thread, the only one making it is you, and honestly mate, from your previous posts, you're not exactly the most informed about basic workings. Complaining about people messing up x86 and 32 bit, when you're spreading misinformation all the same. Hello pot, this is kettle, you're black.

>And 64bit Windows should work faster with our 64bit processor

8/8.

The only significant performance boost x64 provide right now is the ability to address more than 4gb of RAM on Microsoft Windows system, and the ability to address 64 bits of data at a time (important for number crunching like superpi, etc...).

From posts like this

>I always thought 64bit Windows is better the 32bit, why would anyone want 32bit when 64bit works? I am not sure if 32bit OS will be less lagy. , your credibility isn't exactly up there.

I don't agree on the elitist attitude XDA has taken since ~2008 (around when android and phone rooting became mainstream), but this is one of the case that made it hard to disagree.
[MeMO Pad 7 General] vampirefo:
That is completely different than renaming a 32 bit to 64 bit, can the Lenovo use a 64 just by renaming it efilinux.ef? no neither could my 64 bit run a 32 bit renamed 64 bit.

Anyway I did go this route,, I tried https://www.happyassassin.net/fedlet-a-fedora-remix-for-bay-trail-tablets/ this is 32 bit, no way shape or forum will it boot on my nextbook, renaming made zero difference it's a 32 bit and nothing changed that for my tablet. The 64bit Fedora boots right up.

Adamw didn't just rename to 64 to 32, cause it doesn't work on his tablet, his tablet cant boot 64 bit only 32 bit.

A computer is different than a tablet, I have both 32bit and 64 bit running on my computer.

I know there are several tablets that boot 32 bit, and a few that boot 64 bit, haven't seen one that can boot both, my guess that would be on high end tablet, not a cheap one like I have.
[MeMO Pad 7 General] social-design-concepts:
Yeah the windows tablets I configure at work defiantly fall into the high end category well their quote unquote enterprise class devices.

until u know one had tested it, no one was saying that renaming a 32bit efi to a 64bit efi made it 64bit but there are devices that abuse the efi spec that are able to load both 32bit and 64bit efi applications even though they are 64bit firmware.

If Lenovo sticks to the original leaked lollipop ota its firmware will get updated to 64bit
[MeMO Pad 7 General] therealprof:
No, the largest advantage is actually that with x64 there're lot more registers to work with so the CPU can keep much more data in flight rather than having to "spill" all the time. On certain workloads this will create a huge speedup, on average it's usually and advantage in the order of 15% compared to 32bit code.
[MeMO Pad 7 General] Alexadro:
Information on (Olegaslav) with offline 4PDA Russa

For a start, a bit of information:

So, I made out a file from esp.img firmware contents folder EFI and BIOS update file for BiosUpdate.fv!

In Inside the folder is a folder EFI BOOT, so here it is boot efi: bootx64.efi

With never a question: what gives us, if we replace the file such as: bootia32.efi?

Also in the folder is a folder EFI from Intel, it has 2 EIF file: efilinux.efi and warmdump.efi

And yet, change the extension from the file on BiosUpdate.fv bin, turned, and there he is UEFI

He opened his program UEFITool, very interesting content! Bunch of settings, parameters, information! Shorter study and learn!

Another interesting infa: have a tablet Lenovo Yoga Tablet 2 (64-bit quad-core Intel® Atom ™ Z3745 (1,86GGts)

It comes in 2 versions: Android-windows (x86), and so in his file in the folder BOOT esp.img is: bootia32.efi

So it is still possible?

Attached files

http://4pda.ru/forum/dl/post/6560161/UEFITool_0.20.4_win.7z

http://4pda.ru/forum/dl/post/6560164/ESP.img.zip

---------- Post added at 06:17 PM ---------- Previous post was at 05:45 PM ----------

On our unit anyway Wimdows x64 useless. For Ubauntu need is yes. In any case, you and x64 UEFI and x32 EFI
[MeMO Pad 7 General] lambdadroid:
So the UEFI update in the OTA update ASUS released a few days ago didn't break booting other stuff, I was able to boot Lubuntu on it without any problems. So whatever they've changed, it's not related to booting custom things. The interesting thing is that Secure Boot (which would normally only boot signed stuff on the device I think?) is actually disabled on the device so we can actually boot anything we want.
[MeMO Pad 7 General] vampirefo:
So you can flash modified boot.img and recovery.img?
[MeMO Pad 7 General] :
Not sure if this has been posted but here's the Changelog for the latest Lollipop OTA Update (2015/07/20):

1. Fixed GPS issue.

2. Fixed time delay issue

3. Improved stability

4. Fixed App icon can’t be removed after uninstall app.

5. Improved browser capability.

6. Improve IME.

7. Asus Splendid: Reading mode change to Bluelight

Also a full system Update.zip for the latest firmware has been added to the device's download page:

KitKat to Lollipop - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.24_KK-user.zip

NOTE: Make sure your on the last KitKat firmware v3.2.23.201 before applying the above update.

Lollipop to Lollipop - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.24-user.zip

Source - http://www.asus.com/uk/Tablets/ASUS_MeMO_Pad_7_ME176CX/HelpDesk_Download/
[MeMO Pad 7 General] DrBatson:
This kitkat to lollipop update is news to me. Could it be... that it solves the "unable to upgrade because of wrong bootloader" problem? Well hope never dies.:)
[MeMO Pad 7 General] lambdadroid:
No, I don't think so - at least not directly. In the BIOS settings (when I press F2 on startup) it's displaying Secure Boot is turned off, however it is still turned on for the Android bootloader. I guess to make that work we would need to replace the Android bootloader with a custom one? Not experienced with this whole booting stuff so someone else will probably know it better than me :P
[MeMO Pad 7 General] zapz:
I unrooted the device (this is the only thing that i modified in it) and tried to run the new update over OTA and it failed. The good part is that the update is still downloadable from System Update no matter how many times i re-try, so I could check the error that it gives me. The error is the following:

Verifying current sistem...

"/system/bin/install-recovery.sh" has unexpected contents.

E: Error in /cache/dlpkgfile

(status 7)

E: Install of /cache/dlpkgfile failed with status 1

Installation aborted.

Any idea about this? I really don't want to reinstall the whole OS all over again...had so many problems with this tablet and had to factory reset it so many times and also take it to warranty (because of the freeze and reboot problem) that I couldn't even use it properly ever since Lolipop came out. Don't wanna start over again with it.
[MeMO Pad 7 General] lambdadroid:
You could try to install the clean firmware first before installing the update, or just install the new firmware with the update from ASUS directly. I updated my rooted device like I explained in http://xdaforums.com/showpost.php?p=61926393&postcount=2587
[MeMO Pad 7 General] social-design-concepts:
That has to be the biggest derp ever disable SecureBoot in the UEFI but have a loader.efi that is locked down. One of the users that is experienced with booting from the thumb drive should try booting the minnow board max kernelflinger.efi from android-ia if it loads then you have an bootloader to use for booting custom ROMs and Recoveries.
[MeMO Pad 7 General] TalhaGirgen9:
Overall...

We Can Unlock Bootloader And İnstal Custom Roms Or Recoveries Or Custom OS'es On Me176C/CX :D

İf We Can You Make A Guide To How:)

P.S = Sorry For Noobish Question And Sorry For My Bad English :D
[MeMO Pad 7 General] social-design-concepts:
If someone can confirm that the android-ia kernelfliger.efi (the 64bit version of course) will at least boot from a usb disk it shouldn't be an issue placing it in the esp maybe under EFI\AndroidIA\kernelflinger.efi and the use efibootmgr to add it and optional set it to the default boot option.
[MeMO Pad 7 General] Mis012:
[do not ignore again]

So why you all ignored my posts about using bootloader from android-ia? And we do not need to use the one from Minnowboard, because there is also android 4.4.2 GENERIC image. Which should theoreticaly also have bootloader :) And if we are lucky, the bootloader may even be open-source. So anyone interested can backup his emmc, install Intel's android, and start making custom ROM.
[MeMO Pad 7 General] social-design-concepts:
You only want the kernelflinger.efi from it not the rest of the android build just its bootloader.

I'll talk to [MENTION=2472806]vampirefo[/MENTION] directly about testing it doesn't really benefit him his device can natively boot unsigned images but he's always down to help the community.

kernelflinger is open source its newer than the 4.2.2 which was gummiboot

kernelflinger offers some advanced features as well I only suggested the minnow-board maxx build because its prebuilt so its easy to test as of now you can only build it against android-ia source until cyanogen gets it completely integrated into their build system. I'm actually running a self built copy on my build box at home and booting userfastboot and twrp from it.
[MeMO Pad 7 General] lambdadroid:
Does someone know which wifi device/chip or whatever the device is using? It wasn't recognized by any of the Linux distributions I booted, nor does it show up with `lspci`, `lshw` or `lsusb`.
[MeMO Pad 7 General] sutekh137:
So, should I be able to flash this update (Lollipop to Lollipop)? Because I tried, and all I got was the dead android Error! screen when I did:

-- Copy the "command" file to /cache/recovery, the command file that says to use /data/update.zip to flash

-- Copy the Lollipop to Lollipop update file downloaded from the link above to /data/update.zip.

-- Do "adb reboot recovery"

All I get is the dead android, and I can't get out of that with Vol+/Power nor Vol-/Power.

So, I still can't install the update without going back to stock system (I am rooted and have some apps frozen, etc.) There was a time that I thought we could flash updates using this file-based method and it would go through even if we were rooted, etc. Is that no longer the case? Because trying to manually flash this file results in the same error screen as when I tried to do it OTA... Help?

Thanks,

sutekh137
[MeMO Pad 7 General] lambdadroid:
You can try installing the update with the temp CWM recovery (http://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096) instead of the inbuilt recovery, that solved the problem for me.
[MeMO Pad 7 General] sutekh137:
Thanks, that is cool, didn't realize we could use that for flashing updates (I did use it to root...)

But when I try to update from external SD card and point to the update zip file, I get:

This package is for "K013" devices, this is a "K013_1".

So, the installation aborts. I have seen some posts about the whole _1 issue -- is there a way I can make this work?

Thanks,

sutekh137
[MeMO Pad 7 General] lambdadroid:
Not exactly sure but I guess you could just remove the check for the device from the update, open the zip file go to META-INF/com/google/android/updater-script and remove the first line there, then copy it to your device again and try updating with the new zip.