yashsingh1/xdaforums huggingface dataset:
[Moto Z Play Questions & Answers] Aldgod1234:
I was talking about blur mode only.. or you may say bokeh effect or depth mode.
[Moto Z Play Questions & Answers] sillycat98:
I know, I was talking about the video the other guy posted. I hope someone can do what you ask, I would like to have the feature too.
[Moto Z Play Questions & Answers] Zeljko1234:
Yeah, my bad. My first association was vertical video.

You should check someone's profile and messages before call him a troll ;)
[Moto Z Play Questions & Answers] sillycat98:
I said you probably just assumed vertical video because of the orientation being called portrait, perhaps if you don't want to be called a troll don't post a muppet filled fake PSA when someone has a legitimate question? I don't care how many posts and thanks you have, that video is still a troll unrelated to the post.

On another note, I tried all of the zsl mods and modded g cams I can find, no luck with any of them. Most just crash on opening or crash when I click portrait mode. Has anyone tried a 8.1 rom to see if it's just the architecture? Maybe a hardware limitation?
[Samsung Galaxy J7 Questions & Answers] Lrdkenway:
Aosp is the best customization i ever seen . for the J7 it is Only be unofficial releases for the Aosp but There are AoSp dev s trying harder to make it stable for our j7 hats off to that guys. We know there is no official release means there is only unofficial customization with bugs but there is some Currntly Stable and its Can use for daily driver. Im like to hear what kind of AOSP roms your are Currently Using for Daily Driver. Thank you .
[Samsung Galaxy J7 Questions & Answers] kushi.:
Lineage os by smartass

Most stable aosp rom, i tried dot os but faced lockscreen bug so i moved to lineage, just turn off the ambient display and ur all set
[Samsung Galaxy J7 Questions & Answers] Lrdkenway:
Tried but there is a incall whats app problem .
[Samsung Galaxy J7 Questions & Answers] TomeGJ7p:
The ambient display is the worst on the port, probably the best lineage advice lol.
[Samsung Galaxy J7 Questions & Answers] Lrdkenway:
I think its hardware problem
[Samsung Galaxy J7 Questions & Answers] jimmytrivedi:
RR OS Beta 6

I tried more than 10 different ROM which is, Lineage OS, RR, Google Alpha, ENIGMA Rom, .Legend OS, Dot OS etc..

Actually, when I first time flash the RR Beta 6 version ROM and used 2 days, it was working very very fast with 1000 of customizations & smooth running also. But for testing purpose I tried different ROM, but I don't like it. And now when I tried to install same RR Beta 6, it is not working. Only Stable version is working.

Believe me that Beta 6 version is more stable, than the stable version.
[Honor 8 Pro  Questions & Answers] skotch:
Is anyone else still waiting??? I have an international version am in the US...

My current version is DUK-L09C900B122
[Honor 8 Pro  Questions & Answers] grizzlyspid86:
Go to play store, install firmware finder apps, search for your model, download firmware build number 8.0.0.360. If got newer build number search for full OTA.
[Honor 8 Pro  Questions & Answers] skotch:
The firmware finder app always comes back with not approved for my phone.
[MeMO Pad 7 Original Android Development] lambdadroid:
Version History

me176c-boot 0.3.0

me176c-boot 0.2.0

me176c-boot 0.1.0

Download: esp-0.1.0.zip
[MeMO Pad 7 Original Android Development] Nexive:
Succesfully flashed the new bootloader.

The android logo is showing up and booting after that.

Scrolling throught the boot menu is also working!

Thanks for doing this! :)
[MeMO Pad 7 Original Android Development] n30wav3:
wow. You have really outdone yourself here..... Considering this device didn't even had an untethered recovery at one point this is BIG!.... this opens up a lot more possibilities now for this tablet.... buddy you deserve recognition here
[MeMO Pad 7 Original Android Development] jerbear294:
It really is impressive how far this device has come. For a long while I was willing to accept that despite the unlocked bootloader, we would be stuck with ZenUI for the future.
[MeMO Pad 7 Original Android Development] Skyrimus:
Hi, i try boot in TWRP - error Failed to execute recovery (\android.efi): Unsupported, reinstall TWRP - it s work
[MeMO Pad 7 Original Android Development] lambdadroid:
So is everything working now? This could happen if you use a really old recovery and/or your (recovery) partition is corrupted.
[MeMO Pad 7 Original Android Development] f35suarezj:
will be possible to boot windows on the go (portable windows 10) from micro sd or a usb? maybe with a powered hub? (I made one with a normal hub, a diode and a usb cable and works as a charm)
[MeMO Pad 7 Original Android Development] jerbear294:
It's very much possible, but it won't work well at all due to the missing drivers.
[MeMO Pad 7 Original Android Development] jziggy101:
errors flashing

