(J710MN) Adb says unauthorized - Samsung Galaxy J7 Questions & Answers

Hello i need some help i just flashed my J710MN with DeluxeROM_v3 (Android 7 Nougat)
im trying to fix my phone certificate and when i open ADB devices says unauthorized, I already activate the developer options and put the debbug usb ON, i cant revoke the debbug because it doesnt show on options what can i do?
** i don't get a prompt on the phone to tell my i must accept the connection **

Related

I'm rooted! but I have a problem. (Help)

When I try to run the spoof-cid. It says the following...
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device.
Press any key to continue . . .
It is rooted, and it does have usb debugging enabled. Mildly frustrating to say the least.
Following instructions from Here http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Do you have ADB set up properly? you can check by running adb devices and see if your device gets listed. Also, you can go to your device manager and see if your phone shows up to check if your drivers are set up properly by looking for "myHTC" or "android device".

This is how you disable the annoying heads up notifications in Nougat without root :)

Hello guys i found a way to disable the irritating heads up notifications on my a3 2017 without root this also have to work on other nougat devices from samsung s6,s7,s8 lets start.
first download and install this program and say Y to everything and install driver when it asks for it, and then go and enable developer options on your phone by going to settings, about phone, software info and click 7 times on buildnummer now its enabled, enable OEM unlock, USB debugging and disable verify apps via adb after that connect phone to computer and it wil ask for connection just grant it, open cmd and typ adb devices push enter now your phone will be in the list after that just typ this adb shell settings put global heads_up_notifications_enabled 0 and push enter again wait 2 seconds restart your phone and goodbye heads up notifications

"error: no device/emulator found" in fastboot

As the title says.
I'm trying to unlock the bootloader on my XZs so I can root it.
My device is listed normally when turned on w/ the command window, but in fastboot mode it disappears and when I try a command, an error comes up saying ""error: no device/emulator found". (see attached image)
As far as I'm concerned, I have all the necessary drivers, I've tried on another PC, the result is always the same.
And when I try to change the drivers (Via Device Manager>Update Driver>Browse My Computer...>Let me pick...>Have Disk...)
I get yet another error saying "The folder you specified doesn't contain a compatible software driver for your device..."
Can someone please give me a solution. This has been asked before on XDA by someone else (that thread has no replies). It seems it's always us little guys with actual problems which need solving who get little to no help at all here.
Reinstall driver again.
It doesn't work. The problem is I want to install the Google USB drivers for my Xperia phone but Windows 10 will not let me and driver signing seems to be impossible to disable (currently typing this on my laptop while it's in test mode).
1. Turn off your phone. Boot in to fastboot mode and plug the cable. After your heard the sound from the computer for new device found. Go to device manager look to usb S1 device. Reinstall driver by manual choose (do not search) from the menu with the name is Android Google. When prompt for install. Choose install anyway. After successful install driver, please check status from flashtool to make sure your device show connected in fastboot.
2. Change the usb port. Sometimes you get problem with usb port 2.0 and 3.0
Hope you can fix it asap.
Nothing by the name of 'Android Google' appears in the menu when selecting new drivers.
I clicked on 'S1boot Fastboot' under 'other devices' in Device Manager and clicked on update driver
>Browse Computer
>Let me pick
- and then there's something similar called 'Android Device' but no 'Android Google' so I click on that
- then I get three options:
Android ADB Interface Version 11.0.0.0
Android Bootloader Interface Version 11.0.0.0
Android Composite ADB Interface Version 11.0.0.0
None of them worked when I tried.
I think the solution is to have the phone on, with USB debugging enabled, connect via USB to PC, test your adb devices again, if all good, go ahead and
Rich (BB code):
adb reboot fastboot
This is because some phones use Fastbootd (notice the d..).

Pixel 2 broken screen, Need to recover a file

Hi,
I tried lots of things! Can't do anything yet... I really need that file.
My USB debugging is not turned on, if it was I'll be ok. I found that if you copy the adbkey.pub from your users directory to the phone it
will bypass the USB debugging function, but can't push it with adb.
I can only boot in recovery and use fastboot or adb but with no access to the phone... I don't have TWRP installed.
I tried to flash TWRP with: fastboot flash recovery twrp.img
and I got an error telling me: FAILED (remote: 'No such partition.')
Probably because USB debug is not enabled... again...?
EDIT: tried to make me a walkthrough for the keyboard using a working phone, I can get up to the settings app, there's no focus on the settings items so I can't select them...
- I have access to the fingerprint sensor, but not gonna do much since I rebooted the phone i'll need to enter the unlock code.
- I can plug in a keyboard/mouse combo in my phone, for this to work i'll need a walkthough for arrows key/enter key to press to I can enable USB debugging.
- The screen is broken(black) touch sensor also broken.
- The phone is not rooted but is OEM unlocked
- I tried several software to mirror screen, they all require USB debugging enable or accept something on the phone or both.
- I know where the file is located on the phone but I don't know it's exact name (it's a .mp3 file, not a song ) it's in /storage/emulated/0/Recorders
Any help is greatly appreciated.
Thank you

[How-To]ADB not able to recognize device

I tried running the command - ADB devices, and it does not show my device, but when I run the command fastboot devices, then I can see my device.
I am using this to take a backup and remove the pattern from my phone as I forgot the pin here.
But most functionality is present with the ADB command.
A lot of posts have suggested checking if the USB Debugging option was on, and MTP is on, but since the phone is password locked, I am unable to check either of them.
Can you please help me out, as this phone has a lot of data that needs to be recovered?
Mija21 said:
I tried running the command - ADB devices, and it does not show my device, but when I run the command fastboot devices, then I can see my device.
I am using this to take a backup and remove the pattern from my phone as I forgot the pin here.
But most functionality is present with the ADB command.
A lot of posts have suggested checking if the USB Debugging option was on, and MTP is on, but since the phone is password locked, I am unable to check either of them.
Can you please help me out, as this phone has a lot of data that needs to be recovered?
Click to expand...
Click to collapse
I was able to get the ADB device detected by entering the recovery mode. Previously I was trying to run the command while in fastboot mode.
So I have now been able to get the ADB devices, but now I am getting device unauthorized, due to which I am unable to enter the shell.
Is there any way, where I can use ADB without clicking on the device for authorization.
Thank You in advance
If
Code:
adb devices
doesn't show your phone as connected then a connection couldn't get established. Point.
FYI: The major reason why you get "Unauthorized Error" is that you haven’t authorized your PC to recognize your device in ADB Mode. You probably haven't enabled the USB Debugging on your device and that is where you are getting the alphanumeric code. The "unauthorized message" is because you haven’t given your permissions to authorize this connection.
jwoegerbauer said:
If
Code:
adb devices
doesn't show your phone as connected then a connection couldn't get established. Point.
FYI: The major reason why you get "Unauthorized Error" is that you haven’t authorized your PC to recognize your device in ADB Mode. You probably haven't enabled the USB Debugging on your device and that is where you are getting the alphanumeric code. The "unauthorized message" is because you haven’t given your permissions to authorize this connection.
Click to expand...
Click to collapse
@jwoegerbauer That might be the case, but now there is no way to check and change or authorize as my device is locked and I do not remember the password. Is there any way I can bypass or get around this step.
Mija21 said:
@jwoegerbauer That might be the case, but now there is no way to check and change or authorize as my device is locked and I do not remember the password. Is there any way I can bypass or get around this step.
Click to expand...
Click to collapse
factory reset

Categories

Resources