Database Develop

[Q] Trying to flash drunk- failed. Now what?

Ok guys, so I was trying to flash the software on my Sprint HTC One with a custom one, while drunk. Needless to say it didn't work. I suspect that chrome f*cked up downloading the rom, because it was only 800mb, and should have been about 1gb. Now, the phone isn't working. When I try to turn it on it shows the htc logo and then boots up in fastboot. Fastboot still receives cmd commands, but I still havent found a way to flash an RUU on it. Tryed with twrp as a recovery- cant mount to computer. Tryed sending the file to phone through cmd- some error about not working radio came through. I'm cutting corners explayning all the methods I tryed to make it work, but there were a lot of them and I dont remember all. I have flashed the boot and the recovery back to the stock ones, bootloader IS unlocked. Phone vertion (as shown in the bootloader screen):
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT- 1.44.0000
OpenDSP-v31.120.274.0617
eMMC- boot
Jul 5 2013,17:19:22:-1
My question is how do I return it to stock condition (or unlocked to all networks if possible)? Please, I've been trying to fix it on my own for over a week now, and am getting desperate. If possible please give links to step-by-step tutorials and/or files I'll need. Thank you in advance.
PS.: Also, for some reason my computer does fails to install the HTC MTP device driver. Could it be from that, and if it is- will using a different computer solve the problem (tryed a million times to fix that as well- no luck)?

drobalqk said:
Ok guys, so I was trying to flash the software on my Sprint HTC One with a custom one, while drunk. Needless to say it didn't work. I suspect that chrome f*cked up downloading the rom, because it was only 800mb, and should have been about 1gb. Now, the phone isn't working. When I try to turn it on it shows the htc logo and then boots up in fastboot. Fastboot still receives cmd commands, but I still havent found a way to flash an RUU on it. Tryed with twrp as a recovery- cant mount to computer. Tryed sending the file to phone through cmd- some error about not working radio came through. I'm cutting corners explayning all the methods I tryed to make it work, but there were a lot of them and I dont remember all. I have flashed the boot and the recovery back to the stock ones, bootloader IS unlocked. Phone vertion (as shown in the bootloader screen):
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT- 1.44.0000
OpenDSP-v31.120.274.0617
eMMC- boot
Jul 5 2013,17:19:22:-1
My question is how do I return it to stock condition (or unlocked to all networks if possible)? Please, I've been trying to fix it on my own for over a week now, and am getting desperate. If possible please give links to step-by-step tutorials and/or files I'll need. Thank you in advance.
Click to expand...
Click to collapse
It sounds like you have the same problem that a lot of people are getting into around here, myself included. You tried to flash a non-cdma compatible rom onto your phone.
There are numerous postings about how to fix this, however, it depends on the condition of your phone which step you take.
If you have recovery installed and you have access to recovery you will take different steps than if you only have access to fastboot.
You need to have a recovery installed and you need to relock your phone to fastboot ruu. Once that is done you basically start from scratch and unlick your phone again and then you can reinstall the recovery and then flash the correct cdma compatible roms.

MrFixit007 said:
It sounds like you have the same problem that a lot of people are getting into around here, myself included. You tried to flash a non-cdma compatible rom onto your phone.
There are numerous postings about how to fix this, however, it depends on the condition of your phone which step you take.
If you have recovery installed and you have access to recovery you will take different steps than if you only have access to fastboot.
You need to have a recovery installed and you need to relock your phone to fastboot ruu. Once that is done you basically start from scratch and unlick your phone again and then you can reinstall the recovery and then flash the correct cdma compatible roms.
Click to expand...
Click to collapse
The recovery I can install in a matter of seconds, same with relocking. I have the lastest vertions on both TWRP and Clockwork. Which one do I install and how do I proceed after? Thank you

drobalqk said:
The recovery I can install in a matter of seconds, same with relocking. I have the lastest vertions on both TWRP and Clockwork. Which one do I install and how do I proceed after? Thank you
Click to expand...
Click to collapse
do you have adb access? or only fastboot access?

