Database Info

[Q] Help-Bootloop + no recovery

I have a T-Mobile Nexus S that has a bootloop. Its my friends so I dont know what he did to it. I can get to the bootloader but when I connect it to my computer it won't recognize it. I thought of a driver problem but i can't get past the bootloop to enable usb debugging. It also won't show up in device manager. The phone's usb port works. It will still charge. I just need to get rid of the bootloop. Any help would be greatly appreciated. Thanks!

MAGnum_21 said:
I have a T-Mobile Nexus S that has a bootloop. Its my friends so I dont know what he did to it. I can get to the bootloader but when I connect it to my computer it won't recognize it. I thought of a driver problem but i can't get past the bootloop to enable usb debugging. It also won't show up in device manager. The phone's usb port works. It will still charge. I just need to get rid of the bootloop. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
If it has a custom recovery, boot into it and wipe data/factory reset.
If it does not, flash a custom recovery. These forums are chockful on guides how to root, flash stuff and fix bootloops.

I looked up how to install recoveries but when i plug in my nexus to my computer it is not recognized. At the bottom of the bootloader screen it says "USB Control Init" and then "USB Control Init End". I do have the proper drivers installed. Is there a fix for this?

Are you sure that you have the correct drivers installed, though?
It's known that people who use Windows have a lot of success with the PDAnet drivers (you can search around here for those), rather then with the standard USB drivers the Google SDK provides.
Greetz

Did you try to run "fastboot devices" in command prompt while it's at fastboot mode and plugged into the PC? What do you see as the result? The guides on XDA should help, but you may also head over to nexusshacks_dot_com for more references.
Sent from my Nexus S using XDA App

With pdanet it requires me to plug in my phone with usb debugging turned on to get the drivers with i cant do because of the bootloop. and when i go into command prompt it says "waiting for device" and won't recognize it. Thanks for the help

[Q] Unlocking Bootloader Using SDK and ADB

I'm wondering if anyone has run into this problem before?
I'm trying to unlock the bootloader on my friend's Photon Q, I downloaded the SDK and installed the Motorola drivers. But when I put his phone into Fastboot mode, the "fastboot oem get_unlock_data" command does not work and CMD just says waiting for devices.
Yes I'm shift+right clicking on the platform-tools folder in the SDK to run the Command Prompt and I did download the correct Fastboot file. The command "adb devices" shows nothing when his phone is plugged in, but it shows my own phone (A Motorola Droid Bionic) when it's plugged into the USB cable. RSD Lite also recognizes both phones when powered on or in Fastboot mode.
I have no idea what to do at this point, we just need to get that unlock data to plug into the Moto site. Would it be possible to use someone else's unlock key or is each one randomized individually for the device? Or would that even work because my computer can't do the command for the unlock data, so maybe it couldn't push the unlock key onto the phone?

quick thought: did you enable usb debugging on the device?
edit: i guess that wouldn't make any difference in fastboot mode...
anyway, yeah, i'm pretty sure each device has it's own unique code. it's odd that fastboot recognizes the device, but the command isn't working. i bet you will get it somehow tho. a similar thing actually does happen to me sometimes, and in my case, it is because my usb ports are going bad and the computer loses connection with the phone.

Man nobody has anything eh? That's a crying shame. I tried using a different computer and went through the same course and still nothing.
I did try USB debugging on and off on both machines, didn't change a thing.

In order for the drivers (and therefore adb) to pick up the phone, I needed usb debugging *and* the phone not to be in charge only mode. Maybe that will help?
If not, when you reboot to fastboot and connect the cable, look at the devices installing list (if win 7) or device manager, and confirm the pc sees the fastboot device. If not you may need to reinstall the driver. Strange I know, but I needed to after getting my unlock data, holding off on unlocking due to the warranty voiding note, then trying again a couple days later where it wouldn't recognize. Seems to be finicky drivers to match a finicky device. But I do love this keyboard lol...
Sent from my XT897 using Tapatalk 2

We've only ever tried it in MTP mode and USB debugging enabled. This is day three of plugging it in and pulling it out and still no go. This is a royal pain, that is for sure.

Download Motorola Device Manager from the website, install, plug in phone. Place the phone into mass storage mode WITHOUT debugging enabled, then other modes, then back into bootloader mode then into fastboot mode. This will install EVERY driver, I didn't see that as one of the things tried.
Once you are in those modes, Android ADB device driver will install.
Hope that helps...
Sent from my XT897 using xda premium

HTC one E8 Dual SIM (M8SD) Unlock Bootloader Error

Hi
I was trying to unlock my htc one e8 dual sim bootloader but i cannot get the device to be indentified as adb device. Here's what i did
1) Installed Android SDK platform tools and google usb driver and downloaded the fastboot binaries from htc dev
2)Installed htc sync manager for the drivers
3)Enabled USB debugging on phone
4)When the phone is turned on, it is shown in the adb devices list BUT as soon as i boot it in fastboot, it is not listed. I have tried installing the google usb driver , connecting it in Charging and Media Transfer mode but to no avail.
My laptop has only usb 3.0 ports
Kindly Help Me
Regards

Well... if you have the proper drivers installed, when you turn on the phone with the Vol - and PWR combination, you boot first on HBOOT, you must select Fastboot and then let the drivers get installed, thats the only way

Device not recognized in fastboot on Mac and not recognized at all on PC

