Database Users

[FIX] Asus Zenfone 2 Laser ZE550KL Marshmallow update problem, failed to mount /asdf

I have good experience with other phones but this is my first time working with ZE550KL.
So I took my uncle's phone and he asked me to update his phone to the latest firmware to get the VoLTE feature.
He is was on ZE550KL_WW_21.40.1220.1708 which is Marshmallow of the ZEN UI.
I have downloaded the latest firmware from the ASUS website but I couldn't update it because the recovery which came with the marshmallow update is broken.
These are the errors I got
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is what I did, and hope this works for everyone.
Hoping that you already went and searched about the problem over the internet.
These are the things you need to download :
ADB and fastboot
https://drive.google.com/file/d/0B0aDjdU4gTwZZW1HUHhqWnEteXM/view
Recovery image file
https://drive.google.com/open?id=0B0aDjdU4gTwZa1MyUmVPN3BhQjQ
Latest firmware:
https://www.asus.com/in/support/Download/39/1/0/22/ZROQURlyupei1ZQz/32/
1. Download the adb and fastboot drivers. Download the latest firmware and copy it onto your internal storage.
2. Boot into the bootloader.
3. Download the recovery image and paste it into the adb folder.
4. Now type the following command.
Code:
fastboot flash recovery recovery.img
5. This step is very important.
Now, all you have to do is hold the power button and the volume down button to boot into the installed recovery.
Remember that if you restart your phone after step 4, your old recovery(which does not work) will still be there.
6. Now select update from sdcard and select the zip file of the latest firmware you downloaded.
7. It will take at least 10 minutes to install, don't panic if you think the screen froze.
I hope this solves the issues many users are facing.
Feel free to ask questions, I will be very happy to answer.
The recovery we installed is the recovery of Android Lollipop version of the Zen UI ROM.

Thanks. It worked. The only difference is that after flashing the old recovery, my SD card was showing blank. So i selected the adb sideload option and flashed the new build.. Thanks for your guide.

Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?

hellbraker said:
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
Click to expand...
Click to collapse
Before I tried any of this... First thing I did was boot TWRP and install the lastest firmware.
But I couldn't do so because TWRP doesn't let you flash .img files.
And for the best result it is always better for you to use the official recovery to flash an official firmware.
Because ASUS f***ed up, I needed to install the previous version of the recovery to flash the firmware.
And I'm very happy that my guide worked for you.
Don't forget to give thanks. :laugh:

I haven't tried it yet. So you didn't tamper with boot.img at all. Right?
Also as previously asked what's the build number from which you extracted the recovery.img? Is it from .1503?
My current build is .1708 same as what you worked on. And will data get erased during this process?

How can I boot into the bootloader? is it by unlocking it? or is there any other non-invasive way?
Update: I installed as per your instructions. Device shows "Optimizing app 5 of 51".
Thank you.

Thank you
Thank you sir, this helped me a lot.

recovery link is asking need access plzz help

My Asus Zenfone doesn't boot anymore and doesn't even allow me to factory reset it from the bootloader. How to force reset it??

SM-g935df hang with boot screen

hello..SM-g935df suddenly battery low while updating firmware.now its hang with boot screen.FRP lock also on.I tried many firmware (7.0 and 6.0.1 etc)all firmware fail at flashing "recovery.img" in odin.in recovery mode i can see like below image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i reset the device.now its show like this image.please help me

https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
a brilliant method.
I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!