I have root access on the tablet but believe the bootloader is still locked & i was trying to load your bootloader.

I am having issues.

When I press Volume Down & Power I do not get a recovery menu but rather the tablet boots in an Android Safe mode. There are a limited number of apps available and the table has the word "Safe mode" at the bottom of the screen.

If instead I press Volume Up & power i get a different menu that includes Normal Boot, Power Off, Reovery Mode then Restart Recovery

At the bottom of the tablet in Normal Boot it says "FASTBOOT CMD WAITING...."

I can see the tablet with fastboot devices but get errors when I try "fastboot flash ESP esp.img"

D:\Asus Memo Pad 7>fastboot flash ESP esp.img

target reported max download size of 536870912 bytes

sending 'ESP' (33792 KB)...

OKAY [ 1.601s]

writing 'ESP'...

FAILED (remote: flash_cmds error!

)

finished. total time: 2.401s

On the tablet it says :

NORMAL BOOT

FASTBOOT MODE

PRODUCT_NAME - K01A

VARIANT - K01A

HW_VERSION - (blank)

BOOTLOADER VERSION - unknown

IFWI VERSION - 64.33

SERIAL NUMBER - 0123456789012345678

SIGNING - ?

SECURE_BOOT - ?

FASTBOOT CMD WAITING.......

I do not remember how I rooted the tablet but obviously it cleared the serial number and input a new one.

Is there anything else I might provide that might allow you to assist me?
[MeMO Pad 7 Original Android Development] lambdadroid:
I'm afraid this package is for the ME176C (also named K013), not for the K01A. Now theoretically this doesn't mean anything, because the bootloader itself does not have any device specific code.

But given that you get an error trying to flash the "ESP" partition it is possible that your tablet never received the UEFI update (usually introduced with the update to Android 5.0). The bootloader only works on UEFI systems.
[MeMO Pad 7 Original Android Development] seamo123:
I've been having an overheating device and serious battery drain lately, is there any possibility it's related to this new bootloader? It's unlikely I know, just trying to eliminate all possible causes.
[MeMO Pad 7 Original Android Development] lambdadroid:
That's unlikely. The bootloader doesn't do much except load the kernel and then hands over all control to it. It doesn't run except very early in the boot process.
[MeMO Pad 7 Original Android Development] DaVince21:
Wow, kudos. It's really nice how painless this was to install (and then to install the LineageOS you also provided)! :)
[MeMO Pad 7 Original Android Development] lambdadroid:
me176c-boot 0.2.0

Redesigned charger detection: There is now an additional charger boot option that is automatically selected when the device is started due to charger insertion.

This allows customizing the boot target in this situation. Examples:

Boot into charger from stock ROM while having a custom ROM installed (in my experience it still charges slightly better with less heat): See "Using the stock charger".

Always boot into main OS: See "Booting into main OS on charger insertion"

android-efi 0.2.0:

Boot Android images from files instead of just partitions.

Pass additional kernel parameters

systemd-boot-me176c 239.0:

Boot images from other partitions on the internal storage.

This is mainly useful for dual booting, because the main EFI System Partition (ESP) is very limited in its size (only 16 MB).

Download: esp-0.2.0.zip

Note: Upgrading wipes all custom boot configurations. (You don't need to worry about this unless you have manually made changes to the bootloader configuration...)
[MeMO Pad 7 Original Android Development] RichardCooper:
For more than a week, I have been trying to reverse from lineage 14 to the asus firmware .36 whit TWRP 3.02.-0

. I get this error:

Could not find META-INF/com/google/android/update-binary in the zip file.

What im doing wrong?
[MeMO Pad 7 Original Android Development] lambdadroid:
This is not related to me176c-boot, and it seems like you are not using one my TWRP builds either. Please open a separate thread here: https://xdaforums.com/memo-pad-7/help
[MeMO Pad 7 Original Android Development] lambdadroid:
me176c-boot 0.3.0

Tip: Using the ASUS stock charger for offline mode charging is a great way to be able to charge at any time, even when the current ROM is in a non-bootable state. It also charges a bit more efficiently than the LineageOS ROM.

me176c-boot 0.3.0 contains major improvements and new features in all three of its components. Some of the new features will be required for future versions of the LineageOS ROM, however, booting the stock ROM is still supported.

me176c-bootstrap 0.3.0:

Moved some device specific code from the kernel to the bootloader

Technical details: https://github.com/me176c-dev/me176c-acpi#global-nvs-area

android-efi 0.3.0:

Added option to load additional init ramdisks (initrd)

systemd-boot-me176c 241.0:

Updated to systemd-boot v241

Added custom "android" loader type that makes it possible to write nicer boot configurations using android-efi

Example: https://github.com/me176c-dev/android-efi#systemd-boot

Download: esp-0.3.0.zip

Note: Upgrading wipes all custom boot configurations. For example, if you have been using the stock offline charger option, you will need to re-install it after installing this update.
[MeMO Pad 7 Original Android Development] Jason928591:
Had zero issues getting it installed on my tablet. I look forward to seeing how linux runs on this as well! thanks
[MeMO Pad 7 Original Android Development] Nexive:
Succesfully flashed the latest esp and re-installed stock charging. :)

