Database Users

bootloop after flashing incorrect boot image

Hello. I have a XOLO Play Tegra Note 7.
A couple of days back I, in an attempt to flash a ROM that I downloaded from the NVIDIA website, I accidentally flashed a boot file from a CyanogenMod image that I downloaded for another purpose. Now, I'm neither able to flash the correct boot image (it is not recognised by adb) nor apply update through bootloader recovery (it says E:footer is wrong, E:signature verification failed). All that's happening is that its bootlooping.

Error while flashing ROMs.

I've been trying to flash Nougat ROMS on my OnePlus 2. Every time I flash a new ROM, the process says "patching system unconditionally" and ends with
E:/ unknown error[log]
E:/ unknown error[log]
Then when I reboot, I get a boot loop and stays at the OnePlus logo.
I've tried different versions of TWRP. I've flashed both CM14 and RR14. Both showing the same error. Both original zip files showed Error 7 at first. I changed the updater-scripts in the META-INF folder and rezipped it. This solved Error 7. That is when this showed up "E:/ unknown error[log]".

It's not an error. It's informing you that the system image is getting patched with new ROM.

Downgrade to Marshmallow

Hello Friends, I just upgraded my Zenfone 3 ze520kl to Nougat, but i prefer Marshmallow i try from recovery mode to flash Marshmallow, it shows error and the installation aborted. Can any one help . Thanks.

What error does it show?

Error with some numbers follows by 'install aborted'. I unable remember the error numbers. I did three times all the time with same remark.Thanks.

That's not very helpful. Can you try it again and tell us exactly what it says?

Hi,
I downgraded a few days ago, here's an overview of the steps.
WARNING, this requires a factory reset so you will lose the data on the phone, so make sure you have backups before you proceed. You do this at your own risk and I am not responsible for any damages.
I assume you have adb / drivers all configured and know to how use them.
1) download firmware file http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-13.20.10.152-user.zip and save to SD card / insert card in phone.
2) download recovery and boot img files for Z017D_WW_13.20.10.152
- https://mega.nz/#F!ok0V0RIA!5WKtHe98opzjVI3NPbM7Ww
- under the folder Z017D_WW_13.20.10.152
3) Go to fastboot mode (power + vol up)
- flash recovery.img (command: fastboot flash recovery recovery.img)
- flash boot.img (command: fastboot flash boot boot.img)
4) reboot to recovery (power + vol down)
5) install update form micro sd card.
set the file UL-ASUS_Z017D_1-WW-13.20.10.152-user.zip that you saved earlier
6) wipe cache
7) factory reset
If you don't do a factory reset and reboot, Android pretty much crashes on multiple processes on start up, it is unusable.
Regards,
TK

Credit goes to https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524 for laying the foundation.

Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.

Same thing happened to me as well. I just went ahead to flash the RAW file (http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html) and updated the software to the latest marshmallow update, followed by a factory reset.

If we Downgrade
Then we get update in future yes or no??
Sorry for bad English??

Yes.

Hi, thanks for the help. Please answer this:
Do I need to use Recovery and Boot.img the same version of ROM? Why?
Why do I need to install Boot.img?

I think I brinked my phone. Please help [SOLVED!]