MrFixit007 said:
do you have adb access? or only fastboot access?
Click to expand...
Click to collapse
adb- Im not sure. How do I check? Fastboot- I think so. It accepts my cmd commands for flashing recovery and rom (although when I tryed to flash rom it failed).

drobalqk said:
adb- Im not sure. How do I check? Fastboot- I think so. It accepts my cmd commands for flashing recovery and rom (although when I tryed to flash rom it failed).
Click to expand...
Click to collapse
In your command window in the same directory you run fastboot from, you should be able to run adb.
The easiest way to check is to type: adb devices
this should return a value if you are booted into recovery.
it will give you nothing if you aren't in recovery.
if you cannot get into recovery then you need to make sure your phone is unlocked and then fastboot a recovery onto your phone.

MrFixit007 said:
In your command window in the same directory you run fastboot from, you should be able to run adb.
The easiest way to check is to type: adb devices
this should return a value if you are booted into recovery.
it will give you nothing if you aren't in recovery.
if you cannot get into recovery then you need to make sure your phone is unlocked and then fastboot a recovery onto your phone.
Click to expand...
Click to collapse
I currently have the stock recovery flashed on it. Is that one going to work or should I flash TWRP/ Clockwork?

drobalqk said:
I currently have the stock recovery flashed on it. Is that one going to work or should I flash TWRP/ Clockwork?
Click to expand...
Click to collapse
as long as you can boot into recovery, it should work. i personally favor twrp, but any recovery should work.
try out some adb commands and see.
adb sevices
adb shell
if you get anywhere with those while booted into recovery you should be ok.

MrFixit007 said:
as long as you can boot into recovery, it should work. i personally favor twrp, but any recovery should work.
try out some adb commands and see.
adb sevices
adb shell
if you get anywhere with those while booted into recovery you should be ok.
Click to expand...
Click to collapse
adb devices returns no values
adb services returns big list of commands
adb shell returns error device not found.
I'm into TWRP v.2.6.1.0 start screen.

drobalqk said:
adb devices returns no values
adb services returns big list of commands
adb shell returns error device not found.
I'm into TWRP v.2.6.1.0 start screen.
Click to expand...
Click to collapse
did those adb errors or no devices found occur while your phone was showing the twrp start screen?
if yes, then we need to reboot into the bootloader-- to fastboot.
if no then try adb shell again while showing the twrp start screen.

MrFixit007 said:
did those adb errors or no devices found occur while your phone was showing the twrp start screen?
if yes, then we need to reboot into the bootloader-- to fastboot.
if no then try adb shell again while showing the twrp start screen.
Click to expand...
Click to collapse
Yes, I was IN TWRP recovery home screen. I'll try the commands in fastboot as soon as I come back from work. Thank you for the time you spend trying to help me, I do very much apreciate it.