Thx!
[MeMO Pad 7 Original Android Development] Zhaqyp:
For some reason it fails to flash for me.

Context: I turned my device on and instead of booting normally, it booted into a UEFI. Every time i boot my device it boots back into the UEFI. I am now trying to fix it.

When i hold power + vol up + vol down it says "fastboot starting... Fastboot starting...#1" etc up to #3. I used this method to enter the fastboot screen:

I then attempted to:

However it came up with:

Sending 'ESP' (33792 KB) OKAY [ 0.811s]
Writing 'ESP' FAILED (remote: 'flash_image is not implemented')

At this point i don't know what to do. I want to flash TWRP recovery so i can flash the stock firmware back, but cant as the bootloader is locked.

Does the fact it kept booting into UEFI mean the internal storage is broken?

I'm new to doing all of this, so sorry for the poorly put together post :)
[MeMO Pad 7 Original Android Development] lambdadroid:
When you run "fastboot boot droidboot.img" during the recovery procedure, does it boot into the other fastboot ("droidboot") screen (where you can switch between NORMAL BOOT/RECOVERY MODE etc)?

Because the error looks like you are trying to flash ESP from DnX mode (the screen that says "Fastboot starting...").

With UEFI you mean the setup menu? Usually, if you boot into the setup menu while turning on normally, there is simply no (working) bootloader is installed. This could be due to a mistake during installation or a hardware failure (quite unlikely).

In any case, this is not a big deal: as long as you still see something, it should be possible to get your tablet back into shape. :)
[MeMO Pad 7 Original Android Development] Zhaqyp:
Yes, it boots into the menu with the android where i can scroll between normal boot, recovery etc. after i run fastboot droidboot. I then try to flash the EFI partition, but get the Failed error.

The UEFI looks exactly like a PC BIOS/UEFI. I've attached an image i found of the same screen. Its strange though, as it started booting like this out of nowhere - no system updates or anything.

[IMG="UEFI of me176c"]https://img.xda-cdn.com/KbG2YMeMRWhJ2y4ghzewL3EKUvs=/https%3A%2F%2Fi.imgur.com%2FNysiea2.jpg[/IMG]

Thanks for the help, hopefully it can get fixed :)
[MeMO Pad 7 Original Android Development] lambdadroid:
That's weird... I tried exactly the same steps and it flashes ESP correctly. Few more suggestions:

Make sure you are using the correct droidboot.img, from https://dlcdnets.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip

Make sure you use the correct "esp.img" and the correct command "fastboot flash ESP esp.img" (ESP must be upper case)

Try booting a temporary recovery session using https://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (T4). With that, you could flash the entire UL-K013-WW-12.10.1.36-user.zip, or flash ESP from there.

So it started happening before you tried installing me176c-boot?

Yeah, that's the UEFI setup menu. Everything looks fine in that image.
[MeMO Pad 7 Original Android Development] Zhaqyp:
I re-downloaded and droidboot.img from the .zip and am now using the new version to get to the fastboot screen.

I re-downloaded the .zip with the esp.img and used the correct command. Still says failed.

The temporary recovery session has booted successfully. I wasn't sure which recovery option to use so i used "5 . cwm.zip". I used T4 and it booted into a recovery menu, as shown in the attached image. From the menu i tried to use: "install zip" -> "Install zip from sideload" and then used my PC to "adb sideload UL-K013-WW-12.10.1.36-user.zip" but my device is "Unauthorized", which it also says under "adb devices". I'd imagine this is becuase i didn't turn on the USB debugging before it started not booting. Hopefully installing from an SD will work, I will update when i try, i just need to find a spare one.

