Since the update I can no longer access my M510 via explorer.
Scratch that, sorted it.
Related
Rather than using Root Explorer, I would like to have full root access to the file system via USB, so I can do my file management through the PC.
Is this possible?
You could try Droid Explorer, I haven't been able to yet since it started giving me low memory errors on startup, but it might work for the Atrix.
Ideally, I would want to use my own file manager. I guess that's not really a viable choice at the moment, I take it?
is there a way to do this without a pc, I have a backup, and I lost the usb cable, and the one from my g2x, doesnt seem to work
so the phone charges, but the pc cant "see" it for some reason
anyway to manually root this device?
Download the files in untermesch thread on modyifing 3e recovery do it through root explorer
Sent from my SGH-T959 using XDA Premium App
That was my first time, but door explorer doesn't allow the movement of system files with root control, ie r/wpa_supplicant doesn't work
appreciate the help though
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.
Problem: I wanted to find an easy way to transfer files back and forth to my G watch and I could not find a way to connect as a MTP device in Windows or in TWRP. Although ADB push/pull commands are easy enough, it is a bit cumbersome when copying over a bunch of songs. Also copying and moving files on ES file explorer is a bit tedious.
After trying a bunch of things out, I found a solution that may help others.
Solution: Android Commander, a windows(GUI) based ADB file explorer.
http://forum.xda-developers.com/showthread.php?t=622390
The dev's website is down, but you can find the download on the facebook page:
https://www.facebook.com/androidcommander/timeline?ref=page_internal
Bluetooth connection not an option?
I installed ADB and fastboot from http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 and Bloater from http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294.
I have one KFHD6 that got the OTA 4.5.4 update prior to anything else. This one connects to my PC just fine and ADB works. It's the device I used to install PDANet, which helped me get the computer to recognize the Kindle in ADB.
I took another KFHD6 out of the box today (on 4.5.3), ADB was enabled by default, I did not setup Wi-Fi so I could keep 4.5.3. When I connect it to my PC, I get the Autoplay popup on my computer, but ADB does not connect. There's no prompt to trust the computer. I've tried the same cable. I've tried turning ADB off and back on. I've rebooted my devices.
I did notice that the Autoplay icon is different for the two Kindles. The 4.5.4 looks like a phone ( http://www.groovypost.com/wp-content/uploads/2012/09/Open-Device-to-View-Files-AutoPlay.png ). The 4.5.3 looks like a tablet like the icon here ( http://cnet1.cbsistatic.com/hub/i/r.../066e9701a8d91559092f149bd6b32516/drivers.jpg )
Does anyone have any suggestions? Thanks!
I figured it out. I don't have PDANet installed on the 2nd Kindle. Can someone tell me the path in the Silk Browser to execute the apk? For example,
file:///Download/PdaNet.apk
But that's not it. I don't have Internet on the Kindle yet, because I don't want OTA updates, so I can't install ES Explorer from the Store. I just need to be able to execute the APK file that I transferred to the Kindle via the USB cable. Thanks!
I figured THAT out. But Silk is not executing the file. It states that it has to download it and that it can be found in Downloads, but then the screen goes black and nothing happens. I hit home to get out of Silk, go back in and it's still black. If I reboot, and then open Silk, it asks if I want to restore my tabs. Yes, gives a black screen. No puts me back at the Silk browser again. The file doesn't show up in the Downloads section of Silk, so I'm unable to execute it. Surely there's a way to install APK files without ES Explorer (I'd actually like to install ES Explorer, but without Internet access).
Which came first--the chicken or the egg? Please help. Thanks!
I have yet to figure this out. I have several KFHD6's. The first one was a breeze to get ADB working. The second one had trouble, but it finally started working when I uninstalled the driver from the Device Manager and the ADB Driver installed. I have 3 more new Kindles which don't want to get on the ADB bus. Does anyone have any suggestions? Here's what I've done:
Installed Minimal ADB and Fastboot (http://forum.xda-developers.com/showthread.php?t=2317790)
Installed PdaNet (http://pdanet.co/)
Installed Android SDK (http://dl.google.com/android/installer_r24.3.3-windows.exe)
Updated an inf file and tried to update the driver (http://www.jayceooi.com/how-to-install-kindle-fire-adb-usb-driver/)
The first worked after the first 2 bullets. The second worked after the first 3 bullets and then uninstalling the driver in the Device Manager. Any input would be greatly appreciated.
Here's the solution if anyone has this problem:
Plug in the new device. Let it install the driver in Device Manager. Right-click --> Properties on it. Uninstall device and unplug it. Reboot your PC and you Kindle. Plug your Kindle back in.
It was that easy for me--on 2 new devices. The 3rd was literally plug-and-play. Very weird.