drobalqk said:
Yes, I was IN TWRP recovery home screen. I'll try the commands in fastboot as soon as I come back from work. Thank you for the time you spend trying to help me, I do very much apreciate it.
Click to expand...
Click to collapse
It seems like you need to fastboot flash recovery onto your phone again.
Here are the steps as I think they should work to get you back up and running.
**Make sure your phone is unlocked. (it should display ***UNLOCKED*** at the top of the bootloader screen)
if you ARE unlocked do the following(+++see below if you are NOT unlocked+++)
1. from bootloader select fastboot - connect phone to computer. fastboot should change to fastboot usb when you have a good connection.
on your computer:
2. open a command window and navigate to the folder where adb and fastboot are located
3. type in "fastboot flash recovery xxxxxxxx.zip" where xxxxxxxx.zip is the name of recovery zip file without quotes. Make sure you download a good copy appropriate for your phone. I would use this one: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.1.0-m7wls.img
4. type fastboot reboot
on your phone:
5. once it is rebooted and in bootloader select recovery and boot into recovery.
on your computer:
6. once your phone shows recovery main screen then typeat the command prompt: adb shell
7. no matter what the prompt looks like type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
8. no matter if it errors or not type: adb reboot bootloader
9. type: fastboot oem lock
10. type: fastboot oem rebootRUU
11. type fastboot flash zip xxxxxxxxxxxxx.zip where xxxxxxxxxxxxx.zip is the name of the ruu.zip file. i would use this one: http://www.androidfilehost.com/?fid=22926241640219526
12 reboot your phone once that is successful!! If you get the "flush image again immideately" error message then repeat step 11. then reboot your phone.
you should now be running a stock sprint phone.
you can now unlock your phone again and reinstall a recovery.
to unlock your phone the second time:
13. boot your phone into bootloader then go to fastboot - make sure the phone is connected to the computer
14. on your computer type in: fastboot flash unlocktoken Unlock_code.bin
15. on your phone select unlock with volume rocker and press power once unlock is selected
16. on computer type: fastboot flash recovery xxxxxxxxx.zip where xxxxxxxxxx.zip is the same recovery zip file we used above in step 3
17. reboot your phone and you are now unlocked and you have a custom recovery installed and you can download a CDMA compatible rom to your phone and install it with the recovery like normal. or you can continue to run stock.
MAKE SURE YOU ONLY DOWNLOAD CDMA COMPATIBLE ROMS FROM THE SPRINT HTC ONE FORUMS.
enjoii!!
+++if you are NOT unlocked+++
try the following:
step 13
step 14
step 15
step 16
step 4
step 5
step 6-17
make sure you complete all the way through 17 after you do step 6. good luck and let me know what your results are.

MrFixit007 said:
It seems like you need to fastboot flash recovery onto your phone again.
Here are the steps as I think they should work to get you back up and running.
**Make sure your phone is unlocked. (it should display ***UNLOCKED*** at the top of the bootloader screen)
if you ARE unlocked do the following(+++see below if you are NOT unlocked+++)
1. from bootloader select fastboot - connect phone to computer. fastboot should change to fastboot usb when you have a good connection.
on your computer:
2. open a command window and navigate to the folder where adb and fastboot are located
3. type in "fastboot flash recovery xxxxxxxx.zip" where xxxxxxxx.zip is the name of recovery zip file without quotes. Make sure you download a good copy appropriate for your phone. I would use this one: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.1.0-m7wls.img
4. type fastboot reboot
on your phone:
5. once it is rebooted and in bootloader select recovery and boot into recovery.
on your computer:
6. once your phone shows recovery main screen then typeat the command prompt: adb shell
7. no matter what the prompt looks like type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
8. no matter if it errors or not type: adb reboot bootloader
9. type: fastboot oem lock
10. type: fastboot oem rebootRUU
11. type fastboot flash zip xxxxxxxxxxxxx.zip where xxxxxxxxxxxxx.zip is the name of the ruu.zip file. i would use this one: http://www.androidfilehost.com/?fid=22926241640219526
12 reboot your phone once that is successful!! If you get the "flush image again immideately" error message then repeat step 11. then reboot your phone.
you should now be running a stock sprint phone.
you can now unlock your phone again and reinstall a recovery.
to unlock your phone the second time:
13. boot your phone into bootloader then go to fastboot - make sure the phone is connected to the computer
14. on your computer type in: fastboot flash unlocktoken Unlock_code.bin
15. on your phone select unlock with volume rocker and press power once unlock is selected
16. on computer type: fastboot flash recovery xxxxxxxxx.zip where xxxxxxxxxx.zip is the same recovery zip file we used above in step 3
17. reboot your phone and you are now unlocked and you have a custom recovery installed and you can download a CDMA compatible rom to your phone and install it with the recovery like normal. or you can continue to run stock.
MAKE SURE YOU ONLY DOWNLOAD CDMA COMPATIBLE ROMS FROM THE SPRINT HTC ONE FORUMS.
enjoii!!
+++if you are NOT unlocked+++
try the following:
step 13
step 14
step 15
step 16
step 4
step 5
step 6-17
make sure you complete all the way through 17 after you do step 6. good luck and let me know what your results are.
Click to expand...
Click to collapse
Nope, adb still doesn't work. Could it be something wrong with the drivers my computer installs? Because when I'm in recovery my computer detects the device in "Other Devices" as "M7WLS", and I don't have a driver for that and neither does microsoft update. Any suggestions?