Yes. I turned it on a few nights ago and it booted into the UEFI. I read somewhere that that means the something is wrong with the bootloader and so i'm now trying to install me176c-boot.

Thanks so much for the help so far. I think progress is being made!

[IMG="Recovery Menu"]https://i.imgur.com/sxGJSLo.jpg[/IMG]
[MeMO Pad 7 Original Android Development] lambdadroid:
I don't really understand this error. I haven't seen it myself before and I have not heard of anyone else with something similar, either.

ADB in recovery should be independent from your main installation. But I'm not sure if ADB is working at all in the temporary recovery session. If I recall correctly, I've been having problems with that, too. But loading it from a SD card should work.

As for the recovery, any of them should work, although the TWRP portrait one might have a slightly nicer touch UI. Maybe ADB works with that one.
[MeMO Pad 7 Original Android Development] zoomer296:
Has anybody tested this with K00X/ME375CL?
[MeMO Pad 7 Original Android Development] lambdadroid:
The bootloader may work if you have received the Android 5.0/Lollipop update, but the LineageOS ROM won't work at all. All tablets with mobile connectivity are based on an entirely different SoC with an other GPU.
[MeMO Pad 7 Original Android Development] zoomer296:
Noted. I'll see if I can do a full backup first.
[MeMO Pad 7 Original Android Development] zoomer296:
Does anyone know a root method for stock with original BL?
[MeMO Pad 7 Original Android Development] lambdadroid:
We're really getting off-topic here, but on the me176c this was done using the temp recovery session (https://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096) and then flashing something like Magisk, SuperSU, ... Maybe only a system partition based root works, not sure if the bootloader verifies the boot image.
[MeMO Pad 7 Original Android Development] Luponius:
Hi My Android version is 4.4.2, not 5 and checking for updates says nothing an error relating to network. What are my options? Attempting to fastboot flash ESP for esp 0.3.0 gives me a "Can't find OSII index!!" error. My product is a WW_K013 - is this compatible?
[MeMO Pad 7 Original Android Development] lambdadroid:
Yes, this bootloader is compatible with ME176C and ME176CX, also known as K013. But it works only if you have installed the stock Android 5.0 (Lollipop) update.

You can install the update manually by flashing: https://dlcdnets.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36_KK-user.zip

Make sure your tablet is charged, and do not turn it off during the update. Note: Although some users have managed downgrading from 5.0 to 4.4, it is somewhat difficult to go back once you have updated.

As for how to flash that ZIP package: I would normally use https://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096, but I'm not sure if it works on Android 4.4... Otherwise placing the ZIP file on an external SD card may ask you to install the update after booting into Android. Or you could try the ADB steps at the bottom of https://xdaforums.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965 (but with the ZIP file I linked above).

Or maybe someone else knows it better than I do.
[MeMO Pad 7 Original Android Development] andrococo:
how to install the new bootloader 0.3.0 if I have ep-0.2.0 already installed
[MeMO Pad 7 Original Android Development] Luponius:
Hey Lambdadroid, cheers for the reply. The Intel Android I think does indeed work, it allowed me to load into TWRP with it, however when I passed the Asus update firmware it didn't take. I tried loading a SuperSU file which installed successfully but trying to run an 'su' command in terminal it says not found under /sbin/sh

I'm currently screwed since having wiped the tablet without backup I can't even root it, have no idea how to do that nor any clue how to install any firmware, and I don't even have the original firmware I had before, with no clue where to get a replacement. Any tips on what my next step should be?

EDIT: It's no longer bricked, I reinstalled the original 4.4.2 OS on it and it's working ok. I might retry the provided suggestions to see if I make it anywhere
[MeMO Pad 7 Original Android Development] lambdadroid:
Just re-install it the same way you installed it originally.

What does "it didn't take" mean? Does it display an error?
[MeMO Pad 7 Original Android Development] zoomer296:
Tried to flash, it ended with the same "flash_cmds" error as the person on the first page.

Thanks anyway.
[MeMO Pad 7 Original Android Development] simthadim:
I messed up. Flashed this on my device (ME176C, model K013) using

sudo fastboot flash ESP esp-0.3.0.zip instead of "sudo fastboot flash ESP esp.img ... stupid.

Now my device is stuck in the BIOS menu, if I may call it that. I can control it via a USB OTG with a keyboard, but it keeps looping back to it. Even "save and exit" returns back to the main BIOS screen.

