Database Develop

Stuck in Fastboot Flash Mode PLease Help

Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?

It's stock, locked and unrooted. All you did was try to install their OTA right? Sounds like their fault to me.

Calleja said:
Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?
Click to expand...
Click to collapse
you are going to have to flash a factory image

simms22 said:
you are going to have to flash a factory image
Click to expand...
Click to collapse
But how if the Rootkit can't? I can't seem to be able to flash anything to the device :/

Calleja said:
But how if the Rootkit can't? I can't seem to be able to flash anything to the device :/
Click to expand...
Click to collapse
rootkit is nothing official and only has in it whatever the developer has in it, flashing a factory image is why we have fastboot. if the rootkit cant do it, fastboot can. anyways, new users, newbs, should never be using root toolkits.

simms22 said:
rootkit is nothing official and only has in it whatever the developer has in it, flashing a factory image is why we have fastboot. if the rootkit cant do it, fastboot can. anyways, new users, newbs, should never be using root toolkits.
Click to expand...
Click to collapse
I wouldn't consider myself a newb, I've used fastboot and adb to flash factory images before. I used the toolkit in this instance because googling around made the toolkit's Soft Brick option seem like my best bet. It did not work.
How do I do that if the Fastboot Flash Mode seems to be borked/soft bricked and I can't seem to unlock the bootloader?

Calleja said:
I wouldn't consider myself a newb, I've used fastboot and adb to flash factory images before. I used the toolkit in this instance because googling around made the toolkit's Soft Brick option seem like my best bet. It did not work.
How do I do that if the Fastboot Flash Mode seems to be borked/soft bricked and I can't seem to unlock the bootloader?
Click to expand...
Click to collapse
because before unlocking the bootloader, you have to enable the developer setting. if your bootloader is still locked, then there is nothing that you can do except try to get a rma, sorry.

simms22 said:
because before unlocking the bootloader, you have to enable the developer setting. if your bootloader is still locked, then there is nothing that you can do except try to get a rma, sorry.
Click to expand...
Click to collapse
The developer setting WAS unlocked before all this started.... the problem seems to be with the partition table? Does anyone have any ideas?

Calleja said:
The developer setting WAS unlocked before all this started.... the problem seems to be with the partition table? Does anyone have any ideas?
Click to expand...
Click to collapse
oh, it was unlocked? and you tried unlocking the bootloader?

simms22 said:
oh, it was unlocked? and you tried unlocking the bootloader?
Click to expand...
Click to collapse
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?

Calleja said:
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?
Click to expand...
Click to collapse
Have you tried doing fastboot oem unlock? The cammands you're using are for the 6P

nms247 said:
Have you tried doing fastboot oem unlock? The cammands you're using are for the 6P
Click to expand...
Click to collapse
Yeah, fastboot oem unlock brings up:
FAILED (command write failed (Unknown error))
The funny thing is I get the same exact error when I try "fastboot oem device-info", is that a driver/fastboot installed wrong thing, maybe? (I had only used fastboot from OSX before, now on Win10, although "fastboot devices" does seem to work)

Calleja said:
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?
Click to expand...
Click to collapse
you are missing the one and only command that you can unlock the bootloader with.. fastboot oem unlock. if it gets unlocked, then you can flash a factory image.

simms22 said:
you are missing the one and only command that you can unlock the bootloader with.. fastboot oem unlock. if it gets unlocked, then you can flash a factory image.
Click to expand...
Click to collapse
Ok, so if "fastboot oem unlock" returns "FAILED (remote failure) there's nothing whatsoever I can do? RMA is the only option?
The first android device I don't root and leave completely stock and it's the only one I've ever bricked..... sigh

No, Google bricked it, with his stupid OEM unlocking switch, which is totally stupid. But they'll give you a new one.

istperson said:
No, Google bricked it, with his stupid OEM unlocking switch, which is totally stupid. But they'll give you a new one.
Click to expand...
Click to collapse
Anyone know how trustworthy Motorola's RMA service is in Mexico? Bought the N6 through motorola.com.mx, kinda regretting that decision now.

help
Calleja said:
Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?
Click to expand...
Click to collapse
How do you overcome? can show me the
thanks !

