Develop Bugs

Boot without power button

Hey guys,
I recently repaired the display of my girlfirends OP3. After that she complained about the power button not working every time. So I opened it up again, but this time, I completely ripped off the power button.
Now the phone is off and i can't get it to boot. Online i found the "solution" to boot it into download mode. The problem is, im not sure if I am really in the download mode. The bootloader is unlocked.
Do you have any other mechanics to boot into the system?

Did you try the following options?
1. Plug in the charger. It should get a phone started.
2. Install Android SDK tools from here https://developer.android.com/studio/releases/platform-tools
Open a command prompt, navigate to the folder where ADB is installed, and run 'adb devices' after plugging in the switched off OP3 to the computer.
Then execute 'adb reboot' or 'adb reboot fastboot' or 'adb –s <device ID> reboot'.
Kyreus said:
Hey guys,
I recently repaired the display of my girlfirends OP3. After that she complained about the power button not working every time. So I opened it up again, but this time, I completely ripped off the power button.
Now the phone is off and i can't get it to boot. Online i found the "solution" to boot it into download mode. The problem is, im not sure if I am really in the download mode. The bootloader is unlocked.
Do you have any other mechanics to boot into the system?
Click to expand...
Click to collapse

Rooting LG K9 LM-X210YMW, an impossible task or an interesting challenge?

I've managed to get myself an LG K9 LM-X210YMW (body has CV1 0415 on it), but rooting this device is turning out to be VERY hard. Has anyone else had success? Its running Android 7.1.2 with Kernel 3.10.49+
I've got ole developer options set:
Enable OEM lock is ON
USB debugging is ON
Automatic updates are OFF
It's easy enough to get adb to recognize it:
Code:
evryd4y$ ./adb devices
List of devices attached
LMX210cXXXXXXX device
But rebooting with adb reboot bootloader just reboots it to lock screen.
Methods tried include:
connect then reboot with adb reboot bootloader - this just reboots to lock screen
Power on holding volume DOWN button until LG logo appears - this boots into safe mode
Power on holding volume down and power button - this reboots to safe mode
King o root (YES I know but desperate times call for depserate measures) give error 0x1c8bb4
Tried platform tools (Adb, fastboot) on Linux, Windows, Mac... same results... nothing
BUT I can get it into firmware mode by powering on and holding volume UP. This mode then hangs until I rip the battery out and throw it into space.
Has LG managed to make an un-rootable phone? Are you having the same problems?

I literally have the same problem...

evryd4y said:
Has LG managed to make an un-rootable phone? Are you having the same problems?
Click to expand...
Click to collapse
Same problem here with an LM-X210EM, have you had any luck since then?
Only thing I'd like to add is if I "adb reboot recovery" then it reboots to a sick android screen.

Strange Problem On Bootloader/Fastboot

Hello Everyone,
I Have A Strange Problem When I Press Power+Down Button Then Device Goes To Bootloader/Fastboot And Mi Bunny Appears, But After 3-5 Seconds Mobile Device Automatically Switch Off Without Connecting The Cable Or Doing Anything.
Note That, I Have A Latest Build V11.0.9.0.QDLMIXM Installed Without Rooting And Device Working Properly. Since I Just Want To Root The Device And Bootloader Is Unlocked. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode.
Thanks In Advance !!!
Thanks,
MUHAMMAD Asif Qasim

Can you get fastboot to see it in this brief window? I'm wondering if it will stay if it sees fastboot but maybe reboots because it doesn't? (Or because some other app on your PC is confusing it?)

a1291762 said:
Can you get fastboot to see it in this brief window? I'm wondering if it will stay if it sees fastboot but maybe reboots because it doesn't? (Or because some other app on your PC is confusing it?)
Click to expand...
Click to collapse
Thankyou For Prompt Response.
I Couldn't Get Your Point. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode Even I Connect The Cable Or Not. Its Automatically Switch Off With In 3-5 Seconds.
In Addition To That, I Can Use ADB Commands & Shows My Mobile Connectivity When I Use.
Thanks,
MUHAMMAD Asif Qasim