Download mode no longer works. Any option for me to save this device, or is it completely bricked.
[MeMO Pad 7 Original Android Development] fgfgfyuyyy:
Bios and secure boot

Hello , I flashed the bootloader and it is working perfectly , but I want to know how to disable secure boot and get into the bios , because [MENTION=9870272]Zhaqyp[/MENTION] did it
[MeMO Pad 7 Original Android Development] lambdadroid:
UEFI Secure Boot is not enabled on this tablet. You can enter the UEFI/BIOS setup by selecting "Reboot into firmware interface" in the boot menu (i.e. when pressing Volume Down while turning the device on).

However, you can only navigate using an USB keyboard connected through a USB OTG adapter with external power supply. In that case, you can also enter the UEFI/BIOS setup by pressing F2 during boot like on normal desktop PCs.
[MeMO Pad 7 Original Android Development] lambdadroid:
Sorry, I missed your message for some reason. You can restore your device by following the documented recovery procedure.
[MeMO Pad 7 Original Android Development] fgfgfyuyyy:
What do you mean with power supply?
[MeMO Pad 7 Original Android Development] lambdadroid:
The tablet will not power the USB keyboard during early boot. So you need an USB OTG adapter where you can connect an external power supply.

I got this one a few years ago: http://www.leicke.eu/en/products/DS38603 but there are probably many others available. I connect the USB keyboard and the power adapter, then connect it to the tablet.

The tablet will turn on automatically and you can keep pressing F2 on the keyboard to enter the BIOS/UEFI setup menu.

WARNING: Do NOT make random changes to the UEFI settings. Someone managed to break USB OTG after changing an option. Then they were unable to revert the changes because the keyboard was no longer working...
[MeMO Pad 7 Original Android Development] fgfgfyuyyy:
Thank you for the explanation. I know what I am doing.

---------- Post added at 08:13 AM ---------- Previous post was at 08:01 AM ----------

Is this one good?

https://www.amazon.com/dp/B07PCPWYQR/ref=cm_sw_r_cp_apa_i_wIeiDbQJPEE6V
[MeMO Pad 7 Original Android Development] lambdadroid:
I cannot say if it is "good" or even if it will work, but it looks like the right thing. You will need to power it through an extra micro USB cable to power the USB keyboard.
[MeMO Pad 7 Original Android Development] fgfgfyuyyy:
Thank you!
[MeMO Pad 7 Original Android Development] Sumptiz:
is work with the model K01A?
[MeMO Pad 7 Original Android Development] Daouid:
Hello,

Thanks for your great work :)

Can we boot on USB key ?

Or linux ISO ?

I'm looking to directly install a debian, like on other Atom tablet with Windows, Acer for example.

Thanks in advance

Have a good day

Daouid
[MeMO Pad 7 Original Android Development] lambdadroid:
You can boot from USB, but only using an USB hub with external power supply. Connect the USB flash drive and an USB keyboard to the USB hub, and the USB hub to the tablet. Keep pressing F2 while turning on the tablet. Then it will end up in a pretty much regular UEFI setup and you can boot the USB key from there.

Personally, I would not recommend erasing the internal storage. I don't know if it will still work correctly. I would recommend postmarketOS if you just want a quick way to install a regular Linux distribution.
[MeMO Pad 7 Original Android Development] xXSantyXx:
Hi, i have been trying to get the pc to recognized the device in fastboot mode, but i can't. Do i need root access? I have enabled usb debugging, installed adb abd fastboot drivers on two pc's, i can get the device recognized on adb devices, when its booted into system, but when i do adb reboot fastboot, i can no longer detect it. Any help?
[MeMO Pad 7 Original Android Development] ISmokeAir:
I had the same problem. I almost went insane trying this. After hrs of research here's what worked for me. I downloaded the driver from asus's site. After dis you need to disable driver signature. You do this by pressing and holding shift and then press restart. You have options and then you press the number corespondent for disabling driver signature. Then you need to go to device manager and select the tablet and update the driver. Select driver from my files or something in those lines, instead of automatic search. And after this you can finally use fastboot. Is this the stupidest problem with the stupidest solution? Yes. But this is what get with custom weird ass **** not supported by the manufacturer. Welcome to the community! ^_^
[MeMO Pad 7 Original Android Development] xXSantyXx:
Thanks, i just solved it the same way, like 2 minutes before your post. I was going insane...
[MeMO Pad 7 Original Android Development] Daouid:
Thanks, I have take time to try, but it work well !