Database Develop

Stuck in bootloop. No custom recovery or unlocked bootloader.

So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?

As far as I know the only fix is the one in that link but it does require custom recovery. I'm assuming the fastboot boot command doesn't work when locked but I've never tried, if it does then you could temp boot into twrp. Worth a shot I guess.
Hindsight's 20/20 but NEVER touch anything other than your data or cache partition with a locked bootloader. Google's security jump with lollipop has caused nothing but havoc for us.

ChaosDr0id said:
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
Click to expand...
Click to collapse
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info

or, you can grab the factory image of whatever version of android that you were on, "unzip" it, grab the system.img, and flash it via fastboot. its the same thing as if was a "custom recovery", youre just reflashing the rom, and wont lose your data
first thing id do is flash a custom recovery and unlock my bootloader, and make a backup in recovery.

AlkaliV2 said:
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
Click to expand...
Click to collapse
Hi, thanks for the reply.
It says
'device info' is not a supported oem command. See fastboot oem help.
FAILED <remote failure>
However I'm fairly certain the bootloader is still locked as I was unable to flash TWRP, or a stock image of android, as it tells me to unlock before doing those things.

AFAIK when you have this problem together with a stock recovery and a locked bootloader means bricked. >repair

Your bootloader is lock and you can't boot android to enable OEM unlock to unlock it. You have ruined your phone and there is no known fix.
RMA time for you.
Literally no solution unless you can invent one on your own.

Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?

CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
yes

CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc?
Click to expand...
Click to collapse
Absolutely. Otherwise anybody with a notebook could swipe your phone, download everything you've got on it, then return it without you knowing, and that would mean more nekkid selfies on reddit.

CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
The entire concept of a locked bootloader is that you can't flash images through it.

How to Unlock Bootloader, Flash TWRP, and ROOT LG G4 H811 T-Mobile.

Now, I know this tutorial exists all over the place, like one-click and UnjustifiedDev tutorial but none seemed to work. I am sharing the steps and method I used IN-DEPTH command for command on how to unlock, flash, and root the LG G4 from Tmobile.
NOTE THIS WILL FACTORY RESET YOUR DEVICE SO BACKUP ALL YOUR DATA
1. Activate developer settings by entering the about section and tapping build number 7 times.
2. Enter your developer settings and MAKE sure you have 'Allow OEM unlock' and 'USB Debugging' enabled.
3. Download the latest SuperSU zip and move it onto your SD card.
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
5. Once the Command window is linked to the folder, connect your device via USB and allow the connection.
6. On the command window type 'adb reboot bootloader' and the device should reboot with the fastboot options on the upper left of the phone screen
7. Once again on the command window type 'fastboot oem unlock' and the command window should say OKAY and complete the action.
8. To Confirm that the device is unlocked type 'fastboot getvar unlock' and the window should respond with 'Unlock: YES'
9. Now download the latest available TWRP and drop it into the platform-tools folder where your ADB.exe is located.
10. On your Command Window type 'fastboot flash recovery "NAME OF TWRP FILE" if you get the error ' cannot load 'twrp-X.X.X.X-h811' you need to add .img to the end of the filename
11. Once the process completes you will see 'target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 1.088s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time:'
THE FAILED UNKNOWN COMMAND NOTICE CAN BE IGNORED
12. Once the process completes the device may not let you enter recovery from the traditional method using the buttons on the back of the phone so the easiest method is to, on your command window, type
'fastboot boot twrp-2.8.7.0-h811.img' and the device should respond within just a few seconds and reboot into TWRP.
13. Once the device reboots, enter twrp and tap on install and locate the SuperSU.zip and allow it to install.
14. Once the process completes successfully, wipe cache to be safe and reboot your device.
15. Resetup your device and restore your data if necessary and install a root checker from Google Play to confirm root!
THATS IT GUYS! This took me a long time to figure this out and it's a combination of different methods to get it to work!
All credit goes to the Devs of TWRP and SuperSU!
I posted in General because I'm a new user so please move to appropriate forums! thanks!

This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things

Please refer to the first line of my post. I understand that there are a large series of posts about how to do this but this is the only one that works for me even with me running android M.

Shows how to install TWRP for devices on 6.0
marcviado said:
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Click to expand...
Click to collapse
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.

joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.

marcviado said:
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
Click to expand...
Click to collapse
It is totally there... I looked at that guide for a really long time too. I concede.

joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Yes it does. You do not need to use any codes, just enable oem unlocking in dev settings and type fastboot oem unlock and it will be unlocked.

