Hey guys... friend of mine asked me to put in a custom ROM to his Hero, tires of waiting for HTC to release a 2.1/2.2 for us here in SE Asia.
The phone had already been rooted, but I could not manage to put in a recovery partition, even trying with the GoldCard method.
So, I dug around and found recommendations to try Droid Explorer, which I did, very nice program!
What I did was to use the "update custom ROM" function to put in the ChocolateEclair ROM
Everything seemed to run fine, phone rebooted, showed the new boot animation, then went to a green screen for a few minutes, but this is normal as per the ROM's details page.
But, since then, it's rebooted, it does the boot animation (hand-drawn droid), over and over again, can't get past that. I can get into bootloader and stock recovery screens, though. I'm thinking I should try to wipe the device again, but I cannot select this option in the recovery, it says to press alt-w but that's a bit hard without a keyboard!
I also tried to connect with adb shell (when in recovery mode) but it tells me it cannot find the shell.
So... have I bricked this poor phone? Right now I am downloading the latest RUU I can find, and hope it will work, but if anyone has any experience and advice to share it will be greatly appreciated!
Hey mate... You should have posted in ChocolateEclair topic. Can a mod merge the topics?
To answer you... This does not mean the phone is bricked. Are you sure you don't have a custom recovery image?(boot with home+power) Please paste me your logcat(adb logcat) and I'll tell you what causes the reboot, there's nothing to worry about.
Hey RaduG,
Thanks for getting back so quick! I posted a general thread as I thought it would not be a problem specific to your mod but rather my method or lack thereof
Now the problem is... I can't run logcat either.:
- exec '/system/bin/sh' failed: No such file or directory (2) -
when I go to the recovery image I am quite sure it is the stock one (3D exclamation mark with a phone next to it, then loads the reboot/apply update.zip/wipe data menu. There's also a warning "E: can't open /cache/recovery/command" in yellow at the bottom.
How you try to run logcat? "adb logcat"?
Apparently you can reinstall a recovery using that Droid Explorer?.... I'd try that for AmonRa1.6.2 if Radug cant help you once you have supplied a logcat.
Then load into the recovery, do your wipes, and flash again.
..... And please post in GENERAL or QnA next time.
are you able load into armon recovery console?
if yes try wipe everything & reflash others custom rom then wipe again & reflash ChocolateEclair 1.0.1. i also face the same problem just now when i'm at work *playing with roms secretly* ^^"
i load in success without seeing the green screen now =)
& best not to use the ExtremeKernel as not all phone can support as stated on the dev post =)
ddotpatel said:
Apparently you can reinstall a recovery using that Droid Explorer?.... I'd try that for AmonRa1.6.2 if Radug cant help you once you have supplied a logcat.
Then load into the recovery, do your wipes, and flash again.
Click to expand...
Click to collapse
he is unable to do this atm, as he is stuck at the boot screen...so unable to load previous ROM...
ADB stuff should be the way
Most likely his hero cant be overclocked to 69x mhz. So flash the low kernel.
jarski12345 said:
Most likely his hero cant be overclocked to 69x mhz. So flash the low kernel.
Click to expand...
Click to collapse
I'm quite sure this is the case... but I am so far unable to put in any other ROM. When i get into the stock recovery console, I can select the "apply update.zip" option, but pressing the trackball does nothing, same with the factory wipe option. Are there any other button combinations for these? It says Alt+S and Alt+W for these options, but without a physical keyboard, how to do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Droid Explorer does let me update a new ROM, but... nothing happens on the phone.
As for trying to put in a new recovery through Droid Explorer, it can only do so by pulling the file for the SDcard... which is not detected when the phone is in recovery mode
I tried to run a recent HTC RUU, but it does not detect the phone...
Last option seems to be working from ADB, yes... But half the commands I try end up with the error "- exec '/system/bin/sh' failed: No such file or directory (2) -"
So, are there any ADB commands I could try, to wipe the device?
Related
So I got a htc mytouch 4g And it has that phone icon with a triangle and exclamtion mark. I dont know anything about this phone since I have a att captivate From what I read is that if you have recovery you might be able to do it.
Also when I plug in the usb I go into recover and I Get a fasboot screen and other sorts of menus i have put a pd15img.zip in my external sd card and it loads installs It I guess but still boots into the same Icon.
from what I also read is that you can fix this by loading a stock rom pushing into your sdcard via adb but make sure is name update.zip but when I do that I get Invalid Operation.
when in recovery I have this message E:cant't open /cache/recovery/command also phone boots right into that icon.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I assume this is a soft brick since I get into recover and the other fasboot menu when I plug in USB any help is appreciated
This is my first time with a phone like this so I'm doing what I would normaly do with a captivate ish
I answered in your other thread here. However, now that you've posted a screenshot, I see that the phone isn't even rooted. I have no idea how you get into a custom recovery without root.
I connect usb while the phoneis off and then press volume up + power and that appears.
chibixzero said:
I connect usb while the phoneis off and then press volume up + power and that appears.
Click to expand...
Click to collapse
Yeah, see where it says "S-ON"? That means the phone isn't rooted. You need to perm root and it install CWM recovery, but with those cache errors you're getting, I'm not sure there's any point since those usually indicate a failed eMMC.
Guess my options are
1. call t-mobile and tell them what happen maybe they will replace it but I didnt buy it with contract I'm att and was going to ask my friend to get me unlock code, But idk if its possible I drop it and theres a crack on the phone
2. sell it for parts...
>.< money down the drain I guess fuggin phone
You're booting into stock recovery by default, that's the "triange". That might happen if you have a VolumeDown key/trackpad stuck.
The error in the recovery is natural - stock recovery expects a command when booted into, but finds nothing.
Check that you're indeed installing a correct PD15IMG that contains a complete system image, and if you are and it still doesn't help - try to shake the phone on the side / upside down, to try and release the possibly stuck buttons. If it doesn't help - the phone needs warranty repair. T-Mobile or HTC directly, your choice. To send it to HTC, you pay the shipping. But in any case it's under warranty, unless it has water damage or something.
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
atifsh said:
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
Click to expand...
Click to collapse
That appears to be the Gingerbread leak from the Canadian HTC Panache, but you might want to describe to the OP what exactly it is. Most people won't blindly flash something to their phone without a little info first. Also, could that be flashed to a non-rooted device?
yes thats the official RUU of panache which is glacier inside.
yes u can flash as its RUU.exe u dont need root.
u can even comeback to official mytouch RUU.zip using this exe later if wanted.
because its exe it will reflash everything boot, recovery, splash, radio every thing, thus fixing any problem thats not hardware.
atifsh said:
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
Click to expand...
Click to collapse
i used this as noted but I get this error
Customer ID error (131) I read on these forums is has something todo with a goldcard?
Edit-
I manage to load a stock rom into a External sd card. it updated it everything pass exept step 8 it skip it and the said finish updateing press power to reboot. Rebooted but the whole (second) mytouch splash was going for a long time. I try to use the RUU.exe and it wont boot into bootloatder just boots and stays on the splash screen.
this is what I get now and is stuck on That screen updating radio
Damn.
That would be the first completely stock Mytouch4G in the forum that has a failed eMMC chip.
Yes, it's bricked, you need to exchange it.
But it's also a good proof that gfree has nothing to do with failed eMMC, extra write cycles of flashing ROMs most probably just speed up the destruction process.
you got one large scratch on screen, how good have you kept your phone? have you droped it badly once or twice?
when you used the RUU.exe when did u get that error, does it go upto where it showed you the rom version?
if u got there than you can try one more time but this time with official mytouch RUU.zip. i'll tell you how to do that, later if u got upto that part.
edit nevermind my post cameback above this
If it shows "Fail-PU" in bootloader - then the eMMC isn't functional anymore. No flashing will help him in this case, only warranty repair.
hmm too bad, feel sorry for him
Im in great confusion right now... please developers, please help me... yesterday I used alpharevx to s-off my wildfire that has 1.01.002 unbranded hboot.. successful and then i have rooted it and its successful and then i tried flashing cyanogen 7 its stuck for 3hrs in installing updates, iremoved the battery now i only have htc whitescreen.. ican still boot to hboot and recovery (3.0.0.6) ive downloaded different roms, ihave openfire and couple of other roms under froyo build. but i had the "amend scripting error" i have searched and it seems that i need to flash an older version of clockworkmod .. i ended up downloading everything all versions.. when im trying to flash it... its giving me an error "installation aborted" I ended up STARTING this thread LOOKING for a small string of hope that my phone will BOOT TO NORMAL MODE... please, I'm not a developer and im in great panick... i hope my phone is not brick... thankyou
Try a different version of Clockworkmod. 3.0.0.6 is giving similar issues to many users. Try 3.1.0.2 for installing CM and Gingerbread ROMs . and 2.5.0.7 for Sense based Eclair / Froyo ROMs.
Both can be found here (Point 6)
http://forum.xda-developers.com/showthread.php?t=1029318
You can use Fastboot Mode for replacing and installing a new Recovery. Short Guide:
1.) Install Android SDK,
2.) Get the Recovery.IMG file of the Clockworkmod version you want to flash. (I linked the thread above, where you can get it)
3.) Place this in the SDK's Tools folder.
4.) Reboot your phone in the bootloader mode. (Power Down. Press Vol Down + Power Key together)
5.) Enter Fastboot mode (Press Power button on Fastboot).
6.) Open Command Prompt on Windows.
7.) cd (browse) to the SDK's tools folder.
8.) Type the following command: "fastboot flash recovery recovery.img". (Without quotes.)
Screen here (My SDK is in D:\Android)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: You don't even need the complete Android SDK to do this. Just the ADB and Fastboot Binaries will do. But, still I wrote with the SDK, because that is how I did it, and, it worked for me. Anyway. you can get that here:
http://forum.xda-developers.com/showthread.php?p=14693680 (Check Attachments)
thank you very much!
3xeno thankyou... i will try it now
the best!
3xeno i sucessfully flashed the old recovery! i successfully flashed ANONIMO'S-ROM (Froyo 2.2.1)! thank you very much its been 28hrs now without sleep and i thought my phone is bricked! THANK YOU VERY MUCH!
hydro25 said:
3xeno i sucessfully flashed the old recovery! i successfully flashed ANONIMO'S-ROM (Froyo 2.2.1)! thank you very much its been 28hrs now without sleep and i thought my phone is bricked! THANK YOU VERY MUCH!
Click to expand...
Click to collapse
If u can access hboot/fastboot/recovery menu, then u can solve any software problem the phone has. And certainly the phone is not bricked in above cases.
A bricked phone will not even show the splash screen on powering on. Although excluding the offline charging bug (search for it if u don't know).
And AFAIK, possibility of brick is only when flashing hboot and radio.
Sent from my HTC Wildfire using XDA App
bharatgaddameedi said:
If u can access hboot/fastboot/recovery menu, then u can solve any software problem the phone has. And certainly the phone is not bricked in above cases.
A bricked phone will not even show the splash screen on powering on. Although excluding the offline charging bug (search for it if u don't know).
And AFAIK, possibility of brick is only when flashing hboot and radio.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
noted... thank you for spending time reading...
Hello there.
I am writing because I need your help on unbricking my Nexus 7 3G (2012). Yesterday night I was trying to upgrade it from 5.1.0 to 5.1.1 (from the OTA) and I couldn't because I had an error produced by Stickmount. It changed a file on system/bin which I tried to push manually (following some thread's intructions on XDA) and it didn't work, showing error Status 7 (unexpected content on file debuggerd).
Because of that, I decided to flash the 5.1.1 system image using Nexus Toolkit. I set it up so it'd download and install it automatically (using the "Flash stock + Unroot" option). Everything went okay and started the flashing process until the command prop window force closed mid flash, thing that never happened to me before (as I had tried many times flashing from zero my N7 before).
I tried to start the Toolkit again and the command prop window says it flashes bootloader and radio img's successfully, but then a line of code appears and the cmd window force closes again (it says "No se esperaba ( en este momento" or roughly translated as "The ( was not expected at this moment" into English) and my N7 turns off.
Next, I try to turn it on and it shows the Google logo and a green arrow saying "start". I press it and the N7 reboots to the same screen, saying "booting failed" at the top of the screen. If I choose recovery, the same thing happens.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just can make it to boot to bootloader mode but I cannot flash the firmw (even when this mode must be selected in order to the Toolkit to start flashing). It shows the same line of unexpected code as above.
I tried pushing the files manually using ADB and I cannot may it work either.
What can I do to solve this? I've read that as long as you can get to bootloader mode you can unbrick a device.
I hope you could help me out. Thanks in advance.
Anyone?
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
wombat3 said:
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
Click to expand...
Click to collapse
Thanks wombat. Actually, the N7 is listed under adb devices. It starts the flashing process but ends automatically without finishing the installation.
Happened when I was updating twrp:
I downloaded the .img from their website, booted into my older version of twrp, went to flashing pressed the butting in the bottom right corner, selected the file and selected 'recovery'
Said it was successful, so I rebooted, then it wouldn't do anything anymore except for fastboot.
1. Can't boot into recovery
2. Can't boot normally
3. USB debugging disabled
4. oem locked
Only thing I can enter is fastboot.
I followed this guide, but no luck on my end.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
passion8059 said:
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
Click to expand...
Click to collapse
It's no use because oem is locked. That means I can't flash anything.
toolbox should still help you unlock bootloader again
Just use the Qualcomm factory restore image to return the phone to original shape of things.
passion8059 said:
toolbox should still help you unlock bootloader again
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pitrus- said:
Just use the Qualcomm factory restore image to return the phone to original shape of things.
Click to expand...
Click to collapse
I have no idea how I would do this without being able to flash anything.
Do you mean that the Qualcomm download program also crashes like fastboot? Sounds like you either have some problems with your windows installation or perhaps you haven't searched for and downloaded the Qualcomm restore if your still trying to flash the ordinary way instead of the emergency way.
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Theevilsocks said:
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Click to expand...
Click to collapse
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Redjax said:
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Click to expand...
Click to collapse
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Theevilsocks said:
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Click to expand...
Click to collapse
Literally JUST finished with this guide, and my OP2 is alive again! I was going to come back and post. Thanks for the link.
Anyone trying to use this guide without success:
There's one very important step I somehow missed. You MUST disconnect your phone, hold the power button for ~15-20 seconds until it's off, and hold the Volume+ button, THEN plug it back in. Your computer will make the "device connected" sound, but the screen will stay black. THIS IS OK! That means you're in a special recovery, which is where you need to be for the tool.
I also installed the certificate file in the folder I downloaded, then rebooted (it did not work before a reboot, but did work after).
So, the steps:
1. Download the files, make sure your signature signing for drivers is off.
2. Install the trusted certificate, then the driver.
3. Reboot PC
4. Power off phone (hold power for 15-20 secs), hold volume+, then connect through USB (wait for device connected sound, screen on phone will still be black)
5. Run the tool (I ran as admin, not sure if that's required)
6. Weep with joy that you finally found a solution that works.
Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help
arksoother said:
Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help
Click to expand...
Click to collapse
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54
rahimali said:
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54
Click to expand...
Click to collapse
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.
arksoother said:
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.
Click to expand...
Click to collapse
Can you not even boot into bootloader/fastboot or TWRP/recovery?
You should be able to boot to recovery by following the steps shown here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/recovery-mode/
You could also try and boot into safe mode and try and use the magisk manager to uninstall magisk - howto here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/safe-mode/
okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?
arksoother said:
okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?
Click to expand...
Click to collapse
somebody else apparently had the same experience although on a different LG device -> https://forum.xda-developers.com/lg-spirit/help/help-fastboot-error-loading-keystore-t3430163
So it seems that fastboot commands may have been disabled which means you can't interact with the device in fastboot mode whatever you do.
If nothing else works, you could try and re-flash stock ROM if you can manage to get into download mode.
Best of luck!