JeffDC said:
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
a brilliant method.
I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
Click to expand...
Click to collapse
thank you for the reply bro.1st I flash g935fd with "G935F_(EXYNOS).tar" but odin was stuck at 99% here result
after i remove the USB and plague it again with download mode and flash 2nd file (G935F_(STOCK).tar" )via odin.its also stuck when 99%complete.here result firmware version is what can i do now bro..please help me.
fw version is SM-G935FXXS1BPJ1

geeth said:
thank you for the reply bro.1st I flash g935fd with "G935F_(EXYNOS).tar" but odin was stuck at 99% here result View attachment 4345010
after i remove the USB and plague it again with download mode and flash 2nd file (G935F_(STOCK).tar" )via odin.its also stuck when 99%complete.here resultView attachment 4345011 firmware version is what can i do now bro..please help me.
fw version is SM-G935FXXS1BPJ1View attachment 4345042
Click to expand...
Click to collapse
Head over to the OP's post and ring him up. I think after the first flash, as I get it, you have to somehow run the .bat file in adb, It is the .bat file that deletes the Persistence file/partition, where, as he explains, the FRP (Google enctypted file) is held. Once that is out of the way, FRP should be gone, then flash back your stock BL, or leave it on the U (Universal) BL if you wish?
That's my understanding. I don't think the OP's been around his post for several months. We are hoping he returns to answer and clarify some questions.

Update rooted device (v 2017) to new version

Hi everyone.
Few months ago I was here folloging some tutorials to root my device so I can install a Magisk module that requieres root (an rclone implementation, but this is not relevant right now).
Now I have seen many times this message on my Shield:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I tryied to install it with the typical method (OTA), but it's not working anymore. I think it's because of the root (and bootloader unlocked maybe... I'm not an expert of these stuff).
I've been looking for some reference in this forum in order to upgrade the version in a rooted device as mine for a long time, but I didn't find anything. So I came here to ask if anybody has encounteder this situation or knows how to do it.
Regards and my respects to this amazing comunity.

xeviff said:
Hi everyone.
Few months ago I was here folloging some tutorials to root my device so I can install a Magisk module that requieres root (an rclone implementation, but this is not relevant right now).
Now I have seen many times this message on my Shield:
View attachment 5385511
And I tryied to install it with the typical method (OTA), but it's not working anymore. I think it's because of the root (and bootloader unlocked maybe... I'm not an expert of these stuff).
I've been looking for some reference in this forum in order to upgrade the version in a rooted device as mine for a long time, but I didn't find anything. So I came here to ask if anybody has encounteder this situation or knows how to do it.
Regards and my respects to this amazing comunity.
Click to expand...
Click to collapse
Download and extract the latest developer image from Nvidia:
https://developer.nvidia.com/gameworksdownload
Make sure to enable usb debugging in developer options.
Connect computer to the shield using a USB cable in the port furthest away from HDMI.
Code:
adb reboot bootloader
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
For Magisk, download:
boot-magisk23.0.img
Code:
adb reboot bootloader
fastboot flash boot boot-magisk23.0.img
fastboot reboot
Release Nvidia Shield (darcy) Android 8.2.3 patched boot img · BaIanced/Nvidia_Shield
Nvidia Shield For Nvidia Shield (2017 darcy) running Android 8.2.3 developer image. If you are currently in bootloop, download the developer image Extract/flash using official instructions Basicall...
github.com

Thank you very very much.
Wonderful answer.
It helped me a lot many times, from the first day flashing the img for root state, to today restoring the factory state.
Hace a nice 2022 !

xeviff said:
Thank you very very much.
Wonderful answer.
It helped me a lot many times, from the first day flashing the img for root state, to today restoring the factory state.
Hace a nice 2022 !
Click to expand...
Click to collapse
Here's the current files for the latest update (9.1.0) if you're interested
Release 9.1.0 · BaIanced/Nvidia_Shield
Nvidia Shield For Nvidia Shield (2017 darcy) running Android 9.1.0 If you are currently in bootloop, download the developer or recovery image Extract/flash using official instructions Basically... ...
github.com

Is this instruction on lineageosroms wrong?

Hi all, came across this instruction in a Lineage OS installation guide: (https://lineageosroms.com/fajita/#temporarily-booting-a-custom-recovery-using-fastboot). Item 5 says:
Temporarily flash a recovery on your device by typing:
fastboot flash boot <recovery_filename>.img
However I've noticed that guides for other phones (including the guide for the 5T and the 8T on the same site, e.g https://lineageosroms.com/instantnoodle/) specify running an instruction like:
fastboot flash recovery <recovery_filename>.img
Can anyone confirm whether this is a mistake in the guide for the 6T? I did run the command as per the 6T guide but could not boot into recovery mode after. Also supposing it should have been 'recovery' not 'boot', is it likely that I can rectify it now simply by running the correct command now?
--------- EDIT ------------
Having looked up some documentation on fastboot (which say the structure of the command is basically fastboot flash <partition> <filename>) and then read around a bit on partitions on Android phones, I'm getting the impression android phones pretty much always have a recovery partition, which would make me think that the 'boot' command is indeed wrong. That said, I've got next to no experience with this so it's hard to be sure that the command isn't correct for some reason I'm not aware of, that only pertains to a few generations of phones. Anyone?
Some links I've looked at:
Fastboot Commands List and Cheat Sheet with Explanation
Fastboot is a command-line tool for Android. You can execute Fastboot commands to flash and boot factory and TWRP recovery images.
technastic.com
How can I identify partitions of an Android device from the shell?
I'm trying to find which partition is used for what, e.g. /boot, /recovery, /system, from adb shell. While this is trivial for partitions currently mounted (using the mount or df commands, see e.g....
stackoverflow.com
Android Partitions Explained: boot, system, recovery, data, cache & misc
Unless you have been using your Android phone just for calls, SMS, browsing and basic apps, you should know that Android uses several partitions to
www.addictivetips.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Just a follow up - the maintainers of the official wiki got back to me and have said that the command in question is correct (i.e. it should be fastboot flash boot <recovery_filename>.img). Apparently 'That device doesn't have a recovery partition, the newer ones do'.
I did get a comment elsewhere saying that it ought to have been fastboot boot <recovery_filename>.img (i.e. without the 'flash') but as the maintainers of the lineageos.org wiki have gotten back to me with a confirmation it's meant to be as written, I'd say in the absence of any other strong evidence to the contrary that it's correct.
They also pointed out that https://lineageosroms.com/fajita/ is largely a repost from the official wiki and I they recommend using the official page (wiki.lineageos.org) instead - I definitely prefer to do so. FWIW, I have checked the links and also the sha256 sums of the recovery and ROMs I downloaded via the links on lineageosroms.com with the one's from wiki.lineageos.org - and at least the ones that I checked for fajita were the same - and the instructions they've copied do appear to be faithfully reproduced (currently) - but again, I'd suggest going to the page they've copied from instead.
Regarding my problem, I'm still at an utter loss as to why I'm seeing what I see. Any ideas? I guess I'll try to flash the stock ROM again and start over but I've no reason to suppose I won't see the exact same behaviour as I've no idea whatever where it's gone wrong, or how to reasonably set about diagnosing that.
As I've not done too well with getting the right sources so far anyone care to recommend a good set of instructions to recover the stock ROM from a soft brick?

PS I think there's a good chance the issue was to do with firmware not being up to date before flashing lineageOS , but I can't be 100% sure as in the end I decided to install via TWRP anyway. I missed the instruction to ensure I was using latest android 11 firmware because I was (unknowingly) viewing a repost rather than the original wiki.

Moto G6 plus flashing does not work

I am trying to flash Pixel Experience on my Moto G6 plus but when flashing the recovery file this message keeps coming up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

GamingBar said:
I am trying to flash Pixel Experience on my Moto G6 plus but when flashing the recovery file this message keeps coming up.
Click to expand...
Click to collapse
Bootloader unlocked? Did u try fastboot boot IMAGE?
BTW: you can rename your image and give it a shorter name.

WoKoschekk said:
Bootloader unlocked? Did u try fastboot boot IMAGE?
BTW: you can rename your image and give it a shorter name.
Click to expand...
Click to collapse
@GamingBar, this ^^^ (making shorter name). I've had many commands error out with random errors simply because the pathname and/or filename was too long (Windows is stupid for never being clear that that's the reason why the command doesn't go through).
Also, what version of fastboot are you using? I'm concerned over the "preflash validation failed" -- when I flash my monthly factory image for my Pixel, there is an extensive preflash validation; so I'm thinking either fastboot version is outdated where it is having a hard time flashing or this type of image or to the moto G6 is meant to be flashed in either a package or a particular way to your device.....

simplepinoi177 said:
@GamingBar, this ^^^ (making shorter name). I've had many commands error out with random errors simply because the pathname and/or filename was too long (Windows is stupid for never being clear that that's the reason why the command doesn't go through).
Also, what version of fastboot are you using? I'm concerned over the "preflash validation failed" -- when I flash my monthly factory image for my Pixel, there is an extensive preflash validation; so I'm thinking either fastboot version is outdated where it is having a hard time flashing or this type of image or to the moto G6 is meant to be flashed in either a package or a particular way to your device.....
Click to expand...
Click to collapse
the fastboot version is up to date because it's asking for logical partitions. this is not the outdated Minimal ADB crap or sth.
the way of 'fastboot flash boot ...' is the recommended way in the PE install guide.

GamingBar said:
I am trying to flash Pixel Experience on my Moto G6 plus but when flashing the recovery file this message keeps coming up.
Click to expand...
Click to collapse
if the fastboot method keeps failing you should use TWRP by 'fastboot boot TWRP'. DO NOT flash it because it won't decrypt your data then. In TWRP you can flash the Pixel recovery image. Then reboot to recovery and the Pixel recovery should boot. Then flash the ROM.
DO NOT flash the ROM in TWRP!!