Hey guys I am trying to use droid explorer and every time I launch it it connects but then crashes. I am using JH3 with SRE 1.2.1a and ext4 lagfix please help!
I have it working fine .. but it doesn't show ALL the folder contents like Root Explorer would..
make sure it's running as Administrator and you're on debugging mode
darkamikaze said:
I have it working fine .. but it doesn't show ALL the folder contents like Root Explorer would..
make sure it's running as Administrator and you're on debugging mode
Click to expand...
Click to collapse
I have it running and i can see all my files, but i can't change perms on them. Had to launch its console do it old school style with chmod and chown and all that good stuff.
Sounds about right.. I just use it to side load tbh lol dint think its optimized for captivate or something
Sent from xdaApp - Captivate
I gave up on trying to use another program to manage the Captivate. It's just so much easier to use the adb shell.
Think u also need the latest version of busybox installed on ur phone.
Sent from my SAMSUNG-SGH-I897 using XDA App
I also can not get the Captivate to work with Droid Explorer.
I have BusyBox 1.16.1 from the SuperUser.apk.
tubaboy26 said:
Hey guys I am trying to use droid explorer and every time I launch it it connects but then crashes. I am using JH3 with SRE 1.2.1a and ext4 lagfix please help!
Click to expand...
Click to collapse
Can you mount the phone?
If you can't get any type of communication from the phone to your pc it may be a driver issue.
Don't give up..
i have same problem my computer reads and I can see my device and files inside, but I'm not able to write,move, or delete.
tubaboy26 said:
Hey guys I am trying to use droid explorer and every time I launch it it connects but then crashes. I am using JH3 with SRE 1.2.1a and ext4 lagfix please help!
Click to expand...
Click to collapse
exact same problem with me.....same set up i believe too
i just got sideload wonder machine and said screw it until further notice.
Droid explorer isn't working since I updated to Cognition 2.2 beta 7. It is unable to find the device. I have the device in debugging mode and Kies will recognize it (but I don't have Kies open while trying to use Droid Explorer). It worked fine with 2.1
Has anyone else experienced this since updating?
I gave up on Droid Explorer to modify folders and add files.
But all you need to do is go back into your Settings>Applications>Development *uncheck debug.
Then replug into computer, and in the dropdown notification area, pull it down and tap on the USB connect. Then your PC will read it like a mass storage device again.
Related
ROOTING:
Since z4root, one of the easiest ways to root, is not working on Froyo in Galaxy 3, I decided to make this separate thread for instructions on how to root Froyo using Superoneclick.
First and foremost: Enable USB Debugging by going to Settings>Applications>Development. Make sure it is ticked.
Download the attached Superoneclickv1.5.zip file. Extract its contents. Make sure your phone drivers are installed on the computer (Samsung Kies). Then follow the steps:
1. From the extracted contents, run the file named Superoneclick.
2. Turn off your phone, then connect it to the computer using the USB Cable. Don't turn on the phone. Keep it off but connected to the computer.
3. In Superoneclick, click on the 'Root' button. After a few seconds, it'll say 'Waiting for device'.
4. Now turn on your phone (while it is still connected to the computer). Superoneclick will detect the phone.
5. Now the phone will be rooted, while it is starting up. When it is started, it'll be rooted.
6. After rooting, download and install busybox on your phone. It should take care of any slowing down of your phone after rooting.
That's it. The phone is now rooted, although it would be so much better if z4root worked on Froyo..
For those getting stuck at the 'pushing raceagainstthecage' step, try this method. Credits go to haree:
1. login as admin and then open the application. Or right click on Superoneclick.exe and click on 'Run as administrator'.
2. turn off ur Virus protection
3. remove all the additional external USB devices(this seems to confuse the SW)
i removed all the above mentioned
and then follow the instructions u will be successful
it worked for me now i have 2.2 and rooted
Click to expand...
Click to collapse
UNROOTING INSTRUCTIONS:
Unfortunately, the method to unroot by clicking on the Unroot button in Superoneclick does not work. So follow the following steps to unroot.
1. Download rootexplorer.apk (attached) and install Root Explorer on phone.
2. Run Root Explorer. A 'Superuser Request' prompt will come up. Press Allow.
3. Now, on the top, there will be a button saying 'Mount R/W'. Press it. It should change to 'Mount R/O'. The button should say 'Mount R/O' in order for you to be able to do anything in the following steps.
4. Now scroll to the bottom, click on system. Then click on bin.
5. In the bin folder, look for a file named 'su'. Long press on this file, and select Delete to delete it.
6. Now go back to the system folder by pressing the Back button once.
7. Now enter the app folder. Scroll down and look for the file named 'superuser.apk'. Long press on this file and delete it.
8. Exit Root Explorer after this. Uninstall it if you don't want to use it.
9. That's it. Your phone will be un-rooted.
Another method to unroot:
1. Download and install Terminal Emulator (attached).
2. Run Terminal Emulator on the phone. If you don't see a keyboard to type, press Menu and press Toggle Soft Keyboard.
3. Type su and press enter. Press Allow on the 'Superuser Request' prompt. The $ sign will change to a #.
4. Now type the following line exactly as it is and press enter: mount -o rw,remount /dev/block/mtdblock3 /system
5. Nothing will happen visually. The pointer will shift to a new line.
6. Now type the following line and press enter: rm /system/bin/su
7. Again, type following line and press enter: rm /system/app/superuser.apk.
8. Now exit Terminal Emulator. Your phone is un-rooted.
Hehe, first i thought it makes no sense to write a howto on this since its described in the SOC thread anyway, but man the idea to do it during boot is ubercool, didn't think of that...
FadeFx said:
Hehe, first i thought it makes no sense to write a howto on this since its described in the SOC thread anyway, but man the idea to do it during boot is ubercool, didn't think of that...
Click to expand...
Click to collapse
I know it's explained in the SOC thread, but many people keep asking on the "Samsung Galaxy 3 GT-i5800: root, gps fix, upgrading" thread about rooting Froyo, so I thought it's better to have one SOC thread right in the Galaxy 3's Development Section. It'll save everyone reading through a lot of pages on that thread..
addicted2088 said:
I know it's explained in the SOC thread, but many people keep asking on the "Samsung Galaxy 3 GT-i5800: root, gps fix, upgrading" thread about rooting Froyo, so I thought it's better to have one SOC thread right in the Galaxy 3's Development Section. It'll save everyone reading through a lot of pages on that thread..
Click to expand...
Click to collapse
hi
when i see a few reports that this is working for our G3 ill add this link to the roll up thread very nice of you to give this info to all keep up the good work
one question will this also un root the phone
haree said:
hi
when i see a few reports that this is working for our G3 ill add this link to the roll up thread very nice of you to give this info to all keep up the good work
one question will this also un root the phone
Click to expand...
Click to collapse
Can't unroot using the same procedure, but have added another procedure to do it.
This method does work for everyone. The only new step in my procedure is to do it while the phone is booting.
help! !
cant root. stuck at "waiting for device"..... tried everything.. no luck. can anyone help?
coolzarjun said:
cant root. stuck at "waiting for device"..... tried everything.. no luck. can anyone help?
Click to expand...
Click to collapse
Are your phone drivers properly installed? Does your computer make a 'Hardware connected' ding sound when you turn on the phone? If not, then you'll have to install Samsung Kies and then connect the phone to the computer to install the drivers. Try rooting after that.
all drivers are installed.. i reinstalled twice.. when i connect in usb debugg.. says installing some adb stuff after fews secs.. comp says hardware might not work properly not properly installed. all other drivers wrk fine.. wat can i do to install adb drivers properly. . i have windows xp
coolzarjun said:
all drivers are installed.. i reinstalled twice.. when i connect in usb debugg.. says installing some adb stuff after fews secs.. comp says hardware might not work properly not properly installed. all other drivers wrk fine.. wat can i do to install adb drivers properly. . i have windows xp
Click to expand...
Click to collapse
Connect your phone to your computer. Then open the Device Manager. Then look for the entry 'SAMSUNG Android Composite ADB Interface' in the list. It might be under the ADB Interface tab. Right click on the 'SAMSUNG Android Composite ADB Interface' and uninstall it.
Then reconnect your phone to the computer and see if the ADB drivers get installed properly this time.
did that also....uninstalled and connected the phone. still the same error..
hardware not properly installed.. it might not work properly
i got windows xp 32-bit
can u help ?? plz !
coolzarjun said:
did that also....uninstalled and connected the phone. still the same error..
hardware not properly installed.. it might not work properly
i got windows xp 32-bit
can u help ?? plz !
Click to expand...
Click to collapse
Sorry, I'm using Windows 7, so I've no idea what to do about the drivers in Windows XP. Try updating Kies..
i also have win 7 and it doesnt work...help??
reist said:
i also have win 7 and it doesnt work...help??
Click to expand...
Click to collapse
I can't help if the drivers on your computer are not installed properly. After connecting the phone while it is ON, open the Device Manager and see if the ADB driver is properly installed.
If the drivers are properly installed, this method will work..
Edit: As mentioned by mhndk14 below, enable USB Debugging in Settings>Applications>Development.
I also had the same problem with windows 7. Just make sure that the USB Debugging is enabled and then try again. It worked for me.
how to bring the phone back to factory settings
hi how can i get back my phone to the original factory settings? i rooted using z4mod and when unrooted the live wallpapers wont go... and how do i get my boot menu when restarted on my 1 5801??
nageshkaja said:
hi how can i get back my phone to the original factory settings? i rooted using z4mod and when unrooted the live wallpapers wont go... and how do i get my boot menu when restarted on my 1 5801??
Click to expand...
Click to collapse
To remove the Live Wallpapers, you'll have to root your phone, and then use Root Explorer to remove the files Livewallpaperspicker.apk from system/app, and libRS.so and librs_jni.so from system/bin. Then un-root your phone. Be sure to press the 'Mount R/W' button in Root Explorer to be able to delete the files.
As for restoring your boot menu, that procedure is there somewhere in the Development section. The boot menu changes because of upgrading, not rooting.
It seems i have lost haptic feedback after rooting(jpb), anybody else experience this?
Edit: lol
It was probably sue to the "forced" reboot, but I accidently dropped my phone (batteries feel out) and now it's working
stubborn_d0nkey said:
It seems i have lost haptic feedback after rooting(jpb), anybody else experience this?
Edit: lol
It was probably sue to the "forced" reboot, but I accidently dropped my phone (batteries feel out) and now it's working
Click to expand...
Click to collapse
Yeah, haptic feedback stops working sometimes on JPA and JPB after rooting. But restarting the phone corrects it. (Although your method of restarting the phone was too brutal!! )
Thanks addicted2088...worked perfectly...
successfully rooted..........
now i need to know how to install live wallpapers......
thanks
I have downloaded the one click and samsung drivers. The program opens fine. But I have read some people getting phones messed up from rooting with this program?
Should I remove the SD card first before rooting?
Does this program work with 2.2 one click for Galaxy?
Thanks!
Hey
the version i used is 1.7 and no problem here ....
I have read somewhere that you should unmount your sd card , well i didnt and still got phone rooted..
i dont see much of problem with it ..... it will take around 5 mins so just be patient.....dont forget to install samsung drivers .... and put phone into developer mode
Can not get it to work.
Yes I did download Samsung drivers succesfuly.
Yes I enabled Debugging mode succesfully
Tried using both One click 1.7 in Rage mode. Tries to work but just cursor flashing and does nothing.
Then used the other One click program that comes up with BLUE SAMSUNG I9000 and has choice to One click 2.1, 2.2 or remove root.
I choose 2.2 and then phone resets like when I used Clockwork on my old HD2.
I chose correctly to install the files.
PHone loads files but then get error code and wont install them. Reads Signiture Verification Failed!
I read others having same issue of phone not letting files install.
Anyhelp!
I know its not rooted as Titanium Backup is not getting root permission..
iceshark said:
Can not get it to work.
Yes I did download Samsung drivers succesfuly.
Yes I enabled Debugging mode succesfully
Tried using both One click 1.7 in Rage mode. Tries to work but just cursor flashing and does nothing.
Then used the other One click program that comes up with BLUE SAMSUNG I9000 and has choice to One click 2.1, 2.2 or remove root.
I choose 2.2 and then phone resets like when I used Clockwork on my old HD2.
I chose correctly to install the files.
PHone loads files but then get error code and wont install them. Reads Signiture Verification Failed!
I read others having same issue of phone not letting files install.
Anyhelp!
I know its not rooted as Titanium Backup is not getting root permission..
Click to expand...
Click to collapse
Down root check fron the market. Just because Titainium is not getting root permission does not mean it's not rooted. It’s not that difficult to root the SGS 4G Phone. The first thing you need to do is make sure your phone is communicating with your computer. Install the Samsung USB drivers.(make sure you have the right drivers for your O.S. either 32bit or 64bit) In your phone go into Settings/Applications/Development and make sure you check “USB debugging”. Connect your Tethering cable to your phone. On your home screen you should see “USB Connected” popup on top of your screen. You should be able to press USB connected button from the drop-down menu on the home screen and see the external SD card on the computer now. If that works then Turn off USB storage. (leave “USB debugging” checked) Then Download SuperOneClickv1.7-ShortFuse, expand the file and go to SuperOneClickv1.7-ShortFuse Directory. Run the SuperOneClick App. When it opens don’t change anything and just click “Root” and let it run. It should say rooted when done. Then go to the Market on your phone and get Titanium Backup and install it. It will ask for SuperUser permission and accept that on your phone. If that fails press “Problems” button, Then “Get Busybox”. Install the new Busybox. You may have to close and reopen Titanium Backup again. BTW this post should be in general.
yeah, i dont suggest you use rage. it took forever for me to root the phone that way. i left it on psneuter and it rooted in about 5 minutes
Sent from beyond the Galaxy
Thanks guys! Yes Rage was the issue. I followed his instructions and left in pnuueter and it worked perfectly! Now my Titanium is rooted and working.
Now if we could just get a good Apsd to let us format the SD card to ext 4 that would be a perfect world!
Thank you.
Moved to proper forum.
menacetwosociety said:
yeah, i dont suggest you use rage. it took forever for me to root the phone that way. i left it on psneuter and it rooted in about 5 minutes
Sent from beyond the Galaxy
Click to expand...
Click to collapse
^ thats what i forgot to tell him to change it lol
Rooted my SGS4G using Superoneclick.
2 things I noticed. Your AV will think that Rage is a virus. NOD32 kept quarantining it. I turned off both AV and FW.
Also, after you install the Samsung USB driver, reboot your computer. I had that "waiting for device" message until I rebooted computer. Then it flew. The driver doesn't offer to reboot, or tell you to.
Z
Help! When I try to root my evo shift with gui shift root and recovery all I get is an adb error message. I have installed htc sync on my laptop. I also cannot connect to sync. These problems may be related? I am running windows vista.
sounds like the drivers may not have installed... Where did you get the version of sync you installed? You're best bet is to use the one off the sdcard. I've had an occasion or two also where things got messed up, and I uninstalled it all and reinstalled. (under programs and features you'll find HTC sync and driver installer, remove both and reinstall if necessary)
I installed it off the sd card and have did the install/ uninstall at least 5 times. still no luck.
i had same error but i just did mine maually. theres a video now for manually rotting it. if you fllow the steps you will root your shift
candler72 said:
I installed it off the sd card and have did the install/ uninstall at least 5 times. still no luck.
Click to expand...
Click to collapse
I'm in the same boat no matter what I do it my shift won't connect to sync and when I run adb devices it kicks a blank line then right back to platform-tools I'm running Vista myself and messed with it for hours and no luck I'm mad because I have rooted my shifts already and don't know what went wrong with the drivers sync or my pc this sucks as I need to be able to adb to help test some things
Sent from my PG06100 using Tapatalk
You do have adb debugging on right... the only other thing I could think of.
Yes I do have debugging on.
have you tried getting sync from htc's website to be sure?
If I'm correct the old version of syn from sprints website was giving me problems loading the drivers. I used the newest version from htc website and voila I was good to go. U may want to try that. I just re rooted earlier use the gui and it worked like a charm
Sent from my PG06100 using Tapatalk
I have the sync from htc website. I still get error running adb try again. Ive used the same usb cord and ports with my archos pad and have no trouble transfering files.
What exactly does the error message say? And with what command?
Sent from my PG06100 using XDA App
Error running and. Try again
Sent from my PG06100 using XDA App
Adb
Sent from my PG06100 using XDA App
Maybe it's your sdk that is messed up... Maybe try downloading and installing again.
Sent from my PG06100 using XDA App
Ive got temp root now with visionary. And have it set to reroot when i turn my phone off/on. I have wireless tether (non adhoc) which is what I was wanting to tether my archos 101. I still can't connect to sync. Wondering if its a vistas issue?
danaff37 said:
What exactly does the error message say? And with what command?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
I dunno what the other guys error is but I know on mine if I go to device manager there is an error code 37 with my HTC on my Vista pc.....I can cd to my c:\Android\Android-sdk\platform-tools
But when I hit add devices it kicks back and empty line after it starts the Damon on whatever then right back out to platform tools...it does the same thing with every sync I install, plus my phone can't find sync on my pc at all even if its open...and help would be really appreciated
Sent from my PG06100 using Tapatalk
candler72 said:
I have the sync from htc website. I still get error running adb try again. Ive used the same usb cord and ports with my archos pad and have no trouble transfering files.
Click to expand...
Click to collapse
I'm having the "error running adb try again" problem as well. Unfortunately when I try to run adb from the cmd prompt its output goes to a popup cmd prompt window which disappears before I can read it. My guess however is that it's blank like yours.
I'm convinced I've done everything they way I'm supposed to. Has anyone yet gotten the htc drivers to work under vista?
I had this same issue with ADB..all I did was, while connected via usb, uncheck debugging and then recheck. Clicked root again and it worked.
Sigh, there was a adb update. Install the new version from the sdk, delete the one in shiftrr, copy the new one in, close adb with task manager, then run as you were trying to do before. That fixed it for me.
And make sure when you install the recovery, not to use the one it comes with, it doesn't support the newer roms we have on the shift now. If you want to flash current ones, use clockwork 5.0.2.0, our twrp (recommended)
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
droidmark said:
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
Click to expand...
Click to collapse
Hi - Would really appreciate your help here. Thanks for the tip on turning debugging off to get to the phone so I could install the USB drivers. Problem now is that ADB just refuses to connect to it. It shows up asa disk drive in Devices, but when I do a kill-server then start-server then adb devices, it doesn't list any devices, and an adb shell just says device not found.
Do I need to reboot Windows, or the phone? Seems unlikely. I can open a window to the phone, but can't get access to install the Gingerbreak and su files I need to root it. Going crazy!
Thanks,
Eric
Try rebooting both. Couldn't hurt.
Oh yeah, and if you haven't make sure the phone is back in debug mode.
Sent from my SCH-I510 using XDA App
Black-Falcon said:
Try rebooting both. Couldn't hurt.
Oh yeah, and if you haven't make sure the phone is back in debug mode.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Well, I'll be a monkey's brother in law. I rebooted both, checked debig mode - and it wasn't on, to my surprise. I've turned it on and off a bunch of times, so...
Anyway, I was able to finally get adb working!!! Yaaaayyy! But now I'm trying to root it, and Superuser doesn't show as an app, and Root Explorer says the f-er isn't rooted. And the Gingersnap Root Utility I've been trying to use, says it's all good to go, but its not.
Gonna try a different method, but if anyone has any ideas, I'm open.
Thanks!!!!
Use gingerbreak.
You gotta download superuser from the market
Sent from my SCH-I510 using XDA App
ClarkSt said:
Well, I'll be a monkey's brother in law. I rebooted both, checked debig mode - and it wasn't on, to my surprise. I've turned it on and off a bunch of times, so...
Anyway, I was able to finally get adb working!!! Yaaaayyy! But now I'm trying to root it, and Superuser doesn't show as an app, and Root Explorer says the f-er isn't rooted. And the Gingersnap Root Utility I've been trying to use, says it's all good to go, but its not.
Gonna try a different method, but if anyone has any ideas, I'm open.
Thanks!!!!
Click to expand...
Click to collapse
Try downloading busybox from the market, or downloading titanium backup and hit the "problems" button when you open it and select get busy box
Black-Falcon said:
Use gingerbreak.
You gotta download superuser from the market
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Tried GingerBreak. No good. "permission denied".
Good idea - I got Busybox installed this way, but still no joy from Gingerbreak.
Just flash the ED1 odin package and done
Sent from my SCH-I510 using XDA App
DroidXcon said:
Just flash the ED1 odin package and done
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
If I could flash anything I'd be rooted already, wouldn't I? How do I flash? ROM Manager needs root. Vicious circle.
I've heard that its not possible to root the Charge using current methods since the f-ing update the other day.
ClarkSt said:
If I could flash anything I'd be rooted already, wouldn't I? How do I flash? ROM Manager needs root. Vicious circle.
I've heard that its not possible to root the Charge using current methods since the f-ing update the other day.
Click to expand...
Click to collapse
Check the development thread for the Charge. There's a thread on how to rollback to ED1 with root using Odin.
Edit: Direct link: http://forum.xda-developers.com/showthread.php?t=1085190
droidmark said:
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
Click to expand...
Click to collapse
Dude - THANK YOU!!!! I could not get those drivers to install!!!
Please - Stickie!!!
If you want the drivers and don't trust the sources posted anywhere (we're not trustworth ?) you can get them from the phone itself. They are located in the file /system/etc/autorun.iso and you can extract them from it.
I have just received my sensation this morning. It is an amazing phone. I have had the HD2 for nearly two years now and ran android on it for the last few months.
I have put S-OFF on and rooted my phone with out any problems. I then connected it to droid explorer. Droid see's the phone and connects to it, but doesn't bring up any directories or files.
Is there anything I am doing wrong?
Other issue I have is the weather keeps dissapearing and I have to sync it again. Very odd.
GhostXSeries said:
I have just received my sensation this morning. It is an amazing phone. I have had the HD2 for nearly two years now and ran android on it for the last few months.
I have put S-OFF on and rooted my phone with out any problems. I then connected it to droid explorer. Droid see's the phone and connects to it, but doesn't bring up any directories or files.
Is there anything I am doing wrong?
Click to expand...
Click to collapse
Hey, I've ran across this issue before and apparently it has to do with permissions of ADB and the sensation. Only solution I had was to change permissions (suggested in quote below)
"this has to do with the default permissions of /data. ADB, which is what Droid Explorer uses to currently communicate with your device, does not have 'root' access in the shell and some directory like /data dont allow you to access them unless you have root permissions. This is something that is being worked on, but I do not have an ETA yet to when it will be released. Another option is to change the permissions to /data with chmod."
Droid Explorer
EDIT: I just did this with a different computer as well to make sure it works. As long as your device is rooted:
- Install ES File Explorer.
- Open its settings, enable Root Explorer.
- Click on the star for favorites, phone, and it should open up root directory.
- Hold down on /data, scroll to the bottom and select view permissions. If the permissions are not set correctly, reset them (rwxrwx--x)
- Plug USB back in, make sure you are using HTC Sync (not disk drive), check that adb recognizes the device (adb devices)
- Open up Droid Explorer and you should be able to use it to navigate!
Treid that and the permissions were set to rwxrwx--x all ready. It is still not working. It is not a big issue. I can do everything I need through root explorer and I can still install apps using droid but it would be nice to get this to work!