Database Users

[Q] Adb not recognize in fastboot[Q]

I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.

YoungCorruptionV2.0 said:
I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.
Click to expand...
Click to collapse
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.

RMarkwald said:
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.
Click to expand...
Click to collapse
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2

YoungCorruptionV2.0 said:
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
You can't use adb in fast boot . Reboot to the boot loader. If you type 'fastboot devices' in fast boot your phone will show
Sent from my One X using xda app-developers app

I had the same problem.
What version of adb.exe Ade you using?
The latest is dated sometime in November this year. If it's earlier than that, download the SDK from android development site and use newer version of adb.exe
That should fix the issue...
Sent from my Nexus 7 using xda premium

From bootloader use fastboot commands, from recovery use adb commands.

You can't do adb commands in fastboot mode. To do adb commands you either need to be in Android or in a recovery.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!

If you have twrp recovery installed you can boot to recovery and use adb sideload.
So just download a rom on your computer boot to recovery and sideload the rom to your device and then install it.
Not sure if this can be done with cwm though
Sent from my Nexus 7 using Tapatalk 2

Unable to install TWRP to root

Just got my Nexus 7 Flo. I unlocked the bootloader, but I can't successfully install TWRP Recovery. When I try to flash it in CMD, it says "waiting for device" and I get stuck there, nothing else happens.
The tablet is in Bootloader mode when I try to flash TWRP. I tried using GooManager as well after, and even though I get the impression that it flashed successfully at first, I can't boot into it. It didn't work.
Anyone know why I'm stuck in "waiting for device" in CMD? I've been at this all night.

Did you switch the connection from Mtp to camera?
Sent from my Nexus 7 using xda app-developers app

Weird. If you unlocked the boot loader it should work.
Boot up first after you unlock, skip setup and enable developer options and then USB debugging. It should pop up and ask to allow ADB connection.
Then do "adb devices". If it returns a device, type "adb reboot bootloader". Then at the boot loader, type "fastboot devices" then "fastboot flash recovery recovery.img".
Sent from Nexus 7 FHD from XDA Premium HD

Doesn't find my device in Recovery mode

I get error: device not found.
But i tried adb and fastboot devices and it finds it but not after i choosed recovery mode. Using latest SDK tools and installed the usb driver through the device manager.
Running adb devices works but it shows it as empty.
I'm at lost.

similar issue
dj christian said:
I get error: device not found.
But i tried adb and fastboot devices and it finds it but not after i choosed recovery mode. Using latest SDK tools and installed the usb driver through the device manager.
Running adb devices works but it shows it as empty.
I'm at lost.
Click to expand...
Click to collapse
I'm experiencing a similar issue... My device doesn't show up when its in bootloader, but it does show up when the phone is operating normally. Also, I noticed under Device Manager, my phone is listed as "android bootloader interface" (while in bootloader), but it shows up as "android composite adb interface" when it's fully booted up normally.

What is the output of the 'fastboot devices' command when you are in boot loader mode? My first guess you are using some kind of Windows and you don't have the drivers installed.
Sent from my Nexus 4 using xda app-developers app

When I used the code above, it did recognize my device. The problem before was that I was attempting to use "adb devices" instead of "fastboot devices".
Thanks!

Use 'adb' while in recovery or fully working environment(you have to have a loaded kernel for adb), use 'fastboot' while in boot loader mode. Welcome.
Sent from my Nexus 4 using xda app-developers app

Nexus 4 (4.4.2) not mounting after unlocking bootloader

Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!

go to settings/storage open 3dots menu /usb computer connection. if nothing is selected that is why your phone doesn't connect. select mtp an problem solved.
if it's not that i cannot help you except suggesting to reinstall android from scratch using wug toolkit.

wasabitobiko said:
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
Click to expand...
Click to collapse
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?

acejavelin said:
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
Click to expand...
Click to collapse
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..

