Related
Hi
I have a old nexus with broken touchscreen . I want to use it via mirror on pc.
unfortunatly USB debuggin wasn't enable so i can't install any app.
any tips?
thanks
PS: i saw many use usb adapter to connect a mouse but i don't have it
EDIT: right now i just need a rom/kernel with USB debugging mode enabled by default
the screen still works , only the touch screen is broken
power , and volume bottons still work
the device is rooted
If it's only installing apps you could install them via recovery. (as zip)
Or you could check for a cheap replacement touchscreen.
nonameleft4me said:
If it's only installing apps you could install them via recovery. (as zip)
Or you could check for a cheap replacement touchscreen.
Click to expand...
Click to collapse
thanks for the answer!
sorry i forgot to mention that i need USB debuggin for make the app works correctly.
I'm trying now to find out what rom i have installed and maybe then find a kernel with OTG support . (yes i found a otg cable )
i'm not a expert of rooting
I think google has an app called voice control. Not sure how operational it is though. Supposedly you can control the entire system via voice.
nonameleft4me said:
I think google has an app called voice control. Not sure how operational it is though. Supposedly you can control the entire system via voice.
Click to expand...
Click to collapse
i need to unlock the phone and tap on the widget "search" to start voice command .
I think the best way is to find a way to enable OTG and then use a usb mouse
Boot into Recovery and mount*Data*partition.
Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace*~/*with home directory of your OS.
Open that file in a text editor and you would possibly see*mtp*written there. Change it to*mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using*adb pullbut doing:
adb shell echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the*echo*command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
Unmount*Data*and reboot into Android OS. USB Debugging would probably be enabled.
Sent from my Aqua Trend using Tapatalk
Itzabhaysingj said:
Boot into Recovery and mount*Data*partition.
Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace*~/*with home directory of your OS.
Open that file in a text editor and you would possibly see*mtp*written there. Change it to*mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using*adb pullbut doing:
adb shell echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the*echo*command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
Unmount*Data*and reboot into Android OS. USB Debugging would probably be enabled.
Sent from my Aqua Trend using Tapatalk
Click to expand...
Click to collapse
thanks!
i tryed
1) i went in recovery mode
2) i connect via usb the nexus4 to my pc
3)went in "mounts and storage"
4)then "mount /data"
5)in cmd i tryed your command "adb pull /data/property/persist.sys.usb.config" but i says i'm unauthorized
i checked via command "adb devices" and it return a alphanumerica string plus "unauthorized"
i tryed then to
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
adb shell reboot
but it still says error : device unauthorizated . please check the confirmation dialog on your device
i tryed also with a different version of adb and now gives me after "adb devices" an "offline" response
NB: if i connect the phone (not in recovery mode) via usb i can copy files in and out (i can explore onlyfew folders) , maybe this could help.
hartman11 said:
i tryed also with a different version of adb and now gives me after "adb devices" an "offline" response
NB: if i connect the phone (not in recovery mode) via usb i can copy files in and out (i can explore onlyfew folders) , maybe this could help.
Click to expand...
Click to collapse
Sorry but this could not help... Now only thing you can do is connect any USB mouse to your phone via otg cable (as it is not costly also), and you can also try USB gamepad. I also have used USB gamepad before when my touchscreen was not working.
Second thing you can do is download any android device manager for your PC like mobogenie or mobilego they directly install any app from play store to you android device, through USB.And I don't think they need USB debugging option to be enabled.
Sent from my Aqua Trend using Tapatalk
my problem is not installing an app (i could do it in recovery mode with a .zip) but enabling the USB debuggin
I have a otg cable but not the "Y" type ( the one with power source ) , also i don't know if OTG is supported by my kernel . I would like to install maybe another kernel which has OTG support and usb debuggin mode enable by default but i don't know what kind of rom i have D:
right now i just need a rom/kernel with USB debugging mode enabled by default
up
Hi, I've got an old S5 with a broken screen. There's no image going on and there's no indication that the touchscreen is working.
I'm not looking to recover data, I'm looking to play around with it by controlling it from my PC. Last I remember, the phone is running a Cyanogenmod OS (I don't think LineageOS was around at that time) with either TWRP or CWM recovery, but I'd bet on TWRP.
Now: the device reaches the OS properly, I can tell because if I try to turn the ringing sound up it gives me an audio feedback.
If I connect it to a PC from the OS:
- the phone shows up in Windows Explorer as "SM-G900F"
- Device Manager shows me a "SAMSUNG Mobile USB Composite Device" under Universal Serial Bus controllers
However I cannot access any files (Windows Explorer shows the device as empty), and if I attempt to 'adb devices' in the console it shows me an empty devices list.
Now, I suspect that USB debugging might be off. So I also tried connecting it to a PC from recovery and the exact same thing as above can be observed, PLUS:
- Device manager also shows me a "SAMSUNG Android Phone" list which can be expanded to show me one entry called "SAMSUNG Android ADB Interface"
However it's the same as before, no files available and 'adb devices' shows an empty list.
Now I heard that I can theoretically enable USB debugging through ADB, by writing to a config file. That would allow me to enable USB debugging and try something like Vysor in order to control the phone from my PC.
However that's a moot point until I can figure out why the ADB service on my PC isn't seeing the device. Any help would be greatly appreciated, and if you need more info I can provide it.
Extra info:
- I installed Samsung USB drivers at some point while trying to make it work
- Windows Explorer shows a phone icon for this device, and if I recall correctly that's what happens when it's connected through MTP (Mass Storage should show it like a memory card)
_sepiroth said:
Hi, I've got an old S5 with a broken screen..........
Click to expand...
Click to collapse
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Ibuprophen said:
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks a bunch, that pointed me in the right direction with my research! I solved my issue, I can now control my phone from my PC.
By doing this I ran into a couple of problems, I'm going to describe them and their solutions:
Problem 1: couldn't ADB into the device when in Recovery Mode. That is because after a long head scratching session I came to the conclusion that I didn't have TWRP Recovery installed (I had Philz Touch CWM Recovery and LineageOS 14.1 instead).
Solution 1: ADB mode is enabled in TWRP by default. So I flashed the latest TWRP through Odin, ADB instantly started working afterwards in Recovery Mode.
Problem 2: USB Debugging was disabled inside the OS.
Solution 2: from the thread that Ibuprophen posted, you can enable USB debugging in your OS by opening an ADB shell into your device and modify the build.prop like so
Code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop
reboot
Problem 3: /system was empty so there was no build.prop. If I attempted to create a build.prop file it wouldn't be saved after a device reboot, so USB debugging still didn't work.
Solution 3: it seems like TWRP doesn't mount /system by default, only /data. You can mount it manually through ADB like this:
Code:
mount -o rw /dev/block/bootdevice/by-name/system /system
I found this out from this stackexchange question: https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
Problem 4: When an app tries to use USB Debugging you need to allow it to do so from the phone. Since the screen was broken, I couldn't do this.
Solution 4: You'll need to push a public key to your device with ADB. Boot into Recovery Mode and make sure your device is recognized by your PC and type
Code:
adb push <path to adbkey.pub on your PC> /data/misc/adb/adb_keys
This solution is from: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android
This will make sure that you won't need to confirm debugging permissions for apps coming from your machine.
So for anyone who has a broken phone screen (my screen is dead and touchscreen/touch buttons are kaput too) and wishes to control their phone from their PC but USB debugging is disabled:
1. Boot device in TWRP Recovery (flash it if you don't have it)
2. ADB into the device
3. Make sure /system is mounted (if it's empty it means it's not mounted), else mount it manually like in Solution 3
4. Configure build.prop to have USB Debugging enabled like in Solution 2
5. Push your public key to the device like in Solution 4
6. Restart the phone (into its OS)
7. Download the Chrome extension called Vysor and launch it
8. Connect your phone through a USB cable
9. The device should appear in Vysor, connect to it and have fun controlling it
Note that if you just want to backup your files, steps 1 + 2 are sufficient. After making sure ADB works you can just 'adb pull' all your files which should be located in /sdcard. Google it, it's easy to find.
The same goes for backups, you can do them directly through ADB.
Again, thanks Ibuprophen!
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
aIecxs said:
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
Click to expand...
Click to collapse
Very well pointed out, thanks for this.
Hi,
I think I've already explain everything in title.
My Galaxy S5 on Android 8 (I think) as her screen broken (black)
Before that it already wokr badly and slowly. I bought a new phone but this one break just before I can transfer data.
I can unlock the patern (I know that because the volume + buton react)
Smart switch say that the phone is locked (even it's not true). Tested on 2 PC
The phone appear in Windows but no file or folder appear.
In adb the device is shown unauthorised and even if I click where the message to unlock should be, notihng append.
The phone is connected on Wifi, apparear in Google Find it but not Samsung find it...
I think that it's already to much information...
My question : how can I do the unlock the phone and do a smart switch backup ? or an other way to transfer data.
Regards
James
The Samsung Galaxy S10 comes with a USB OTG adapter. OTG stands for "On the Go" and is used for the connection between smartphone and USB stick / cable. Connect this USB OTG adapter to the USB Type C port of your Samsung, then connect the USB OTG adapter with USB Type C port of your computer.
You should see the data stored on your Samsung.
jwoegerbauer said:
The Samsung Galaxy S10 comes with a USB OTG adapter. OTG stands for "On the Go" and is used for the connection between smartphone and USB stick / cable. Connect this USB OTG adapter to the USB Type C port of your Samsung, then connect the USB OTG adapter with USB Type C port of your computer.
You should see the data stored on your Samsung.
Click to expand...
Click to collapse
It's an S5. But I have a OTG adaptor for it but my new phone A52s doesn't connect to the S5.
I try with a S7 but I can see that there is a lot autorisation to give on the old phone which will be very hard to do with a black screen.
If ADB is unauthorized, the only way to back up any data would be via a custom recovery. That would require that the device have an unlocked bootloader though
iBowToAndroid said:
If ADB is unauthorized, the only way to back up any data would be via a custom recovery. That would require that the device have an unlocked bootloader though
Click to expand...
Click to collapse
ADB authorised is not require for Smart Switch... I think
And my device have access to recovery and it's root so the bootloader is unlocked.
jameslevalaisan said:
ADB authorised is not require for Smart Switch... I think
And my device have access to recovery and it's root so the bootloader is unlocked.
Click to expand...
Click to collapse
So then flash a custom recovery, and then enter it. That will either give you MTP access to the files and folders, or ADB should also be enabled - and does not require authorization
iBowToAndroid said:
So then flash a custom recovery, and then enter it. That will either give you MTP access to the files and folders, or ADB should also be enabled - and does not require authorization
Click to expand...
Click to collapse
purehaps you have forget that the screen is broken. I can't access the phone for complicated manipulation. I'have already have TWRP installed on it but without a view it's impossible to manipulate it. Also, it's not normal that the phone are not viewed on windows or is shown locked on smart switch.
In recovery mode, the phone isn't show on windows also. Find the MTP option in TWRP without a screen view is very diffucult and dangerous, (the wipe option are near)
If I can access file on phone I will be able to view screenshot and configure it.
jameslevalaisan said:
purehaps you have forget that the screen is broken. I can't access the phone for complicated manipulation. I'have already have TWRP installed on it but without a view it's impossible to manipulate it. Also, it's not normal that the phone are not viewed on windows or is shown locked on smart switch.
In recovery mode, the phone isn't show on windows also. Find the MTP option in TWRP without a screen view is very diffucult and dangerous, (the wipe option are near)
If I can access file on phone I will be able to view screenshot and configure it.
Click to expand...
Click to collapse
1. No, I didn't forget that the screen is broken
2. I wasn't telling you to press anything in TWRP. When it's in TWRP and you plug it in, you will either get MTP and/or ADB access automatically
3. Yes, it is perfectly normal to not have access to the files and folders in Windows, when it's powered on normally. There's a popup on the phone that you have to tap in order to grant permission to the folders and files. That's why it shows up as an empty device when you plug it in while in normal mode
iBowToAndroid said:
1. No, I didn't forget that the screen is broken
2. I wasn't telling you to press anything in TWRP. When it's in TWRP and you plug it in, you will either get MTP and/or ADB access automatically
3. Yes, it is perfectly normal to not have access to the files and folders in Windows, when it's powered on normally. There's a popup on the phone that you have to tap in order to grant permission to the folders and files. That's why it shows up as an empty device when you plug it in while in normal mode
Click to expand...
Click to collapse
Ok excuse me.
Hum when I'm in recovery mode, my phone doesn't appear in Widows. And in adb, I haven't access to all folder. Data is empty for exemple.
For 3. Ok, I don't remember this notification. But I'm shure that I'have already use this phone with my PC. If I wasn't able to ring it on Whastapp, I will think that the phone doesn't works anymore at all. But it's not the case.
jameslevalaisan said:
purehaps you have forget that the screen is broken. I can't access the phone for complicated manipulation. I'have already have TWRP installed on it but without a view it's impossible to manipulate it. Also, it's not normal that the phone are not viewed on windows or is shown locked on smart switch.
In recovery mode, the phone isn't show on windows also. Find the MTP option in TWRP without a screen view is very diffucult and dangerous, (the wipe option are near)
If I can access file on phone I will be able to view screenshot and configure it.
Click to expand...
Click to collapse
ADB commands work by default while in TWRP, you can back up almost anything that your TWRP version allows through your PC using ADB commands, TWRP will serve as intermediary, but you will not go to operate over your broken screen device but through your ADB/fastboot CMD.
In normal mode I can unlock the phone but after that even if I click where the message should appear it doesn't do anything.
In adb I can't access a backup command (and if I can do this, It will not the easyer way to transfer my sms.)
I have some old other phones to see some message exemple and know where to clic but it doesn't works. I have install Vyzor, It asks me a permission but even if I tap in the right of the screen the permission doesn't works.
I also try to transfert a new adb key but I think it doesn't work because Wyzor still ask permission.
jameslevalaisan said:
In normal mode I can unlock the phone but after that even if I click where the message should appear it doesn't do anything.
In adb I can't access a backup command (and if I can do this, It will not the easyer way to transfer my sms.)
Click to expand...
Click to collapse
There is no backup command in ADB that you can use. And the reason that you can't access /data is because that requires going into TWRP settings and mounting the system partition.
What you can do in TWRP is to adb pull all of the files and folders off of the internal storage
Other thing, I can phone my phone with Whatsapp but I can't click to hang off.
iBowToAndroid said:
There is no backup command in ADB that you can use. And the reason that you can't access /data is because that requires going into TWRP settings and mounting the system partition.
What you can do in TWRP is to adb pull all of the files and folders off of the internal storage
Click to expand...
Click to collapse
ok to do have a exemple of command to tap ?
And there no way to just be able to connect my phone with smart switch on windows ?
jameslevalaisan said:
I have some old other phones to see some message exemple and know where to clic but it doesn't works. I have install Vyzor, It asks me a permission but even if I tap in the right of the screen the permission doesn't works.
I also try to transfert a new adb key but I think it doesn't work because Wyzor still ask permission.
Click to expand...
Click to collapse
ADB backup is not to operate while your device is on, but it is to operate while your device is in TWRP mode.
TWRP has integrated by default the ADB options not need to authorize through your broken screen because it is already authorized.
Messages as an app user (the same with root or system user) is part of userdata, you want to back up userdata to restore it after in other device or a scenery where your device get repaired, no?
I'll give you an example, you have to use this command, create a folder on a convenient place onto your PC directory, something like "BACKUP", assuming that you set it up correctly the environment for ADB/fastboot to use it along all of your system, you should open from this newly created folder an CMD (I use the new Windows terminal for easy/comfortable results) then type from the terminal adb shell twrp backup userdata , you'll have the userdata backed up in your PC in less of 2 minutes depending on the size of the partition, and so on successively.
What you can back up from TWRP depends on the restrictions from your TWRP version, you should back up the normal that you can see from the TWRP screen and even more but for example if your TWRP have some issues mounting vendor partition of course the ADB commands can't do the job for this specific partition, but anyway you have a lot you can do through it.
jameslevalaisan said:
ok to do have a exemple of command to tap ?
And there no way to just be able to connect my phone with smart switch on windows ?
Click to expand...
Click to collapse
1. The command depends on what the mount point for your internal storage is. The command would be "adb pull /(mount point)" , so it could be:
adb pull /sdcard
adb pull /storage0/sdcard
Or several others
2. No, you can't connect with Smart Switch without allowing permission on the popup box on the phone screen
Hi guys,
I'm very happy to find here some people to help me. thank you a lot. I just now in recovery mode.
here is some result of command
Code:
adb devices
List of devices attached
487e969e recovery
adb root
adbd is already running as root
adb shell
~ # ls
cache init.recovery.qcom.rc selinux_version
charger init.recovery.service.rc sepolicy
data init.recovery.usb.rc service_contexts
default.prop license sideload
dev oem sys
etc prebuilt_file_contexts system
file_contexts proc tmp
fstab.qcom property_contexts twres
init res ueventd.qcom.rc
init.rc root ueventd.rc
init.recovery.hlthchrg.rc sbin vendor
init.recovery.nano.rc seapp_contexts
~ #
as you can see there is not storage in the ls result
Code:
~ # ls /res
images keys
~ # ls /data
~ # ls /data
Code:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db ./
adb: error: remote object '/data/data/com.android.providers.telephony/databases/mmssms.db' does not exist
Is there something inspired you ?
iBowToAndroid said:
1. The command depends on what the mount point for your internal storage is. The command would be "adb pull /(mount point)" , so it could be:
adb pull /sdcard
adb pull /storage0/sdcard
Or several others
2. No, you can't connect with Smart Switch without allowing permission on the popup box on the phone screen
Click to expand...
Click to collapse
1. the ls command doesn't show any sdcard or storage
2. Ok bit wyh I can't click on the permission popup ?
SubwayChamp said:
ADB backup is not to operate while your device is on, but it is to operate while your device is in TWRP mode.
TWRP has integrated by default the ADB options not need to authorize through your broken screen because it is already authorized.
Messages as an app user (the same with root or system user) is part of userdata, you want to back up userdata to restore it after in other device or a scenery where your device get repaired, no?
I'll give you an example, you have to use this command, create a folder on a convenient place onto your PC directory, something like "BACKUP", assuming that you set it up correctly the environment for ADB/fastboot to use it along all of your system, you should open from this newly created folder an CMD (I use the new Windows terminal for easy/comfortable results) then type from the terminal adb shell twrp backup userdata , you'll have the userdata backed up in your PC in less of 2 minutes depending on the size of the partition, and so on successively.
What you can back up from TWRP depends on the restrictions from your TWRP version, you should back up the normal that you can see from the TWRP screen and even more but for example if your TWRP have some issues mounting vendor partition of course the ADB commands can't do the job for this specific partition, but anyway you have a lot you can do through it.
Click to expand...
Click to collapse
I try this...
C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb shell twrp backup userdata
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
^C
C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb shell twrp plat-form-tools userdata
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
^C
I'm not sure I understand your command. But it return a result. "Backup" is the name of a folder ? or it's a commande for twrp ?
Is there a way to be sure that twrp is installed (with all my phone, sometime, I don't remember what is on it. The thing it's sure it that this phone is root because I use root function with some app but perhaps just with magisk or Super SU.
hi guys I need help to recover some personal photos I had saved on my device. The phone has a broken screen and touch so I cannot use a mouse or try to blindly unlock it, but it has been rooted and usb debugging is enabled; unfortunately my pc is not authorized by the phone and I have no way to authorize it through the pop up without a screen. I have searched around many forums to find a solution but it seems every time there was something wrong, so I need some help.
The solution that got me the nearest to a conclusion that I tried are:
using adb in custom recovery (which I do have) and trying commands like "adb pull /sdcard" which resulted in "pull: building file list... 0 files pulled. 0 files skipped.", I don't understand why it's unable to pull any file.
trying to authorize usb debugging for my pc through adb by "adb push adb_keys /data/misc/adb", adb_keys is the adbkey.pub file in the .android folder renamed. I can confirm i pushed them since "adb pull /data" pulled "data/adb/misc/adb_keys" as the only file, but I still don't have authorization
I'm not too literate in this kind of commands so please be patient but I really need help
RECAP OF MY PHONE STATUS
Xiaomi Mi 10 5G is the device
both screen and digitizer broken, I'm not able to see the screen or use touch (but I'm 100% sure the phone still works)
Android 12 rom (xiaomi.eu stable)
custom recovery available
rooted device
usb debugging enabled
no device authorized by the phone for usb debug
I found somewhere on xda that the problem could be solved by mounting/unmountind sdcard, but I have no ideea hoe to do that
damndaniel0 said:
hi guys I need help to recover some personal photos I had saved on my device. The phone has a broken screen and touch so I cannot use a mouse or try to blindly unlock it, but it has been rooted and usb debugging is enabled; unfortunately my pc is not authorized by the phone and I have no way to authorize it through the pop up without a screen. I have searched around many forums to find a solution but it seems every time there was something wrong, so I need some help.
The solution that got me the nearest to a conclusion that I tried are:
using adb in custom recovery (which I do have) and trying commands like "adb pull /sdcard" which resulted in "pull: building file list... 0 files pulled. 0 files skipped.", I don't understand why it's unable to pull any file.
trying to authorize usb debugging for my pc through adb by "adb push adb_keys /data/misc/adb", adb_keys is the adbkey.pub file in the .android folder renamed. I can confirm i pushed them since "adb pull /data" pulled "data/adb/misc/adb_keys" as the only file, but I still don't have authorization
I'm not too literate in this kind of commands so please be patient but I really need help
RECAP OF MY PHONE STATUS
Xiaomi Mi 10 5G is the device
both screen and digitizer broken, I'm not able to see the screen or use touch (but I'm 100% sure the phone still works)
Android 12 rom (xiaomi.eu stable)
custom recovery available
rooted device
usb debugging enabled
no device authorized by the phone for usb debug
Click to expand...
Click to collapse
There is a way to do it, but it costs money
@damndaniel0
If USB-MTP mode is enabled on phone - what should be default - then you can access all user-data stored in /storage/emulated/0 directory where among others photos are stored.
See also here:
MTP USB Device Driver Windows 10 64bit Driver | Device Drivers
MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for...
oemdrivers.com
xXx yYy said:
@damndaniel0
If USB-MTP mode is enabled on phone - what should be default - then you can access all user-data stored in /storage/emulated/0 directory where among others photos are stored.
See also here:
MTP USB Device Driver Windows 10 64bit Driver | Device Drivers
MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for...
oemdrivers.com
Click to expand...
Click to collapse
If you mean simply to connect the phone through usb to pc, I cannot do that because MIUI asks everytime if I want to transfer photos, files or just charge with a pop up on screnn (which I obviously cannot do)
iBowToAndroid said:
There is a way to do it, but it costs money
Click to expand...
Click to collapse
what would it be
damndaniel0 said:
If you mean simply to connect the phone through usb to pc, I cannot do that because MIUI asks everytime if I want to transfer photos, files or just charge with a pop up on screnn (which I obviously cannot do)
Click to expand...
Click to collapse
Not in system but in custom recovery (which you do have).
Timmmmaaahh! said:
Not in system but in custom recovery (which you do have).
Click to expand...
Click to collapse
Honestly I did not try, but I don't remember the phone directory showing up in windows file explorer after connecting the phone in recovery mode, I'll try againg when I'm home and I'll let you know
anyway I checked and no, I cannot access phone files
In Recovery mode you should can run
Code:
adb devices
adb pull <LOCATION_OF_DATA_OF_INTEREST> <STORAGE_LOCATION_ON_PC>
xXx yYy said:
In Recovery mode you should can run
Code:
adb devices
adb pull <LOCATION_OF_DATA_OF_INTEREST> <STORAGE_LOCATION_ON_PC>
Click to expand...
Click to collapse
unfortunately the result of this operation is always "pull: building file list... 0 files pulled. 0 files skipped". I tried already to pull form /sdcard, /storage, /data. Am I getting the location wrong?
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
Due to the security implications of remotely enabling USB Debugging, the only way to enable it is through Developer Options. You can try rebooting to recovery and clearing cache although I am doubtful as to how much that might help you. If your device took a swim, you're going to be looking at repair, which will most likely result in wiping your data.
V0latyle said:
Due to the security implications of remotely enabling USB Debugging, the only way to enable it is through Developer Options. You can try rebooting to recovery and clearing cache although I am doubtful as to how much that might help you. If your device took a swim, you're going to be looking at repair, which will most likely result in wiping your data.
Click to expand...
Click to collapse
Do you know if changing the screen could solve the problem? Or do you think there's a way to copy data 1:1 on another device (such as a used mi 9t I could buy)?
Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
How long ago was it dropped in water, have you allowed it thoroughly dry out? Can you open the body of the device to allow it to dry?
Droidriven said:
How long ago was it dropped in water, have you allowed it thoroughly dry out? Can you open the body of the device to allow it to dry?
Click to expand...
Click to collapse
It stayed in the water for few seconds, the bottom half of it. I shut it down and I let it dry for 2 days, after removing the battery. Anyway I brought it to a center that made a treatment for electronic contacts, an they said that it's needed to change the display first, then run some tests to see what else is wrong. The problem is that changing the screen costs 130€ and, in my opinion, won't solve the issue.
Dona2592 said:
It stayed in the water for few seconds, the bottom half of it. I shut it down and I let it dry for 2 days, after removing the battery. Anyway I brought it to a center that made a treatment for electronic contacts, an they said that it's needed to change the display first, then run some tests to see what else is wrong. The problem is that changing the screen costs 130€ and, in my opinion, won't solve the issue.
Click to expand...
Click to collapse
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Droidriven said:
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Click to expand...
Click to collapse
Droidriven said:
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Click to expand...
Click to collapse
The procedure looks good, I'd give it a try but is there any alternative to the SD card? Cause my phone has no SD slot available. Maybe an external usb card reader to plug into the phone?
Droidriven said:
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Click to expand...
Click to collapse
Plus, I don't really get why the system fails right after the lockscreen, I'm actually able to enter the code and the phone unlocks but the launcher seems not working, while the notifications bar works fine, and after some seconds the phone reboots. How can the system work fine in some aspects and bad in others at the same time? Can it be some flash memory issue?
Dona2592 said:
The procedure looks good, I'd give it a try but is there any alternative to the SD card? Cause my phone has no SD slot available. Maybe an external usb card reader to plug into the phone?
Click to expand...
Click to collapse
Yes USB should work in place of sdcard
Dona2592 said:
Plus, I don't really get why the system fails right after the lockscreen, I'm actually able to enter the code and the phone unlocks but the launcher seems not working, while the notifications bar works fine, and after some seconds the phone reboots. How can the system work fine in some aspects and bad in others at the same time? Can it be some flash memory issue?
Click to expand...
Click to collapse
That or kernel panic due to some other important hardware is damaged.
Maybe you can use a adb script to interrupt the running processes right after the device unlocks. Something to stop everything from loading beyond screen unlock. It might allow you to use adb to pull whatever you want from the device via adb pull commands.
Or, if there is a custom recovery for your device and if your bootloader is already unlocked(if it isn', don't unlock it, it will wipe your data), you can install the custom recovery and use it to create a backup of your data then extract your data from the backup.
Droidriven said:
That or kernel panic due to some other important hardware is damaged.
Maybe you can use a adb script to interrupt the running processes right after the device unlocks. Something to stop everything from loading beyond screen unlock. It might allow you to use adb to pull whatever you want from the device via adb pull commands.
Or, if there is a custom recovery for your device and if your bootloader is already unlocked(if it isn', don't unlock it, it will wipe your data), you can install the custom recovery and use it to create a backup of your data then extract your data from the backup.
Click to expand...
Click to collapse
Unfortunately I still have the stock recovery. Plus USB debug is deactivated. What really boggles me is the fact that I can still enter settings and get to developer options, turn ON the toggle of USB debug, but it's like the phone doesn't save the setting, cause if I go back to the main setting screen and enter again developer options, USB debug is OFF. I mean, what the hell?
Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot
Dona2592 said:
Unfortunately I still have the stock recovery. Plus USB debug is deactivated. What really boggles me is the fact that I can still enter settings and get to developer options, turn ON the toggle of USB debug, but it's like the phone doesn't save the setting, cause if I go back to the main setting screen and enter again developer options, USB debug is OFF. I mean, what the hell?
Click to expand...
Click to collapse
Hardware damaged. You're going to have to repair the hardware or forget about retrieving your data, unless you can find a reputable shop that has the equipment and experience to pull your data directly from the chip itself.
xXx yYy said:
Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot
Click to expand...
Click to collapse
Thanks mate, I'll give it a try for sure
Droidriven said:
Hardware damaged. You're going to have to repair the hardware or forget about retrieving your data, unless you can find a reputable shop that has the equipment and experience to pull your data directly from the chip itself.
Click to expand...
Click to collapse
Ok, but do you know what could be the damaged piece of hardware?
Dona2592 said:
Ok, but do you know what could be the damaged piece of hardware?
Click to expand...
Click to collapse
NO
xXx yYy said:
Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot
Click to expand...
Click to collapse
That might work but I've never had any luck with adb in stock recovery, not on the devices that I've owned, at least.
Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
Is your bootloader locked?
Droidriven said:
That might work but I've never had any luck with adb in stock recovery, not on the devices that I've owned, at least.
Click to expand...
Click to collapse
Yeah in fact when I type "adb shell" it gives me error, but I can enter fastboot mode and the phone is seen. Unfortunately I can't do much from there
Arealhooman said:
Is your bootloader locked?
Click to expand...
Click to collapse
Yeah. **** me, for once I kept everything stock and this happened . I've always rooted and customized my phones and nothing like this has ever happened.