aasiaasi said:
I Couldn't Get Your Point. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode Even I Connect The Cable Or Not. Its Automatically Switch Off With In 3-5 Seconds.
Click to expand...
Click to collapse
I run this on my PC and it waits for a device.
$ fastboot getvar current-slot
< waiting for any device >
3-5 seconds should be enough time to connect your device and see if fastboot can talk to it (and if that stops it from rebooting).
If it happens when there is no cable plugged in... that's a bit more concerning. Does it also happen if you get to fastboot by typing adb reboot bootloader (from a normally-booted system)?

a1291762 said:
I run this on my PC and it waits for a device.
$ fastboot getvar current-slot
< waiting for any device >
3-5 seconds should be enough time to connect your device and see if fastboot can talk to it (and if that stops it from rebooting).
If it happens when there is no cable plugged in... that's a bit more concerning. Does it also happen if you get to fastboot by typing adb reboot bootloader (from a normally-booted system)?
Click to expand...
Click to collapse
Thank You Dear. Yes I Can Use The Command On ADB When Mobile Is Switched On Here Is The Example Snapshot.
The Problem Is That When I Boot To Bootloader It Doesn't Stay On Bootloader And Shutdowns Automatically With In 3-5 Seconds. As You Suggested Me To Check The Command When Mobile Is On Bootloader Mode The Shell Shows "waiting for any device". Ahd Restarts Automatically.

aasiaasi said:
As You Suggested Me To Check The Command When Mobile Is On Bootloader Mode The Shell Shows "waiting for any device". Ahd Restarts Automatically.
Click to expand...
Click to collapse
I don't know exactly what the bootloader does while in fastboot mode, but I'm going to guess it draws the rabbit and then gets ready to talk to the PC. And something fails and it dies.
If it's working normally, that's something... But it's going to stop you from unlocking the bootloader.
I have no idea how to fix. Maybe EDL with the test points? There are 2 aboot partitions (apparently hold fastboot).
# ls -l aboot*
lrwxrwxrwx 1 root root 21 1971-09-16 02:23 aboot_a -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1971-09-16 02:23 aboot_b -> /dev/block/mmcblk0p32

I think the fastboot mode will exit automatically if it doesn't receive any command from PC. It happened to me before and about the <waiting for any device> when you did a command probably related to it. Check if the driver are properly installed because it happened to me on Windows 10 but not on Windows 8.1.

