Related
A few days ago I've tried using ADB but it said my device is offline. Earlier I tried ADB over network. Again, it said my phone is offline. So I wanted to see if I can get ADB access from the bootloader. Surprize: I can't get into the bootloader. If I turn my phone off and press Volume Down + Power, it just boots.
Now, my phone is working good, I just wanted adb access to do that darn EFS backup. And what's up with that "can't get into bootloader" stuff? I did it fine and dandy when I rooted my phone..
EDIT: well, since I can not do the backup the normal way, I just downloaded the efs folder as a zip. and dev/block/. Is it as effective as the normal way?
andrei1015 said:
A few days ago I've tried using ADB but it said my device is offline. Earlier I tried ADB over network. Again, it said my phone is offline. So I wanted to see if I can get ADB access from the bootloader. Surprize: I can't get into the bootloader. If I turn my phone off and press Volume Down + Power, it just boots.
Now, my phone is working good, I just wanted adb access to do that darn EFS backup. And what's up with that "can't get into bootloader" stuff? I did it fine and dandy when I rooted my phone..
EDIT: well, since I can not do the backup the normal way, I just downloaded the efs folder as a zip. and dev/block/. Is it as effective as the normal way?
Click to expand...
Click to collapse
It is Vol-Up + Power for bootloader. And you can't have adb access in bootloader mode. Only fastboot access.
Ok but why isn't adb working? Why does it always say it's offline?
Sent from my Google Nexus S
andrei1015 said:
Ok but why isn't adb working? Why does it always say it's offline?
Sent from my Google Nexus S
Click to expand...
Click to collapse
It could be that you installed some software/driver that overrides a working USB driver.
Try install Google USB driver from Android SDK Tools.
Install Android SDK Tools
When SDK Manager runs, select Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Also, make sure you turn on Developer options and "check" Andoid (USB) debugging option in Developer options setup.
_android_ said:
It could be that you installed some software/driver that overrides a working USB driver.
Try install Google USB driver from Android SDK Tools.
Install Android SDK Tools
When SDK Manager runs, select Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Also, make sure you turn on Developer options and "check" Andoid (USB) debugging option in Developer options setup.
Click to expand...
Click to collapse
Yup, I have all of the above.. Still offline >.<
andrei1015 said:
Yup, I have all of the above.. Still offline >.<
Click to expand...
Click to collapse
Do you have the Samsung Galaxy Nexus ADB interface showing in your device manager?
Try uninstall and reload again.
Almost = https://dl.dropbox.com/1/view/xiulpm329s4wxcd/Apps/CloudShot/shot_25022013_192328.png
Still it says offline.
(thank you for trying to help me )
In fastboot mode it looks like this:
just tested at work and it says "device" instead of "offline" which is good I think. The only difference is that at work I installed the SDK long after I got it at home and it has a slightly different folder structure and it also comes with eclipse.
Resolved. Downloaded the new SDK with ADT from the android site and it works. Please forgive me for posting so many times. Can someone please delete this thread?
andrei1015 said:
Resolved. Downloaded the new SDK with ADT from the android site and it works. Please forgive me for posting so many times. Can someone please delete this thread?
Click to expand...
Click to collapse
Good for you.
Anyway, if you followed post #4 and installed the new SDK Tools, would have saved you a lot of time.
Hello xda users!
I have bought a CAT s50 device and I am very used to feature that phone vibrates once when someone answers my call. Since it runs andorid 4.4.2 it does not support this feature by default. So I found app Vibrate Call (on Play store) (if someone knows better way around without rooting it would be cool)
So there is a main problem - when I try to access my phone via "adb devices" command it is not shown there (I enabled USB debugging and device can be seen in explorer). So I cannot run the shell to enable app. I tried it as well on Linux where no drivers are needed
Any solutions? Anyone faced the same problem?
pmDx22 said:
Hello xda users!
I have bought a CAT s50 device and I am very used to feature that phone vibrates once when someone answers my call. Since it runs andorid 4.4.2 it does not support this feature by default. So I found app Vibrate Call (on Play store) (if someone knows better way around without rooting it would be cool)
So there is a main problem - when I try to access my phone via "adb devices" command it is not shown there (I enabled USB debugging and device can be seen in explorer). So I cannot run the shell to enable app. I tried it as well on Linux where no drivers are needed
Any solutions? Anyone faced the same problem?
Click to expand...
Click to collapse
Try to unmount the storage / deactivate MTP when you are going to use ADB. Have you checked the devicer manager if your phone is listed?
Still no success. Looks like there is missing ANDROID (not USB) driver for s50 (under device manager). But it is strange that it did not work on Linux, but I am not sure that I tried PTP mode insted of MTP as you said.
pmDx22 said:
Still no success. Looks like there is missing ANDROID (not USB) driver for s50 (under device manager). But it is strange that it did not work on Linux, but I am not sure that I tried PTP mode insted of MTP as you said.
Click to expand...
Click to collapse
Try to disable the storage mount at all. Just adb connection.
LS.xD said:
Try to disable the storage mount at all. Just adb connection.
Click to expand...
Click to collapse
There is no right-click option to unmount it -> is there any other way to do it?
pmDx22 said:
There is no right-click option to unmount it -> is there any other way to do it?
Click to expand...
Click to collapse
Unmark all the checkboxes MPT/PTP/Mass storage (In the Android interface)
LS.xD said:
Unmark all the checkboxes MPT/PTP/Mass storage (In the Android interface)
Click to expand...
Click to collapse
There is the problem - I cannot uncheck, just switch between those 2. Any other ideas?
Thanks for answering!
LS.xD said:
Unmark all the checkboxes MPT/PTP/Mass storage (In the Android interface)
Click to expand...
Click to collapse
Any other ideas? Tried to contact developer from Bullit group, but still no answer.
My FRD-L09 doesn't show up in
Code:
adb devices
Just to make sure I'm not just being retarded: I plugged in my phone with the delivered usb-to-usb-c cable. USB Debugging is on. And I set the USB mode to Files in the persistent notification.
I can browse the internal storage and the SD card from my pc.
Do I need to install usb drivers first?
Where do I find the correct files?
The Hihonor support page doesn't even list anything related to Honor 8.
This XDA thread about drivers has a dead link to Huawei drivers.
I don't see drivers on this Huawei Honor 8 downloads page.
The naked driver listed on the xda page looks old, didn't try.
I found a shady page linking to some files by Single Drivers on blogspot and a random G+ message linking to said page.
It's late and I'm tired so I guess I'll postpone the rest of my search for another day.
Does any of you know where to download the correct drivers?
Maybe I should mention I'm on Windows 7. I tried plugging my device in a different usb port but don't get a popup it's automatically downloading drivers.
Have you tried HiSuite?
miva2 said:
My FRD-L09 doesn't show up in
Just to make sure I'm not just being retarded: I plugged in my phone with the delivered usb-to-usb-c cable. USB Debugging is on. And I set the USB mode to Files in the persistent notification.
I can browse the internal storage and the SD card from my pc.
Do I need to install usb drivers first?
Where do I find the correct files?
The Hihonor support page doesn't even list anything related to Honor 8.
This XDA thread about drivers has a dead link to Huawei drivers.
I don't see drivers on this Huawei Honor 8 downloads page.
The naked driver listed on the xda page looks old, didn't try.
I found a shady page linking to some files by Single Drivers on blogspot and a random G+ message linking to said page.
It's late and I'm tired so I guess I'll postpone the rest of my search for another day.
Does any of you know where to download the correct drivers?
Maybe I should mention I'm on Windows 7. I tried plugging my device in a different usb port but don't get a popup it's automatically downloading drivers.
Click to expand...
Click to collapse
Try the mtp & ptp selection. Or ptp selection
try changing usb mode i.e MTP or PTP
Thanks for your suggestions.
adriansticoid said:
Have you tried HiSuite?
Click to expand...
Click to collapse
Nope I have not but I prefer to avoid it.
Tmobilefan906 said:
Try the mtp & ptp selection. Or ptp selection
Click to expand...
Click to collapse
I didn't see those options. Is it the same as the "photo" and "files" option that appears in the notification?
How do I change my usb modes on EMUI 4.1?
miva2 said:
Thanks for your suggestions.
Nope I have not but I prefer to avoid it.
How do I change my usb modes on EMUI 4.1?
Click to expand...
Click to collapse
I forgot what drivers I used to make ADB work in mine. But I believe it's a generic Huawei driver. As for USB modes, you can find it under Developer options. OR, enable USB debugging, plug your phone, then you can select USB modes in the status bar.
miva2 said:
Thanks for your suggestions.
Nope I have not but I prefer to avoid it.
I didn't see those options. Is it the same as the "photo" and "files" option that appears in the notification?
How do I change my usb modes on EMUI 4.1?
Click to expand...
Click to collapse
Yes...isn't there a pull down to change USB options? If not, go into your dev options and chose "select USB configuration"
Developer options and usb debugging were (and are) enabled.
Yes I see now there is USB configuration menu in de developer options. The available options are charge only, MTP, PTP, RNDIS, audio source and MIDI. MTP is selected. I assume the Files button corresponds to MTP and the Photos button to PTP. (or whatever the buttons are called)
I'll look for a generic Huawei driver. I suppose I can find those on a Huawei site
Only generic Google drivers for ADB. The rest, including mass storage, is automatic in Windows 10.
If there's already drivers for ADB, you need to remove them and install Google's.
zinko_pt said:
Only generic Google drivers for ADB. The rest, including mass storage, is automatic in Windows 10.
If there's already drivers for ADB, you need to remove them and install Google's.
Click to expand...
Click to collapse
Generic Google drivers didn't worked for me. At least on my laptop.
Sent from my honor 5X using XDA Labs
adriansticoid said:
Generic Google drivers didn't worked for me. At least on my laptop.
Sent from my honor 5X using XDA Labs
Click to expand...
Click to collapse
Probably you have a different configuration. Throughout all the brands I've used, it was always Google drivers. Sometimes the cable didn't help.
zinko_pt said:
Probably you have a different configuration. Throughout all the brands I've used, it was always Google drivers. Sometimes the cable didn't help.
Click to expand...
Click to collapse
Will check that.
Sent from my honor 5X using XDA Labs
I really couldn't find drivers for Honor 8 even though I found for older Honor devices and other Huawei devices (not sure if those would work, didn't try)
I ended up installing HiSuite and it works fine now. I can see my device in
Code:
adb devices
now.
I preferred not to clog up my laptop even further but it looks useful still.
miva2 said:
I really couldn't find drivers for Honor 8 even though I found for older Honor devices and other Huawei devices (not sure if those would work, didn't try)
I ended up installing HiSuite and it works fine now. I can see my device in now.
I preferred not to clog up my laptop even further but it looks useful still.
Click to expand...
Click to collapse
HiSuite is the last resort if generic adb drivers don't work. Have you tested fastboot?
miva2 said:
I really couldn't find drivers for Honor 8 even though I found for older Honor devices and other Huawei devices (not sure if those would work, didn't try)
I ended up installing HiSuite and it works fine now. I can see my device in
Code:
adb devices
now.
I preferred not to clog up my laptop even further but it looks useful still.
Click to expand...
Click to collapse
Do a restore point. That way you can always revert.
Its not working for Honor 8 pro
zinko_pt said:
Do a restore point. That way you can always revert.
Click to expand...
Click to collapse
I tried installing all ADB and fastboot, Nothing worked for me, Finally installed Hisuite the device is connected but my ADB is not working.
My device is not listed in "adb devices"
Am an android developer it is most required for me. Please help.
Livemaker said:
I tried installing all ADB and fastboot, Nothing worked for me, Finally installed Hisuite the device is connected but my ADB is not working.
My device is not listed in "adb devices"
Am an android developer it is most required for me. Please help.
Click to expand...
Click to collapse
i'm stuck at the exact point of this last poster @Livemaker. Got Hisuite installed but can't see my phone when ADB devices is ran, did you ever solve it?
edit: please ignore me I needed to enable usb debugging :fingers-crossed:
cable_guy said:
i'm stuck at the exact point of this last poster @Livemaker. Got Hisuite installed but can't see my phone when ADB devices is ran, did you ever solve it?
edit: please ignore me I needed to enable usb debugging :fingers-crossed:
Click to expand...
Click to collapse
Yeah issue solved just enable "allow ADB debugging in charge only mode" in developer option.
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
- copy apps/APKs between phones
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: https://play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I also ported Fastboot - user should be able to execute fastboot commands
Thanks
Correct me if I'm wrong, but can't you use a local terminal to execute certain commands?
SaadatM said:
Correct me if I'm wrong, but can't you use a local terminal to execute certain commands?
Click to expand...
Click to collapse
Not sure if I understand what you mean with "local terminal". .. Do you mean a shell spawned from regular app running on your phone?
The point of the app is to perform some privileged tasks that cannot be performed by regular apps on non-rooted phone.
You should be able to perform these tasks without the need to install ADB on your PC, or even without having a pc currently at your hands(e.g., if you're on-the-go).
Additionally, you should be able to perform a lot of these tasks with a couple of taps (instead of typing shell commands).
Is it possible to connect to localhost (127.0.0.1), and issue adb commands to the device running this app?
crunchybutternut said:
Is it possible to connect to localhost (127.0.0.1), and issue adb commands to the device running this app?
Click to expand...
Click to collapse
It's actually doing the opposite.
You issue commands from app to the connected device. The app is running the adb components you are running on your pc.
You connect one device that runs the app to another device that you want to debug. You can connect the devices via Wi-Fi or USB OTG.
bugjaeger said:
It's actually doing the opposite.
You issue commands from app to the connected device. The app is running the adb components you are running on your pc.
You connect one device that runs the app to another device that you want to debug. You can connect the devices via Wi-Fi or USB OTG.
Click to expand...
Click to collapse
I get that is the purpose, I was just curious if it was possible to point at the same device. It would make ADB stuff much simpler when no other devices are available.
I get that is the purpose, I was just curious if it was possible to point at the same device. It would make ADB stuff much simpler when no other devices are available.
Click to expand...
Click to collapse
If you made adbd listen on specific port before(adb tcpip 5555), then yes, you can issue adb commands from the app to the same device running the app.
bugjaeger said:
If you made adbd listen on specific port before(adb tcpip 5555), than yes, you can issue adb commands from the app to the same device running the app.
Click to expand...
Click to collapse
I believe you'd need root to do that though, right?
crunchybutternut said:
I believe you'd need root to do that though, right?
Click to expand...
Click to collapse
No, I don't think you need root. I used it a lot on my non-rooted Nexus 5x and once on an old Asus Zenfone during testing and it was working as expected.
That's great . I was just wondering if there was something like this already out there. Thanks for your efforts and I hope you are prosperous.
bugjaeger said:
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I've added the possibility to copy apps/APKs between phones
Thanks
Click to expand...
Click to collapse
I have a question about this app. I have installed it and find a few over internet connections (android box, fire tv) but when i connect my wifes non rooted S9 snapdragon. It asks what i want to use visa otg cable. (Smartswitch ect..)
Maybe the best way to put this is to tell you want i want to do.
I have a rooted note 5 and my wife has a new non rooted S9 from T mobile. The bloatware sucks as i am sure you can imagine. I have read how to remove the bloat with package disabler without root. My issues is i need to make PIP a sister app for package disabler a device owner app. This is done through adb and a few simple commands. My problem to solve my issue is i have no PC in order to use ADB on. I have looked for way to use phone to phone ADB with OTG but never been able to put ADB on my note 5 to use the terminal like from a PC.
Any help would be great thanks.
lodk said:
I have a question about this app. I have installed it and find a few over internet connections (android box, fire tv) but when i connect my wifes non rooted S9 snapdragon. It asks what i want to use visa otg cable. (Smartswitch ect..)
Maybe the best way to put this is to tell you want i want to do.
I have a rooted note 5 and my wife has a new non rooted S9 from T mobile. The bloatware sucks as i am sure you can imagine. I have read how to remove the bloat with package disabler without root. My issues is i need to make PIP a sister app for package disabler a device owner app. This is done through adb and a few simple commands. My problem to solve my issue is i have no PC in order to use ADB on. I have looked for way to use phone to phone ADB with OTG but never been able to put ADB on my note 5 to use the terminal like from a PC.
Any help would be great thanks.
Click to expand...
Click to collapse
So you tried to connect your phone (with Bugjaeger installed) to you wife's phone via USB OTG cable? And the phone with Bugjaeger app doesn't detect any ADB device connection (or other dialogs pop up)? Did I understand this correctly?
You might need to temporarily disable the other protocols that Android offers via USB so that there are no other dialogs popping up (on your wife's phone). On my Nexus with Android 8, I can go to Connected devices -> USB and switch it to only "Charge this device" (so PTP or the other stuff is disabled).
In case there is some other app doing stuff with ADB USB devices, you might also need to change your defaults so that Bugjaeger can handle ADB USB devices.
Then you also need to make sure that Developer options are enabled on your wife's phone (and USB debugging of course).
Once you successfully connected and authorized the phone, you should do the following
- In Bugjaeger app switch to Packages tab and click on Add button top right (the button with the plus sign). Then you should pick the package disabler APK. This should install the package to your wife's phone
- Switch back to Commands tab (first tab) and either click on plus button in top right or shell into the device with the floating action button ("<>").
You can then activate the device owner with something like this
Code:
dpm set-device-owner disabler.package.name/.DisablerAdminReceiver
*Note that I don't prefix the command with "adb shell" here
When activating device owner you also need to make sure that there are no other accounts configured on your wifes phone (e.g. google account) because otherwise it probably won't work.
You can also check my blog post where I describe how to activate device owner with Bugjaeger in more detail (at the end of the blog post)
https://sisik.eu/blog/android/dev-admin/set-dev-owner
Hope that helps
going to give this a try thanks will post later with results,
Hi, I have a problem and I hope your app can help me.
I am without a PC and I have a tablet without root where I installed the application and a Samsung mobile phone that starts only in download mode, otherwise it gives me the message: Custom Binary blocked by FRP lock
Can I install a rom or a custom recovery with the app? I tried to connect them with the cable but it does not find the device.
Crisal said:
Hi, I have a problem and I hope your app can help me.
I am without a PC and I have a tablet without root where I installed the application and a Samsung mobile phone that starts only in download mode, otherwise it gives me the message: Custom Binary blocked by FRP lock
Can I install a rom or a custom recovery with the app? I tried to connect them with the cable but it does not find the device.
Click to expand...
Click to collapse
Hi,
Unfortunately, I don't think my app can help you in this case.
Hi, thanks for the reply. Do you know a way to help me?
please help me!!
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
bugjaeger said:
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
- copy apps/APKs between phones
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I also ported Fastboot - for now the user can dump bootloader info
Thanks
Click to expand...
Click to collapse
lindser112 said:
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
Click to expand...
Click to collapse
I don't have any wear os watch at my hands right now and I can't test it at the moment. Is the APK compatible with the watch? If you're able to establish an adb connection between Bugjaeger and the watch, try to check the "Packages" tab in Bugjaeger app. There's a "+" button in the top toolbar, which allows you to select apk for installing on the target device.
The official docs are showing how to establish ADB connection with the watch - https://developer.android.com/training/wearables/apps/debugging
In Bugjaeger you then need to tap the connect button (plug with a plus sign in top toolbar), type in the IP address of the device, and tap on connect button. Both devices should be connected to the same WiFi network to make this work.
i figured it out!!!! go to packages, press the plus button, install from apps installed on phone. it was soooo easy. i couldnt get adb to work on my pc!! i am so thankful to you for this app!!!!!
lindser112 said:
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
Click to expand...
Click to collapse
lindser112 said:
i figured it out!!!! go to packages, press the plus button, install from apps installed on phone. it was soooo easy. i couldnt get adb to work on my pc!! i am so thankful to you for this app!!!!!
Click to expand...
Click to collapse
Perfect :laugh:
The mystery: I cannot establish a USB connection between my Pixel 7 Pro (Android 13) and PC (Windows 11). When I try, the PC makes that characteristic "connected device" sound, but Windows Explorer doesn't discover the Pixel, nothing shows up anywhere in the Windows Device Manager, and the ADB command
.\fastboot device
returns nothing. The Pixel is similarly not discoverable as a bluetooth device to the PC, although it IS to other devices (like my earbuds).
This is the first task I have attempted since I performed a factory reset (and walked through the automated Pixel setup process) last night. I have spent the last three and a half hours reading Android forums, testing USB port-cable permutations, and installing and uninstalling drivers. There is no obvious solution to this problem within the first ten pages of Google search results. I would be beyond grateful for any possible insight, but please, take a moment to review what I have attempted already before you expend any effort helping me troubleshoot.
The Pixel CAN connect to an older laptop running Windows 10, appearing both in the Windows Device Manager (which says my drivers are up to date) and in File Explorer (where I can access the internal memory). But ADB similarly returns nothing on the ADB
.\fastboot devices
command. Also, my old phone (a Samsung Galaxy S20 FE 5G running Android 13) connects fine--both by USB and by bluetooth--to all three devices.
So the PC (Windows 11) connects to the Galaxy and the laptop (Windows 10) connects to the Pixel (kinda), which fairly well eliminates the possibility of an issue related to my hardware or USB cables. But the PC (Windows 11) won't connect to the Pixel--not anymore. Everything worked just fine when I unlocked the Pixel's bootloader a few weeks ago.
What I need now is to recover the functionality of the USB and bluetooth connectivities between the Pixel and the PC running Windows 11, especially for file transfers. For several reasons, WiFi reliant solutions are untenable for my situation. I also need to re-lock the bootloader by any method (not necessarily with the PC). As mentioned above, ADB has not succeeded in finding the device on either platform.
Finally, in case it's relevant: when I open the Pixel's USB Preferences menu, I cannot switch from "USB controlled by...This device" to "USB controlled by...Connected device"--in both cases, the Pixel returns a "couldn't switch" dialogue. And yes, I have of course enabled USB debugging.
If you took the time to comb through all those particulars, Thank you. I'm getting desperate for some thoughtful expertise, and while I'm open to retrying anything for the fifth or sixth time, (maybe I somehow missed the magic driver package), it is a special kind of tribulation to review the same tired list of perfunctory solutions to a different problem. I promise, the solution I need isn't one of the usual suspects.
I spent $800 on this device. That's a lot of money for me. It feels absurd and unfair that such a basic functionality--one that far more affordable devices have been delivering reliability for decades--should be missing from the Pixel 7 Pro. Please please please help me!
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
jaseman said:
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
Click to expand...
Click to collapse
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
GodieDan said:
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
Click to expand...
Click to collapse
Have you tried putting in Fastboot mode and then connect to computer?
schmeggy929 said:
Have you tried putting in Fastboot mode and then connect to computer?
Click to expand...
Click to collapse
Putting what in fastboot mode?
GodieDan said:
Putting what in fastboot mode?
Click to expand...
Click to collapse
Your phone in Fastboot Mode aka bootloader Mode.
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
yurishouse said:
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
Click to expand...
Click to collapse
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Yeah, you probably just need to install the official USB driver from Google. That was a problem that numerous people had when the Pixel 7 series first released.
GodieDan said:
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Click to expand...
Click to collapse
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
We'll I'm certainly not above learning new vocabulary but but in this case I don't think the issue is having read too little. Do you mean recovery mode? So far there is no custom recovery available for the Pixel 7 Pro, but yes I did try with the phone in the stock recovery
I have read every relevant article on XDA and three other forums and nothing has helped so far. I promise you I would not have posted if I could find the solution elsewhere.
Also the phone doesn't work fine on the windows 10 system. I was able to view my files but I couldn't read, write or execute ADB commands. I do consider USB file transfer to be a basic functionality, and windows 11 is backwards compatible with every storage device since punch cards.
Anyways I'm no pro, but I have had success with rooted devices in the past. For my benefit it would be helpful to be assiduous with language choice.
.
H
bobby janow said:
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
Click to expand...
Click to collapse
I there, yes, my objectitve was to lock the bootloader, not unlock it. However I got that part figured out at least, by getting the phone replaced (i had fortunately splurged on the extra protection). But also I never bricked my device, and as best I can tell, the issue at hand isn't related to the rooting, or everything would be working again with the new phone. I wanted to re-lock the bootloader because everything was just getting to be so unstable. This was never a problem on my Nexus 6p, but that was two devices ago. Also, is it just me, or are there generally fewer benefits to rooting than there were in the teenies?
Hi there
simplepinoi177 said:
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
GodieDan said:
Hi there
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
Click to expand...
Click to collapse
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
simplepinoi177 said:
...Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
simplepinoi177 said:
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
Click to expand...
Click to collapse
Wow, thank you for the speedy reply!
1. Having splurged on the protection plan, yesterday i went to best buy and replaced my device, and I'm no longer interested in messing with the bootloader. So where ADB is concerned, I don't need it. What i DO need is the functionality of making file transfers between my PC and my phone. Do you still suggest I look for the ADB driver on the developer website, or is there something more basic (and hopefully reliable)?
2. The device status reads:
"
The device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
"
I spent a few minutes googling around about those errors, no luck yet.
3. It would be straightforward to uninstall (or disable) the device, but when I do, I worry it will be difficult to locate where the drivers are hiding (to delete manually). Under the "Driver" tab I clicked "Driver Details" and found the directories for three files, winusb.sys and two .dll files. Are these the culprits? Might there be others anywhere?