Unlocked, can't be trusted, can only boot system via bootloader - Moto G5 Plus Questions & Answers

EDIT: I don't think it's verity. I think something more is going on. I tried installing another rom with its own kernel, and the problem did not go away. So what's keeping me from getting rid of this nuissance and booting normally?
I've done some searching around to try to fix this problem, and frankly, I've got a headache now. Ok. I've got my bootloader unlocked, and I've installed TWRP and Magisk. Now I want to disable DM Verity so my device will boot normally. As it is, I have to go into the Bootloader in order to get the system to boot: no other option. Edit: Is it even verity doing this? Is it something else?
The guides for disabling dm verity have not worked. Iinstalled Magisk, and some people said that that would disable dm verity all on its own. It didn't. I installed the no-verity-opt-encrypt thing, hoping that would disable dm verity. I actually tried that option before installing Magisk. It didn't work.
Well, any ideas? Do I have the right dm verity thing? Is there more than one? Did I maybe use the one for the G5 by mistake? How do I get past this annoying thing? Please advise.

I'm not familiar with the layout of the Moto G5, so I can only relate what I've learned on Pixel devices.
I assume this is what you're seeing when you attempt to boot:
{
"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"
}
What this means is that a verification error was encountered during run time. This is a function of Android Verified Boot; more details here.
Disabling dm-verity is generally done by flashing the [icode[vbmeta[/icode] image with the --disable-verity --disable-verification arguments, as such:
Code:
fastboot flash vbmeta <vbmeta image> --disable-verity --disable-verification
However, this may not apply to the Moto G5, as I'm not sure its partition structure is similar to the Pixels. Additionally, this should generally be unnecessary if you're on a stock ROM with a stock kernel.
It seems others have encountered the same problem before. It's rather wise to search before posting. Check out this thread:
Stuck at 'Your device has been unlocked and can't be trusted'. Can't enter recovery
I was flashing a rom and followed all the steps correctly: unlocked bootloader, flashed twrp, rooted and then flashed. Everything worked fine on the first go but the phone app was foreclosing instantly so i rebooted into recovery to wipe data and...
forum.xda-developers.com

No, that's not it. What happens is that when I reboot it tells me:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
Click to expand...
Click to collapse
And then it boots into recovery.
My device is by no means "stuck". It boots into recovery. In order to actually boot the system, I have to choose the option Reboot > Bootloader. And then when the bootloader comes up, I choose Start, and then the system boots. But this is not what I want my phone to do! I want it to, you know, behave!
There doesn't appear to be a separate vbmeta thing. There's just boot.img. AND when I tried installing a custom rom that came with its own kernel, it did not solve the problem. So something else must be going on here.
And I did everything this guy said to do regarding flashing the stock rom: https://forum.xda-developers.com/t/guide-moto-g5-plus-flashing-stock-firmware-rooting-2021.4205293/
No good. Need more help.

For anyone who goes searching desperately for a solution to this same problem: There is a workaround, and that seems to be the best we can do.
Step 1: Get the raw boot.img from your firmware package.
Step 2: Patch boot.img with Magisk. Copy it to your PC.
Step 3: Get TWRP. But you've gotta get an older version, because it's smaller. Get 3.5.0. It's going to matter in a moment.
Step 4: Reboot to Bootloader (hold Vol- while phone is turning on or rebooting).
Step 5: Use fastboot to flash the modified Boot image to the Recovery partition (fastboot flash recovery <themodifiedbootimage>). It's not where a Boot image is supposed to go, but in this case, it's what needs to happen.
Step 6: Likewise, flash TWRP to the Boot partition (fastboot flash boot <twrp.img>).
So far, that seems to work. Now, when you reboot, your phone will boot into the system like it's supposed to. If you want to launch Recovery, what you now have to do is boot into the Bootloader (see Step 4 above) and choose Start. This would normally start the system, but because TWRP is sitting in the Boot partition, it will launch TWRP instead.
I don't have a guide yet for how to make the Boot partition bigger, so that the latest version of TWRP can comfortably fit into it. And I don't know where this whole problem came from in the first place, and how to fix it the right way. But this is what we've got for now, and as far as I can tell, it works pretty well.
But remember: Your Boot and Recovery images are switched now. So any time you want to make any modifications to either, you have to remember where they are.

Related

Update to 5.1.1 without loosing data

Hello together,
these were the steps to update to 5.1.1 (LMY47X) from 5.0.1 (LRX22C).
It was working for me - without loosing data.
Notes:
OTA didn't work cause of having custom recovery / root.
Maybe it was also in another thread here - but I didn't saw it
It work for me (WIFI-Version) - but might kill your device :crying:
from post #4: In case you using fastboot no very often - look here for more details: http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26 - Thanks the.teejster
Steps
Make sure you have working fastboot on your PC
Download Factory Image and unzip it
Also unzip the included image-volantis-lmy47x.zip
Boot your Nexus 9 into fastboot (Shutdown device; Hold Vol-UP + Power on)
Flash bootloader & reboot
Code:
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
Erase everthing but data partition
Code:
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase vendor
Flash the file (found in the unpacked image-volantis*zip)
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Reboot device
Optional: Root it again.
Download CF-Autoroot
Use the root-Scripts
Hope it helps and works for you.
One question. I am rooted and have twrp recovery. I this case : Why should we update recovery?
Alternatively, you could remove the "-w" flag from the flash-all.sh script and run it without losing data
A few key prerequisite items are missing in the OP..
I wrote up a similar "how to" over here :
http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26
Hello,
I always upgraded android manually flashing while in fastboot.
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
{
"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 lot of apps force close (gmail opens, but when i try to open a mail fc, eurosport same, opens but when i reada news fc, and many other)while others works flawless.
I tried wiping everything, also userdata, but problem not solved.
What can i do?
I read here that someone when upgrade android also erase "vendor", it's the only thing i didnt do, but i never did it.
Please help, finally with 5.1.1 this device flies but now i can't use it!
Thanks.
What about Vendor and recovery ?
Please see my instructions linked about 2 posts up. Follow those exactly and you shouldn't lose any data and the upgrade should be fine.
Sayan1987 said:
Hello,
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
Click to expand...
Click to collapse
Sayan1987 said:
Hello,
I always upgraded android manually flashing while in fastboot.
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
And lot of apps force close (gmail opens, but when i try to open a mail fc, eurosport same, opens but when i reada news fc, and many other)while others works flawless.
I tried wiping everything, also userdata, but problem not solved.
What can i do?
I read here that someone when upgrade android also erase "vendor", it's the only thing i didnt do, but i never did it.
Please help, finally with 5.1.1 this device flies but now i can't use it!
Thanks.
Click to expand...
Click to collapse
try fastboot flash vendor vendor.img
For the fc you are experiencing, it is possibly due to the modified ART in 5.1.1 or you check if you have the latest Android Webview
I just thought I would throw this out here in case anyone needs or wants to know...
You do not need to flash the bootloader to upgrade from 5.0.2 to 5.1.1, I can not tell you if this will work coming from 5.0.1
Also after first boot and you flash twrp, you can boot to recovery then immediately reboot back to system. Twrp will install su for you. You'll just need to update the su apk in the market. No need to mess with any kind of su zip anymore.
That's all I have to add to an already great guide.
the.teejster said:
What about Vendor and recovery ?
Please see my instructions linked about 2 posts up. Follow those exactly and you shouldn't lose any data and the upgrade should be fine.
Click to expand...
Click to collapse
laill said:
try fastboot flash vendor vendor.img
For the fc you are experiencing, it is possibly due to the modified ART in 5.1.1 or you check if you have the latest Android Webview
Click to expand...
Click to collapse
Thanks guys flashing vendor fixed everything!!
All the forced closes, heat problems, May I ask are you really stock? No such problems here
Verstuurd vanaf mijn HIGHWAY SIGNS met Tapatalk

[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??

moto g4 stuck in fastboot mode (Hard brick)

hi, yesterday mi moto g4 xt1621 was working well but today when i switch it on it didn't show me the boot logo and started in fastboot mode
{
"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"
}
so i tried to went to the recovery and it gave me an error which said: "start up failed:
your device didn't start up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant
AP Fastboot Flash mode (secure)
Fastboot reason: failed to initialize partition table
error: no bootimage found. skip to fastboot
boot up failed
i tried a lot of things, when i connected it to my pc recognizes it as Fastboot athene_13mp S
and i didn't get the software repair assistant
and
i don't know what to do if someone could help me, I would be very grateful
have you found the solution
adithya11198 said:
have you found the solution
Click to expand...
Click to collapse
unfortunately i haven't found the solution yet
System lost perhaps?
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?
null2025 said:
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?
Click to expand...
Click to collapse
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again
Omega Adrek said:
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again
Click to expand...
Click to collapse
Ok thanks adrek, i'm going to try it when my PC recognizes my smartphones again, it's another problem which I have but I don't want to bother you with that
Rom flashing failed . What should I do?
adithya11198 said:
Rom flashing failed . What should I do?
Click to expand...
Click to collapse
As the message says, it can't find a bootlogo. (usually logo.bin). If you've got a locked bootloader, you must have all key partitions, including logo.bin on the same patch level (and as such you may have to flash all partitions).
Which firmware did you try to flash and what flashing commands did you use, and can you show us the outputs of said commands?
This will help You : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
thank you
Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you really much omega adrek, it worked, my moto g4 owe you its life

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"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"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP
is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""

Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""
I'm handling a bricked Zenfone 3 ZE552KL WW model, but I am unable to flash the stock rom back into the device.
For context, this device has never been unlocked, rooted, and always worked under its original factory Android. As told by the owner, he received an OTA update notification last week and confirmed all prompts to initiate the update. As instructed, he plugged the device to its original charger, left the update running and went by with his day doing other stuff. When he returned, the device was completely OFF with 0% battery. We figured the charging cable disconnected due to a bad connector endpoint, and the phone ran out of juice while the update was running!
The result is a bricked Zenfone unable to boot beyond the ASUS logo. It keeps crashing and gets into a boot loop.
I have tried most of the basic tech support I can give him.
I have downloaded a fresh copy of the official ZE522KL firmware from the ASUS website.
I can boot the phone into recovery, which is still the original ASUS recovery. But as I try to flash the firmware, I get this lovely error message:
{
"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"
}
ERROR: This package is for "WW_Phone" device. This is a "".
I know for a fact this is a WW_Phone device because when I try to flash the JP firmware, the error message is different.
ERROR: This package is for "JP_Phone" device. This is a "WW_Phone".
Already tried "Wipe data/factory reset" and "Wipe cache partition" from the recovery menu, but that didn't help.
Already tried pushing the firmware via "adb sideload" and placing it in a SD card. Those didn't help either.
I am also willing to flash a community ROM, like LineageOS or Mokee, but I first need to unlock the bootloader. I'm running adb and fastboot from Linux, and I can't find a descent tool to unlock using Linux is proving to be a real pain. Every tool seems to be made for Windows only.
So, I'm resorting to anyone here, hoping anyone could give me a light before we send this phone directly to ASUS tech support, not available in our region (we'll need to ship it to another city).
Anything I can try before that? I'm running out of ideas.
Best regards and thanks in advance for any help.
Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg
Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.
wang1chung said:
Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.
Click to expand...
Click to collapse
Since his phone is locked, he can't flash anything except RAW firmware.
---------- Post added at 11:52 AM ---------- Previous post was at 11:41 AM ----------
juliohm said:
Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg
Click to expand...
Click to collapse
Hey juliohm,
Just follow these steps & your device will operate normally
1) Download and install ASUS Flash Tool :
2) Download Latest Oreo RAW
ZE520KL:
ZE552KL:
3) Enter Fastboot Mode (Power + Volume Up)
4) Open ASUS Flash Tool
5) Select device & select firmware (select YES on wipe data tab too)
6) Connect phone to PC
7) Hit Start and wait 10-15 minutes (ignore the error 5 [FRP])
MOD EDIT: PAY-PER-CLICK LINKS REMOVED
Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?
juliohm said:
Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?
Click to expand...
Click to collapse
Check PM
Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.
GrenadeofTacos said:
Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.
Click to expand...
Click to collapse
No need. Flash RAW firmware is enough.
Just a quick follow up.
The owner decided to take it a local assist shop. I don't know what method they used, but they managed to reflash the stock firmware back into the device, and it's working fine again.
Thank you all for the tips. If this was my own device, I would be tinkering a lot more. But the owner decided to play safe and pay for repair in some authorized assistence shop.
Best regards all!

Categories

Resources