Adbd's $ADB_VENDOR_KEYS is not set - Samsung Galaxy J7 Questions & Answers

Ive been trying to fix this but cant find a concrete answer.. when im trying to use adb i get this message.. should add its only with my custom stock boot image that it is having this problem. The official stock boot image i can use adb no problem.

Should note my adbd in my ramdisk is a adbd kernel file from chainfire adbd insecure application which i got rid of stock adbd and replaced it with a better one..

scary alien
Moderator @ android forums
Well, my first thought about "device unauthorized" with regard to adb is that the device you're trying to connect to/with has not been authorized from the pop-up dialog that you get when you first connect via adb (the "Allow USB debugging?" RSA fingerprint pop-up -- we discussed this in one of your other adb thread, Lana).
If you don't or can't authorize the device from this pop-up--which would certainly be difficult (impossible) to do with a non-working touchscreen, then I'm afraid @lordvincent 90 's suggestion about using adb with your device when it's in custom recovery (where it won't / shouldn't ask for authentication) is probably your only recourse.
The only gotcha with regard to that would be if you had to disable MTP from the custom recovery screens in order to get adb to work (I know I have to on my N5--don't know about the Samsung Galaxy Tablet, though).
edit: I don't believe the stuff about the ADB_VENDOR_KEYS is necessarily relevant if you haven't and/or can't authorize/authenticate the connecting device. I'm guessing this is the page where you read about deleting the adbkey file?
http://stackoverflow.com/questions/32132434/set-adb-vendor-keys​
This is the closest i got to a working answer.. i guess using a custom recovery for adb bypasses the need to have to verify the rsa fingerprint... but i dont have a custom recovery to test and not sure about if stock recovery bypasses it too or if its just the custom recovery.

JUST RESOLVED THIS PESKY ISSUE
Please reaв my answer on SO:
http://stackoverflow.com/a/42052776/3278855

Related

[Q] Fastboot problem

hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz

Device not being detected in recovery mode?

I'm trying to install the 4.4.1 update but my device isn't being detected in recovery mode and thus adb sideload is not working. Would really appreciate some help. I've tried almost every solution that I've googled and nothing seems to be working.
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Sent from my Nexus 5 using xda app-developers app
jkimbro said:
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Click to expand...
Click to collapse
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
You just need the Google drivers from their website:
http://developer.android.com/sdk/win-usb.html
I had to force the installation of the drivers for the "AOSP on Hammerhead" device in the device manager.
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
I used USB ADB Composite Interface or something like that by pointing the device manager's Update Driver dialog to the USB drivers from the SDK that EddyOS pointed at.
Windows 7 x64
Yep, had issues with my work PC (Win 7 Pro x64) - had to manually point Device Manager to the android_winusb.inf so it would find the drivers. Bit of a ballache but all working after that!
greenkabbage said:
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
Click to expand...
Click to collapse
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
a hammerhead wrote this.
beekay201 said:
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
Click to expand...
Click to collapse
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
jt3 said:
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2513339
jt3 said:
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
Click to expand...
Click to collapse
Try it. Select "apply update from ADB", and then try to get a ADB prompt like you would normally, you know, ls /sdcard/, something.

[Completed] [Q] Interrupted flashing process

Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.
Hi,
Thanks for using XDA Assist please post here Android Q&A, Help & Troubleshooting
Good Luck!

Samsung M30s Not Recognized By PC Via USB

Hello Everyone..!
I Am Using Samsung M30s [Rooted]
[Please Read Patiently]​4 To 5 Months Ago My Phone MTP Stopped Working.
Still Finding Solutions.
My Device Can't Be Recognized As A MTP Device By Any PC Via USB.
I Tried Many Cables And Many PCs.
My Phone Doesn't Show Fast Charging Since It Started Not Recognized By PC.
I Watched Almost All YouTube Videos About This Issue None Of Them Worked.
I Think It Would Be Charging Port Problem But I Am So Confused.
Please Help And Suggest Me Someting.
Whenever I Restart Or Switch-Off From Home Button My Root Getting Lost.
I Have To Click Factory Reset To Get Into Recovery In Order To Restore Root.
[I TRIED 100+ METHODS. I DID EVERYTHING BUT NO LEAD]
Thank You.!​
In Android settings enable USB-MTP mode if not done yet.
BTW: If in phone's USB-options PTP is listed but not MTP, then maybe what Android may refer to as "File transfer" is the same as MTP.
Thanks For Your Reply But Sadly It Is Not The Problem.
As I Mentioned Above I Explored Almost All YouTube Videos On Related Topic.
This Is Not The Problem.
BTW Thanks...
cursedhawk said:
Hello Everyone..!
I Am Using Samsung M30s [Rooted]
[Please Read Patiently]​4 To 5 Months Ago My Phone MTP Stopped Working.
Still Finding Solutions.
My Device Can't Be Recognized As A MTP Device By Any PC Via USB.
I Tried Many Cables And Many PCs.
My Phone Doesn't Show Fast Charging Since It Started Not Recognized By PC.
I Watched Almost All YouTube Videos About This Issue None Of Them Worked.
I Think It Would Be Charging Port Problem But I Am So Confused.
Please Help And Suggest Me Someting.
Whenever I Restart Or Switch-Off From Home Button My Root Getting Lost.
I Have To Click Factory Reset To Get Into Recovery In Order To Restore Root.
[I TRIED 100+ METHODS. I DID EVERYTHING BUT NO LEAD]
Thank You.!​
Click to expand...
Click to collapse
The USB issues might be a hardware problem, the port itself might be faulty or maybe the soldering around the pins where it connects to your main board may need re-flowing due to breakdown from heat. Have you tried using wireless methods of transferring files between your device and PC?
But I don't see how that has anything to do with your device losing root. These issues may or may not be related.
Is your bootloader unlocked(OEM unlock)?
Do you have stock recovery or custom recovery?
What method did you use to root the device?
Hello Brother Thank You For Your Reply...
And I Will Sure Check Out My Charging Pin.
I Thought It Could Be
Soon If I Discover Something I'll Tell You
And One More Thing. I Used A Method From YouTube Channel AndroidHowTo 10 Months Ago.
I Have TWRP Custom Recovery.(But I Can't Boot Into It) [Because Of This USB Problem]
I Have Root.
Bootloader Unlocked.
cursedhawk said:
Hello Brother Thank You For Your Reply...
And I Will Sure Check Out My Charging Pin.
I Thought It Could Be
Soon If I Discover Something I'll Tell You
And One More Thing. I Used A Method From YouTube Channel AndroidHowTo 10 Months Ago.
I Have TWRP Custom Recovery.(But I Can't Boot Into It) [Because Of This USB Problem]
I Have Root.
Bootloader Unlocked.
Click to expand...
Click to collapse
When you installed TWRP, what method did you use to install it? Which rooting method did you use, SuperSu or Magisk? Did your rooting method include flashing DM-verity?
Can you give me a link to the specific guide/video that you followed?
Install a terminal emulator app on the device, open the app and type the following commands:
su (press enter, grant superuser permission if prompted)
Then type:
reboot recovery
If you are properly rooted, have granted su permission to terminal emulator and if TWRP is properly installed in the correct partition, this should boot you into TWRP.
You may have overlooked a step or you may have missed a detail somewhere in your rooting method. Or you may have used an incorrect method or file for your specific device. Your device might require something that wasn't in the guide that you followed.
Off the top of my head, those are possible causes of your issue, I may think of others, if I do, I'll post them here.
Droidriven said:
When you installed TWRP, what method did you use to install it? Which rooting method did you use, SuperSu or Magisk? Did your rooting method include flashing DM-verity?
Can you give me a link to the specific guide/video that you followed?
Install a terminal emulator app on the device, open the app and type the following commands:
su (press enter, grant superuser permission if prompted)
Then type:
reboot recovery
If you are properly rooted, have granted su permission to terminal emulator and if TWRP is properly installed in the correct partition, this should boot you into TWRP.
You may have overlooked a step or you may have missed a detail somewhere in your rooting method. Or you may have used an incorrect method or file for your specific device. Your device might require something that wasn't in the guide that you followed.
Off the top of my head, those are possible causes of your issue, I may think of others, if I do, I'll post them here.
Click to expand...
Click to collapse
The Video Guide I Followed While Rooting.
I Did All The Guy Did.
The Method You Told That Using "reboot recovery" Code In Terminal Emulator Is Booting As Usual Like ReBooting.
Doesn't Seems TWRP Exists
Thank You For Your Help..!
And I Wanted To Change The Port But When I Go To Nearby Service Centers They Are Not Seem To Be Right...!
They Told Me To Reset But I Can't Do It.
Whenever I Click On Factory Resett It Just Reboots
I Can't Reset My Phone.
But The Service Guys May Not Know About The Problem
I Have To Send It To A Samsung Repair Center

[SOLVED] confused noob - adb/fastboot : install or just run?

Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.

Categories

Resources