Develop Bugs

Fastboot Problems, because of hw keys

Hey
im trying to unlock my bootloader again (had to lock it because i did a OTA on unlocked stock firmware)
im currently on stock ics, if that has anything to say. but the problem is when trying to install the fastboot drivers in windows device management
as far as i have read, when going into fastboot, is powering of the device, press and hold the menu button and connect the usb cable to the phone then u will get a blue light, find the drivers and install
but my menu button does not work anymore, idk why but it wont work when running android either. i have also tried getting in fastboot mode by holding the back button, then i get a green light as usual.
is there any way to enter fastboot without holding the menu button, or do i need to order a new keypad board for my phone
Thanks, Joakim
EDIT!!!!: i dont know what i have been thinking about, as you could enter fastboot, by typing adb reboot bootloader in adb, sorry

good you found out... there's also an option in flashtool inside fastboot window called "reset to fastboot through ADB"... also works... obviously your phone but be turned on and connected to PC through ADB.

Help!!! Bricked and I have a unique problem...

I did refer to this thread:
http://forum.xda-developers.com/showthread.php?t=2656275&page=13#post55838770
This is what happened:
I bricked my phone trying to install the autorec custom recovery after successfully rooting my phone. I get this " fastboot mode started" then on the 2nd line "uds_start()"
I think I am getting into download mode, it just says fastboot: processing commands.
however I don't see anything about com ports or LPT in device manager. all i see when i plug in my phone is "adb interface", and in that is "fastboot interface (google usb id). i can't find anything about my lg phone in there. so i can't reassign it to com41. is there any other workaround?

I have the same problem, look for solution.
Greetings

you have to download the laf.img and boot.img from http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions and then using fastboot, do fastboot flash laf.img and also fastboot boot.img. You should then be able to get into download mode correctly (with phone completely off, press and hold volume up button (dont let go) and also plug phone into computer using usb cable. When you see "DOWNLOAD MODE" on your phone, you can let go of the volume button. At this point, just tot back to stock.

jcwxguy said:
you have to download the laf.img and boot.img from http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions and then using fastboot, do fastboot flash laf.img and also fastboot boot.img. You should then be able to get into download mode correctly (with phone completely off, press and hold volume up button (dont let go) and also plug phone into computer using usb cable. When you see "DOWNLOAD MODE" on your phone, you can let go of the volume button. At this point, just tot back to stock.
Click to expand...
Click to collapse
i have been trying to tot back to stock and have all the files. I can get into download mode now but i can't get my phone to show up in device manager at all.

[Q] Download Mode / USB Drivers not working

Hey there,
I press volume up + insert the USB, when the LG screen appears I let go of the volume button and leave it. After roughly 1 minute it says Download Mode however it only stays in this mode for roughly 20 seconds and then it goes into Fastboot mode saying "reset" and "changed port". I got the correct ROM for my IMEI and LGFlashTool however I think the main problem could be the LG USB drivers. When I try install the official drivers the installer says success however windows says not successful.
Image 1 - i.imgur.com/hPkZbLx.png
Image 2 - i.imgur.com/nxdYm39.png
I have tried uninstalling all LG drivers/software, restarting etc.
I am fairly sure I can flash if I can just figure out how to successfully install the drivers or connect the phone to the PC. Anybody have any ideas? I can use linux or try any suggestions/alternative software.
Kind regards,
Desperate G3 owner

Just an update that I was able to manually apply the LGE PORT/COM driver in device manager however the PC only recognises the device when it is in Fastboot Mode. When it starts in Download Mode as stated above, nothing happens, but after ~20 seconds it will automatically switch to Fastboot Mode and then the PC will detect the phone and says Fastboot Commands.
I have tried using adb.exe devices and fastboot.exe devices in cmd but nothing shows up, any ideas?

Power button not working, stuck in "hTC download mode"

After running into some messenger problem on my device, I've read that I should power down my device, take out the SIM card and power it on again. Problem is, my power button stopped working ages ago, but I downloaded an app to let me shut it down.
I followed a guide on how to reboot it without the power button, aka plug it in the USB and hold down the volume down key. This booted my device, but the only things I can do are selecting options like system info, reboot to bootloader, reboot, power down -
without actually doing them, it seems like I need a working power button to actually select the option to reboot and now I'm stuck without a phone.
Any suggestions on how I can reboot it?
I also tried using an older version of ADB to reboot, but my device is not recognized apparently in the command prompt.

I have just tested that on my device.
Rebooted in stock recovery (white screen) and download mode - fastboot seems to work there.
Install HTC Sync (for HTC drivers)
Download htc_fastboot (someone around the readme should be a link) and do
1. fastboot devices
Your device must be recognised
2. fastboot reboot

Thank you very much!

Betrakiss said:
I have just tested that on my device.
Rebooted in stock recovery (white screen) and download mode - fastboot seems to work there.
Install HTC Sync (for HTC drivers)
Download htc_fastboot (someone around the readme should be a link) and do
1. fastboot devices
Your device must be recognised
2. fastboot reboot
Click to expand...
Click to collapse
Betrakiss, I registered just to thank you, many thanks and good luck.

Can't access Fastboot mode/ADB

So, I flashed Derpfest A12 ROM, It boots fine but gets stuck on "getting your Android 12 Ready" screen with the animation. I can access wifi and visiblity options but not settings. I flashed TWRP from the official website to install the recovery. But now when I reboot and press Volume Down, TWRP is stuck on boot animation. So I thought just reset using fastboot and start again and pressed volume up and power button but it does NOT work. I tried the volume buttons again in the rom [i can change volume in the starting screen] and they are working. I can press volume down and power button to reboot into recovery and it works fine but gets stuck. So, I just want to have access to adb or fastboot to reset this phone but neither seems possible. I Cant enable advanced reboot in the starting screen. Fastboot doesnt work. ADB not recognizing as it is a new rom and havent enabled it [i enabled in the previous rom]. Thanks for you Help in Advance!
P.S. I have tinkered POCO F1 fairly so I am not totally new to this scene!
EDIT: Thanks for all the replies! But I solved the problem, Idk how but i got access to fastboot mode after some tries and reflashed everything and now it works, also I use linux and the adb drivers and fastboot were in repos so it was easy.

hello,
I am a novice and use a translation tool to write to you (sorry if there are errors...).
Ok I already installed roms (but a long time ago on a OnePlus One...
I have an OP5T, I want to install lineage Os 19.1 on it.
I followed the tutorial on the lineage wiki.
I installed ADB and fastboot well, as well as universal adb driver.
I'm on windows 11, it works.
I enabled debug mode
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?

ezivoco_163 said:
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
Click to expand...
Click to collapse
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.

No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)

Nimueh said:
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
Click to expand...
Click to collapse
Renate said:
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Click to expand...
Click to collapse
ok thanks, i a going to try this