Hello. I tried downgrading from the latest ASUS firmware to Android 6.0.1
I used this tutorial to install the raw firmware: http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html
Went all the way to the last step when the app hanged. ASUS Flash tool went all the way saying
Code:
Run flash image script ...
It was hanged there. And as per this video, went all the way to the end where it showed the "code bar" on the right (https://www.youtube.com/watch?v=P8xg7A-P7Ak)
This is when the "Android" uninstalled driver showed up in Windows. This is under "Other devices - Android". I tried updating this driver using the ASUS_Android_USB_drivers_for_Windows found here: https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_Download/ but it wouldn't install the drivers.
Note that I used these ASUS USB drivers to get the ASUS ADB Interface installed. As per the tutorial I showed in the very first paragraph, I never got the "ASUS Android Bootloader Interface". This is what I think this "Other devices - Android" is found under Computer - Manager - Device Manager.
Most tutorials on the internet shows that the "ASUS Android Bootloader Interface" should be installed using these drivers found on ASUS website, the ASUS_Android_USB_drivers_for_Windows.
Now of course because I unplugged the phone, it will continously stay on the Android splashpage showing the loading circle infinitely.
As a last attempt I tried installing the "stock", not "raw" firmware (the one I wanted to install WW_13.16.5.49 but ASUS would not let you downgrade using the recovery "power+volume down" and using "Apply update from microSD card". It would give the
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
)
Well, after it brinked, I tried it again and this time it DID install WW_V13.16.5.49. Was succesfull. But after the ASUS splashscreen it's still stuck in the booting process.
I am very sorry if my post is convoluted but I tried explaining everything I did. Any way to un-brink it? I think maybe if I figure out how to properly install the ASUS Android Bootloader Interface, I can try again ASUS Flash tool and install the raw image and maybe that will fix it?
Please help. Any questions if my thread is too confusing, please let me know and I will answer it. I can't even turn off the phone. While it's stuck into the load splash screen, if I press the power button it just restarts, not turn off.
I still have access to fastboot (pwr + volume up) or recovery (pwr + volume down)
EDIT: Phone won't get recognized anymore in ASUS Flash Tools. Serial number won't show up to select

Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.

wang1chung said:
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
Click to expand...
Click to collapse
Thank you, this actually worked!!
Aaaand, it's actually on the version 13.16.5.49!!!! THIS IS EXACTLY WHAT I WANTED!
So apparently by brinking my latest nougat 7.0 update from ASUS via the ASUS Flash Tool trying to flash the .RAW 13.20.10.137, the standard recovery system (power+volume down) allowed me to install the 13.16.5.49 version. Then I assume remnants files didn't allow to properly boot, and your idea to wipe cache and factory reset fixed that!
What is so great is that I was scared that because the .RAW firmware was newer than the version I needed (13.16.5.49), I wouldn't have been able to install it. It was the same problem initially, when I tried to install 13.16.5.49 directly via recovery over the latest nougat 7.0 version from ASUS, but it was giving me
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
I think this error was due to the fact that ASUS won't allow older firmwares to be installed over newer ones, as per their webpage
https://www.asus.com/support/faq/1009748
Code:
You can not change the SKU from one to another, e.g., WW -> TW, and also can not downgrade your firmware, e.g., V2.20.40.13 -> V2.19.40.18
So in the end, what allowed the 13.16.5.49 stock firmware to be succesfully installed? The installer not detecting a proper firmware anymore because of the damaged update due to ASUS Flash Tools hanging because my computer won't install ASUS Android Bootloader Interface?

Glad you got it going :good:

Zenfone 3 Brick

I was using Lineage OS on my Asus Zenfone 3 (ZE552KL). When my battery was empty it's stucks on fastboot mode. Got stuck unlocking my bootloader via adb. Phone is detecting in ADB. The phone is getting stuck at ASUS logo and I cant boot to recovery either. It does get detected by fastboot but nothing more. I have tried :-
(1) It only seems unlocked boot screen and the choices is start volume up countinue boot but isn't any happening.
(2) I used Asus flashtool (various versions- 1.0.45). The latest one says battery is -1% while the earlier version returns various errors including "ftp request server log access is denied" and "failed to write partition".
(3) I have (seemingly) couldn't recovery and boot images.
(4) I flash factory RAW rom, and then Stock Rom but It's stuck on Fastboot Mode.
Read a lot of threads but not much seems to be working.
Help please !
Thanks

1st Try to Flash with latest RAW,
If fail, Try with CSC
If still fail try with EDL File (Unbrick) - ZE552KL Libra_QFIL_8953_01020_20170714_Aboot.7z

eemmiirr said:
I was using Lineage OS on my Asus Zenfone 3 (ZE552KL). When my battery was empty it's stucks on fastboot mode. Got stuck unlocking my bootloader via adb. Phone is detecting in ADB. The phone is getting stuck at ASUS logo and I cant boot to recovery either. It does get detected by fastboot but nothing more. I have tried :-
(1) It only seems unlocked boot screen and the choices is start volume up countinue boot but isn't any happening.
(2) I used Asus flashtool (various versions- 1.0.45). The latest one says battery is -1% while the earlier version returns various errors including "ftp request server log access is denied" and "failed to write partition".
(3) I have (seemingly) couldn't recovery and boot images.
(4) I flash factory RAW rom, and then Stock Rom but It's stuck on Fastboot Mode.
Read a lot of threads but not much seems to be working.
Help please !
Thanks
Click to expand...
Click to collapse
I have this problem too. How did you fix it ?