Database Develop

ADB access broken....beyond frustrated

This about as short as I could make it:
I haven't tried to use ADB with my G1 for about a month, so I'm not exactly sure when the problem started, but it's become a royal headache now. For whatever reason when I launched ADB shell today, I got an error saying 'device not found'. The first thing I did was check device manager where I noticed the phone showed as a 'USB composite device' with a yellow exclamation mark over it. I thought to myself "drivers." So I tried pointing it to the driver in the Android SDK folder. That just popped an error saying that Windows couldn't find a better driver match than the one I was already using.
From there I got the googling and came across this insanely long Google Groups thread. Following the advice listed, I started pulling some USB .sys files. I tried using an older copy of the USB driver from a previous SDK. I tried using Haruyko's modified USB driver. None would install.
Same error.
Reading down some more I saw that some people had success with with usinfg HTC Sync. It was worth a shot, right? Well it certainly made things different, but doesn't resolve the issue. Now in device manager I have an 'HTC Remote NDIS' listing under Network Connections. The old 'USB Composite Device' item is now gone. But still, I can't use ADB. "Device not found."
It's driving me nuts.
At this point I figured that it'd be best to try this on a different PC. Maybe my primary one is wonking out. These things happen. Well, that hope was quickly crushed when I discovered that NOT EVEN on a VANILLA XP SP3 setup, will Windows detect the G1. I downloaded a fresh copy of the SDK, plugged it in, pointed it to the USB driver....and nothing. Same error as PC number one:
"Windows can't find a better version of the driver than you're currently using."
Tried switching the USB cable. Same thing.
Back to PC number one, I removed all HTC software from 'Add/Remove Programs, then ran USBDeview. There, I removed the HTC NDIS device, unplugged the G1, and plugged it back in.
The HTC NDIS Remote device returned. **** my life.
SO.....before I throw this phone into traffic, does anyone have any clue as to what's going on here? All I want to be able to do is regain ADB access to my phone. I don't care about USB tethering (and toggling that option does nothing btw) or none of that. Just looking to regain ADB access. The only thing that's changed since the last time I used ADB is the version of Cyanogen's mod. I'm currently using v4.2.3.1. Maybe this broke shell access?
Thoughts?
**EDIT***
-Toggling USB debugging does nothing either.
-Ditto that for Fastboot

device not found has to do with the phone....make sure your cable is not messed up.

B-man007 said:
device not found has to do with the phone....make sure your cable is not messed up.
Click to expand...
Click to collapse
Tried switching the USB cable. Same thing.
Click to expand...
Click to collapse
Tried that already.

the.snks said:
Tried that already.
Click to expand...
Click to collapse
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again

