Zenfone Go zb551kl Invalid Boot img - Asus Zenfone Go Questions & Answers

So I wanted to try and hide the root status of my phone and found the app called magisk. I install the app and allowed the app to install a custom boot img. After restarting my phone it now gets stuck in the asus logo showing Error: Invalid Boot Img on the top of the screen. My phone is rooted and it has no recovery. I tried flashing through fastboot but it gives me a security error. Seems my oem is locked. I really need help on how to go about fixing this.

Related

Error using fastboot

Hello,
I have a Google Nexus One that doesn't start up, i tried booting into bootloader and it works fine. I hadn't rooted my phone, so i did, everything was working fine, then i couldn't boot into recovery, i would get an exclamation point with the green android.
I am trying to flash clockworkrecovery, or Recovery_RA, however everytime I try to use the fastboot command it gives me the following error: ERROR: Unable to create a plug-in (e00002c7) and I have to shut down the terminal.
I searched for the error but couldn't find anything, is there anyway to install a recovery image, my phone doesn't boot up so i can't access anything, it just blocks on the splash screen with the Unlock icon, and in the bootloader, it says Unlocked.
I don't know if it helps but i have the HBOOT-0.35.0017
When I Rooted and flashed superboot, the command was working fine.
Any help is appreciated.
Thanks.
I just restarted the whole process from different sources and flashed Oxygen!
Working great!
If a mod can please close the thread

(Solved) Nexus 6 can't get past bootloader.

Apologies if this is a repost, I couldn't find anything that was specifically related. My Nexus 6 updated to 6.0.1 recently, worked fine. Next day, battery had run out of charge, plugged it in and it would only boot up to the bootloader menu. It won't boot up fully, or won't boot up recovery mode either. In the bootloader logs I get the following;
'failed to validate boot image: ret=-1'
If you try to run recovery mode;
'failed to validate recovery image: ret=-1'
I've tried to flash a stock recovery image and a stock boot image but to no success. Anyone have any solutions? Bootloader is unlocked and device is not and has not been rooted.
Edit - Nexus 6 fully working again! For whatever reason, I took out the SIM card tray and it worked first time. Thank you for all the responses!!
benjackson26 said:
I've tried to flash a stock recovery image and a stock boot image but to no success. Anyone have any solutions? Bootloader is unlocked and device is not and has not been rooted.
Click to expand...
Click to collapse
What does fastboot say?
benjackson26 said:
Apologies if this is a repost, I couldn't find anything that was specifically related. My Nexus 6 updated to 6.0.1 recently, worked fine. Next day, battery had run out of charge, plugged it in and it would only boot up to the bootloader menu. It won't boot up fully, or won't boot up recovery mode either. In the bootloader logs I get the following;
'failed to validate boot image: ret=-1'
If you try to run recovery mode;
'failed to validate recovery image: ret=-1'
I've tried to flash a stock recovery image and a stock boot image but to no success. Anyone have any solutions? Bootloader is unlocked and device is not and has not been rooted.
Click to expand...
Click to collapse
Have you tried booting directly to your recovery? Try the following command without the quotes and replace "xxx.img" with the name of your custom recovery: "fastboot boot xxx.img". example.. fastboot boot twrp.img
istperson said:
What does fastboot say?
Click to expand...
Click to collapse
It says it's sending 'recovery', writing 'recovery' and then finished. I restarted bootloader after it had done and tried to enter recovery mode but the same thing happened. It does say now in bootloader logs 'invalid boot image header'.
Then try booting to recovery.
http://forum.xda-developers.com/nexus-6/help/flash-n6-t3422968
May you find some solutions here
Okay, I took the SIM tray out, as I read that on the thread suggested, and I've been able to flash all the images necessary. Just booting up now, I'll let you guys know if it works! Thank you to everyone for the responses!!
This makes no sense as to why it works but it did just fix my spare nexus 6 that wouldn't turn on after sitting in a drawer for a week

XT1064 Stuck in fastboot mode (Recovery option wont open)

Hi guys, I buyed a phone used phone with this problem. The original owner tryed to flash a custom rom and at the middle of the progress the phone shut down because low battery. Then, when they turned on the phone, it only boot in fastboot mode. In fastboot mode, Recovery option wont open, Normal boot wont open too. The bootloader is unlocked. Then, i tryed to flsah a 5.0.2 stock rom but the console show me up an error like "FAILED" or "bootloader FAILED" The phone shows "recovery downgrade" in purple. I tryed 6.0.0 too and Kit Kat for the XT1064 USA version. I cant flash nothing, always the same error. i installed Motorola drivers, ADB, etc. Any help?
Bootloader version is: 48.07. I serarched this number in google and it shows a 5.1.1 custom rom. Propably this rom was the same that he tryed to flash before, i dont know. Unlocked status also is 3.
Edit 1: When a choose "Normal boot" it says: Invalid boot Image Header! Fastboot reason: Fall-Through from recovery boot mode.
When i choose "Recovery" it says: Invalid boot Image Header
boot up failed
When i choose "Factory": The phone just restarts into fastboot again...
Checking Motorola Device Update, the firmware inside this phone is: 21.11.17.titan.retuaws.retuaws.en.us what it means, it have android 5.0.2 Lollipop, right?
Hope you can help me
Thanks.

Stuck at "your device is booting now..." after flashing a rom

When I was trying to root my P10 I was trying to install SuperSU via TWRP but my file names were crypted, and I couldn't find the .zip file.
After some research I found out that it's a common problem, and can be solved by flashing a custom rom (no-verity-opt-encrypt.xxx.zip)... And that is supposed to decrypt the filenames.
After sideloading that file, I can't boot my phone as I get stuck on a screen saying: "your device is booting now..."
I can get to huawei eRecovery by pressing the volume up - I can't do a factory reset, it just says your device is not supported.
I can also get to fastboot & recovery mode screen, and by typing "fastboot devices" in console I can see my device's number so I can acces it.
If I type fastboot flash recovery twrp-3.1.0-0-P10.img it would successfully fiinish but it wont do anything.
Can I somehow fix this?
EDIT: saved the phone with
https://forum.xda-developers.com/p10/help/model-t3713886/post74719465#post74719465

Bricked leeco le2

Hi guys,
I've a leeco le2, it's in some sort of bootloop. I now have a phone which I hope is not actually bricked.
To cut to the chase:
The phone boot loops - it shows the "Leeco" on the black background for less than a second, then reboots, after 2 seconds, it comes back up with the "Leeco" and reboots, and so on.
I can get into fastboot mode. Interestingly, the status shows "Device is LOCKED"
I cant get to recovery mode. It just goes into the boot loop again.
Using the adb tools, I cant issue the "fastboot flashing unlock" or "fastboot oem unlock" commands because it returns: "FAILED (remote: 'oem unlock is not allowed')"
I am unable to get into the phone OS to change the settings because the phone is boot looping
. I am flashed several time in flashone,qfil and Miracle thunder but problem is same.
Given the fact I am unable to get to recovery, I am unable to sideload an OTA zip. And given the fact that I cant boot into the OS, I cant enable oem unlocking.
Do I have any hope at resurrecting this phone in any way? please help me
Check this : https://forum.xda-developers.com/t/...-le-2-s3-noob-friendly.3515555/#post-69996355

Categories

Resources