Hello, recently I've ran into a stupid problem after unlocking bootloader on my M7. Here is what happened, after unlocking I was not able to use my phone in debugging mode, the authorization pop-up didn't show up wherever I connected my phone to PC in ADB mode. This was not Drivers fault I just lost RSA Key, I managed to get it back, I hope it will help you also.
To get RSA keys you need to do next thing.The trick is to create the .android directory elsewhere, for example on the SD Card:
You need Android Terminal Emulator and Root for this operation. ( Link to Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en )
Open Android Terminal Emulator and write:
adb kill-server
HOME=/sdcard adb start-server
At this point you should have /sdcard/.android and the 2 keys in it.
Then just copy adbkey from your phone to your computer into C:/Users/YOURNAME/.android then write in terminal.
stop adbd
start adbd
Then connect you phone in ADB mode Wifi or USB and check again:
adb kill-server
adb start-server
adb devices
Now authorization prompt should pop up!
This issue is also known as Unauthorized device in ADB mode.
Good luck!
Related
When i try typing " adb devices" in CMD.
I get
"list of devices attached"
what am i doing wrong?
You need to be in bootloader, turn off, then turn on while pressing and holding the trackball. Make sure USB debug is enabled in the N1 Applications setting.
did as u said still the same thing "list of devices attached"
i downloaded latest sdk2.0
and did all as the google page says. its weire why it doest read ADB
fastboot read fine when i write fastboot devices, it show the serial of the phone...
can i add applications through fastboot? instead of adb?
did as u said still the same thing "list of devices attached"
i downloaded latest sdk2.0
and did all as the google page says. its weire why it doest read ADB
fastboot read fine when i write fastboot devices, it show the serial of the phone...
can i add applications through fastboot? instead of adb?
I have the exact same problem. Did you ever figure it out?
What directory are you working out of? If you did the default install of the Android SDK. Try this:
Code:
cd c:\android-sdk-windows\tools
Then:
Code:
adb devices
You have to open the command prompt from within the tools folder from sdk folder.
Also, its never worked for me while my phone is in the bootloader, i run abd commands while my phone is booted normally (with debugging enabled).
I use adb shell stop, adb remount, whatever commands you wanted to do originally, adb shell reboot.
Hope that helps, good luck man.
Sounds like maybe the driver isn't installed correctly. Check your device manager and see if the N1 shows up in there and what it's named.
tamarian said:
You need to be in bootloader, turn off, then turn on while pressing and holding the trackball. Make sure USB debug is enabled in the N1 Applications setting.
Click to expand...
Click to collapse
That is fastboot, fastboot for the bootloader, ADB for everywhere else
Are you on windows or linux?
Also try "adb remount" when you are in the /tools folder, then try "adb devices"
Make sure USB Debugging is on..that could be it
I've searched a lot, but did not find a solution.
When I connect my HTC Kaiser with Android Ion 1.5 on the top to my Linux box (all UDEV settings are as recommended), the adb utility (launched as root) does not recognize it correctly. It shows a set of questionmarks instead of the device name:
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? device
adb basic commands (pull/push/install/shell) work, though, but DDMS does not work and I can't debug my application when the device is attached.
Does somebody have a solution?
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
it is root
Super Jamie said:
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
Click to expand...
Click to collapse
Like I mentioned in my question - I do run adb as root.
When it's launched not as root, I can not even do "adb shell" and
"adb devices" shows:
"????????????? Permission denied". So, it is root, I assure.
BTW, on my work Windows 2k3 machine I can use ddms, but
"adb devices" still shows some garbage letters instead of the device name.
Sorry for my English, if my explanation is not clear.
Hey Guys,
I Clockwork3'd my Aria, but I wanted to update my sources (thread 730398) so I can get non market apps. When I follow the instructions in that post I get an error:
Code:
./adb remount
remount failed: operation not permitted
'adb devices' does show my Aria's SN, I'm su'd and I'm running in debug mode. I also chowned everything in the android sdk tools and its subdirectories.
Here's the question -
In searching, I found (thread 614645) that suggested ro.secure wasn't set properly, and sure enough if I do:
Code:
./adb shell
$ getprop ro.secure
1
$
Shouldn't applying clockwork have set that properly? Would the instructions at (thread 8041739 post 9 ) be the right steps to resolve this on an Aria?
Thanks!
PS - sorry I can't post direct links.
if you have all the drivers installed, it should work...
which OS are you using?? (Mac, Win7, etc)
dont rund SDK command in Clockwork, with phone on connect data cable and select "charge only" when asked.
the ./ command is used for Linux i think, i never got that command to work either. just go to the folder where SDK/Tools is located in CMD prompt or Terminal(depending on the OS) and run the following command:
adb remount
hope this helps a bit
I had a lot of issues with driver installs on Windows 7, so I'm doing this on a netbook with Ubuntu netbook remix. Also tried the reflash CD, similar issue.
Right, so with Ubuntu, and the cable my phone came with (have tried a few others just in case)
1. phone on and operational
2. plug in to laptop
3. phone gives happy USB connected and Charge Only notifications
4. fire up terminal window, and su
5. type ./adb remount
and I get the error above. If I do kill-server to refresh it, I get the demon starting successfully on port 5037.
Yeah, I was hoping I'd just missed something stupid. Should I need to modify the boot.img file outside of what Clockwork did?
My symptoms match those described in thread 685146 post #3, however, I've only applied Clockwork (which seems to work) not done anything else funky.
I have my windows 7 machine at the same point now -
adb remount gives 'remount failed: operation not permitted'
and
getprop ro.secure at the adb shell returns 1.
I think this means there's something wrong on the phone, if both machines act the same.
One other data point, I noticed the new Superuser Permissions app that installing clockwork gave me is asking to give superuser permissions to /system/bin/sh when I try to run the adb shell, but it doesn't trigger that when I do the adb remount.
Not sure what this means, any ideas most welcome - TIA!
steps here fixed it, thanks - http://forum.xda-developers.com/showthread.php?t=730398
First of all, I have the T-Mobile G2 with the Gingerbread OTA update. I am running Ubuntu 11.10 on a netbook. I have tried to follow the instructions for rooting my phone, but I am getting stuck trying to install the Google USB driver in the SDK manager. Any suggestions on how to get past this roadblock?
mrfilbert said:
First of all, I have the T-Mobile G2 with the Gingerbread OTA update. I am running Ubuntu 11.10 on a netbook. I have tried to follow the instructions for rooting my phone, but I am getting stuck trying to install the Google USB driver in the SDK manager. Any suggestions on how to get past this roadblock?
Click to expand...
Click to collapse
no need for usb drivers in linux
you have to be sure that you are su on your pc... (i have fedora)
i think ubunto it´s sudo, isn´t it?
and before you can see your device through adb you have to type "./adb kill-server" and then "./adb start-server"
... then "./adb devices" and so on
Thanks. I tried ./adb devices and it gave me the following:
List of devices attached
???????????? no permissions
???????????? no permissions
Since I do not see a serial number, do I need to re-install something?
mrfilbert said:
Thanks. I tried ./adb devices and it gave me the following:
List of devices attached
???????????? no permissions
???????????? no permissions
Since I do not see a serial number, do I need to re-install something?
Click to expand...
Click to collapse
no that happens because you are not root on your pc...
in fedora i have to do the following to see my device:
su (enter)
then enter password
i get this symbol: # = means i´m root on my pc
then i go to my platform-tools directory (cd whatever)
./adb kill-server
./adb start-server
./adb devices ...now you should see your device
then start the rooting procedure, good luck
Use 'sudo su' in ubuntu to get a root prompt.
otherwise you have to set a 51-android.rules file (instructions here http://developer.android.com/guide/developing/device.html)
-Nipqer
I managed to install the drivers but how do I open the shell? I want to access some lost files.
I followed the instructions but adb_usb.ini was nowhere to be found so I had to create it.
I have to control ADB via cmd.exe right? Anyone can guide me?
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/Android_Debug_Bridge
Ok, to get to a shell on the Nook you have to use a shell on the host computer.
In Windows, a shell is known as cmd.exe, "MS-DOS Prompt" or command.
That's the (by default) black window with text.
You can start a Windows shell through the Program list if a shortcut already exists.
If not, you can start it by holding down the Windows key, hitting "R" and typing cmd.exe in the box.
The little box is in a sense already a shell, but it makes a bigger looking shell.
The program adb.exe is the one that you will run to interact with your Nook.
You will have to either be in the same directory as where adb.exe or else have that directory in your PATH.
There are a bunch of commands that you can use (documented in the second link above).
You must first tell ADB how to connect to your device through either a "connect" (for WiFi) or "usb".
Once you are connected you can issue the other commands.
Code:
adb shell
This will let your Windows shell access a shell on your Nook.
Since this is an entirely different system, the commands are different.
In Windows, to list files you type "dir", in Linux (the basis of Android), you type "ls".
I can get to the directory of adb.exe on command.
I don't get it what am I supposed to do next.
If I run adb.exe it starts to load something and then nothing. The Nook is connected, it has Noogie as it's CWR.
After running adb.exe what do I do? Do I go to the nook directory or something? The thing is that I don't even know if I'm running ADB correctly. I followed everything on the wiki
vdguzman said:
it has Noogie as it's CWR.
Click to expand...
Click to collapse
Um, Clockwork Recovery and Noogie are two separate and unrelated things.
Code:
C:\>adb usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
At that point it will either say that it found a USB device or that it didn't.
If it's connected, you can type "adb shell".
On Windows, when you click on the USB icon on the taskbar it will list what is connected.
Normally with CWR you should see two lines, USB Mass Storage and ADB.