B-man007 said:
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again
Click to expand...
Click to collapse
As far as I know the USB port is ok. It charges fine. And to update everyone on where I am, I tried the following today:
-Removed all HTC software (Sync and Drivers).
-Used USBDeview to remove all instances of HTC, and Android devices.
-Tried downgrading my test machine (PC #2) to Service Pack 2.
-Tried a third USB cable.
And I'm still getting the same problem. So there's no doubt in my mind that it has to be the phone. Like I said, the only thing I've done lately is update the version of Cyanogen's ROM.
I know it definitely worked before I updated to v4.2.3.1. Also I noticed that I am no longer able to mount the sdcard as storage in Windows. I do not get a prompt on the G1 asking if I wish to mount it. However, the USB debugging notice still pops up (weird).
....and here I'm stuck once again.

Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.

rp1783 said:
Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.
Click to expand...
Click to collapse
Yes. Multiple times in fact. It can't be the computer if the same issue is happening across two different PC's, with three different USB cables.

At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stuck in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues

goldenarmZ said:
At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stick in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues
Click to expand...
Click to collapse
PROGRESS! I booted into recovery mode and plugged the G1 into the computer. I got the 'new hardware' prompt and was asked to install the driver. I did so using the one from the SDK. Now I have ADB access, and Windows tried to mount the sdcard but that failed. I'm guessing because there's no way for me to 'ok' that in the recovery console.
So what does this tell us? I'm not sure if I understand what's wrong here.
(Sidenote: Man I'm so tempted to try to install the new Google Maps now....)

the.snks said:
So what does this tell us? I'm not sure if I understand what's wrong here.
Click to expand...
Click to collapse
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd for windows when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file

goldenarmZ said:
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd as storage when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
Ah....that blows but you do what you gotta. I'll try wiping and report back in case this thread helps anyone else.
Thanks man.

Alright, here's what I did to get working again:
Doing a wipe did NOT resolve the issue. However, updating to v4.2.4 did (remember I was using v4.2.3.1 originally). For clarity, I wiped both before and after the update. And I had to use a sdcard reader to get v4.2.4 onto the phone. I can now ADB and mount the sdcard in Windows without issue. I'm not sure if this was a one off, or possibly a bug in v4.2.3.
Somebody may want to bounce that Cyanogen.
B-man007 and goldenarmZ, the help was much appreciated.

This probably is related to USB tethering Cyan put in his rom.
Also for future reference, if you want to mount your SD card in recovery and you have Cyan 1.3 or greater or RA recovery, you can just type
ums_enable
to mount and
ums_disable
to dismount
saves you from typing that hideously long line lol

Screen broken, need to recover data from internal storage

Hello, my Samsung Galaxy S I9000 fell and the screen is broken.
When I turn on the phone, I can hear the start up sound. When I connect it to PC, the drives are recognized but not mounted as I cannot select the menu in the phone.
USB debugging was not selected.
Is there a way to access the internal storage as I need to recover the data?
Please help.

1)activate phone in recovery mode (POWER+VOL UP+HOME)
2)connect the phone via usb to a computer
3)use adb to recover your files (i would recommend checking this guide or any other you can find, if you dont know how to use adb: http://forum.xda-developers.com/showthread.php?t=619153 )

You can mount USB Storage in CWM Recovery if you have it. If not try to flash a kernel with it, like CF-root or Speedmod.

Having the same problem, however I can't enable USB Debugging as my touchscreen is non-responsive and my android device doesn't support OTG USB mice etc

jleafe said:
Having the same problem, however I can't enable USB Debugging as my touchscreen is non-responsive and my android device doesn't support OTG USB mice etc
Click to expand...
Click to collapse
you have a big problem, have you try with linux, like ubuntu, perhaps you have more luck

You can flash cf root which comes with CWM recovery. Then mount USB storage with cwm recovery (press volume up+home+power) then you can access the internalbsd card.

similar problem
Hi I have a very similar problem with my Xperia S LT26i. I dropped it into the bath and it was only in the water for about 30 seconds. Now the touchscreen is not working and the colour has stared to bleed out of the screen. the screen was fine first (looked normal) but now it is very faint and mono-colour which seems to keep changing for dark to white.
I have plugged it into three different computers now and the phone is shown but nothing in it is shown. The USB debugging was not enabled, as previously I didn't know this had to be enabled. Please tell me there is a way around this? the phone itself is still working as I have had a phone call and texts come through. really want to save my data please help!
PC companion doesn't read it either as it says the phone has to have USB debugging enabled. also apparently the Xperia S doesn't have a recovery mode.

Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it
Click to expand...
Click to collapse
Link here

Backup of phone with broken screen, no adb. CWM script or keypress walktrough?

Hi,
My GF broke the screen on her Galaxy S i9000 today. Completely black with She would like to get a copy of what's in the internal memory. Initially I thought I'd install CWM and copy it out using ADB. However, ADB does not work. It will intermittently be able to see the device with adb devices, but adb shell fails, and so does adb backup. After trying three different USB cables (two of which I know to bee good) and two different cf-root recoveries (CF-Root-XW_NEE_JVH-v3.2 and CF-Root-XX_OXA_JW4-v4.4-CWM3RFS) I have concluded this is most likely because the USB port on the phone was damaged on the trip to the ground, and is unable to keep a connection. Heimdall kernel flashing succeeded two of three times though, so it is strange. However, it was impossible to connect to the phon with both Kies and as Mass Storage device while it was still booted into Android, so it is most likely the USB port that's the problem.
Anyway, I can see one possible solutions that is likely to succeed:
Is it possibly to, by way of init scipts or similar, to make CWM copy everything from the internal SDcard to the external one, as well as everything on the /data partition?
Have someone already made such/ sa similar script a script, or could anyone possibly be willing to write one?
Note: I can't flash CWM.zips on the phone, I can only flash imagefiles via heimdall (which is like Odin). Is it a all possible? I guess I COULD flash another CWM, come to think of it, by putting it on the sdcard and follwing keyprrss instructions.
Thanks for any help or suggestions in advance, they will be appreciated.

[Q] Recovering files from broken phone

First of all, i have tried to solve this problem for hours and so far i don't have found anything that could help me.
So my screen is broken, completetely black, and i would like to save some files from my galaxy S(files are NOT on external SD card). Connecting phone to computer doesnt help because i should turn mass media mode on, and thats kind of hard when the touch screen is not working. Kies recognizes my phone(tries to connect), but can't connect because i should turn some other mode on? I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:

tuotanin said:
First of all, i have tried to solve this problem for hours and so far i don't have found anything that could help me.
So my screen is broken, completetely black, and i would like to save some files from my galaxy S(files are NOT on external SD card). Connecting phone to computer doesnt help because i should turn mass media mode on, and thats kind of hard when the touch screen is not working. Kies recognizes my phone(tries to connect), but can't connect because i should turn some other mode on? I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:
Click to expand...
Click to collapse
Hi,
I have a solution for you
No need to turn on mass storage.
What you need:
USB cable
Working pc
Android SDK http://developer.android.com/sdk/index.html
USB Driver http://developer.android.com/sdk/win-usb.html
1. Download and install this tool: http://de.codeplex.com/releases/view/107423
2. Boot your phone into recovery (worked for me) ( volume up+home+power)
3. Connect your usb cable
4. Start Droid Explorer and search for your sd card

cixty said:
Hi,
I have a solution for you
No need to turn on mass storage.
What you need:
USB cable
Working pc
Android SDK
USB Driver
1. Download and install this tool:
2. Boot your phone into recovery (worked for me) ( volume up+home+power)
3. Connect your usb cable
4. Start Droid Explorer and search for your sd card
Click to expand...
Click to collapse
Thank you for your answer. I think i can't get my phone into recevory mode. At least Droid explorer doesn't find it. When i try to boot it into recovery, my computer makes that "connected sound" several times, so i think the phone really is broken... Also, when the phone is connected to computer with usb cable, and i put the battery into the phone, i can hear that connected sound immediately, so i guess the phone automatically boots on? Well i keep trying but i think it is not possible to boot this phone into recovery mode

tuotanin said:
I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:
Click to expand...
Click to collapse
What you need therefore is a (rooted) phone and USB debugging must be enabled - at least I never tried withouit thos options turned on. Since you don't need to do sthg with su I think technically you can go without root as well, but did never run it without so not sure on that. Hope you had USB debugging active before your screen broke...
Install the adb tools on your pc if you haven't already. (google is your friend )
What you want to do now is connect your phone to the PC, open up a terminal session (within windows e.g. execute -> cmd ) and then fire up those commands:
Code:
adb
lot of stuff, ignore - if it doesn't work: google installing drivers and the adb tools
Code:
adb devices
here your phone should be listed if it is in debugging mode.
then just
Code:
adb pull [pathToYourHolidaypics] [pathToSaveOnHarddisk]
so for example:
Code:
adb pull /sdcard/DCIM Holidaypics
and you photos should be rescued. Good luck!

2 Be said:
What you need therefore is a (rooted) phone and USB debugging must be enabled - at least I never tried withouit thos options turned on. Since you don't need to do sthg with su I think technically you can go without root as well, but did never run it without so not sure on that. Hope you had USB debugging active before your screen broke...
Install the adb tools on your pc if you haven't already. (google is your friend )
What you want to do now is connect your phone to the PC, open up a terminal session (within windows e.g. execute -> cmd ) and then fire up those commands:
Code:
adb
lot of stuff, ignore - if it doesn't work: google installing drivers and the adb tools
Code:
adb devices
here your phone should be listed if it is in debugging mode.
then just
Code:
adb pull [pathToYourHolidaypics] [pathToSaveOnHarddisk]
so for example:
Code:
adb pull /sdcard/DCIM Holidaypics
and you photos should be rescued. Good luck!
Click to expand...
Click to collapse
Thank you for your answer. Unfortunately, this method doesn't find my phone either.. I think that USB debugging mode was on but can't say for sure. Maybe my Samsung is just completely broken. I guess we are out of ways to recover files . Thank you for your help and of course feel free to post anything if anybody have any idea.

tuotanin said:
Thank you for your answer. Unfortunately, this method doesn't find my phone either.. I think that USB debugging mode was on but can't say for sure. Maybe my Samsung is just completely broken. I guess we are out of ways to recover files . Thank you for your help and of course feel free to post anything if anybody have any idea.
Click to expand...
Click to collapse
if usb debugging off, mtp still working so pc must detect ur fone unless its already not working.if pc recognised ur fone when plugged in, use any partition backup app in pc to backup da entire partition
n i m sorry if its doesnt help u
Sent from my GT-I9000 using xda premium

compacity said:
if usb debugging off, mtp still working so pc must detect ur fone unless its already not working.if pc recognised ur fone when plugged in, use any partition backup app in pc to backup da entire partition
n i m sorry if its doesnt help u
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
It should be in USB storage mode. I dont know what mode is on atm. Even Kies doenst recognize phone

Stuck on lockscreen without ability to type in password

Samsung Galaxy S10
Android 10
TWRP
Rooted with Magisk
I just put my phone in ultra power saving mode, but unfortunately i cant unlock the lockscreen because i disabled samsung keyboard and now there is no keyboard where i can type in my password, and since i am in power saving mode it also disabled my other keyboards
So i tried removing the screenlock by deleting the locksetting files in /data/sys/, but since my phone is encrypted i can only see nonsensical filenames, so i dont know which files to delete
Can i safely delete every file there ?
I dont want to factory reset my device because i have a lot of important data on it
I already tried to remove the lock using https://findmymobile.samsung.com/, but it says that that function is disabled on my phone
I have no physical keyboard that i can plugin in into my phone
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
Can i safely delete the other files too ?
Because i dont know which encrypted filenames correlate to the files that i have to delete
EDIT: Thanks, i solved it by connecting a USB Keyboard to my phone using an USB-OTG connector included in the package of my Galaxy S10

If the device supports OTG, you can try connecting a full size PC USB keyboard via OTG.
I went through similar situation when I changed screen render resolution to less than half, then accidentally locked the phone, the keyboard and Screen-Guard were rendered at low resolution, and lock screen was not interactable.
The only way to restore that without prior arrangements was to flash stock Samsung ROM, via PC, with carefully choosing options to not format internal storage and data partitions.
If you have custom recovery, you could enable insecure USB debugging options in build.prop that always allows USB debugging via ADB, then re-install Samsung keyboard, or find some other solution with ADB.
If you have custom/twrp recovery, I'd say connect to PC in recovery mode and copy to PC all important files from /sdcard just in case.

Old Android versions like Android-5 had build.prop files where you could force USB debugging for development uses, that would Allow ADB even the device was locked.
I am not aware if newer Android versions allow that.
Once you get to TWRP, you need to use
Bash:
vi /system/build.prop
Or just
Bash:
echo "text-lines" >> /system/build.prop
To the build.prop file
in command line and enable debugging mode.

The build.prop lines :
Forced USB debugging

Harshiv989 said:
Old Android versions like Android-5 had build.prop files where you could force USB debugging for development uses, that would Allow ADB even the device was locked.
I am not aware if newer Android versions allow that.
Once you get to TWRP, you need to use
Bash:
vi /system/build.prop
Or just
Bash:
echo "text-lines" >> /system/build.prop
To the build.prop file
in command line and enable debugging mode.
Click to expand...
Click to collapse
I cant access /system/ from twrp, it just says that there is not such folder despite it being there, but i think that i have enabled debugging anyways and i already made a backup, which is somehow useless because of the encryption
Harshiv989 said:
If the device supports OTG, you can try connecting a full size PC USB keyboard via OTG.
Click to expand...
Click to collapse
I read in several other threads that in ultra-power-saving mode, android only allows USB devices to charge the phone, and i have no keyboard that i can plug in anyways, i cant buy one because everything is locked down (COVID)
The only way to restore that without prior arrangements was to flash stock Samsung ROM, via PC, with carefully choosing options to not format internal storage and data partitions.
Click to expand...
Click to collapse
As far as i know i cant just flash stock firmware without having to wipe my data
If you have custom recovery, you could enable insecure USB debugging options in build.prop that always allows USB debugging via ADB, then re-install Samsung keyboard, or find some other solution with ADB.
Click to expand...
Click to collapse
How could i reinstall samsung keyboard ? I have no access to the pm command in the twrp shell, and the files are encrypted anyways
Another related thing: https://forum.xda-developers.com/t/...-galaxy-s10-e-5g-exynos.4180287/post-84456927

I see that with combination of FBE, UPSM and disabled Samsung keyboard, you have put yourself in far more idiotically constrained situation than I had, as well as what Samsung devs imagined was possible.
With encrypted file system, you wouldn't even be able to flash an update.zip that includes a build.prop (from your stock ROM)with forced ADB enable-ment lines from recovery I guess. ( this is different than doing it from developer options, allows adb access without unlocking device )
I would still suggest you to charge your phone 100% and attempt a HW external keyboard method,
I am willing to bet Samsung was not stupid enough to block USB I/O devices at kernel level in UPSM.
You don't necessarily need to buy a new keyboard, just find one that connects to PCs via USB, wire or wireless dongle, either should work (no RGB/W backlights in keyboard if wired, we want a low powered keyboard, smaller if possible), from any other computer geek you know, and an OTG connector.
I have always been able to flash the stock ROM that only rewrites /system partition, and leave /data mostly untouched, have done it numerous times with odin, with new devices, you should be able to do that.
The device encryption is a hurdle which severely limits your options.

Also, my UPSM allows both wifi, and Bluetooth, if you had either of them ON, you could use a Bluetooth keyboard or debugging via wifi, if Bluetooth keyboard was previously paired(it auto connects), or wifi debug feature was set up already , ADB access might be possible, though wifi ADB is more secure, unlikely to work in locked screen guard state.

funny the most command and most upvoted answer for this issue on the internet for the average joe (not xda) is to reset the mobile.. disgusting reallly.. i also cannot imagine do the massive reconfiguration for this trivial issue. just had the gboard disappear and took a really short time to plug PC keyboard and an adapter i always have with me.

plug and play to the rescue...