Mewwo2 said:
I think the fastboot mode will exit automatically if it doesn't receive any command from PC. It happened to me before and about the <waiting for any device> when you did a command probably related to it. Check if the driver are properly installed because it happened to me on Windows 10 but not on Windows 8.1.
Click to expand...
Click to collapse
Thankyou Mewwo2,
Could You Please Check Your Device ? Without Connecting The Cable , That Your Device Automatically Switched Off In Few Seconds Or Not. Please Let Me Know So I Can Figure Out Or Take A Clue For Fixation.
Secondly I Have Windows 8 And Drivers Are Properly Installed. If The Drivers Have Issue The Adb Command Doesn't Work And Doesn't Shows My Mobile (Note That I am Taking About When Mobile Isn't on Bootloader Mode)
Thanks In Advance...

Can you type another adb command like 'fastboot oem device-info' and see the output.

it's not a problem.
Mi a2 lite turns off automatically from fastboot when it doesnt detect any fastboot signal.
You can go to device manager and then see if mi a2 lite gets recognized as a device, now go to cmd and type fastboot devices and boot to fastboot again, now it shouldn't power off again.

minicm94123 said:
it's not a problem.
Mi a2 lite turns off automatically from fastboot when it doesnt detect any fastboot signal.
You can go to device manager and then see if mi a2 lite gets recognized as a device, now go to cmd and type fastboot devices and boot to fastboot again, now it shouldn't power off again.
Click to expand...
Click to collapse
Thankyou For Your Support. I Will Check & Respond Accordingly.

Rooted G7 Play: Forgot pattern lock, can't factory reset either

I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.

veryspecialagent said:
I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.
Click to expand...
Click to collapse
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot

sd_shadow said:
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.

veryspecialagent said:
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.
Click to expand...
Click to collapse
Window 10?

Yeah. It should remember this phone, since I used this computer to root it when I first got it a year and a half ago.
I used a different cable and got it to pick up the phone (as an unknown device) in Windows but NOT ADB, and the phone to realize it was connected (see last line on phone screen) but they're not talking.
If I boot it all the way up, either regular or recovery (root), it doesn't show at all on my computer.
Like I said, I'd be fine with wiping it, but can't even get to that option.

Install the moto drivers. If that doesn't work then make sure your using a usb2 port and not a usb3 port as its a known issue with moto phones.

I just ordered a new OEM cable.
Also ordered an OTG cable to see if I can force it to startup into a different mode that'll allow me to do something with it.
I'll update this thread once I'm able to test them out.

I got a new cable. My USB ports are not labeled, and my Moto drivers reinstalled.
After rebooting to the recovery screen, I plugged it in and apparently I have fastboot. I checked the bootloader logs and it says:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Volume down key pressed
USB connected
Windows doesn't pick up anything connected by USB. I can't restart to get root because then adb doesn't pick up the phone either because of the screenlock preventing me from hitting ok to trust my computer.
I'm asking the following because I can't find answers: Can you delete the screen lock file with the only bridge being fastboot, not adb. How can I do a factory reset if rebooting to recovery is our normal way of turnin gon the device with root access? Or would reflashing something work?
command line commands are a perishable skill and it's been a couple years since I did this stuff.
Thanks in advance.

To recap, I either need to be able to get into the directory to delete the pattern lock, or factory reset the phone.
I've tried the pattern lock 79 times, which means I have to wait 300+ seconds between tries. I think an error is causing that though.
Fastboot is my only option at this point as far as using commands goes. Rebooting recovery just reboots it with root permissions, but neither adb or Windows 10 picks it up. Using a brand new factory cord and tried every USB port on my computer, even the USB-C to USB-C. But I can't find anywhere that shows how to get into the directory using fastboot.
In Device Manager, I've been getting an error with Android ADB Interface (The device cannot start; Code 10). I uninstalled, reinstalled various drivers, killed adb.exe, etc., Still happening.
HOWEVER, Motorola ADB Interface is working just fine and goes away when I unplug my phone, returns when I plug it in. Only when it's in recovery/fastboot mode though.
I got into Safe Mode, but computer won't pick it up.
I can't get into Field Test Mode. I did reboot it into something else. I don't know what, but the screen was off and the home button was illuminated. EDL mode? I don't know. Neither my computer or adb read that anything was attached, and i can't figure out how I did it.
I also tried sideloading some pattern lock removers, but apparently you can't do that in fastboot.
Thoughts?

Just to close this out with a solution: I had forgotten that in order to get to the recovery menu, you have to hold the buttons when you reboot recovery. Didn't realize that until I was rooting my Moto e6.
Factory reset complete. No more pattern lock. Though since I've now tried rooting it 4 times with 4 different images and have not succeeded even though I had root before all this, I wish I could have realized the above and possibly gotten in and deleted the gesture.
Lesson learned.

Hold what buttons? I'm afraid I'm in same spot.

onefstfoknv6 said:
Hold what buttons? I'm afraid I'm in same spot.
Click to expand...
Click to collapse
Volume up button and power button

sd_shadow said:
Volume up button and power button
Click to expand...
Click to collapse
Just found this. Timing is everything apparently.
Press and hold the Volume Down and Power buttons simultaneously until the Android Recovery screen appears.
Press the Volume Down button to navigate to Recovery.
With Recovery displayed, press the Power button.
When you see the 'Droid' with 'No Command,' hold Power and tap Volume Up just once and immediately release both buttons.
Scroll to wipe data/factory reset by pressing the Volume Down button
Press the Power button.
Scroll to YES by pressing the Volume Down button.
Press the Power button.
The 'phone will wipe all contents.
Press the Power button.
The 'phone will now reboot to the initial setup screen.

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