I'm hoping someone can help me out here. I've rooted phones before and didn't have any trouble previously. I just bought a used Pixel 3 on eBay with the plan to root using Magisk. The only problem is I can't get the device to be recognized at all on my PC. I've tried all the usual things like different USB ports, different cables, cleaning out the port, etc. I have the latest drivers installed and I have a Pixel XL that is recognized by my PC immediately so I know I have the correct drivers installed. Pixel 3 does not show up in Device Manager at all. I have USB debugging enabled on the device, but it never prompts me to Allow USB debugging when I connect the Pixel 3 to my PC.
Now, here's the weird part. I know the cable is working fine because I use the same cable and plug it into my Mac. The Pixel 3 is recognized immediately and I'm prompted to enable USB debugging. ADB then works just fine on my Mac. 'adb devices' shows my phone. But I then try to use 'adb reboot bootloader' and my phone reboots to the bootloader as it should. At this point my phone says it's in FastBoot Mode, but the device isn't recognized using 'sudo fastboot devices' and if I try 'sudo fastboot flashing unlock' it just sits there saying 'waiting for any device'. I've also tried putting it into FastBoot mode manually by using the Power and Volume Down key, but run into the same issue with it not being recognized while in FastBoot mode.
Could the previous owner have done something to the bootloader to cause the device to not be recognized in FastBoot mode? And is there any way to fix it? Why would the phone be recognized on my Mac without issue, but using the same cable and multiple different ports on my PC, it never gets recognized?
Any help would be very much appreciated here as I'm at a loss as to what I can do and fear I just spent money on an expensive paperweight.

I tested the cable I'm using with my Pixel XL and it's immediately recognized by my PC and the notification for USB debugging shows on the phone, so I know the cable is working out. No device ever shows in the device manager when I have my Pixel 3 connected though. I've even uninstalled the drivers while my Pixel XL is connected to hopefully put Windows into a driverless state hoping my Pixel 3 would then show up as an unrecognized device, but no device. I can't get it to show up at all in Windows for some reason and it's not recognized while in fastboot mode on my Mac. Fastboot mode information all seems to match what a Pixel 3 should look like as well, so I don't think the previous owner installed the wrong software causing device id mismatch. Anyone have any other suggestions for what I can try?

No ABD devices found Samsung A9 2018 SM-A920F

I rooted my Samsung A9 2018 SM-A920F, but now i have problems with smalipatcher to mock gps. I installed Java, but an error occurs. NO ABD devices found. I tried it with platform tools, in device manager i tried to update drivers, but keeps saying best drivers are installed, but the phone is still not recognised. OEM debug and OEM unlock is on, tried to revoke oem debug as well, but smalipatcher still cant find phone. Tried different cables as well. Someone that can help me?

Add Samsung A9 2018 SM-A920F to this thread's title thus mainly owners of such device get addressed.

Lucvdkant said:
I rooted my Samsung A9 2018 SM-A920F, but now i have problems with smalipatcher to mock gps. I installed Java, but an error occurs. NO ABD devices found. I tried it with platform tools, in device manager i tried to update drivers, but keeps saying best drivers are installed, but the phone is still not recognised. OEM debug and OEM unlock is on, tried to revoke oem debug as well, but smalipatcher still cant find phone. Tried different cables as well. Someone that can help me?
Click to expand...
Click to collapse
What does
Code:
adb devices
return?

jwoegerbauer said:
What does
Code:
adb devices
return?
Click to expand...
Click to collapse
Nothing. Gives no number. I rebooted my usb drivers as well. When I connect the usb and check device manager it adds Samsung Android Phone en when i open it gives Samsung Android ADB interface. My phone does not pop up as Samsung A9 but as MTP-USB-device

Lucvdkant said:
Nothing. Gives no number. I rebooted my usb drivers as well. When I connect the usb and check device manager it adds Samsung Android Phone en when i open it gives Samsung Android ADB interface. My phone does not pop up as Samsung A9 but as MTP-USB-device
Click to expand...
Click to collapse
You have to switch phone's USB mode to ADB.

jwoegerbauer said:
You have to switch phone's USB mode to ADB.
Click to expand...
Click to collapse
OEM unlocking and USB debugging are on, I put default usb configuration on Transferring files. Is that what you Megan? How do I put it on ADB?

Lucvdkant said:
OEM unlocking and USB debugging are on, I put default usb configuration on Transferring files. Is that what you Megan? How do I put it on ADB?
Click to expand...
Click to collapse
Your phone is configured to connect to phone via USB in Media Transfer Protocol (MTP) mode what is for transfering files.
As already said you have to configure phone that it connects via USB in Android Debug Bridge (ADB) mode.
IDK how you can achieve this because I don't have a phone as yours.
Follow my advice given in post #2

jwoegerbauer said:
Your phone is configured to connect to phone via USB in Media Transfer Protocol (MTP) mode what is for transfering files.
As already said you have to configure phone that it connects via USB in Android Debug Bridge (ADB) mode.
IDK how you can achieve this because I don't have a phone as yours.
Follow my advice given in post #2
Click to expand...
Click to collapse
Thanks, My device is not found in platform tools using the adb devices command, but it's on OEM unlock and USB Debugging is on. I added the phone in the tiltle, hope someone had an solution for my problem. Don't understand why it's not working. When I connect phone without the USB debugging it get's recognised, but with debugging mode on, nothing to find

Lucvdkant said:
Thanks, My device is not found in platform tools using the adb devices command, but it's on OEM unlock and USB Debugging is on. I added the phone in the tiltle, hope someone had an solution for my problem. Don't understand why it's not working. When I connect phone without the USB debugging it get's recognised, but with debugging mode on, nothing to find
Click to expand...
Click to collapse
Enabling OEM Unlock and/or USB Debugging simply sets an allowance flag, nothing else. It doesn't configure phone's USB mode.

I tried it on the laptop from work and there the phone is recognized in adb. But sadly I don't have administrator rights on that laptop to open Smalipatcher. Is there an alternative or work around available?