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!
Related
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
pannic514 said:
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble. We cannot provide technical support nor can other members reply to your posts here on XDA Assist but fortunately there is an XDA area dedicated to the HTC One (M7) at http://forum.xda-developers.com/htc-one which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/htc-one/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.
On the normal boot mode, my Asus zenfone2(ZE551ML) running android 5.0 is listed when I type adb devices. Then, I put the phone to the fastboot mode by adb boot bootloader. When the phone is already entering the fastboot mode, fastboot devices returns no result. But, lsusb listed the device's details including vendorid, productid, and device name.
I have tried to modified the 51-android.rule, run fastboot as root, change owner of the /dev/bus/usb/, re-install and update the android-tools. But my ubuntu still can not detect the zenfone2 on fastboot mode.
Moreover, I connect my other phone(Redmi2) which also on fastboot mode and it can be detected seamlessly. Also,when I tried to connect the zenfone2 to other ubuntu PC, it can be detected.
Has anyone ever encountered and solved the similar problem? Or perhaps have an idea what is the potential cause?
Any help will be appreciated! Thanks.
Hi,
Try posting your question here:
ZenFone 2 Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!
I am having trouble getting consistent results with the "fastboot boot <recoverimgname>.img" command.
I am working with both an Amazon Fire 5th generation tablet, a Nexus 4 and HTC One X.
I followed the directions and youtube video posted by awesomeslayerg and rootjunkysdl for rooting the Amazon Fire, and was successfully able to do so (CyanogenMod version 12.1-20151115-UNOFICCIAL-ford, Android 5.1.1).
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
I was also able to put Android version 6.0 on the Nexus 4 by following these directions:
http://forum.xda-developers.com/nexus-4/development/rom-unofficial-cm13-marshmallow-builds-t3236487
The one thing I'm struggling with is the fastboot command "fastboot boot <recoverimgename>.img".
On both devices, I'm able to get the devices in communication with the PC (ie "fastboot devices" returns the appropriate information about the devices).
I then run the "fastboot boot <recoverimgename>.img" command:
For Fire: "fastboot boot TWRP_Fire_2.8.7.0.img" (obtained from http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery)
For Nexus 4: "fastboot boot twrp-2.8.7.0-mako.img" (obtained at https://dl.twrp.me/mako/)
In both cases the recovery file is in the same directory from which I am running adb/fastboot.
The issue with both is that sometimes they'll reboot into the respective recovery, and sometimes they won't.
When they won't, the Nexus 4 hangs at the Google splash screen. The Amazon Fire boots to the system.
I can't figure out why they don't consistently boot to the recovery.
I've tried getting into fastboot mode via "adb reboot bootloader", by shutting the devices off and booting into fastboot manually (volume button + power switch), by rebooting to recovery then to fastboot, etc.
Also tried waiting a long time after getting the correct response to "fastboot devices" to make sure things had settled down.
Nothing seems to have given a consistent response.
I'd like to be sure that I can boot into a recovery on the PC when I need to (from fastboot on the device). At the moment it seems to be luck whether I can or not, but I assume there must be some cause that I can solve.
Anyone else experience this problem? Have ideas how to solve? Or can point me to a forum which is addressing this?
Thanks.
fastboot boot <recoverimgename>.img Inconsistency
I've just looked through the entire forum discussion on rooting the Amazon Fire 5th gen tablet, and not found an answer to this problem.
I've already rooted the Fire (Ford) and gotten Cyanogenmod 12.1-20151115-UNOFFICIAL-ford running on it, so this device is OK.
But I have continue to have erratic results booting to a recovery on the PC using fastboot: C
I can get the tablet connected to the PC in fastboot mode, fastboot devices gives me the right answer, my driver is Android Composite ADB Interface, and everything seems OK.
But most of the time when I enter the "fastboot boot TWRP_Fire_2.8.7.0.img" command the Fire reboots to system, and occasionally to Amazon's recovery version. Only occasionally to TWRP, and I don't know why.
How can I consistently boot into the TWRP_Fire_2.8.7.0.img recovery on the PC that I used when I rooted the thing in the first place?
Any ideas?
Hi,
Here's a guide you could try to be sure you are set up properly, http://forum.xda-developers.com/showthread.php?p=48915118
And as far as specific help for each device, you would be best to ask in those devices Q&A sections,
http://forum.xda-developers.com/nexus-4/help
http://forum.xda-developers.com/amazon-fire/help
Or ask in the threads you linked yourself. :good:
Good luck!
Thanks much. I'll try the guide. I've managed to get it all to work (ie "fastboot boot TRWP_Fire_2.8.7.0.img") on another PC, so it must be the setup on the 1st PC. I'm really struggling with the drivers.
I'd post questions in the other threads, but don't have the status yet...
I also see that Amazon's new update has throw a monkey wrench into fiddling with the Fire. I'll keep working at it.
Darth said:
Hi,
Here's a guide you could try to be sure you are set up properly, http://forum.xda-developers.com/showthread.php?p=48915118
And as far as specific help for each device, you would be best to ask in those devices Q&A sections,
http://forum.xda-developers.com/nexus-4/help
http://forum.xda-developers.com/amazon-fire/help
Or ask in the threads you linked yourself. :good:
Good luck!
Click to expand...
Click to collapse
Go to your device sections and contribute some meaningful posts to threads that interest you, and you'll be able to post in the other threads in no time. :good:
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!
Hi,
I'm looking for some assistance to unbrick an Allview Viva P8 Pro tablet.
All this mess started from looking after some disk space to install more apps on on the default second partition.
First I've tried some tools like app2sd with no luck and finally decided to try adb/fastboot way, using a linux machine, to root the device.
Before starting the root procedure i was able to boot into recovery mode and while being into recovery mode I could see the tablet as a google device with the proper vendor id 0x18d1. Also "adb devices" command could find the device as expected. Right after issuing "adb restart bootloader", i cannot enter into recovery mode and it hangs with the logo displayed on the screen, i think it's a boot phase before entering into recovery mode.
I can still see it as usb attached device, not with google vendor id but identified as "Onda unverified", with vendor id 0x1f3a. Windows OS finds it as Android Bootloader Interface USB Developer and that's it. I've tried to install some drivers to establish communication but with no luck so far.
Thank you in advance.
iulian.popa said:
Hi,
I'm looking for some assistance to unbrick an Allview Viva P8 Pro tablet.
All this mess started from looking after some disk space to install more apps on on the default second partition.
First I've tried some tools like app2sd with no luck and finally decided to try adb/fastboot way, using a linux machine, to root the device.
Before starting the root procedure i was able to boot into recovery mode and while being into recovery mode I could see the tablet as a google device with the proper vendor id 0x18d1. Also "adb devices" command could find the device as expected. Right after issuing "adb restart bootloader", i cannot enter into recovery mode and it hangs with the logo displayed on the screen, i think it's a boot phase before entering into recovery mode.
I can still see it as usb attached device, not with google vendor id but identified as "Onda unverified", with vendor id 0x1f3a. Windows OS finds it as Android Bootloader Interface USB Developer and that's it. I've tried to install some drivers to establish communication but with no luck so far.
Thank you in advance.
Click to expand...
Click to collapse
Greetings!
Thank you for using XDA Assist.
Please consider posting your question here:
http://forum.xda-developers.com/android/help
You'll receive expert advice there.
Good luck!