(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

Nexus 6 Bootloop Issue/ Android N - Help!

I've been running the Android (N) Beta program for almost a month now. Yesterday, when I picked the phone up, it just simply turned off. When I tried to boot it up, it got stock in a Bootloop. The phone would not go past the boot animation and the only screen I would get is "Enter Your Password), and after it, it's an endless bootloop. (I have not tried to do anything on the phone, just the official stock build from Google).
When I go into the Bootloader it displays the following:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.21 (sha-f12f8c2, 2016-05-10 11:30:37)
Baseband: D4.01-9625-05.39+FSG-9625-02.113
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: ZX1G22T6ZZ
CPU: APQ8084 ES1.1
eMMC: 32GB Sandisk RV=07 PV=01 TY=57
DRAM: 3072MB Samsung S8 SDRAM DIE=6GB
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Status Code: 2
Transfer Mode: USB Connected

Same Problem
I encountered same problem yesterday I have TWRP installed In recovery i erased cache and dalvik cache then phone booted in normal mode I also have Android (N) Beta program
mkmathers said:
I've been running the Android (N) Beta program for almost a month now. Yesterday, when I picked the phone up, it just simply turned off. When I tried to boot it up, it got stock in a Bootloop. The phone would not go past the boot animation and the only screen I would get is "Enter Your Password), and after it, it's an endless bootloop. (I have not tried to do anything on the phone, just the official stock build from Google).
When I go into the Bootloader it displays the following:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.21 (sha-f12f8c2, 2016-05-10 11:30:37)
Baseband: D4.01-9625-05.39+FSG-9625-02.113
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: ZX1G22T6ZZ
CPU: APQ8084 ES1.1
eMMC: 32GB Sandisk RV=07 PV=01 TY=57
DRAM: 3072MB Samsung S8 SDRAM DIE=6GB
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Status Code: 2
Transfer Mode: USB Connected
Click to expand...
Click to collapse

karwankar said:
I encountered same problem yesterday I have TWRP installed In recovery i erased cache and dalvik cache then phone booted in normal mode I also have Android (N) Beta program
Click to expand...
Click to collapse
I'll make sure to check it now, but one thing my friend, is your phone Locked/Unlocked ?

Quick question. With being enrolled in the beta program, do updates overwrite the recovery? Meaning you have to flash TWRP every time?

karwankar said:
I encountered same problem yesterday I have TWRP installed In recovery i erased cache and dalvik cache then phone booted in normal mode I also have Android (N) Beta program
Click to expand...
Click to collapse
Can you tell me which TWRP did you install on your phone

Could you not reflash via NRT?

XxD34THxX said:
Could you not reflash via NRT?
Click to expand...
Click to collapse
thing is, whenever I try to use NRT to fix the problem it demands for the Bootloader to be unlocked, and for it to be unlocked it should be restarted and so as NRT says, and since it's in a bootloop it's no good. Tried to unlock the bootloader via cmd like it would happen on android M you know after entering certain commands, then on the phone a message telling you your phone will be wiped appears, but the thing is, a new menu drops in cm telling as in repartition, format and stuff, and nothing on the phone appears, and to be honest I don't wanna be too foolish and wreck the phone or something, since these type of things are not in my field

Install minimal fastboot and adb drivers, use fastboot and flash latest mm factory image without sim card, should work. Don't forget to unlock your bootloader after that, should never been locked if you like to play around.

Unlocked
Sorry for late reply but my phone is unlocked
mkmathers said:
I'll make sure to check it now, but one thing my friend, is your phone Locked/Unlocked ?
Click to expand...
Click to collapse
---------- Post added at 01:38 PM ---------- Previous post was at 01:37 PM ----------
TWRP 3.0.2-0
mkmathers said:
Can you tell me which TWRP did you install on your phone
Click to expand...
Click to collapse

The only choice is awaiting newest OTA with higher version of bootloader (now you have v. 71.21).

Asus k013 stuck on boot.

Please excuse my lack of knowledge I am a complete beginner.
My wife left her working Asus k013 (do not know which model as I no longer have box) on charge over night, next day it would no longer get beyond the boot screen. We are stuck with the Asus Logo and the revolving boot start symbol.
I have tried the start/volume up and start/volume down options to do factory reset but just returns to the boot start. If I hold the buttons down for a long time it just shuts down. I them tried downloading 'clear data' to sd card but this presumably requires the tablet to boot before it works.
I have purchased a new tablet for her so I do not want to send the tablet for repair but would really like to get it working as spare and to experiment with rooting etc. to try an improve my knowledge.

If you boot with Power + Volume Down (stop pressing power once the backlight turns on, but keep pressing Volume Down) does it boot into the Droidboot screen (with NORMAL BOOT, RECOVERY MODE buttons)?

Asus k013 stuck on boot
lambdadroid said:
If you boot with Power + Volume Down (stop pressing power once the backlight turns on, but keep pressing Volume Down) does it boot into the Droidboot screen (with NORMAL BOOT, RECOVERY MODE buttons)?
Click to expand...
Click to collapse
Thanks for trying but this still ends up trying to do a normal boot without completeing

593jim said:
Thanks for trying but this still ends up trying to do a normal boot without completeing
Click to expand...
Click to collapse
Did you install the Lollipop (Android 5.0) update on it when it was still working or were you still on KitKat (Android 4.4)?

Asus k013 stuck in boot
lambdadroid said:
Did you install the Lollipop (Android 5.0) update on it when it was still working or were you still on KitKat (Android 4.4)?
Click to expand...
Click to collapse
Not sure which release it is on. Received an OTA a while ago from the original when bought.
Upgrade was not recent so do not think that's it unless the OTA was done last weekend.

593jim said:
Not sure which release it is on. Received an OTA a while ago from the original when bought.
Upgrade was not recent so do not think that's it unless the OTA was done last weekend.
Click to expand...
Click to collapse
Huh, well. Do you get a "Fastboot starting..." screen if you press Volume Down + Volume Up + Power while turning the tablet on?

lambdadroid said:
Huh, well. Do you get a "Fastboot starting..." screen if you press Volume Down + Volume Up + Power while turning the tablet on?
Click to expand...
Click to collapse
Great we have a start, doing as you said has brought up 'Fast boot starting' then 3 lines #1, #2, #3 but does not move from there.
Thanks for your help so far, how do I proceed please.
Regards,
Jim

593jim said:
Great we have a start, doing as you said has brought up 'Fast boot starting' then 3 lines #1, #2, #3 but does not move from there.
Thanks for your help so far, how do I proceed please.
Regards,
Jim
Click to expand...
Click to collapse
Download http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip.
Install ADB+Fastboot on your PC. There are various guides available online for this, so you should google or take a look at https://wiki.lineageos.org/adb_fastboot_guide.html
Boot into that mode again and connect the tablet to your PC (via USB). On a command prompt, verify that...
Code:
fastboot devices
... displays a device. Extract "droidboot.img" from the ZIP you've downloaded in the first step, then run:
Code:
fastboot boot droidboot.img
Does it now show the "NORMAL BOOT" etc screen?

Asus k013 stuck on boot
lambdadroid said:
Download http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip.
Install ADB+Fastboot on your PC. There are various guides available online for this, so you should google or take a look at https://wiki.lineageos.org/adb_fastboot_guide.html
Boot into that mode again and connect the tablet to your PC (via USB). On a command prompt, verify that...
Code:
fastboot devices
... displays a device. Extract "droidboot.img" from the ZIP you've downloaded in the first step, then run:
Code:
fastboot boot droidboot.img
Does it now show the "NORMAL BOOT" etc screen?
Click to expand...
Click to collapse
Sorry so long to get back, I got help from a friend over the weekend but we did not succeed.
Had another go today and got to normal boot. Tried to go to recovery and got failed. Volume down offers 'power off' 'recovery' and restart bootloader.
I have attached a screen shot, the last line shows
E: No valid installer medium found.
I seem have a problem with the files I downloaded to my computer have the 'user/adb-fastboot/' file but cannot find the bring up the tools extention.
Regards,
Jim

Asus k013 stuck on boot
593jim said:
Sorry so long to get back, I got help from a friend over the weekend but we did not succeed.
Had another go today and got to normal boot. Tried to go to recovery and got failed. Volume down offers 'power off' 'recovery' and restart bootloader.
I have attached a screen shot, the last line shows
E: No valid installer medium found.
I seem have a problem with the files I downloaded to my computer have the 'user/adb-fastboot/' file but cannot find the bring up the tools extention.
Regards,
Jim
Click to expand...
Click to collapse
Sorry, should have added 'Fastboot device' no longer works.
May need to go back to my friend for help.
Can't see how to attach the photo.
Regards,
Jim

593jim said:
Sorry so long to get back, I got help from a friend over the weekend but we did not succeed.
Had another go today and got to normal boot. Tried to go to recovery and got failed. Volume down offers 'power off' 'recovery' and restart bootloader.
I have attached a screen shot, the last line shows
E: No valid installer medium found.
I seem have a problem with the files I downloaded to my computer have the 'user/adb-fastboot/' file but cannot find the bring up the tools extention.
Regards,
Jim
Click to expand...
Click to collapse
Sorry, this might have been confusing but I didn't post all needed steps yet. I just wanted to make sure you actually get to the droidboot screen.
Since you managed to get there, this is what I recommend: Use https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 on the "NORMAL START, RECOVERY MODE" etc screen to get into a temporary recovery session. For this tablet you should use trigger T4 and TWRP portrait. Copy the UL-K013-WW-12.10.1.36-user.zip you already downloaded to a external SD card first.
Once you are in recovery, you can try flashing the ZIP. This might restore your system to a usable state.
As for fastboot devices not showing any device: On Windows you may need to install the right USB drivers to make it work properly. You can try the Universal ADB drivers available from https://adb.clockworkmod.com/ or the USB driver provided by ASUS http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ADB_driver.zip. I cannot help you with this because I'm not using Windows much myself.

Hi. I'm also k013 user, same problem. Stuck on fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
I also tried "fastboot boot droidboot.img" in cmd but my k013 reboot back into fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
Can you help me in this?
Tia
---------- Post added at 06:46 AM ---------- Previous post was at 06:40 AM ----------
Hi. I'm also k013 user, same problem. Stuck on fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
I also tried "fastboot boot droidboot.img" in cmd but my k013 reboot back into fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
Can you help me in this?
Tia

Question [Fixed] ASUS logo stucks on recovery, only access to bootloader

Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.

Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.

To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.

From the bootloader you should be able to flash the raw image again, it should flash everything

Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.

semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason

Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).

semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.

Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.

Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?

I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.