Hello,
I just recently purchased a new Samsung Galaxy Note 3 (N900T) and I am having problems with adb. Whenever I launch adb shell .... It says "Error: Device Unauthorized. Please Check the confirmation dialog on your device." However, this is no confirmation dialog. There has never been one. I do have USB Debugging Enabled, and I have tried disabling it and re-enabling it and it still does not ask me to authorize the device on my phone. I have also restarted the phone, and the computer. Nothing seems to work, and I can not use adb due to this issue.
There is also no "adb_key" file located in /data/misc/adb/ or in the .android folder on my pc.
Can anyone tell me how to authorize my device so I can use adb?
Hi.
Don't know if you found an answer on your problem but I have an Note 3 SM-N9005 an what i have done was to delete the adb folder in /data/misc and then the authorise popup poped up assoon as i plugged my phone into the pc. But just extra info on adb If you want to use adb debugging shell on pc, get the latest version from goolge.
Hope this helped. This worked for me.
how if phone on bootloop, so we can't see pop up confirmation.
any idea?
Clear Auth first, then retry.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my leanKernel 3.2 powered stock 4.4.2 (NF1) SM-N900T
toastido said:
Clear Auth first, then retry.
Sent from my leanKernel 3.2 powered stock 4.4.2 (NF1) SM-N900T
Click to expand...
Click to collapse
i repeat, how if phone on bootloop, so we can't see pop up confirmation.
just stuck at logo.
monkey_kungfu said:
i repeat, how if phone on bootloop, so we can't see pop up confirmation.
just stuck at logo.
Click to expand...
Click to collapse
This has nothing to do with adb. i wasn't even replying to you, i was replying to OP, so lose the attitude.
Edit: i now see this was an old thread. That's what you get for posting in a dead thread.
Sent from my leanKernel 3.3 powered stock 4.4.2 (NF1) SM-N900T
oh... i'm so sorry.
can u help me, with that my problem?
edit : i just want a solution
Instruction with Windows PC:
1. Make a copy from C:\Users\User\.android\adbkey.pub
2. Rename it to adb_keys
3. Paste it in your smartphone under /data/misc/adb/adb_keys
4. Restart the smartphone and adb with "adb kill-server" and "adb start-server"
Related
hi firends
How do I know that my phone (legend) is rooted or not?
what are Symptoms for a rooted phone?
Enable usb debugging, install driver, open cmd, type adb shell and press enter. Then type su and if you get this # you are using a rooted rom. If it says access denied you are not.
Liquid211 said:
Enable usb debugging, install driver, open cmd, type adb shell and press enter. Then type su and if you get this # you are using a rooted rom. If it says access denied you are not.
Click to expand...
Click to collapse
1- how to install driver?
2- please see this picture and tell me what is wrong...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you haven't even installed ADB I don't know how you would think your phone is rooted? Did you buy it used?
Anyways. Download this ADB. Unzip to c: and run adb.exe shell from a cmd in c:\android-sdk-windows\tools
But make sure you install the driver first.
Go to Settings, Programs, Development and Tick Off "USB Debugging". Then when you connect your device to your computer it ask for a driver. It can be located in the android-sdk-windows folder under usb_driver.
thanks Liquid211 very much!
Liquid211 said:
... Then when you connect your device to your computer it ask for a driver. It can be located in the android-sdk-windows folder under usb_driver.
Click to expand...
Click to collapse
I have no such folder under "android-sdk-windows". I only see "add-ons", "platform" and "tools"...
just try a app that needs root rights.
for example many screenshot apps need su.
another way would be to look if u ve got the superuser app in ur app menu.
and ofcause a terminal like program could help to indicate if uve got root rights.
Simply download a terminal emulator from market and type 'su'...
Sent from my Legend using Tapatalk
Hi I am new to this forum and I'm not an expert, I really would like to use the webtop without a dock,i tried following the instructions posted here but nothing happens, I don't know what am I missing. Am I supposed to run the install file on my computer or on my phone? When I run it on my computer a black screen appears and some command and then I says to press any key and that my phone will reboot, but nothing happens. Am I supposed to do something to my phone?
I'm on att gingerbread, not rooted, I enabled debugging mode.
Thank you
You need to root and probably deodex
sent from my Atrix via XDA premium
You are probably right, but why then on Fenny's post it says no root or deodex needed??
http://forum.xda-developers.com/showthread.php?t=980193
oh well look at that,
you run the script from your computer but your phone has to be connected and have all the right drivers on your computer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you please be a little more specific, I have the drivers for motorola media link and the phone portal, also for usb connection.
do you know what ADB is and how to use it?
No. I don't know... I just enabled the debugging mode on my phone
clastrag said:
No. I don't know... I just enabled the debugging mode on my phone
Click to expand...
Click to collapse
ok connect your phone to hyhour computer and make sure the computer knows it is connected
then run the script
good advice
If I were you I'd be VERY CAREFUL and investigate and learn all you can BEFORE doing any mods on your phone. Too many phones have been bricked (rendered useless) by running things you know little about.
I did that but the doesn't do anything, it doesn't reboot like it says on the script. I know it's connected because when I enable debugging I see the pop up screen for the internal memory and the sd card
Thanks for your concern I really appreciate it.what I like about this is that doesn't require root
Root
Hi
I also had exactly the same problem.
I wanted webtop, without really rooting my device.
It didnt work out. Also ran the script no reboot etc.
I then rooted my device, Fenny assisted me to create 2 files for the stock 2.2.2 atrix 4g (The older version of the os)
I copied them manually using root explorer, rebooted, and walla, i had the webtop working.
I still have those files.....
If you need them, PM me, its worth a try...
This is weird. I never had this problem with my Galaxy S3.
I've enabled USB Debugging on the phone.
Even toggled it off, rebooted and turned it on again.
I've also rebooted my computer and even updated SDK Toolkit.
No change in problem though.
Every time I try to connect to my phone from ADB, it just tells me the device is offline (see attached pic).
Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
StolenVW said:
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
I'm not getting any popup for that.
CZ Eddie said:
I'm not getting any popup for that.
Click to expand...
Click to collapse
Try this
http://www.wugfresh.com/faqs/how-to-fix-adb-device-is-listed-as-offline-on-android-4-2-2/
And if you do a Google search for
how to fix adb device offline
It comes up with other things to try
Sent from my A500 using Tapatalk HD
Thanks, I tried the info in that link but never got the pop-up asking for ADB permissions.
I did google prior to posting also. I listed in my OP what I tried (which is what my googling suggested).
I'm about to ODIN back to factory stock anyways. So I'll try again after that. Maybe I messed something up during all the bloatware removal I did yesterday.
Nope, a fresh ODIN install of stock ROM didn't help at all.
Guess I'll have to uninstall & reinstall Android Toolkit maybe.
EDIT:
Using Motochopper root tool, I finally got the popup. And made sure to select "always allow from this computer". I think that should fixit.
EDIT #2:
Nope, that didn't help at all. Still "offline".
EDIT #3:
Actually, using the ADB from Motochopper does work. It's just the ADB from my Android Toolkit that doesn't work.
Sounds like one in android tool kit is out of date
Try updating the android sdk
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Hi!
Whre can I find the Android ID for my S5 ? Need it for Racoon (updates without playstore installed). Tried device ID app but it shows nothing
michael-oc said:
Hi!
Whre can I find the Android ID for my S5 ? Need it for Racoon (updates without playstore installed). Tried device ID app but it shows nothing
Click to expand...
Click to collapse
What ID do you mean? (Samsung) serialnumber or IMEI?
In an ADB shell:
settings get secure_id
russ18uk said:
In an ADB shell:
settings get secure_id
Click to expand...
Click to collapse
Not working for me. Settings not found error.
michael-oc said:
Not working for me. Settings not found error.
Click to expand...
Click to collapse
Sorry, my bad.
settings get secure android_id
russ18uk said:
Sorry, my bad.
settings get secure android_id
Click to expand...
Click to collapse
Also not working. I have to do this in recovery right? Tried it in downloader mode but got an error "device not found". In windows device manager it´s labeled as modem?!
michael-oc said:
Also not working. I have to do this in recovery right? Tried it in downloader mode but got an error "device not found". In windows device manager it´s labeled as modem?!
Click to expand...
Click to collapse
Boot up normally. Make sure you have enabled debugging. If you haven't, follow the guide here.
After that download ADB:
USB drivers required;
ADB interface.
Install the drivers and ADB. You can find ADB in your Start Menu or you can open CMD and cd to c:\adb
When you connect your phone to the computer in your CMD window type adb shell. You may get a security prompt on your phone to allow or deny. Tap on allow or similar.
Retype adb shell if needed and you should see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If good type "settings get secure android_id".
Ask if you get stuck anywhere.
Thanks for all your help! It´s working now. This suggested adb drivers are older than mine and working. Strange
SOLVED UPDATED TO LAST OTA AND DID THE WHOLE TUTORIAL AGAIN.
Tried different USB ports. ( 3.0 / 2.0 )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried in 2 different PCs and 6 usb ports 2.0 and 3.0
Windows 8 and windows 10.
Have you tried using cmd (administrator) istead of PowerShell?
Lamizure said:
Have you tried using cmd (administrator) istead of PowerShell?
Click to expand...
Click to collapse
Yes
It's really strange... Have you unlocked the bootloader?
Yes " Device State - Unlocked "
It's due to the filename being too long. I found a different fastboot which allowed long filenames. Rename it to one letter like r.img or something and see if it works.
Had exact the same problem under Linux
People mention to change to another USB port but that did not help
What helped... if all stuff is correctly installed (adb, root rights, etc.)
1. Reboot into the bootloader (even if you are in already)
adb reboot bootloader
Click to expand...
Click to collapse
2. Then directly (use the arrow up key to really be fast enough) send the command for flashing (my file was called twrp.img)
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
If this doesn't work you could try (under Linux) to write a little script with just the two above commands or try
adb reboot bootloader && fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It seems to be a timing problem... One might need to play around with the time between this two commands. E.g. wait until the bootloader screen is on the phone and directly issue the flash command. Sorry after it worked for me I did not bother to investigate it in more detail.