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!
Related
Okay, I have been able to get ADB access to the I-Mobile i858; but I cannot get root. There is an SU program and Busybox pre-installed on this device. I tried changing the permissions of SU to 4755 and 6755 without success. It looked like it was trying but something is interfering with root. Maybe if we work together we can figure this out. I even modified a flash image to set the permissions when it flashed the new image. That still did not give me root.
Here is how you get ADB to connect. It is kind of a pain but at least now we can talk to the device.
1. Install the "Android Terminal Emulator" by Jack Palevich from the Android Market to your device.
2. Download the Android ADB device drivers from this link and un-rar them.
http://www.generalmobile.com/support/dstl1/DSTL1_USB_Driver.rar
3. Open Device Manager on your computer.
4. Make sure debugging is turned off on your device in Settings>Applications>Devices.
5. Open the Terminal Emulator you downloaded in step 1 and type in the following command "<enter>setprop persist.service.adb.enable 1<enter>".
6. Go back to Settings>Applications>Development on your device and turn USB Debugging on. Click OK when prompted to confirm.
7. Plug the USB cable into your i858 and then your computer's USB port. In my tests using a reliable hub is okay.
8. You will see a device under Universal Serial Bus Controllers that says either "USB Mass Storage Device" or "USB Composite Device." Watch that section in Device Manager to see which one is the new one when you plugged in your device.
8. Uninstall the Mass Storage or Composite Device that was added to Device Manager when you plugged in your computer. You do this by right-clicking it and selecting "Uninstall".
9. On Device Manager Click the Actions pull down menu and click "Scan for hardware changes".
10. If you are lucky an unknown Android Device will no be listed in the Device Manager as not working due to no drivers installed. Go to properties of this device and update drivers browsing to the folder when you unzipped the drivers downloaded in step 2 above. The Android ADB drivers will now install.
11. If that doesn't work keep uninstalling the Mass Storage or Composite Device and rescan until the Android Device appears in Device Manager.
12. If you unplug it you will have to go back to step 4 but you can skip step 5.
13. If you reboot or turn off your device you will have go to back to step 4.
14. Unfortunately, I have to do this ritual every time I want to connect to the device by ADB; but heck it sure beats having no ADB access at all.
Now that you guys have ADB access let's rock this device, root it and have some fun. I spent all day trying to root it without success. I did manage to make the phone do some weird things and reboot a couple of times. I was changing permissions for the pre-installed "su" program in "/system/bin" but obviously there is something else that needs to be done to root this device. At least we are one or two steps closer now.
Thanks for sharing with us your work
For me i just delete apps befor i flash the rom because after when the apps installed i can t delet them because there are protected.
closer66 said:
Thanks for sharing with us your work
For me i just delete apps befor i flash the rom because after when the apps installed i can t delet them because there are protected.
Click to expand...
Click to collapse
If the device was rooted then you could delete them on the phone.
I-Mobile i858 has been rooted!!!
Okay, the I-Mobile i858 comes pre-rooted but there is something wrong with the way it was setup and root doesn't work. You download a program called Universal Androot and let it re-root the device so that it corrects whatever mistakes the ODM put in that made root not work. In your browser go to the following URL and install the program.
http://bit.ly/cwNm9u
When you run the program it says the device is already rooted; but there is some problem as the rooting is not complete. So you tell the program to root the device again. After it is done the device is rooted and stays rooted after reboot. Programs like Boot Control that require root access now work. There is a SuperUser Authorizer app that will intercede the first time and ask you if you want to give root permission to that app. That is a good thing and will protect you from malicious programs getting root that can cause you all kinds of nightmares.
But, I am root and I still cannot uninstall the pre-installed apps. How do you do that even as root? I am missing something.
hey great new s thanks for your work today i went to the i-mobile shop in samui and there say rom update is official confirm to 2.1 or maybe 2.2 there dont know excactly
Now i have root thanks. But following problem when i try to delete some apps that pre installed.
Says delete it but in real do not delete the app ummm
do you have any id why i can not delete the apps??
closer66 said:
Now i have root thanks. But following problem when i try to delete some apps that pre installed.
Says delete it but in real do not delete the app ummm
do you have any id why i can not delete the apps??
Click to expand...
Click to collapse
Any pre-installed apps cannot be deleted the normal way. Install Titanium Backup from the Android Market and let it have root when requested. You can use that program to uninstall pre-installed apps with root.
Rooted! ADB! Now this device gets much more useful! Great work jboxer, thanks!
BTW the rooting app has been updated to v1.6.1
Home page:
http://blog.23corner.com/tag/universalandroot/
Download:
http://bit.ly/aa4jxJ
Follow this Link droidsans.com/node/4018
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.
As the title suggests this is how you enable tethering without the verification process at&t has that checks to see if you are on the tethering plan. Beware it will suck up your data so if you don't have the unlimited data plan (most folks dont) you can run up your bill. Of course you can always just use a custom ROM.
1)get the update from samsung via kies
2)root your phone I used SuperOneClick
3)install TitaniumBackup
4)In Titanium Backup look for an application called Tethering Manager 1.0 uninstall it
Plug your phone in usb and turn on tethering. I unplugged the network cable from my PC and just plugged in my droid so I can verify that this worked for me. I did have to toggle the use packet data under the wireless networks menu off then on one time to get it to work but not on subsequent attempts. I don't have my laptop at work so I can't test the wireless hot spot feature but when you turn it on it doesn't go through the verification so I'm assuming that works also.
So for those of you that don't want a custom ROM and want tethering there you go.
(not responsible for bricked or useless phones with this process.)
chalee76 said:
As the title suggests this is how you enable tethering without the verification process at&t has that checks to see if you are on the tethering plan. Beware it will suck up your data so if you don't have the unlimited data plan (most folks dont) you can run up your bill. Of course you can always just use a custom ROM.
1)get the update from samsung via kies
2)root your phone I used SuperOneClick
3)install TitaniumBackup
4)In Titanium Backup look for an application called Tethering Manager 1.0 uninstall it
Plug your phone in usb and turn on tethering. I unplugged the network cable from my PC and just plugged in my droid so I can verify that this worked for me. I did have to toggle the use packet data under the wireless networks menu off then on one time to get it to work but not on subsequent attempts. I don't have my laptop at work so I can't test the wireless hot spot feature but when you turn it on it doesn't go through the verification so I'm assuming that works also.
So for those of you that don't want a custom ROM and want tethering there you go.
(not responsible for bricked or useless phones with this process.)
Click to expand...
Click to collapse
you can also delete tetheringmanager from the /system/apps folder using root explorer if preferred.
will this also enable Mobile AP or only USB tethering?
Sent from my SAMSUNG-SGH-I897 using XDA App
Just checked from my home laptop and yes Mobile AP also works. On the screen to turn in on or off it will say you need the feature on your account and to dial 611. But you won't need to do that as it will not enter "verifying" mode.
Since the real update was not available until today, I suspect that these tests were not done with "official" AT&T 2.2 update.
Removing the TetheringManager.apk does NOT work with the official release.
PhilipPeake said:
Since the real update was not available until today, I suspect that these tests were not done with "official" AT&T 2.2 update.
Removing the TetheringManager.apk does NOT work with the official release.
Click to expand...
Click to collapse
you sure about that? you know, cause the version we already had IS the official release...it just got to us early.
Just tried removing TetheringManager 0114.apk from /system/app and rebooting.
When I look at Settings > Tethering it still has the notice about needing a tethering account, turning on USB tethering seems to do nothing, and EasyTether still doesn't work.
(With the apk removed, Tethering 1.0 no longer shows up in TitaniumBackup)
I am using the official release that I got over kies from samsung I did it this morning. I shall send a screen shot of my phone if you really want it.
PhilipPeake said:
Just tried removing TetheringManager 0114.apk from /system/app and rebooting.
When I look at Settings > Tethering it still has the notice about needing a tethering account, turning on USB tethering seems to do nothing, and EasyTether still doesn't work.
(With the apk removed, Tethering 1.0 no longer shows up in TitaniumBackup)
Click to expand...
Click to collapse
if you are on official release, you probably need to remove .odex file too, if it exists.
but regardless, when you remove the tethering apk, you will still see the message
To test this. Make sure you have no internet connection on the pc you are connected to disconect or shut off your pc's wi-fi or unplug it from the network. Make sure debug mode is off... Plug your phone in when it gets to the screen asking what you want to do just click home. Pull up tethering turn it on wait. Pull up a browser see if you are connected. If your useing a mac I can't help you. Will try to do this on linux when I get a moment.
Hmm... Looks like there has been some additional posts since my last refresh so I'll change my post a bit.
I tested and verified this on an official rom updated using Kies mini. I used root explorer to rename the TetheringManager0114.apk file to TetheringManager0114.apk.disable. This was to keep the file around just in case it is needed later on. I rebooted the phone and I tested both Mobile AP and USB Tethering. Both worked as expected but I had to do an ipconfig /release and ipconfig /renew to get them to kick through. I had wifi disabled on my laptop (was used to test) and no ethernet cable plugged in. There is no odex file to worry about in the official release for Tethering Manager.
P.S. - As already stated above you will still get that message.
shinji257 said:
Hmm... Looks like there has been some additional posts since my last refresh so I'll change my post a bit.
I tested and verified this on an official rom updated using Kies mini. I used root explorer to rename the TetheringManager0114.apk file to TetheringManager0114.apk.disable. This was to keep the file around just in case it is needed later on. I rebooted the phone and I tested both Mobile AP and USB Tethering. Both worked as expected but I had to do an ipconfig /release and ipconfig /renew to get them to kick through. I had wifi disabled on my laptop (was used to test) and no ethernet cable plugged in. There is no odex file to worry about in the official release for Tethering Manager.
P.S. - As already stated above you will still get that message.
Click to expand...
Click to collapse
i didn't have to take any steps aside from removing the tethering apk
Ok !!! it works.
My problem was really pretty simple ... the tethering AP is on channel 6, as is my home AP.
The home AP was completely swamping the the android AP so I couldn't even see it.
Anyone know how to change the channel on the Android AP???
I completely deleted my file it never occured to me I may need it later on. Can one of you kind people post or pm with it?
chalee76 said:
I completely deleted my file it never occured to me I may need it later on. Can one of you kind people post or pm with it?
Click to expand...
Click to collapse
Which file?
TetheringManager 0114.apk
or you can use an app called pda net
what fun is it if you just go installing apps and not try to break your phone.
chalee76 said:
I completely deleted my file it never occured to me I may need it later on. Can one of you kind people post or pm with it?
Click to expand...
Click to collapse
check cog4 he has a link in the op with the apk
Here's the long and hackish way to do it if you don't want to buy some apps. It's long but relatively safe. Not responsible if you brick or do other bad things(tm) to your phone!
1. Root your phone. Nothing sinister here and easy to do with http://forum.xda-developers.com/showthread.php?t=803682
2. Install the Android Developer SDK onto your machine (good for sideloading apps) For info on installing and sideloading visit
http://ars.samsung.com/customer/usa...ID=2&PROD_SUB_ID=557&PROD_ID=558&AT_ID=303992
Yes, Samsung tells you how to get around AT&T.
3. Open a command prompt (in Windows go to your search bar and type "cmd")
4. Navigate to where adb is installed. In mine (Win 7 64 bit) this was C:\Program Files (x86)\Android\android-sdk-windows\platform-tools
Code:
cd C:\Program Files (x86)\Android\android-sdk-windows\platform-tools
If you need some help, open Windows Explorer (not IE) and search for adb.exe, then copy the path as text and paste (right click) into cmd
4b. If you've not done so before, please put your phone into USB Debugging mode
5. Open the adb shell
Code:
adb shell
6. Go up to root. Your screen will look like this
Code:
$ su
su
#
The # means you are now root. You may, on your phone's screen, need to approve this
7. Mount the system folder into read-write (this is why you need root)
Code:
mount -o remount,rw /dev/block/stl9 /system
8. Move to /system/app
Code:
cd /system/app
9. This is where the aforementioned TetheringManager0114.apk lives (boooo!) If you want to verify this (these commands are all cAsE sensitive)
Code:
ls Te*
Should dump out
Code:
ls Te*
TelephonyProvider.apk
TelephonyProvider.odex
[COLOR="Red"]TetheringManager0114.apk[/COLOR]
We want to RENAME the file
Code:
# mv TetheringManager0114.apk TetheringManager0114.apk.old
10. IMPORTANT - remount /system in read-only
Code:
mount -o remount,ro /dev/block/stl9 /system
11. Restart your phone and enjoy your tethering (but not too much, lest you run up your bill!)
Please note that this does NOT remove the AT&T notices about needing an account when you go to enable tethering.
Trying to run ADB from a Win 7 x64 system to push items to my Xoom 3G. ADB Devices shows nothing yet I'm able to see files and folders on my Xoom. Any help in what driver I need to install in order to be able to take advantage of ADB would be most helpful as I'd like to root my tablet.
Is USB debugging enabled? If not, that's the issue.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Already checked that. Not the issue.
Install the Moto Helper from here:
Link
Once installed plug in the device and it should install the required drivers.
If you have already done this then look for a Motorola folder in your START menu. There you should see a "Mobile Drivers" folder and in that folder a "Motorola Driver Installer" Executable.
Run the executable and tell it to "update". If that doesn't work try selecting "reinstall"
Running Update worked. FYI, the current version doesn't have a "reinstall option."
trouble with adb
I am not hay luck running ADB. It worked several months ago but I'm not sure why it doesn't now and I forgot what I did way back when
When I connect the USB to my PC (Win7), the XOOM mounts and I can see the files, etc., but when trying ADB it says "error: device offline."
I know on my EVO, I have to set the phone to charge only; is that the case here as well?
Any suggestions?
Nexus 5 android 6.0.1
Build number MOB30M
I've had some wifi issues these past few days (where the wifi radio didn't turn on, it was stuck in a "turning on" loop) and a missing wifi MAC address. After testing whatever I could on a stock phone (aeroplane mode, factory resets, you have it) I decided to root it. I read around and found someone claiming that deleting the /persist/wifi foldercould fix my issues. I can't post a link but it was a post on thinkoholic.
I downloaded Nexus Root Tolkit and set out to root my phone. I have no experience with rooting, but with a YouTube guide along with the program popups it seemed easy enough. I did the full driver installation, unlocked the bootloader and then rooted the phone. NRT crashed on me during the rooting process, IIRC while I was at the slider-part on my phone (TWRP?) to confirm a read-only mode or read/write. I restarted the rooting process and the phone booted up alright. I've installed root checker and a terminal window app which both say the phone is correctly rooted, but when I try navigating the /root folders in various explorers/file managers (ES File Explorer, Root Browser), the folder shows up as empty.
Am I looking in the wrong spot for a /persist/wifi folder?
Edit: I managed to find the folders I needed, deleted contents of both /persist/wifi and /data/misc/wifi but to no avail. Still no new MAC address (it just shows 02:00:00:00:00:00) and the problems remain. Even though I'm in aeroplane mode the green loading stripe beneath Wi-Fi settings (in the settings menu) continues going even when I've turned the wifi radio off. Hardware issue maybe?