Can't get twrp installed
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks

I have the G4 LGUS991 gotta can I tell if it's h811?

4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
Click to expand...
Click to collapse
What if your device could not be found despite having the latest LG drivers?

mr_blonde55 said:
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
Click to expand...
Click to collapse
Can't remember which thread, but I ran into the same problem you have and solved it by using an additional command like fastboot erase userdata. If you google it, you'll see the commands I mean. Basically, I had to factory reset the device through fastboot first (it sits there for several minutes to do this) before installing/booting twrp. And yes, the log will show that the process was successful, not a failure as mentioned by OP. Once I did that, I booted in twrp and flashed the rom zip without any trouble.

So, you guys mean we have Marshmallow on T mobile G4, I didn't get it yet.
Please somebody give me a link to the OTA or update.zip for MM of LG G4

This one worked for me!
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...

If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Sent from my LG-H811 using XDA-Developers mobile app

NardVa said:
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Click to expand...
Click to collapse
Could you help me with is or point me in the right direction ? Please & thanks
Sent from my LG-H811 using XDA Labs
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
Majestyk007 said:
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
Click to expand...
Click to collapse
I keep getting this problem.
Sent from my LG-H811 using XDA Labs

I've just got a H811 and it automatically updated to Android 6 when I loaded it up. I will be giving this guide a go this evening. Many of the other links on the web are for lollipop and were released when the phone came out, so I'm thankful that this seems straight forward. http://uslugi.nie-spamuj.eu/rtv,1,0.html Hoping that it goes that way.

How to lock bootloader or hide status: bootloader state: unlocked?
Sr for my English!

So I followed this guide and I appear to be soft bricked at best and hard bricked at worst. I did read the other guide linked in the second response and I found a major difference that might be my problem. So in the guide linked in the second response it doesn't say to even try flashing TWRP from fastboot. It says to just boot from it then install it from within TWRP. I followed the steps verbatim and my phone is currently stuck at the T-Mobile splash screen. Any suggestions? I have tried to boot into recovery by holding down and the power and releasing the power for a second when the logo comes up. I get into the Factory data reset screen and select Yes twice then the green guy shows up and the phone resets but stays at the T-Mobile splash screen. I don't have ADB or fastboot with the phone in this state.

hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks

rmdeathwish said:
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
Click to expand...
Click to collapse
It's not buggy at all. All the tedium has already been bypassed if you already have Marshmallow installed.
Follow autoprime's original guide, steps 2, 4, 5, 6, and 8 under the Bootloader OEM Unlock + Root section. I would recommend a more up-to-date version of TWRP than 2.8.7.1 though. Go to TWRP's download site for the latest version.

Unrooting Nexus 6 with a mid 2010 MacBook Pro

Built-in cd/dvd player is broken, so i can't put Windows 7 on the Mac. That means no tool kits. Tried using terminal command line, but that didn't work either. Is there any other way to unroot this puppy? Thanks for any help.

I'm a bit uncertain what you want to do. Unroot is a lot different whether you still have stock rom, or you use a custom rom.
Before you start, backup all data on the phone, in case it gets deleted.
For stock, use fastboot to flash the newest factory image from Google. I think fastboot is the same on Mac. Afterwards, you can relock the bootloader of you like.
For custom rom, reflash the rom in recovery without any root.

All I want to do is unroot my Nexus 6. Since I can’t put Windows7 on my Mac, I have to rely on using terminal commands. That’s the problem. If I could have gotten the Mac to recognize the Nexus, I would have been done two days ago. I guess that I need a step by step guide on using my terminal.

You'll need to tell more about what you have tried, and what happened exactly.
- can you connect the phone to the Mac with USB and do ordinary file transfer?
- do you know how to put the phone in fastboot mode?
- what happens when you type fastboot devices in the command prompt?

Terminal says" command not found". File transfer works. When i type in "ls", i do get a list of stuff. What i need is the exact commands, one at a time, to get this Nexus 6 unrooted.

Command not found means that you either haven't installed fastboot at all. Or it is in a place where the command prompt doesn't look.
Try this guide to get fastboot ready:
Install and Use ADB and Fastboot on Mac [How to]
If you want to use ADB commands in Mac terminal, you'll have to download and install ADB and Fastboot on Mac or you'll get 'not found' error.
technastic.com

Followed the guide, but it doesn't list my Nexus 6. Anyway, what are the rest of the commands that i need to unroot phone?

