I wanted to install a custom rom for my moto g4 and I just have problems with installing twrp. I downloaded twrp img and adb tools, then connected my phone to the pc in debug mode. In the adb console, the phone is displayed, but when I put the phone in the fastboot mode, it is not recognized.
that's cos there's separate program (e.g. fastboot) for interfacing with bootloader (c.f. Android Debug Bridge for interacting with recovery or Android).
Related
D801
TL;DR: Phone will only boot into download mode, however computer won't recognize my phone.
I installed all the drivers, have multiple versions of flash tool, even tried sideloading via ADB but device isn't recognized. How do I unbrick my phone?
Download and install the Minimal ADB and Fastboot tool v1.1.3...
http://forum.xda-developers.com/showthread.php?t=2317790
While in Download mode and w/ USB Debugging enabled, double click the Minimal ADB and Fastboot shortcut, then at the Minimal ADB and Fastboot> prompt type... adb devices
If your phone isn't recognized by ADB, then you don't have the correct drivers installed.
I can ADB/fastboot my device most of the time.
But when booting into Bootloader mode, I suddenly can't ADB into it?
The driver appears to be loaded up in my Win7x64 computer. Says it's the Motorola ADB device. And I can open my files on the phone. But ADB just doesn't see the phone for some reason. Any ideas?
Bootloader is fastboot.
Code:
fastboot devices
Windows 10 Home on host computer, and ADB tools installed.
USB debug mode on and host computer allowed.
USB PTP mode.
LG Unified Driver installed.
I opened command prompt, locate adb platform-tools. Ran the following commands
Code:
adb reboot bootloader.
The phone rebooted to bootloader.
On the bootloader mode on the phone, I typed
Code:
fastboot reboot
The phone rebooted properly
Does it work right?
Currently the phone is not ready to unlock bootloader until there's no problem, especially speaker problem, found.
Hello there
I had a custom rom on my op2 then i deletet everything over the recorvery. Now i have no OS installed so it only shows the boot screen. I can get into the twrp recorvery and fastboot mode but if i try to fastboot or adb sideload a new rom im unable to connect my op2 to my PC. I doesnt show up.
I tried this guide : https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
I cant make my device show up in my device manager. (I did the windows driver thing).
Can you connect through fastboot? In fastboot mode type in: fastboot devices
If so: flash this https://www.androidfilehost.com/?fid=529152257862717275
Device LG G6
Model : G600LR30c
I was thinking of installing a custom os which requires TWRP recovery installed in the device which recuires the device to be bootloader unlocked. But when I use the command "adb reboot bootloader" in minimal adb the device never goes to boot menu, instead it simply restarts and then if I put the command "fastboot oem device-id", it never shows the id and keeps showing "waiting for a device" instead. Please help me resolve this.
P.S: I also tried to access boot menu using key combo. but in vain
If you can put the phone in Fastboot mode during powerup or restart, it's a Windows issue if it don't work. Windows must recognize the device via PnP and install a different set of drivers each time the usb mode changes. If it don't work when the phone is already in Fastboot mode, try different drivers.
I once had two sets installed, that from the device manufacturer and that ripped from the Google SDK(on XDA). This way all usb modes worked, but Windows couldn't perform the Reboot Fastboot/Recovery commands fom ADB like is the case here and the Windows software had, suitable drivers installed, to be able to access the phone if it was already set to Fastboot/Download etc mode.
That was a TI OMAP based LG L9 under Win7. Starting with Windows 8.1, Fastboot was no longer working at all, you could only perform disaster recovery via D/L mode with a stock image and then root the thing with a one-click rooter to be able to install a recovery from Android etc etc, but that was due to the no longer supported TI SoC. But Qualcomm also tends to completely abandon older SoCs.