Hi,
i've done a clean LineageOS 15.1 with pico gapps on my galaxy tab s2 (gts210vewifi). But i'm not able to use the usb modes, the only thing i can do is charging. The notification for usb mode is missing.
If i plug-in an usb cable (tried many different) the device is not detected as any sort of device (lsusb didn't show anything). I also tried activating the developers options and enable usb-debugging. There are also direct/default mode change for usb and changing this (and replug) also had no effect. I'm sure thats a problem in combination with this device, since on the initial flash with lineage microg as well as the first flash this works perfectly. But after some time (or maybe a reboot) the notification isn't shown. Even a full flash (except the memory card) didn't change anything
Related
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
hello
dropped my N6 on to a marble floor, the screen is black and touch is not responding. the phone seems to be working otherwise. usb debugging is off, the phone is fully stock (stock recovery, bootloader is locked, encryption is the marshmellow default, phone is not rooted). There is no lockscreen pin or pattern, just the standard slide to unlock. photos are not auto-backed up online, so I need access to the phone itself.
when I plug the phone into my computer, I cannot file explore it because I need to enable a prompt on the phone to MTP instead of charge only. as USB debug if off I cannot use ADP PULL / SDCARD.
I have two ideas:
1) use Wug's nexus root toolkit and do something there like put TWRP on, and then use TWRP to avoid the USB debug being off. I'm not sure on the details of this though! Any guide on the steps here? the power and volume hardware keys work, so in theory I can get into recovery with the right steps.
2) get a micro-usb hub, and plug in a wired mouse as well as connect to my computer, then blindly click about hoping that I enable MTP or USB debugging. I can then either copy files off in windows explorer or use Vysor to control the phone over ADB and email files etc as needed. Would this work? I don't have a hub so would need to spend £5-10 buying one
Many thanks in advance for any help!
Option 1 won't work because the bootloader is locked. You'll have to try option 2.
Does anyone know why PTP mode would not be retained across a reboot? It seems to revert to MTP when rebooting into either the bootloader menu or into regular user mode.
I am trying to unlock the bootloader on my Nexus 6 running the latest build N6F27C of 7.1.1 that was sideloaded over 7.0 using ADB from my Mac. Now I'd like to start again and perform a clean flash of the 7.1.1 using ADB.
In normal user mode I can enable USB debugging in Developer Options and when PTP USB mode is selected then ADB will list my device just fine, I can trigger a reboot, etc.
However, after rebooting into the bootloader menu ADB shows that it has lost connection with my device, even though the screen shows that USB is connected. The ADB device list is empty.
On subsequent reboot into user mode I can see that USB debugging mode is still on but PTP connection mode has reverted to MTP, which (at least on a Mac) can account for ADB's lost USB connection to the device.
ADB debugging in PTP mode has worked fine for me in the past, but the phone now has been through several factory resets and restores from Google's backups, plus it is on 7.1.1.
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...
I can't pick any option when I connect the phone to the computer, they all are greyed out. The only way to transfer files from my phone to my PC is through TWRP or changing the default USB option through developer settings.
Can someone help?
Can you attach screenshots?
Jhon_Locke said:
I can't pick any option when I connect the phone to the computer, they all are greyed out. The only way to transfer files from my phone to my PC is through TWRP or changing the default USB option through developer settings.
Can someone help?
Click to expand...
Click to collapse
This happened with me on my phone's stock image. All the usb options were greyed out. I tended to look for solutions, but couldn't find anything relevant. Then, with a later update, it got fixed. However, now I'm using a custom rom(Resurrection Remix), so there are no issues with USB atm.
I would suggest you to install a suitable and stable custom rom(Lineage OS, is the best) on your device. It might help.
If you are on Lineage (You don't say) just set the USB option to always transfer in developer settings, Plus make sure USB debugging mode is turned off.