So is fastboot now working for you? The Nexus is listed on fastboot devices?
If yes, you can flash the Google factory image:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
There are some instructions there as well.
Of course, if you would rather have a custom rom, you won't want to flash factory.
Note that the data on the phone may be lost in the process.

I will try this later today, but there is one thing that I’m curious about. I do not have my SIM card in the Nexus, it’s in my other phone. Is that the reason why my Nexus serial number isn’t coming up in flash boot?

All i'm getting is "permission denied". WTF is going on??????

I'm done with this. It's taking up too much of my time, and causing me too much aggravation. Thanks for trying guys.

Boooader locked in developer options but root working fine

Developer option shows bootloader as locked but after reboot bootloader shows as unlocked . twrp working but Fastboot not working so I'm afraid I might brick my device as I can't flash fastboot rom. Please help.

I wanna know what you mean by 'Fastboot not working'. Does it mean you can't boot into fastboot mode, or does it mean you can't access fastboot commands on your pc?
Also i wanna know, while unlocking Bootloader. Did you used commands
Code:
fastboot oem unlock
and
Code:
fastboot oem unlock_critical
?

The device does boot into fastboot but doesnt respond to any fastboot command
It doesn't even show up on typing fastboot device
I unlocked the bootloader using miunlocktool
But the device doesnt even show up in the tool

pythonner said:
The device does boot into fastboot but doesnt respond to any fastboot command
It doesn't even show up on typing fastboot device
I unlocked the bootloader using miunlocktool
But the device doesnt even show up in the tool
Click to expand...
Click to collapse
If it's not responding to fastboot commands I worry that if correct drivers are installed on your pc.
Plug-in ur device while in fastboot mode to your pc.
Open Mi Unlock tool(this works very first time, you don't even have to install this tool). There's a setting icon on top right corner.
A dialogue box will appear, displaying to install drivers.
Install 'em. It will ask you to remove and plug-in your device again.
Now, download the platform tools file.
Open cmd in the platform tools folder.
Now try using fastboot commands.

It's same for me.
You can ignore that safely.

eleven.co said:
If it's not responding to fastboot commands I worry that if correct drivers are installed on your pc.
Plug-in ur device while in fastboot mode to your pc.
Open Mi Unlock tool(this works very first time, you don't even have to install this tool). There's a setting icon on top right corner.
A dialogue box will appear, displaying to install drivers.
Install 'em. It will ask you to remove and plug-in your device again.
Now, download the platform tools file.
Open cmd in the platform tools folder.
Now try using fastboot commands.
Click to expand...
Click to collapse
I updated the usb driver but unlock tool can't even detect the devices and when I type fastboot devices in platform tools the device is also not detected
I'm afraid of installing custom roms because if I brick it I will not be able to even flash the official fastboot rom

VD171 said:
It's same for me.
You can ignore that safely.
Click to expand...
Click to collapse
Actually when I type fastboot devices in platform tools the device is not even detected. So I'm afraid that if I flash custom rom and brick it I will be unable to flash even the official fastboot rom.

pythonner said:
I updated the usb driver but unlock tool can't even detect the devices and when I type fastboot devices in platform tools the device is also not detected
I'm afraid of installing custom roms because if I brick it I will not be able to even flash the official fastboot rom
Click to expand...
Click to collapse
Boot your phone, connect through USB to PC. Now check in Windows File Explorer. Is your device visible there?
If not, open Device Manager and you'll find something with the name adb (You can go through this guide). In my case it was under Acer. Just update those drivers manually and see if your device is visible now.

eleven.co said:
Boot your phone, connect through USB to PC. Now check in Windows File Explorer. Is your device visible there?
If not, open Device Manager and you'll find something with the name adb (You can go through this guide). In my case it was under Acer. Just update those drivers manually and see if your device is visible now.
Click to expand...
Click to collapse
the devices shows up in file explorer and device manger when its turned on but after putting in fastboot mode the platform tools cant detect the device

pythonner said:
the devices shows up in file explorer and device manger when its turned on but after putting in fastboot mode the platform tools cant detect the device
Click to expand...
Click to collapse
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.

eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
Now developer options is showing as unlocked and adb is also working good
but fastboot is still not working when I type fastboot devices It returns nothing

eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
What could be possible explanation to adb working but fastboot not working. The usb cable is tight and bootloader is unlocked even in developer options

eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
I just realised that I flashed twrp using the root app flashify. Could that be the reason for root not working

VD171 said:
It's same for me.
You can ignore that safely.
Click to expand...
Click to collapse
If you're rooted and have magisk hide enabled, it's normal, Magisk spoofs locked bootloader to pass safetynet in MIUI

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.