I flashed ViperONE which completed successfully. On initial boot though I am stuck on the bootloader menu. If I try to enter recovery the screen goes black and returns to the bootloader. I can get to the fastboot screen but my computer will not detect the device fastboot only says "waiting for device". fastboot menu does not change to fastboot usb. I am assuming since it was a new rom install that debugging is NOT turned on. Doing a factory reset through the bootloader did not help. My bootloader is unlocked and I am S-Off. Any helpers?
EDIT: Upon more research the fact that my HBOOT is 1.44 and not 1.55 as well as my computer running windows 8.1 I might have some troubles here. Is there hope for an RUU?
I tried the guidelines to boot into bootloader, I'm using xz2 non premium/compact, I press vol- a while and connect USB cable to PC but I never boot into bootloader, even when I try using adb command "adb reboot bootloader" it just reboot into normal system, what can I be doing wrong?
Also I have no update, I'm still on 8.0.0,I keep checking and it says you're using latest Android version, how come?
[email protected] said:
I tried the guidelines to boot into bootloader, I'm using xz2 non premium/compact, I press vol- a while and connect USB cable to PC but I never boot into bootloader, even when I try using adb command "adb reboot bootloader" it just reboot into normal system, what can I be doing wrong?
Also I have no update, I'm still on 8.0.0,I keep checking and it says you're using latest Android version, how come?
Click to expand...
Click to collapse
Use xperifirm and newflasher to flash the newest firmware.
Both programs are available on XDA.
MartinX3 said:
Use xperifirm and newflasher to flash the newest firmware.
Both programs are available on XDA.
Click to expand...
Click to collapse
Do you Know of any tricks to boot fastboot/bootloader,I want to unlock it, the current methods not working,I get a black screen and green/blue notification light (-vol and connecting USB cable from pc to phone) when I input fastboot commands, it says "waiting for available devices" and fastboot devices says no device connected, but adb devices (when in normal boot) recognises my device
Sent from my H8216 using Tapatalk
[email protected] said:
Do you Know of any tricks to boot fastboot/bootloader,I want to unlock it, the current methods not working,I get a black screen and green/blue notification light (-vol and connecting USB cable from pc to phone) when I input fastboot commands, it says "waiting for available devices" and fastboot devices says no device connected, but adb devices (when in normal boot) recognises my device
Sent from my H8216 using Tapatalk
Click to expand...
Click to collapse
Then the fastboot driver doesn't work correctly, is not correctly installed or the wrong got installed, while the adb driver is fine
similar problem: fastboot issues
I apparently don't have standing to post my own thread, so I'm replying to this one which is similar. My apologies.
I've downloaded adb and fastboot on my win 7 machine to unlock my bootloader on the way to rooting my xz2 compact. Fastboot will not recognize the phone. Adb does recognize it, and fastboot recognizes my Moto X DE, so both utilities seem to be working fine. Additionally, using 'adb reboot bootloader' cycles through a green, red and then a faint blue led, the latter which just stays there continuously with a black screen.
I've spent quite a bit of time on this looking for a solution, so I'm turning to you all for help.
dmm108 said:
I apparently don't have standing to post my own thread, so I'm replying to this one which is similar. My apologies.
I've downloaded adb and fastboot on my win 7 machine to unlock my bootloader on the way to rooting my xz2 compact. Fastboot will not recognize the phone. Adb does recognize it, and fastboot recognizes my Moto X DE, so both utilities seem to be working fine. Additionally, using 'adb reboot bootloader' cycles through a green, red and then a faint blue led, the latter which just stays there continuously with a black screen.
I've spent quite a bit of time on this looking for a solution, so I'm turning to you all for help.
Click to expand...
Click to collapse
The bootloader is just black with blue led.
Download mode is just black with green led
Recovery is just recovery with red led
System is just system with all led Colorado or none
fastboot
MartinX3 said:
The bootloader is just black with blue led.
Download mode is just black with green led
Recovery is just recovery with red led
System is just system with all led Colorado or none
Click to expand...
Click to collapse
That's helpful, thanks. I am fastboot mode then. I am used to a menu screen of some sort. How do I get to one of those?
dmm108 said:
That's helpful, thanks. I am fastboot mode then. I am used to a menu screen of some sort. How do I get to one of those?
Click to expand...
Click to collapse
Please look into the twrp chat
Yes, my Nexus devices had bootloader menu's
fastboot
MartinX3 said:
Please look into the twrp chat
Yes, my Nexus devices had bootloader menu's
Click to expand...
Click to collapse
Sorry, if didn't communicate this well. I need to unlock the bootloader using the fastboot command, yet fastboot overtly doesn't recogize the device. (no recovery screen menu is a separate problem). so,
'fastboot oem unlock' returns
'< waiting for any device >'
even though the phone is recognized by adb and other phones are recognized by fastboot.
How do I get the phone to be recognized by fastboot is the main issue.
dmm108 said:
Sorry, if didn't communicate this well. I need to unlock the bootloader using the fastboot command, yet fastboot overtly doesn't recogize the device. (no recovery screen menu is a separate problem). so,
'fastboot oem unlock' returns
'< waiting for any device >'
even though the phone is recognized by adb and other phones are recognized by fastboot.
How do I get the phone to be recognized by fastboot is the main issue.
Click to expand...
Click to collapse
Try a Ubuntu Virtual machine with usb passthrough
Best distro for phones - Manjaro
Hi, I was trying to follow https://forum.xda-developers.com/t/...8-mode-every-variant-except-t-mobile.4042207/, and finished performing the steps to flash the V35 Engineering Bootloader using QFIL. Now, I am attempting to get into fastboot/bootloader mode. However, it will only very quickly flash the screen, then displays LG V40 ThinQ logo. I have a LMV405QA.
I've attempted this several times, using two ways: initiating fastboot from adb via "adb reboot bootloader" and via button presses on the phone. It always skips the fastboot screen, then displays the LG logo. At this point, when one checks via commandline:, I get the output below
PS C:\adb> .\fastboot devices
???????????? fastboot
I can otherwise use the phone normally. I just can't proceed with unlocking the bootloader. Oh, wait, It seems that when I issue
"adb reboot bootloader", it stays at fastboot page but only after I issue "fastboot devices" or any fastboot command , that's when it leaves the page and goes to the LG logo. Does this mean I failed to flash the V35 bootloader?
Please help!!! It's been a while since I rooted (my previous phone was LG v30), this process seems very different.
Okay, I moved to another PC and got past the fastboot skipping issue with the fastboot drivers in this post https://forum.xda-developers.com/t/...variant-except-t-mobile.4042207/post-85113159 (Thank you!!!). Now, following those instructions...
Okay, I got as far as flashing abl_a and abl_b.
But, now I am in TWRP, but it cannot see the judypn zip image on the sd card.
I've posted my query on the https://forum.xda-developers.com/t/twrp-lg-v40-judypn.3970111/page-19#post-86839025, since the original issue of bootloader being skipped has been resolved by changing PC's. It was likely a bad driver on the first one.
Hi guys so my device is on global miui 12.0.6.0 stable and whenever i check for updates it says its the latest but I know there is an android 11 already, my device is still on android 10.
So next step is to unlock adb and fastboot right so I can update my device.
I did all the steps necessary.
OEM Unlock is on
MI account is connected on (mi unlock status)
usb debugging is on
install via usb is on
usb debugging security settings is on
No password (lockscreen)
Other things I've done:
I installed the Miui 12 on the check update screen twice
I factory reset on settings
I cleared all data on recovery settings (stock recovery only of miui)
andd still no LUCK! I badly need some of you high IQ guys here to help me resolve this please My mind hurts its like the factory of fastboot of this phone has somehow got corrupted....
I can hear a sound when connecting via usb when on black screen fastboot mode
I can even access adb commands like " adb reboot bootloader & adb reboot fastboot " and they all leads to the BLACK SCREEN FASTBOOT (NO LOGO) MODE T.T
Does >fastboot devices respond with your phone?
HaveSomeCyanide said:
Does >fastboot devices respond with your phone?
Click to expand...
Click to collapse
after tweaking and tweaking it does. Fortunately MI Unlock also works even if its just a black screen fastboot mode. so weird but it is what it is
HaveSomeCyanide said:
Does >fastboot devices respond with your phone?
Click to expand...
Click to collapse
after tweaking and tweaking it does. Fortunately MI Unlock also works even if its just a black screen fastboot mode. so weird but it is what it is
I believe that this shouldn't modify fastboot, try to reflash the latest and original MIUI rom using flash_all.bat (don't use flash_all_lock.bat)
It should fix any corrupted partitions. Or it may not do anything.
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Try installing the usb driver https://developer.android.com/studio/run/win-usb
billyedit said:
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Click to expand...
Click to collapse
I'm confused about "sits unlocked" and if this means you're stuck on the unlocked bootloader warning screen. If the phone hangs you're better off keeping the bootloader unlocked until that problem is sorted out. If it's starting, on the other hand...
Waiting for device means fastboot isn't communicating with the phone. Could be USB drivers. But if you flashed Android 11 from the same computer, drivers were working then, right?
In Developer options make sure USB debugging is enabled. While there, and while the bootloader is still unlocked, make sure OEM unlock is in the On position; it will flip back to Off when the bootloader is locked again.
Use Platform Tools 33.0.3 when trouble shooting USB to avoid trouble shooting Platform Tools 34.x.x.
As long as you get serial number output from commands adb devices and fastboot devices, fastboot flashing lock should work to re-lock the bootloader. Remember to finalize locking with the phone buttons.
Thank you both is was indeed the USB driver that needed the google update... All is well! thanks