Database Info

[Completed] [Q] Fastboot doesn't recognize moto g 4g on linux

I have a Moto G 4g. ADB recognizes the cell and I can restart it in fastboot mode, but when I check in the terminal with:
Code:
fastboot devices
Nothing appears, and if I go on with
Code:
fastboot oem get_unlock_data
It gets stuck at
Code:
< waiting for device >
I tried as a user and as root on an Archlinux machine with android-udev rules as shown in the Archlinux wiki (sorry, i can't put the link). AP Fastboot fast boot menu shows that the cell is locked.

Hi,
You can try a different cable, or USB port on the pc...or even a different pc. Until fastboot devices detects your device, there's nothing you can do.
Reinstall drivers...and you are on the bootloader mode right?
If none of that helps, you can ask in your device section for help....
http://forum.xda-developers.com/moto-g/help
Good luck!

Hi
I've tried with a win 7 machine and i got fastboot working on my phone after installing the drivers. Now i'm able to do the thing i want to, but the problem still persist in linux, so i don't know if i close this thread or leave it open for someone who can solve this.

trichocereus said:
Hi
I've tried with a win 7 machine and i got fastboot working on my phone after installing the drivers. Now i'm able to do the thing i want to, but the problem still persist in linux, so i don't know if i close this thread or leave it open for someone who can solve this.
Click to expand...
Click to collapse
Please start one in your section. Xda Assist is here to help navigate the site, not for support.
Thanks!

[Completed] [Q] Interrupted flashing process

Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.

Hi,
Thanks for using XDA Assist please post here Android Q&A, Help & Troubleshooting
Good Luck!

[Completed] Help! LG G4 bootloop, can't get into recovery or bootloader/fastboot mode

So I was following the instructions here.
http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282
and my G4 is in a bootloop after step 7 (reboot into twrp). Gets a second or two into the animated LG logo then resets.
I want to get back into fastboot mode or recovery so I can flash again, but no button combo does anything, (p+d or p+u, held, or with the short gap as in many descriptions). If I hold all three buttons, it shows imei and a barcode, but I can't go anywhere from this screen.
It's boot loader unlocked as per LG official unlock, and still says so in tiny writing top left when first booting.
Can anyone give me some tips on how to get this thing back into fastboot mode? I have a mac with adb and fastboot working well.
Thanks,

milesritzy said:
There were three methods outlined in the post, but i think this should help you...
In order to successfully complete this method a computer will be required. A connection between your smartphone and your PC will also have to be ensured, so on your LG G4 gain developer rights and then check USB debugging – go to “menu – settings – about phone” and tap several times on built number and then access “menu – settings – developer options”. Also, on your PC flash Android SDK by following: install Android SDK on Windows or set up ADB on MAC OS X / Linux. Don’t forget to charge your handset before going any further and then apply:
Connect your LG G4 with your computer via USB cable.
On your PC access the Android SDK folder.
There, open a command prompt window: press and hold Shift keyboard key and then right click on any blank space.
In the cmd window you have to execute the following command: “adb reboot bootloader”.
Enjoy.
Conclusions
Click to expand...
Click to collapse
I'm familiar with using adb to reboot into bootloader, That's how I got this far. But it only works if you have a working OS with developer options for adb to connect to.
Unfortunately I don't have a working OS, or working anything else.

Hi,
Try posting your question here:
G4 Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!

"Waiting for device" after flashing kernal and rebooting device

Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help

MugenG said:
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
Click to expand...
Click to collapse
Installed adb SystemWide?
adb drivers are Installed corrcetly? , better to reinstall them.

[SOLVED] confused noob - adb/fastboot : install or just run?

Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-

OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-

nope...
No luck
ADB still cannot see my device when in bootloader mode

asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!

In the future some commands in Bootloader Mode require fastboot oppose to ADB.