drobalqk said:
Nope, adb still doesn't work. Could it be something wrong with the drivers my computer installs? Because when I'm in recovery my computer detects the device in "Other Devices" as "M7WLS", and I don't have a driver for that and neither does microsoft update. Any suggestions?
Click to expand...
Click to collapse
Did you install HTC Sync or did you install the naked drivers from here?
Otherwise, where in the process did you get stopped?
EDIT: You can always PM me your teamviewer info and I can work on it.

[Q] Trying to flash zip, now fastboot doesn't work

Hi Guys,
So I have successfully S-OFF'd my device using rumrunner, and I was then using the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2358781 in order to flash my device to a Google Play Edition device.
It worked fine for the commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip
and then I got the expected error message. I then entered the same command again as instructed, but this time I got the message "waiting for device" which didn't go away.
I've tried rebooting my phone a few times, and I can no longer get any fastboot.exe commands to work, I just continuously get the "waiting for device"message. adb.exe still works correctly, so after rebooting my phone I can use adb to boot into fastboot (I know that's not the only way, I'm just saying it to demonstrate that adb appears to be fine) but after that no fastboot.exe commands work anymore.
My phone is running Software version 3.62.401.1. My Hboot I was very sure used to be 1.55 but now after that failed "fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip" it now shows as HBOOT 1.54.
Thanks guys, any help would be immensely appreciated.

Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?

SaHiLzZ said:
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
Click to expand...
Click to collapse
Trying another fast boot package didn't work, but a different computer did. Now I'm all set and ready to go thanks!
Just for the record, on the first computer my phone no longer showed up when I put in fastboot devices. I guess for some strange reason there's now a problem with the drivers on the first computer? I thought perhaps reinstalling HTC Sync would help that apparently not.
Anyways, that problem is solved until I want to do this again and want to use the first computer again.

Cannot get into recovery mode [bootloop]

Hey I cannot get into recovery mode, I don't really know why. This morning everything was ok: I rebooted my phone into recovery mode as usually, with no problems. THEN I rebooted my phone from the custom recovery, and then my phone went to bootloop: The bootloader screen went to black, then to my lockscreen and then to the bootloader screen, then to my lockscreen... etc. (bootloop)
I rebooted into recovery again and tried to do a normal wipe, because usually that's everything I need. But nothing happened: bootloop again.
So, I went to recovery once more to perform a full wipe and erase the data. Then I tried to flash CM13 and the Gapps, but nothing happend. Now, I cannot get into recovery, I'm stuck in the TWRP screen.
Help?
Sorry my bad english
My phone isn't rooted. I just unlock the bootloader

I had the same problem
It's easy just flash a newer version of Twrp using ADB fastboot from PC = problem solved

Thanks! Can you guide me step by step?
[email protected]!# said:
It's easy just flash a newer version of Twrp using ADB fastboot from PC = problem solved
Click to expand...
Click to collapse
I just flash a new version of TWRP and even the latest version of CWM but nothing, same problem. Bootloop in recovery's logo.
I asked to someone else in my city but they told me that the problem it's the motherboard

