Related
I've posted this inside another thread but decided to make a new one so others can see.
To all of you guys who are giving up - DON'T !
Here's how I finally got root on my DINC after about 3 days of trying.
I've read and watched almost every post and walk-throughs available in this forum and few others and was still unable to get into ADB Shell using any of the methods and tricks available and even though none of them worked I kept trying until I found a post on adndroidforums.com by Centsy. So along with his instructions and combination of many others here's how I achieved root:
1. Download the file from the 10 minute incredible root video on YouTube by mejdam. (can't post the link cause I'm new to the forum).
2. Unzip the file and run SDK setup.
3. As soon as SDK setup runs it gives an error message. Close it. then hit Cancel on next window.
4. While still in Android SDK and AVD Manager click on Available Packages (on the left) and then hit the plus sign in the right window for the repository. It will give you a list of packages available. Download the very last one which is the USB_Driver. It will add 'usb_driver' folder to your SDK folder where you ran sdk setup from.
5. Modify android_winusb.inf file inside the 'usb_driver' folder by adding these lines at the end of [Google.NTx86] and [Google.NTamd64] sections:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
6. I used the 2 gig Sandisk memory card that came with the phone. Had it FAT32 full formatted on the pc.
7. insert the card into the phone wait for it to be recognized
8. connect the phone to the pc and use the modified inf file of Android SDK usb_driver to get the phone connected and drivers installed. Note that I do not have HTC Sync installed on my pc.
9. on the phone go to settings->applications->development->turn on USB Debugging. wait for the phone to be recognized
10. open command prompt, navigate to your SDK\Tools folder and type in: adb devices. when you hit enter it should list your phone as being connected.
11. at the prompt type: adb reboot recovery, hit enter
12. as soon as the prompt is back type: loop and hit enter to start the adb shell loop. As soon as the loop starts running, the phone should show the white HTC Incredible screen, start clicking in and out the sd card before you hear the device disconnected sound on your pc. keep clicking the card in and out until you hear device connected sound on you pc. If you still don't see THE message we are looking for after another 10, 15 seconds stop clicking the card. take the battery out of the phone, put it back in, wait for it to reboot and repeat steps 11 and 12.
I had to do steps 11 and 12 about 3 times when I said to myself - next time is the last time and if it doesn't work then I'm going to get the 2gig PNY card that everyone is saying helps them achieve root. Then all of the sudden it took a little longer for the device connected sound to come up and the mouse cursor turned to the Waiting Hour-Glass and as soon as I heard the sound I saw the good old error message we are all striving to see. After that I just followed the instructions on the 10 minute root video to get the phone rooted.
Never give up, Never surrender !
Hopefully this will help some of you guys to achieve root and thanks to everyone who's hard at work on getting this great phone rooted.
Hi,
Having issues with your Step #12. You say to click the card in and out when the white HTC screen comes up and do it till the first disconnect sound. Then you go on to say keep clicking untill it connects. Then you says 10-15 seconds after the connect sounds keep clicking. Don't you mean to say keep clicking from white HTC screen till 10-15 seconds after the 2nd sound(the connect sound) So basically clicking for over 30seconds.
Please clarify as I'm thinking you meant differently thne what you typed. I too have a stock 2G sandisk card that came with my phone and so want to get this rooted without buying a PNY card hah.
- Pete
sonypete said:
Hi,
Having issues with your Step #12. You say to click the card in and out when the white HTC screen comes up and do it till the first disconnect sound. Then you go on to say keep clicking untill it connects. Then you says 10-15 seconds after the connect sounds keep clicking. Don't you mean to say keep clicking from white HTC screen till 10-15 seconds after the 2nd sound(the connect sound) So basically clicking for over 30seconds.
Please clarify as I'm thinking you meant differently thne what you typed. I too have a stock 2G sandisk card that came with my phone and so want to get this rooted without buying a PNY card hah.
- Pete
Click to expand...
Click to collapse
Basically once the white screen comes up, start clicking the card in and out until about 10, 15 seconds after the 2nd connect sound that windows give you. However, you MUST start pushing the card in and out before the 1st disconnect sound.
Okay cool. Fingers crossed I have been trying since yesterday and about to jump out the window hah.
- Pete
Wow, I got it first time with this method! Thanks a lot! I am also using the stock 2gb card that came with the phone.
Thanks man. I got this to work twice in about 4 tries. 1st time it worked I accidently selected reboot option. So had to retry this method. My clicks were medium speed not very fast and not excessively slow in case that helps anyone. About 1 a second.
- Pete
(2G Sandisk Rooter hehe)
Hey this method worked to get the error but I can not write to the SDCard, I get the following when I try to push something: failed to copy 'busybox' to 'sdcard/busybox: Permission Denied
It is the same with any file and I did Apply sdcard:update.zip
Please help!
I think this will help
KingJ50 said:
Hey this method worked to get the error but I can not write to the SDCard, I get the following when I try to push something: failed to copy 'busybox' to 'sdcard/busybox: Permission Denied
It is the same with any file and I did Apply sdcard:update.zip
Please help!
Click to expand...
Click to collapse
Once you get error, I believe that you need to run the "apply update.zip" once and let it fail. Then you can adb to the sdcard.
PS, this method never worked for me, no matter how much I tried.
dreamersipaq said:
Once you get error, I believe that you need to run the "apply update.zip" once and let it fail. Then you can adb to the sdcard.
PS, this method never worked for me, no matter how much I tried.
Click to expand...
Click to collapse
Same here, i still can't get to adb shell . . .
I got into adb doing the click on the 3d try but it kept failing to push the payload and then I accidentally restarted the phone. AHHHH, just spent 30 minutes doing the same thing and couldn't get back in.
Awesome, I got it to work using your method.
First I tried the "10 min..." video, but it was unclear in some areas. I had to try a few times (10+) to get it to work. Problem for me was the speed at which I was putting in and out the SD Card. I did it at some odd pattern like In (4 sec), out (.5 Sec), in (4 sec), etc. Then all of a sudden it worked.
Got it rooted .
Thanks again!
Finally got it. Thanks
Spent probably 6 hours messing with it. Not worth it anymore.
What does this mean:
8. connect the phone to the pc and use the modified inf file of Android SDK usb_driver to get the phone connected and drivers installed.
Click to expand...
Click to collapse
I've connected the phone, it shows up when I type "adb devices", but I have no idea how to "use the modified inf file... to get the phone connected and drivers installed."
dmauro said:
What does this mean:
I've connected the phone, it shows up when I type "adb devices", but I have no idea how to "use the modified inf file... to get the phone connected and drivers installed."
Click to expand...
Click to collapse
if your phone shows up then you may proceed further. Howerver if after quite a few tries you still can't root then you should try updating the driver with the modified inf file.
go to your device manager, you should see the very first item should be Android Phone. right click on the phone and choose update driver and point to the modified INF file.
if your pc tells you that it cannot find a better driver, just uninstall the phone from device manager (right click and choose uninstall), unplug the phone from the pc, wait about a minute and plug the phone back in - but use a different usb port just in case. Then when found new hardware manager comes up point it to the modified INF file.
Good luck.
Doesnt work for me. annoying
*edit* Finally got it 7 seconds awesome
I cannot get my inc to take the driver .inf file. I have edited it correctly, tried forcing the driver to it, and it keeps telling me that the driver is not valid for a 64-bit os. Tried doing it as a legacy device as well.
Win 7 ultimate 64-bit
dont see the plus sign
hit the plus sign in the right window for the repository well for some reason i dont see any plus sign in there to hit tell me what i might be doing wrong
Please Help If You Can
I am logged in; got the recovery; followed the instructions, and it didn't say unrevoked. so i did it again and
did a whole bunch of things
Finding update packge
opening update package
verifying update package
installing update
veridying curernt system
unpacking patches
removing unneeded files
patching system fioles
symlinks and permission s...
then I got
e:multiple firmware images
e: can't store zip image
installation aborted
Now I also cant get into ADB SHELL
when I type adb shell I get
- exec '/system/bin/sh' failed: No such file or directory (2) -
but no prompt
I will try to stay logged in and everything BUT PLEASE HELP. What do I do?
Thanks for these instructions, Op.
I was successful by exactly following your steps.
Edit to provide additional details -- I tried unsuccessfully upwards of 100 times following the instructions in the 10min video. A couple things that probably attributed to the success of this method for me:
1) Formatted 2GB card to FAT32 (4096) as recommended.
2) Uninstalled HTC Sync / HTC Driver Installer. I used the "SDK Setup" to download the USB drivers.
A tip if you're having trouble getting the USB drivers to download... I had to go to the "Settings" menu in the Android SDK and AVD Manager, and check the "Force https://... sources to be fetched using http://..." otherwise the Available Packages menu would fail to get the repository.xml.
I then applied the recommended changes to android_winusb.inf in C:\sdk\usb_driver\ and used this .inf as the Android Phone driver. It was possible to assign the driver after setting to "Debug" mode in the OS.
3) I started clicking the SD card as soon as the white screen would come up, instead of waiting for a few seconds after it appeared. I used a 2 seconds in, .5 seconds out, 2 seconds in, ... pattern.
4) After each failed attempt, instead of pulling the battery and holding volume- + pwr, I went with the ops method. This was to abort the "loop" tool on the PC, pull the battery, boot the phone normally to the OS, verify the phone was recognized by typing "adb devices" on the PC cmd prompt, commanding "adb reboot recovery" to reset the phone into recovery mode, starting "loop" as soon as the command prompt came back, and finally clicking the SD card as described above.
Hi everyone, since the root thread is so bogged down, I thought I'd try posting a new thread. I couldn't find anyone else that was getting the same messages as me, and I suspect they are what's preventing me from getting root.
Whenever I start steps 1, 2, or 4 I get a constant stream of "ABD server is out of date. Killing..." and sometimes a "ADB server didn't ACK"
Any ideas?
adrianoftyriel said:
Hi everyone, since the root thread is so bogged down, I thought I'd try posting a new thread. I couldn't find anyone else that was getting the same messages as me, and I suspect they are what's preventing me from getting root.
Whenever I start steps 1, 2, or 4 I get a constant stream of "ABD server is out of date. Killing..." and sometimes a "ADB server didn't ACK"
Any ideas?
Click to expand...
Click to collapse
The "ADB server is out of date. Killing..." is not a real problem. It just means that there is still an instance of the ADB server running but not active/connected anymore and it should kill the server and start a new instance.
If you get the "ADB server didn't ACK" though it might mean that your X10 deivce isn't properly connected or something. Make sure it's plugged into USB and you are using the same USB bus, also make sure that USB Debugging is enabled on the phone.
Mod. edit: not dev related, moved to general
what concerns me is that I'm getting the error CONSTANTLY... as if it's killing its own process, then starting it again.
I had the same problem. I forgot that I added the adb.exe from the AndroidSDK folder to the Windows path variable. I solved it with deleting the adb files from the "step" folders in the rooting folder so it used the existed adb command, worked without problems then.
Sent from my X10i using Tapatalk
Well, I deleted the adb.exe files, and then nothing worked, it just said adb was not a recognized command. Still haven't got root. Ugh.
No one else has any suggestions??
adrianoftyriel said:
No one else has any suggestions??
Click to expand...
Click to collapse
Did you checked in Taskmanager if there is a second adb process running already ? If so kill it and try again.
I checked and couldn't find one. I just finished rooting on another machine. I finally gave up on my laptop doing it.
Sent from my X10a using XDA App
Restart your pc, and retry, that's works for me!
starfishguts said:
Restart your pc, and retry, that's works for me!
Click to expand...
Click to collapse
Buddy, have you checked the date of the post you have just replied to.
Everything was workinhg great last night but today when i connect my phone and go into command when i type adb remount it says device not found...do i have to delete my entire android sdk folder
extra info:connection type is charge
usb debugging is on
-thnx
Try rebooting the phone and the computer.
HeroMeng said:
Try rebooting the phone and the computer.
Click to expand...
Click to collapse
Lol so simple and i was getting pissed xD thanks but it only worked the 1st time
Hey guys I an having the darnest time root this guy should be easy with these one clickers programs.
Pretty sure its a driver thing, note I can see the device when in cmd and doing the adb devices that shows up. just gets hung up at the end there.
attached a pic of what the cmd line looks like
anybody have the current drivers, googling for them just yields me to forum posts asking where the drivers are
thirty views and nothing
ok its not a driver issue if your loading root.sh (the big block of text) the issue is that the adb server isnt starting back up in time in order for your device to be recognized. solution? open up the bat file and copy and paste the commands one at a time; or if you have a linux/osx computer try doing it there with my scripts in my sig
couple ideas..
1.open up the run.bat file in notepad or similar and go through all the commands manually, that way you have control on speed of commands and allow enough time for adb to startup again.
2. open up the run.bat file and increase the wait time in the script.. -w 3000 or something like that..
i would suggest you do commands manually. The one-click root did not work for me but doing things manually worked right away.
How to do it
Hey man this is how I got it to work. I was having all the problems device not found etc etc. Have been trying since Sunday. What I finally did after installing the drivers was restart the computer and Phone. After that i tried to run the program it failed with device not found again so i unplugged the usb cable from the phone and closed the cmd window. And also brought up Task manager and killed the adb.exe process. then i reran the run.bat file and this time when it gets to the adb restart relogin apart i killed the SMALLEST ADB.EXE IN THE PROCESS TAB OF TASK MANAGER and that is when it finally got it to work. Had to do the same when I tested it with the uninstaller. So that seems to work. If anyone has any questions feel free to pm me.
But thank god it finally worked.
David
other people have done this and it worked for them also.
I tried all kinds of stuff ultimately I ended up using an xp machine. I later remembered the whole xp mode in windows 7 but didn't actually try it ... win7 just gave me a hard time although the post about changing the amount of time to restart adb makes sense
Sent from my SPH-D700 using XDA App
will try all of that thankyou gents
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.
Perfect, worked. Thanks!
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.
I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.
I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.
SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.
after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.
I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.
thanks to the adb kill-server guy! worked for me
gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto