Database Info

Froyo Root Instructions using Superoneclick And Unrooting

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

[ROOT] *UPDATED* RegawMOD Hero Rooter v3.0 | Updated - 04/03/12

Description:
RegawMOD Hero Rooter provides easy rooting of the HTC CDMA Hero. Successful in rooting all builds up to 2.31.651.7
If you have any problems while rooting, reboot your phone completely and try again.
What it does:
Gains root shell on Heroc using rageagainstthecage
Installs SuperUser and su binary
Flashes Clockworkmod 3.0.0.5 recovery
Flashes my patched boot.img for 24/7 root in adb shell
Cleans up non-necessary files after run
Reboots to recovery and flashes S-OFF package by unrEVOked
Usage:
Unzip the .zip file to anywhere on your computer. Leave both "Hero Root.exe" and "AndroidLib.dll" in the folder together. Run the "Hero Root.exe" on your computer, then plug in your Hero. It will recognize that you plugged it in, and a big button the reads "ROOT ME" will appear. Press that button and watch as your phone is rooted in under 1 minute from start to finish.
Requirements:
HTC Drivers installed (installed with HTC Sync)
.NET 4.0 installed
Screenshots
Screenshots
Changelog
Version 3.0 | 04/03/12:
Re-wrote using the AndroidLib .NET library designed by me
Much more stable/reliable
Added S-OFF integration
Download Latest Release
Version 3.0 x86
Version 3.0 x64
Download Info
Version 3.0 x86 Zip MD5 - 32c4545a8f7aeccd571b8ba9f072b4f5
Version 3.0 x64 Zip MD5 - dcff7e2cd0e59a896c6245dd8efe4dde
Source Code on GitHub

.NET Framework 4.0 Download page (Or use Windows Update as mentioned below)
HTC Sync Software First item on the page. (You can cancel install after it installs the USB Drivers)
edited my original post because it really didn't help anyone or do anything other than take up space.

Updated first post. Now with screenshots! Ooooo, aaaaaahh!

here is the cmd dialog i got when i ran it the first time, then i read the next two posts...dont know how i missed that the first time...thanks guys

that just means you need to install .NET Framework 4.0. unless you already have it installed and it still doesnt work, then i dont know.

Keithgordon said:
here is the cmd dialog i got when i ran it
Click to expand...
Click to collapse
Grab .net framework 4.0 off windows update. It'll be in the optional software section.
Sent from my HERO200 using XDA App

...........

Very nice! This makes me almost wanna unroot just to try it. Excelent job!

This is sweet, it's simple yet elegant. I was wondering if you could do something like this for your s-off method/nand unlock method?

I've tried to use this a couple times without any luck both with 2.27.651.6 as well as 2.31.651.7
My phone is recognized by the rooter but seems to lock up on ">Running Exploit"
I know I'm not supposed to remove my phone but after close to thirty minutes I figured I'd see what happens if I did. I get a pop-up informing I can remove my phone and the rooter springs to life telling me root was achieved and complete however it doesn't seem to be rooted. (No custom recovery or SU installed)
I'm running Windows 7 Ultimate and have the USB drivers installed as well as .Net Framework 4.0.

Nate14 said:
I've tried to use this a couple times without any luck both with 2.27.651.6 as well as 2.31.651.7
My phone is recognized by the rooter but seems to lock up on ">Running Exploit"
I know I'm not supposed to remove my phone but after close to thirty minutes I figured I'd see what happens if I did. I get a pop-up informing I can remove my phone and the rooter springs to life telling me root was achieved and complete however it doesn't seem to be rooted. (No custom recovery or SU installed)
I'm running Windows 7 Ultimate and have the USB drivers installed as well as .Net Framework 4.0.
Click to expand...
Click to collapse
Ok thank you for the great feedback. That helped me find out right where the problem was in my code.
I need someone (anyone with a NON-Rooted Hero, and the sdk set up) to run this code for me, then attach the file named "HeroRoot.txt" it creates on your desktop to the thread here on xda.
Code:
adb start-server
then wait until it returns to the normal prompt, then enter:
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system > "%userprofile%\Desktop\HeroRoot.txt"

I had to turn on USB Debugging to get it to try the mount command, otherwise it just said "error: Device not found"
But attached is the requested output.
Hope that helps.

semi-stupid question, I need to have the Android SDK installed to run this right?

Wufei said:
semi-stupid question, I need to have the Android SDK installed to run this right?
Click to expand...
Click to collapse
I think Regaw is trying to make a simple application so that all you need installed is HTC Sync and .NET 4 Framework. I could be wrong
So No you don't need the SDK to run this application.

LazyTech99 said:
I think Regaw is trying to make a simple application so that all you need installed is HTC Sync and .NET 4 Framework. I could be wrong
So No you don't need the SDK to run this application.
Click to expand...
Click to collapse
In that case, it's not even recognizing my phone...installed HTC Sync and have .NET Framework 4 Extended (and Client Profile)

@Wufei
Make sure you have USB Debugging enabled in Settings -> Applications -> Development.

LazyTech99 said:
I had to turn on USB Debugging to get it to try the mount command, otherwise it just said "error: Device not found"
But attached is the requested output.
Hope that helps.
Click to expand...
Click to collapse
My HeroRoot.txt has nothing in it. It's 0 bytes.

I am still getting stuck at running exploit.

Deadsoulsniper said:
I am still getting stuck at running exploit.
Click to expand...
Click to collapse
I think the issue is being fixed.
Sent from my HERO200 using XDA App

yeah sorry, working on the issue now. Should have this bug worked out soon. And no, you do NOT need the sdk for this, I have included adb.exe and the necessary dlls it needs. Thanks for the HeroRoot.txt btw

[Q] 1 Click Root for Mac OS X?

Is there a 1 Click Root for Mac OS X? I want to Root, S-OFF, and Gold Card...

Get bootcamp
Sent from my Desire HD using XDA App

i will be trying to do this from a windows virtual machine on a macbook pro. ill let you know if it works. i see no reason it shouldnt

I had a go at it through Parallels on a Macbook and it worked smoothly.

wats parallels

Moved to general as not android dev.

I did the hack kit using terminal commands. install android sdk for mac and everything else is just step by step in the hack kit. there's a gold card app on the market too.
Sent from my Desire HD using XDA App

g4ess said:
wats parallels
Click to expand...
Click to collapse
It runs Windows in a windowed format through Mac OS as opposed to booting up in Windows like Boot Camp.

I actually ended up using the hack kit with terminal commands and adb. It was my first time rooting and i see the value of doing it this way. You gain more knowledge of what is happening with your phone. And if you have a mac with out a virtual windows machine then I want to recommend not being afraid of manual rooting.
Sent from my Desire HD using XDA App

emarsha said:
I did the hack kit using terminal commands. install android sdk for mac and everything else is just step by step in the hack kit. there's a gold card app on the market too.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I did the same thing the first time I rooted an Inspire. I believe I Still have the terminal output I saved (I was siked I got it to work - it was my first bit of rooting/terminal use ever). If it would help to see what I did, PM me.
EDIT: and Yes, above poster killersnowman is 100% correct. When you do it yourself you learn much more. When I first got my (first) inspire, I looked at the root instructions and they were WAY over my head. After just clicking around and browsing around on XDA, I felt like I was ready to tackle it after a few short days. Granted, it took me probably around three hours of trial, error, and asking for help from the incredibly helpful people on this board - but I got it! You can too.

I did the Simple Root running Windows XP in Parallels without a problem on my MacBook Pro. Now I am wanting to go back and redo the root with the Hack Kit to solve the HUSPA problem we simple root people are having but I am having a few problems with the terminal. For some reason I keep getting told HTC device is not found when I run the first command.
If anyone does use the hack kit on a mac and figures this out please let me know. The Mac users are the minority with Android so we need to stick together a bit here. I still am yet to find a good set of directions on how to "use" the terminal. When the Hack Kit directions start with "navigate to the folder" I have to assume I am doing things right by typing in the file path.
If you did pull it off and are willing to do a screen capture of your terminal that would be pretty great too.

bmolloy said:
I did the Simple Root running Windows XP in Parallels without a problem on my MacBook Pro. Now I am wanting to go back and redo the root with the Hack Kit to solve the HUSPA problem we simple root people are having but I am having a few problems with the terminal. For some reason I keep getting told HTC device is not found when I run the first command.
If anyone does use the hack kit on a mac and figures this out please let me know. The Mac users are the minority with Android so we need to stick together a bit here. I still am yet to find a good set of directions on how to "use" the terminal. When the Hack Kit directions start with "navigate to the folder" I have to assume I am doing things right by typing in the file path.
If you did pull it off and are willing to do a screen capture of your terminal that would be pretty great too.
Click to expand...
Click to collapse
When navigating to a folder on a mac, in the terminal, the command is: cd
Then, I would try to do as little typing as necessary to avoid a mistake. I would put in the command cd and then from my finder, physically drag the folder I wanted to navigate to INTO the terminal window, which automatically puts the correct file path.
cd [drag the folder into the terminal window from finder] and voila! It really is pretty easy. Now that you know that, take another look at the directions and see if you think you can make your way through them.
The only mistake I kept running into which someone helped me out with was that I wasn't making the gold card correctly. When I put the command in to the terminal, I wasn't specifying the actual drive, I was specifying a partition on the drive, and the goldcard failed, but looked like it succeeded. 99.9% of the problems you can run into have to do with making an incorrect goldcard I believe.

I have been trying this without restoring to stock, running CM7. I continue to get the "Error detecting HTC phone on USB connection". I will probably restore to stock when I have more than 3 minutes of free time... So it might be a while!!!
If anyone pulls this off without being restored to stock or while running CM7 any advice would be appreciated.
Thanks.

bmolloy said:
I have been trying this without restoring to stock, running CM7. I continue to get the "Error detecting HTC phone on USB connection". I will probably restore to stock when I have more than 3 minutes of free time... So it might be a while!!!
If anyone pulls this off without being restored to stock or while running CM7 any advice would be appreciated.
Thanks.
Click to expand...
Click to collapse
Is usb debugging on? Is the phone connected but NOT in usb mass storage mode? Im not sure but i think cm7 gets rid of fasboot so i dont think you can turn it off
Also if you have cm7 installed then why do you want to root it again? Its already rooted. If you want a new rom the just use rom manager. But if you want to root again then you should restore to stock
Its from my damn phone!!!

Yes, I am set up with USB debugging on but for some reason it will still not recognize the phone, I am sure it has to do with the fact that I am not running a stock ROM.
The reason I want to root again is because I do not have HSUPA enabled because I rooted with the Simple Root, which flashes a stock radio on that does not allow for HSUPA. Using the Hack kit you end up with the right radio that allows you to have the faster upload speeds. I also want to do the hack kit so I can get a better understanding of terminal commands and adb. I have been never found a reason to use the terminal before so this is a nice new challenge.

[Q] Question about Rooting on a Mac

I tried to post this in the "Beginners Guide for Rooting" but I do not have privileges. I am trying to root my new s3 on a mac so I am trying to follow the guidance in section one of the guide. However the links for samsung drivers are in an .exe format and the link to the java jdk files has expired. I downloaded the samsung drivers from the link and opened the (.exe) file and I attempted to install another version of the java jdk. When I connect Adam's casual the app recognizes my phone but I am unable to see it on my Mac through Finder. Am I ready to flash if the casual app can see my phone? Or do I need the osx compatible samsung drivers (not with a .exe filename) and a specific version of java jdk?
Thanks in advanced for any help. I tried to search for the answers but I have been coming up empty. Even though casual see's my phone, I'm still not sure if its ok to start flashing.

prescottc5 said:
I tried to post this in the "Beginners Guide for Rooting" but I do not have privileges. I am trying to root my new s3 on a mac so I am trying to follow the guidance in section one of the guide. However the links for samsung drivers are in an .exe format and the link to the java jdk files has expired. I downloaded the samsung drivers from the link and opened the (.exe) file and I attempted to install another version of the java jdk. When I connect Adam's casual the app recognizes my phone but I am unable to see it on my Mac through Finder. Am I ready to flash if the casual app can see my phone? Or do I need the osx compatible samsung drivers (not with a .exe filename) and a specific version of java jdk?
Thanks in advanced for any help. I tried to search for the answers but I have been coming up empty. Even though casual see's my phone, I'm still not sure if its ok to start flashing.
Click to expand...
Click to collapse
I don't remember if my phone showed up on my Mac in finder, but Adam's casual recognized my phone, I rooted and unlocked using the tool and have been flashing ROMS ever since.

davefields3 said:
I don't remember if my phone showed up on my Mac in finder, but Adam's casual recognized my phone, I rooted and unlocked using the tool and have been flashing ROMS ever since.
Click to expand...
Click to collapse
Did you download the samsung drivers in the link ( the .exe files) and install them on your mac? Also do you still have a copy of the java jdk files? The link in the "guide " is dead or the files have been moved. Thanks.

Mine did not show up in finder. I did have to download another program to interface with the phone. Just run Casuals and you will be fine.
Sent from my SCH-I535 using xda premium

prescottc5 said:
Did you download the samsung drivers in the link ( the .exe files) and install them on your mac? Also do you still have a copy of the java jdk files? The link in the "guide " is dead or the files have been moved. Thanks.
Click to expand...
Click to collapse
If I remember correctly, you can't download the samsung drivers on a Mac. And no, sorry I don't have the files

There is no drivers for mac. The only thing that will show is a sdcard if you have one. You are good to use Casual.

fr8cture said:
There is no drivers for mac. The only thing that will show is a sdcard if you have one. You are good to use Casual.
Click to expand...
Click to collapse
Mine doesn't show the sdcard. I can use ADB but that's the only way I can communicate to my device over USB. I have't tried Casual.

Well I finally got home so I could use my Mac with my phone. Casuals worked great a couple of weeks ago as did adb. Now, I can't get either to work. I read that some are having issues with the usb ports on the newer MacBook Pros. I will do a little know testing and see if I can find a way to make it work post back. I tried rebooting, different cables, etc with no luck. If anyone knows anything, please chime in.
Sent from my SCH-I535 using xda premium

HHF2 said:
Well I finally got home so I could use my Mac with my phone. Casuals worked great a couple of weeks ago as did adb. Now, I can't get either to work. I read that some are having issues with the usb ports on the newer MacBook Pros. I will do a little know testing and see if I can find a way to make it work post back. I tried rebooting, different cables, etc with no luck. If anyone knows anything, please chime in.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Okay, after a lot of digging, I finally figured out what I did. I take no credit for this, I found it on here in reply to a thread somewhere. I can't remember where as I usually view this site on my cell phone.
sudo kextunload -v /System/Library/Extensions/EasyTetherUSBEthernet.kext
from a terminal. I forget if you have to reboot or not.
This will disable tethering, but you can now see your device via adb.
To renable tethering once you're done debugging, use
sudo kextload -v /System/Library/Extensions/EasyTetherUSBEthernet.kext
This is for EasyTether only, but I am sure that there could be another type of app that would do the same thing? If you could isolate the app, it should be as easy as replacing the EasyTether part of the command and running that. Good luck, I personally know how aggravating that things like this can be.

Getting ADB access in Android 4.2.2

This incorporates the ideas of http://forum.xda-developers.com/showthread.php?t=2144709, so if you want to see how this was resolved for the Nexus 4, check out that thread.
Okay. So you've flashed a spanking new 4.2.2 ROM and ADB no longer talks to your Sensation. What happened?
Well, the fact is that 4.2.2 is significantly more secure, in the good sense. It enforces RSA authentication via ADB. However, RSA authentication is supported only in recent versions of ADB.
What to do?
First, make sure you have the latest version of ADB on your PC.
On Windows you can quickly find out if you your version of ADB is up to date. Check your ".android" folder and see if it holds a file called "adbkey".
On any platform type "adb version" to verify that you have the latest version of ADB. Versions 1.0.31+ support RSA authentication.
-- So now, if you have ADB 1.0.31 or higher. You can skip directly to step 2, then.
-- If you do not have ADB 1.0.31 or higher, and you have the full Android SDK installed, open the SDK manager and update it. If you only have ADB and fastboot installed in a folder on your PC, overwrite files in the folder with those in the corresponding zip file attached (windows or linux -- sorry! I don't have Mac versions at this time). These come from version 16.01 of the android platform-tools package, if you are curious.
-- if you have never installed the SDK or ADB or fastboot, now is the time to do that. I recommend going to http://developer.android.com/sdk/index.html to get started.
[*]Enable USB debugging on your phone
USB debugging is now enabled by selecting Android Debugging in System Settings > Developer Options.
"I don't have the Developer Options items in System Settings!!"
In Android 4.2.x, you need to go to System Settings > About Phone and tap the Build Number item about 6 or 8 times, and Developer Options will reappear.
[*]Plug in the USB cable. Securely.
Dismiss the USB mass storage window.
"I connected the cable, but nothing happened!!"
Okay, chill. You won't get a response until ADB tries to connect to your Sensation. So go ahead and start ADB on your PC. Suggested command:
Code:
adb devices
"Now ADB started, but nothing's happening on my computer!!!"
Uh, didn't I just advise you to chill ? Take a look at your phone...
"What's this pop-up that just popped up??"
(See image below)
Congratulations, that is Android asking your permission to store an RSA key on your Sensation for ADB interaction with your PC.
Fearlessly accept it.
Hint: check the "Always allow from this computer" box to save time later on.
The RSA authentication key you just accepted will be stored on your phone in the file /data/misc/adb/adb_keys.
You are now good to go. Just 3 easy steps with a minimum of panic.
Questions? Problems? Ask away!
Many thanks to XDA member skipjacks for the idea for this post

Hi,
Nice! :good:
People should also not use USB 3.0 slots or USB hubs.
Try several slots if the front ones do not work.
Windows 7 & 8 drivers are HERE in case anyone needs them...

malybru said:
People should also not use USB 3.0 slots or USB hubs.
Click to expand...
Click to collapse
I understand about the hubs, but why not USB 3.0?

Skipjacks said:
I understand about the hubs, but why not USB 3.0?
Click to expand...
Click to collapse
Hi,
I have read a lot of instances of "Device not recognized" when using 3.0 slots.
I am not saying it will never work.
But ,if you use one,and it does not work,then,try it on a 2.0 slot.

Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.

onemanshow85 said:
Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.
Click to expand...
Click to collapse
Hi,
I think there is one solution that will address both issues. Before I mention it, let me ask: are you sure you enabled USB debugging on your Sensation? This is confirmed if, when you plug in the cable to your PC, you immediately get a USB debugging icon in the Notification Bar.
Glad we got that out of the way!
Unplug your device from the PC.
Anyhow, since you already have the SDK installed, the recommended way to update is to use the SDK Manager.
--in Windows, I think this is an executable in the tools sub-folder of your main android SDK folder. Double clock on it.
--in Linux, start up a terminal and type
Code:
android
if that doesn't do it, CD to the /tools directory in android-sdk-linux, or wherever you put the SDK, first. Then type "android".
The window that opens when you start SDK Manager should show that you need an update to (at least) platform-tools. Go ahead and do the update. You will have to accept some license(s) - accept it or them.
Once the install is complete, close SDK Manager.
Now plug your USB cable back in, and try out the "adb devices" command. It should work.
Suppose you still get "device not found", though. Try the following: again unplug.
Type the command:
Code:
adb kill-server
Now plug the phone back in, verify that you have USB debugging, and try "adb devices".
If no go, let me know what platform you are running, etc. I've heard it could be the cable, but I think that you just need to make sure it is plugged in securely.
BTW, the reason you probably won't have to do the adb kill-server step is that the SDK Manager kills running adb processes during the install.
Let me know how it goes!
Yrs,
dkephart
Sent from my HTC Sensation using xda premium

tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot

onemanshow85 said:
tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot
Click to expand...
Click to collapse
Yeah... my random selection doesn't have this problem. But I once seemed to have it with the official cable. You might want to try rebooting both the phone and the PC.
Sent from my HTC Sensation using xda premium

The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.

onemanshow85 said:
The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.
Click to expand...
Click to collapse
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium

dkephart said:
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Some really cheap cables only have 2 wires in them and can only be used for charging. You need the other wires for data transfer.
But some companies only put the charging wires in to save money on the copper.
It must be a REALLY low quality cable though. I mean I get all my cables on Monoprice for like $1-$2 and they all work great for data.
Or, the cable does have all the internal wires and one is just broken inside.
Sent from my HTC Sensation using xda app-developers app

I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.

nemovich said:
I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.
Click to expand...
Click to collapse
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium

dkephart said:
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
no just the serial number

nemovich said:
no just the serial number
Click to expand...
Click to collapse
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium

dkephart said:
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
with adb shell I get $ and with su I get #.

nemovich said:
with adb shell I get $ and with su I get #.
Click to expand...
Click to collapse
Cool! Then you have adb working. To confirm, in the shell, "ls" should come back with a listing of the files on your device. If you do "cd sdcard" and "ls" you get the files on the SD card.
You're good to go.
Sent from my HTC Sensation using xda premium

Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Sent from my HTC Sensation using xda premium

nemovich said:
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Click to expand...
Click to collapse
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium

dkephart said:
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
when I cd to the sdk folder ( C:\Users\Documents\adt-bundle-windows-x86-20130219), it gives me command not recognized. I can run sdk manager from the folder and everything is up to date.
I run adb from platform-tools and it gives me the same thing as before.
one thing though, I don't see the "adbkey" file in platform-tools but it is there in ".android" folder. so I run it from the later folder too but the still the same thing, no pop-up.
it's not just android commander, a lot of other apps give the same thing.