Cuervoazulado said:
Hey, thanks. Can you guide me step by step? I don't really know hpw to do that, so I don't want to make a mess.
Thanks, so much thanks!
Click to expand...
Click to collapse
Download newer twrp: https://dl.twrp.me/titan/
Download and install Minimal ADB and Fastboot Tool http://forum.xda-developers.com/showthread.php?t=2317790, install Motorola drivers from Motorola website: https://motorola-global-portal-de.custhelp.com/app/answers/detail/a_id/91819.
Paste the new recovery image into the Minimal ADB and Fastboot folder, reboot your device in fastboot mode (vol down+pwr), open Minimal ADB &Fastboot folder, hold shift, right click inside the folder and open a command window there. Type
Code:
fastboot devices
If your device is connected you'll see a string of numbers/letters. Type "fastboot flash recovery name-of-new-recovery.img", for example:
Code:
fastboot flash recovery twrp-3.0.0-0-titan.img
.
Type
Code:
fastboot reboot
.
You´re done.

Wolfcity said:
Download newer twrp: https://dl.twrp.me/titan/
Download and install Minimal ADB and Fastboot Tool http://forum.xda-developers.com/showthread.php?t=2317790, install Motorola drivers from Motorola website: https://motorola-global-portal-de.custhelp.com/app/answers/detail/a_id/91819.
Paste the new recovery image into the Minimal ADB and Fastboot folder, reboot your device in fastboot mode (vol down+pwr), open Minimal ADB &Fastboot folder, hold shift, right click inside the folder and open a command window there. Type
Code:
fastboot devices
If your device is connected you'll see a string of numbers/letters. Type "fastboot flash recovery name-of-new-recovery.img", for example:
Code:
fastboot flash recovery twrp-3.0.0-0-titan.img
.
Type
Code:
fastboot reboot
.
You´re done.
Click to expand...
Click to collapse
Thanks bro, but I just tried that, even changing the recovery for CWM, but nothing happened. I'm still stuck. The screen blinks with the recovery logo.
I have no system, so... Maybe I'm totally bricked. I don't really know if I can flash some ROM with the fastboot

Cuervoazulado said:
Thanks bro, but I just tried that, even changing the recovery for CWM, but nothing happened. I'm still stuck. The screen blinks with the recovery logo.
I have no system, so... Maybe I'm totally bricked. I don't really know if I can flash some ROM with the fastboot
Click to expand...
Click to collapse
Forget it bro, you gave me the right version of the recovery. Now I can get into it So much thanks!

Op3t fastboot cannot install twrp

I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?

Install correct driveres or use another usb port. Device have to be adressed via "fastboot devices" or "adb devices".

It's probably a typing error ..Rename the twrp in whatever you want and then type " fastboot flash recovery " whatever you want".img

Rename file
Did you rename the file? You need to rename it before flashing.

IT WORKED
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?

cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I also experienced this thing this morning.
A simple unplug, re-plug solved for me

Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?

Guiliang said:
Did you rename the file? You need to rename it before flashing.
Click to expand...
Click to collapse
no you don't.
Just type the first few letters and hit [tab]. Works on windows, linux, mac os and every other shell made within the last 40 years.

cerfeda.albert said:
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Click to expand...
Click to collapse
The last parameter has to be the EXACT filename, that you are flashing, which is the TWRP image. It has to be in the same folder as your command prompt is or you need to include the path to the twrp file.

Try the last TWRP release, should work!

Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
milanexplorer said:
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Click to expand...
Click to collapse

originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
After installing the twrp and then you type ... Fastboot boot twrp.img. Probably you are stuck on twrp splash screen...
Try to boot manually.to twrp by pressing power button and volume down button...Then you should be able to boot on twrp....

originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
See this thread.

originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.

jmazzamj said:
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
Click to expand...
Click to collapse
how long does it usually take? i've waited more than 10 minutes now.

Razoth said:
how long does it usually take? i've waited more than 10 minutes now.
Click to expand...
Click to collapse
Boot manually on it...

cultofluna said:
Boot manually on it...
Click to expand...
Click to collapse
apperantly i'm a retard, after i rebooted to recovery with hardware keys it shows the oneplus logo and i was like "this isnt twrp startup" and hardreset it... waiting boots into twrp just fine...

adb cannot locate file
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?

chizzwhizz said:
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
Click to expand...
Click to collapse
Reinstall your adb + fastboot drivers

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.