wasabitobiko said:
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
Click to expand...
Click to collapse
OK, so your fastboot commands are not working, that would likely be a driver issue? If you do
Code:
fastboot devices
and get a result, then keep going, if you don't, use one of the driver options in Wugfresh's toolkit, follow the instructions TO THE LETTER...
If you are just trying to get root and are unlocked, download the latest SuperSU.zip (to your phone preferably) from http://download.chainfire.eu/supersu and openrecovery-twrp-2.7.0.0-mako.img then start phone in Fastboot mode and enter:
Code:
fastboot boot openrecovery-twrp-2.7.0.0-mako.img
this will start TWRP on your device WITHOUT flashing it.
If the SuperSU zip file is on your phone, just use TWRP's Install button and navigate the file and flash it, then reboot and enjoy.
If the SuperSU zip is on your PC, then in TWRP go to Advanced, and start ADB Sideload, give it a few seconds for it to be recognized by your PC, you should be able to enter
Code:
adb devices
and get a result of SIDELOAD back, then enter:
Code:
adb sideload UPDATE-SuperSU-v1.94.zip
Or whatever the current SuperSU zip file is named. Then reboot and enjoy, your rooted!

Remember that adb commands only work in android and custom recovery NOT in fastboot mode.
Sent from my Nexus 4 using XDA Free mobile app

Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app

wasabitobiko said:
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
ADB sideload is a special mode that recovery can be placed into, it only allows the "sideload" command to be used. Fastboot is different, it uses the fastboot.exe program and fastboot mode on the android device to allow a limited list of features to be used.
I don't know what you are using for a rooting guide, but basically the end result is to flash SuperSU via recovery, that is all that is really needed.
Sent from my Nexus 4 using Tapatalk

Well, basically if your boot loader is unlocked and you have a custom recovery installed just download the latest superSU zip to your SD card. Reboot into recovery, install SuperSU, reboot. Alas, you're rooted.
Sent from my Nexus 4 using XDA Free mobile app

That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app

wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
If you unlocked your bootloader your drivers should be working fine. If you rebooted your phone now you'd see it works fine. Next step in rooting is to flash custom recovery. Download a custom recovery, I recommend latest version of TWRP, then flash the recovery image. 'fastboot flash recovery recovery.img' (replace recovery.img with whatever .img file you are flashing.
Once custom recovery is installed you can boot into it to flash supersu. If using TWRP it will prompt you to root when you reboot it.

Thanks.. And please don't take offense to this but re-read the thread. Ever since I used wug's rootkit to unlock the bootloader, neither my pc nor linux machine will recognize the Nexus 4. When I plug it in I get a usb error "device failed to load".. When I look at the device mgr it's listed as unknown device. Btw.. I've restarted both my phone and machine multiple times to no avail.
Sent from my Nexus 4 using XDA Free mobile app

Unknown device? Youve probably installed no or wrong fastboot drivers.
Sent from my Nexus 4 using XDA Free mobile app

wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Google tool 15 second adb xda
Sent from my Nexus 5 using XDA Free mobile app

UPDATE: It looks like the micro usb port on the phone is fried... had been charging fine until today. I'll keep you posted. Thanks for all the help. Does anyone know if this is a relatively easy fix?

Update: Fixed..
Replacing the usb port on the Nexus 4 is super easy. Thanks for the help guys. Everything's working and root has been achieved.

[Q] Nexus 4 Not Recognized

MTP works perfectly. ADB works great when the phone is turned on. However, when the phone is in recovery mode, ADB fails to recognize the device (when I type "adb devices" nothing is displayed).. I have previously flashed the OTA zips for 5.0 and 5.0.1 without any issue. I also have factory reset my phone. I tried the Wugfresh Nexus Root Toolkit Full Driver Text, and it gives a pass. However, this begs the question, why doesn't ADB work while my Nexus 4 is in recovery?
BTW my phone is completely stock and and is not rooted.

If your trying to sideload the of a zip just go ahead and do it. If you start sideload and then type adb devices it'll get recognized.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
If your trying to sideload the of a zip just go ahead and do it. If you start sideload and then type adb devices it'll get recognized.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I want to be safe. If in recovery I click "apply update from ADB" and get the message "send the package via ADB sideload", I should be able to type adb devices and see my device? Also, how would I get out of the the sideload screen (ie. which buttons would I hold)?

When you start sideload then open device manager. Find your Nexus 4 an update driver.
Select to choose yourself.
Then List will popup select ADB service in google inc.
Then update driver.
Then type ADB device it will show your device.
Good Luck
Sent from my Nexus 4 using XDA Free mobile app