Hi,
My screen got crack diagonally and touch is not working at all. Is there a way to back up the device?
Worst part : It's in airplane mode and security pattern enabled.
With lock, i could not connect to adb shell and airplane mode not connected to net.
Any suggestions?
KashRaman said:
Hi,
My screen got crack diagonally and touch is not working at all. Is there a way to back up the device?
Worst part : It's in airplane mode and security pattern enabled.
With lock, i could not connect to adb shell and airplane mode not connected to net.
Any suggestions?
Click to expand...
Click to collapse
Oh, I had this problem before. You can connect a mouse to your phone, and use that to control your phone. Just buy a micro usb to usb cable adapter, and connect a usb mouse to it.
http://www.ebay.com/itm/90-Degree-M...TG-Adapter-Cable-Android-Tablet-/301639994675
Mehhish said:
Oh, I had this problem before. You can connect a mouse to your phone, and use that to control your phone. Just buy a micro usb to usb cable adapter, and connect a usb mouse to it.
http://www.ebay.com/itm/90-Degree-M...TG-Adapter-Cable-Android-Tablet-/301639994675
Click to expand...
Click to collapse
Does your phone has been rooted?
If yes, adb shell into your phone as root and dump out all the partiotions on the phone on your SD card and then finally pull them out.
All the partitons can be seen with "ls -l /dev/block/bootdevice/by-name".
If your phone has not been rooted then try to have the SuperU boot.img and boot with to gain root privillege and dump all the partitions out as describe above. ( ATTENTION, I said BOOT with and NOT FLASH it)
Good luck
Cheer.
I was able to reboot in recovery by using key combo and clear the security key thru adb. With that, I have taken backup using titanium backup thru VNC client
Hello guys, a friend of mine and I are trying to recover data from his S6 that has a broken screen and digitizer. Phone is recognized by Windows PC, but can't interact with it, since it has no USB debugging enabled. Is there any way to pull data from it? Repair is not an option, as friend is looking for an upgrade (S8 most likely).
Obviously, when connected to PC phone probably prompts for a type of connection, but as the situation states - I can't select anything, since screen is dead.
Any help?
voolandis said:
Hello guys, a friend of mine and I are trying to recover data from his S6 that has a broken screen and digitizer. Phone is recognized by Windows PC, but can't interact with it, since it has no USB debugging enabled. Is there any way to pull data from it? Repair is not an option, as friend is looking for an upgrade (S8 most likely).
Obviously, when connected to PC phone probably prompts for a type of connection, but as the situation states - I can't select anything, since screen is dead.
Any help?
Click to expand...
Click to collapse
Well using adb commands is out of the question as usb debugging is not enabled. You might get somewhere by connecting a usb mouse or keyboard via otg.
voolandis said:
Hello guys, a friend of mine and I are trying to recover data from his S6 that has a broken screen and digitizer. Phone is recognized by Windows PC, but can't interact with it, since it has no USB debugging enabled. Is there any way to pull data from it? Repair is not an option, as friend is looking for an upgrade (S8 most likely).
Obviously, when connected to PC phone probably prompts for a type of connection, but as the situation states - I can't select anything, since screen is dead.
Any help?
Click to expand...
Click to collapse
Try rebooting your device into recovery, hook your phone upto your computer, and execute these commands in your terminal:
Code:
cd ~/.android && adb push adbkey.pub /data/misc/adb/adb_keys
adb reboot
Wait for a while to let it boot, and execute
Code:
adb pull /sdcard/
If you didn't have USB debugging turned on, you can execute these commands after connecting your phone in recovery to your PC:
Code:
adb shell
cd /system/
echo "persist.service.adb.enable=1" >> build.prop
echo "persist.service.debuggable=1" >> build.prop
echo "persist.sys.usb.config=mtp,adb" >> build.prop
adb reboot
hope it works
LukeHammer said:
hey, buddy, I had the same problem with you last month, but I solve, I got the help from this post (recover data from broken Samsung screen), now I hope that can help you.:highfive:
Click to expand...
Click to collapse
Many thanks, but this thread is over a year and a half old.
voolandis said:
Many thanks, but this thread is over a year and a half old.
Click to expand...
Click to collapse
But you keep the link.
heidisteen said:
https://youtu.be/dnpTiYnp2A8
Click to expand...
Click to collapse
Does this helpful with my broken S5 ACTIVE?
Hi!
Help me please, beause i can't unlock my tablet. I forgot the password, but it's the smallest problem. I go to "Android system recovery<3e>" mode, but in there i can't choose the "wipe data/factory reset" option because the tablet don't have volume button, just a power and a home button. I tried select this option with an OTG cabel+keyboard, but nothing happends.
Do you have any idea?
Thanks.
-Sorry for my english-
there are couple of videos on youtube showing how to reset a device without volume button
ineedroot69 said:
there are couple of videos on youtube showing how to reset a device without volume button
Click to expand...
Click to collapse
that' true, but my problem is not only the missing volume button. The OTG cabel + keyboard combination neither working.
@bentudlik
If you can establish an ADB connection - requires USB debugging got enabled on the phone - there is NO need to use the in-built recovery menu to wipe phone's user-data / do a factory-reset: this all can be done by means of ADB, too. But would require you've some knowledge about ADB and know how use its commands properly.
jwoegerbauer said:
@bentudlik
If you can establish an ADB connection - requires USB debugging got enabled on the phone - there is NO need to use the in-built recovery menu to wipe phone's user-data / do a factory-reset: this all can be done by means of ADB, too. But would require you've some knowledge about ADB and know how use its commands properly.
Click to expand...
Click to collapse
would be terrible if you do erase command on /userdata and can't recreate it i experience that and its stuck on boot logo not bootloop
jwoegerbauer said:
@bentudlik
If you can establish an ADB connection - requires USB debugging got enabled on the phone - there is NO need to use the in-built recovery menu to wipe phone's user-data / do a factory-reset: this all can be done by means of ADB, too. But would require you've some knowledge about ADB and know how use its commands properly.
Click to expand...
Click to collapse
Do you have any idea, how to enable USB debugging while my tablet is locked? Because now my laptop can't recognize this device.
I know ADB should be a right method, but firt i have to connect the tablet to laptop somehow.
bentudlik said:
Do you have any idea, how to enable USB debugging while my tablet is locked? Because now my laptop can't recognize this device.
I know ADB should be a right method, but firt i have to connect the tablet to laptop somehow.
Click to expand...
Click to collapse
Enabling USB Debug on an Android phone always should be the 1st action an user should do when he/she puts a phone into operation. On Android-side ADB gets started when Android boots up. So by means of ADB you would be able to bypass / remove FRP-lock etc,pp.
jwoegerbauer said:
Enabling USB Debug on an Android phone always should be the 1st action an user should do when he/she puts a phone into operation.
Click to expand...
Click to collapse
That's true. It's not my device, i just try the solve the problem. I thought it could be fixed with simple solutions., but my steps not work ...
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.