Every time I download a file onto my tfp I can't see it via usb nor via dlna for hours. I can see the files on my tfp with 'File Manager' but if I plug my tfp into my PC, all recently downloaded files are invisable. Same issue for files via dlna. Initially thought my dlna apps had a floor until I tried to transfer a file via usb and I was like "Where is it"? I can transfer the file wirelessly with 'ES File Explorer' but it is painfully slow.
Same thing happened to me recently too. Only showed the DCIM folder via USB. After a reboot (tablet), the other directories slowly came back and then the files, but it seemed like it was struggling forever.
I finally had access after 1.5 hours and 2 reboots.
Does Android use an indexing service to maintain its listing of files?
If this were the case, maybe a new index is created for newly downloaded files and it is migrated with the master index via a process. In my case, maybe the process isn't working correctly but a reboot will cause it to restart?
Not sure if this is related to the problem but I frequently receive a popup advising "Unfortunately. Asus task manager has stopped".
Just discovered something. I can access all new files via dlna with 'My Net' running but when I use a couple of dlna apps from the market (Imediashare and Skifta), the new files are invisible.
I've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.
Hi everyone, I got my watch 2 days ago and rooted it in the first two hours and since then keept trying different android apps on the watch and since then I managed to find a way to sideload apps without a computer and I am sharing it with you.
Note: This guide assumes you have your watch connected to your phone, your phone connected to the internet, a computer around and adb installed on the computer and some abilities of using adb commands to pull files and installing apk's and some basic linux commands like "cd".
Note 2: Links to the apps are in the 2nd post.
Note 3: List of working apps and tips in 2nd post.
Note 4: Guide to using adb from the phone and connecting the watch to a new device without a format in the 3rd post.
Here are the steps:
Install ASTRO Bluetooth Module on the phone.
Install Bluetooth file transfer on the phone.
Connect the phone to the computer and pull the ASTRO Bluetooth Module apk file from data/app.
Connect the watch to the computer (adb over bluetooth or over USB) and sideload the ASTRO Bluetooth Module you just pulled from your phone.
Open the ASTRO Bluetooth Module app on your watch and tic the OBEX FTP SERVER option.
Open the Bluetooth file transfer app on your phone and switch to the Bloueooth tab (the one with the blue Bluetooth sign).
You will see your G Watch in the Cache list, click on it.
On the list that will open click on "File Transfer Profile (FTP)" and wait for it to connect.
Now the contents of the /sdcard folder of the watch should be shown on the Bluetooth tab.
To send a file switch back to your other tab and long-press on the file you want to send and click upload.
To receive a file from your watch go to the Bluetooth tab and long-press the file you want and click Download.
In the bluetooth tab you can also fully manage your sdcard folder from your watch so you can delete, move and copy any file or folder on your watch,
Enjoy.
Also in case you want to sideload apps to your watch you first need to send them using the method above and then do this:
Install terminal Emulator on your phone and sideload it to your watch the same way you did with ASTRO Bluetooth Module above.
Sideload Minuun keyboard for wear or an other keyboard if you think you can use it.
Optional, usefull only if you have root: Install ES File Explorer on your phone and sideload it to your watch.
To install apps open Terminal Emulator on your watch and go to the folder your apk file is in using the "cd" command and then do: "pm install <appname>.apk" changing <appname> to the name of your apk file.
If you choose to install ES File Explorer you can do that much easyer by enabling root acces in it and the option to automatically install and uninstall apps.
And if you want to uninstall apps directly from your watch do this:
Open Terminal Emulator.
Issue the command: "pm list packages -3" and find the package name of the app you want to uninstall
Issue the command: "pm uninstall <packagenamehere>" replacing <packagenamehere> with the package name of the app you want to uninstall.
NOTE: Uninstalling apps using ES File Explorer does unfortunately not work because it asks if you want to uninstall the app and the buttons are not on the screen so you can't click on the "Yes" option.
Done.
Here you go guys, have fun, hope this helps someone else as much as it does help me, will also try to find a way to connect the watch to the adb daemon on the phone via bluetooth and if I manage to do that I will surely post a guide.
Resources:
Astro Bluetooth Module: https://play.google.com/store/apps/details?id=com.metago.astro.network.bluetooth
Bluetooth File Transfer: https://play.google.com/store/apps/details?id=it.medieval.blueftp
Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm
ES File Explorer: https://play.google.com/store/apps/details?id=com.estrongs.android.pop
List of working apps:
-All the ones that the above post tells you to sideload to the watch
-The apps in this thread: http://forum.xda-developers.com/android-wear/general/list-sideloaded-android-wear-apps-t2908106
-MiXplorer-better as a file explorer in my opinion because of the list view, does not have music player and text editor so you still need ES File Explorer for that, also crashes when you exit-link: http://forum.xda-developers.com/showthread.php?t=1523691
Tips:
-If an app you want to sideload uses holo theme it will most probably not work, I think wear has holo removed
Thanks to:
@EpicLPer for creating that thread of sideloaded working apps.
Someone managed to execute adb commands from the phone to the watch, look here:
http://forum.xda-developers.com/android-wear/development/adb-smartphone-to-android-wear-t2987568
Also on this thread someone managed to connect the watch to a different phone without a factory reset on an older android wear version:
http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962
But it's not that easy anymore, that you now need to do is:
First execute the (adb shell "pm clear com.google.android.gms && reboot") command
And then after the reboot execute the (adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE) command to be able to connect your phone
I have also made shell scripts to do that directly on the watch using terminal emulator and will upload them soon.
Great stuff sir!
crazyeats said:
Great stuff sir!
Click to expand...
Click to collapse
Glad you enjoy it, have now added a list of working apps and tips in the 2nd post, if you test other apps and they work please post them and I will add them.
Solid! Thanks
Great any update then?
johnvuong1999 said:
Great any update then?
Click to expand...
Click to collapse
Sorry I was without a PC for a week and didn't see your message, updates on what are you asking about?
If you are asking about more apps I didn't really get more apps working (android wear is just missing too many things), only some video players but they break the app "Wear Mini Launcher" for some reason, and if you are asking about using adb via bluetooth to debug the watch from the phone that's also something I didn't get working and I did try all the ideas I had.
Root required?
owais113 said:
Root required?
Click to expand...
Click to collapse
If you would have read the whole post you would have seen that it only needs root to install apps using ES File Explorer but unfortunately after the 5.1 update the "pm install" command doesn't seem to work anymore (with or without root) it just gives a "FAILED_INVALID_URI" error.
Other news is that someone on the wear general forum actually managed to run adb over bluetooth so you can now install apps from your phone directly using adb instead (but it does require root on your phone) I will post the link in the 3rd post soon.
Ranomez said:
If you would have read the whole post you would have seen that it only needs root to install apps using ES File Explorer but unfortunately after the 5.1 update the "pm install" command doesn't seem to work anymore (with or without root) it just gives a "FAILED_INVALID_URI" error.
Other news is that someone on the wear general forum actually managed to run adb over bluetooth so you can now install apps from your phone directly using adb instead (but it does require root on your phone) I will post the link in the 3rd post soon.
Click to expand...
Click to collapse
But does the watch need to be rooted or you only need a rooted phone.
owais113 said:
But does the watch need to be rooted or you only need a rooted phone.
Click to expand...
Click to collapse
Do you need root on your watch to execute the "adb install" command command from the PC?
After fighting with this for nearly a month and reading dozens of threads on xda, stack-overflow, etc... I finally figured out this issue, so I'm putting it here in hopes it saves someone else the frustration.
The issue presented itself on my HTC One (M8) running the ViperOne 6.1.0 ROM.
I'm putting this thread in the general section though since I've seen many people with very similar, if not the same issues on a wide variety of devices.
I believe the root cause of my particular issue may be the way HTC sets their devices to simply allow all debugging without authorization if the phones are s-off.
Mine is still s-on, but I have another M8 that's s-off with the exact same ROM as well as an s-off M9, and both of them go straight into debugging, no questions asked, no prompt.
I'm wondering if maybe the ROM was developed using a developer version of the phone and is just missing the prompt, or something similar, but this is just conjecture.
The basic problem was that, when I tried to connect ADB, it showed the phone as "unauthorized" and no matter what I did, the prompt would not come up on the phone to allow debugging.
Also of note, I was missing the "Revoke USB debugging authorizations" menu item entirely (I could search for it, but it wasn't actually there in the menu)
I tried many different combinations of changing drivers, USB modes, enabling/disabling debugging, different machines, deleting the public and private keys for ADB on the computer, etc... all to no avail.
Finally, after much research and testing, I found this comment on stack-overflow and figured out how to manually authorize keys.
Note: This will require root, a custom recovery, or some way of writing the the system partition (I used TWRP at first, then TerminalEmulator later)
The key was to understand what clicking the dialog to 'always allow' a machine actually does.
When you click to always allow, android appends the public key from ADB on the computer into a specific file on the phone.
Since my phone wouldn't connect in the first place though, I didn't have that file or understand the format, etc...
The file is called adb_keys, it is a file (not folder) which is located at: /data/misc/adb/
The format of this file is one public key per line.
Thus, there are a couple of ways to go about manually authorizing a machine for debugging.
First, manually building the adb_keys file. (This is what I did at first)
Second, copying an existing adb_keys file from another device (Which doesn't need root)
For manually building the adb_keys file, the first step is to find the public key on the computer.
For me (Windows 10) it was located at C:\Users\<my profile>\.android\adbkey.pub
For Linux and OSX, I believe it is at: ~/.android/adbkey.pub
If you only need to authorize one computer:
Simply copy the adbkey.pub onto the device location: /data/misc/adb/ and rename it from adbkey.pub to adb_keys
chmod 0644 and then reboot.
Now, the phone should accept debugging from the computer just as though you clicked the dialog.
If you need to authorize several computers...
As mentioned, the /data/misc/adb/adb_keys file is actually a list of all the keys which have debugging permissions, one key per line.
First, collect the adbkey.pub files from each computer you want to authorize.
Then, using a text editor which supports linux style line breaks (Notepad++ if on windows) simply create your own adb_keys file by appending the contents of each adbkey.pub file, putting a line break between each key
Now save the adb_keys file you just created, and put it on the phone's /data/misc/adb/ folder using whatever method you prefer, and chmod 0644
If you need to revoke debugging permissions, (like the menu option, if the menu option is missing)
Simply delete /data/misc/adb/adb_keys
And finally,
If you have access to another device (does not have to be rooted) and want to replicate its debugging permissions
Plug the 'donor' device into the computer first, then issue:
adb pull /data/misc/adb/adb_keys c:\temp\adb_keys
(Or replace "C:\temp\adb_keys" with whatever file path works for you)
Then, copy the file to the 'target' device in the same location (/data/misc/adb/adb_keys) and chmod 0644
I've tested all of these methods and they worked well.
In the end, I used the last method since my tablet had all the debugging permissions I wanted on my phone.
Thanks,I have the same issue with the same rom. I tried your solution and it worked.
Hi, I ran into this issue with my Moto G5 plus. The only difference is that I'm not missing the Revoke Auth option, even though using it does nothing for me, and I still fail to get the Authorization popup when connecting via USB/using ADB.
I tried the above method of copying the adbkey.pub file to my device directory, renaming, etc. I am doing something wrong and would like a hint.
I copied the adb_keys via Windows Explorer to my devices root directory. There was a /data/ directory, but only Titanium Backup had a subdirectory within, so I created .../misc/adb/, and placed the adb_keys file there.
I rebooted to the TWRP recovery Terminal, and navigated to the /data/misc/adb directory. I ran chmod, and the system could not find the file specified. Listing directory contents also showed the directory to be empty (yet when viewed in Explorer or LineageOS, it's visible).
Did I place the keys file in the wrong place?
Copying via windows explorer does not place it in the device root.
Inception
I was trying to Copy one donor device's Adb key file to my broken android phone to mirror it on my PC, Following the guide of another post, and somehow i stumbled across this post, after failing to copy from Donor device. Now i managed to copy the adb_key from Donor device but LOL my broken Android device is Unauthorized. What should i do? IS THERE ANY SOLUTION?
misuvi said:
I was trying to Copy one donor device's Adb key file to my broken android phone to mirror it on my PC, Following the guide of another post, and somehow i stumbled across this post, after failing to copy from Donor device. Now i managed to copy the adb_key from Donor device but LOL my broken Android device is Unauthorized. What should i do? IS THERE ANY SOLUTION?
Click to expand...
Click to collapse
Do you have any way of writing to the /data/misc/adb/adb_keys file on the broken device?
I think i just did!
NFSP G35 said:
Do you have any way of writing to the /data/misc/adb/adb_keys file on the broken device?
Click to expand...
Click to collapse
I rebooted into recovery mode, copied, but still the mirroring application is not working, still prompting for allowing USB debugging. Now i connected the donor device on That mirroring application and Saved the RSA of Mirroring application, and going once again. Wish me good luck
misuvi said:
I rebooted into recovery mode, copied, but still the mirroring application is not working, still prompting for allowing USB debugging. Now i connected the donor device on That mirroring application and Saved the RSA of Mirroring application, and going once again. Wish me good luck
Click to expand...
Click to collapse
Well, don't forget to post back if it worked :good:
Guess I did i good job
NFSP G35 said:
Well, don't forget to post back if it worked :good:
Click to expand...
Click to collapse
Well it didn't work since the Adb server of Cmd and mirroring application were different, so i searched for another application which has same server as Cmd, and luckily i found a great software by Genymobile, named scrcpy, from github, just one click on scrcpy-noconsole and boom? Thanks for all the help.
misuvi said:
Well it didn't work since the Adb server of Cmd and mirroring application were different, so i searched for another application which has same server as Cmd, and luckily i found a great software by Genymobile, named scrcpy, from github, just one click on scrcpy-noconsole and boom Thanks for all the help.
Click to expand...
Click to collapse
Cool, glad to help.
For a while, I looked for ways to get around this from a different angle (for example, making the keys match on the ADB server side) but I ran into some issues and ended up getting what I needed via the steps in the OP.
Glad you got it working though!
"And finally,"...you should have led with that
I cannot thank you enough! Other proposed solutions to this hellish problem made my head hurt. This was beautifully simple - copy file from the working device onto non-working, change permissions and BOOM! It works.
Thanks again, you're awesome!
Happy to help!
Oh my god, it's not a folder! Thank you so much! I was about to give up, this was driving me totally crazy. Everywhere on the internet they just keep repeating the same advice that did nothing, I actually created that as a folder and no wonder it wasn't working.
I still can't believe it's working now, ahhh...
can't believe in my eyes. work perfect for me. thanks you so much!!
I am trying to use the 'copy keys file from another device' method.
I've copied the adb_keys file to my PC.
Now, how do I copy that file from the PC to the data folder?
adb won't allow it as it's not authorised, what am I missing?
Thank you in advance for your help!
Bungle2000 said:
I am trying to use the 'copy keys file from another device' method.
I've copied the adb_keys file to my PC.
Now, how do I copy that file from the PC to the data folder?
adb won't allow it as it's not authorised, what am I missing?
Thank you in advance for your help!
Click to expand...
Click to collapse
You can't copy to the device through ADB until you get ADB authorized... that's the whole point... you have to use some other method to get the file there.
I used TWRP custom recovery to copy the file from an external SD card the folder.
If you don't have an external SD card, use USB MTP/PTP, Mass Storage, a USB OTG adapter and thumb drive... if you desperate, zip the file and email it to yourself... pretty much endless methods of actually getting the file onto the phone somehow.
But you'll need root (or a custom recovery) to copy the file from wherever it is on the device to the correct location (/data/misc/adb/adb_keys)
You could potentially use several methods, for example you could use terminal emulator or a root file explorer to get the file to the correct folder.
NFSP G35 said:
You can't copy to the device through ADB until you get ADB authorized... that's the whole point... you have to use some other method to get the file there.
I used TWRP custom recovery to copy the file from an external SD card the folder.
If you don't have an external SD card, use USB MTP/PTP, Mass Storage, a USB OTG adapter and thumb drive... if you desperate, zip the file and email it to yourself... pretty much endless methods of actually getting the file onto the phone somehow.
But you'll need root (or a custom recovery) to copy the file from wherever it is on the device to the correct location (/data/misc/adb/adb_keys)
You could potentially use several methods, for example you could use terminal emulator or a root file explorer to get the file to the correct folder.
Click to expand...
Click to collapse
Hey NFSP G35, thank you for the reply!
I figured there was something I was missing, I just don't know the steps to do it right.
I have a Moto X Play that has a broken screen, so no display, and does not accept touch input.
It powers on and is working as it was before the screen broke as far as I can tell, so I'm trying to connect it up to the PC to get all the data off it.
However, before it broke, something happened with the software that meant Google Play disappeared.
The device is stock Motorola device, so not rooted, no TWRP etc. USB debugging is enabled but not authorised.
What would you recommend is the best way to get the adb_keys onto the phone given the issues above?
Your help is greatly appreciated!
Sorry, given your circumstances, it's likely impossible or very difficult
?? Thanks, it worked perfectly on Samsung J6 run Evolution X 4.0
Thank you it's working