just flashed 8.1.1.0 and adb popup confirmation dialog doesnt not show up. it is shown as unauthorised in adb. i tried installing drivers/reboots with no success. folder data/misc/adb is empty as well.
mmystere68 said:
just flashed 8.1.1.0 and adb popup confirmation dialog doesnt not show up. it is shown as unauthorised in adb. i tried installing drivers/reboots with no success. folder data/misc/adb is empty as well.
Click to expand...
Click to collapse
flash again , you can use mi flash tool
first of all , unlocked bootloader ?
Have you enabled usb debugging?
mmystere68 said:
just flashed 8.1.1.0 and adb popup confirmation dialog doesnt not show up. it is shown as unauthorised in adb. i tried installing drivers/reboots with no success. folder data/misc/adb is empty as well.
Click to expand...
Click to collapse
type in command prompt " adb devices " , then adb popup confirmation should show up , if not try this
unplug device , adb kill-server , adb start-server , plug device
mar.ur said:
type in command prompt " adb devices " , then adb popup confirmation should show up , if not try this
unplug device , adb kill-server , adb start-server , plug device
Click to expand...
Click to collapse
its a usb debugging, you have to allow it first from developer option
tried all of these...none worked.... but i already reverted back to miui 8.0.2.0..... damn miui update sucks....im staying on that build....
Related
i m trying to root my lg p500 v20c ......
i downloaded SuperOneClickv1.9.5-ShortFuse ....
now when i type adb devices command on cmd it says list of devices attached....
but it didn't show any device.....
after that when i type adb shell command ..it says error : device not found...
idk what's happening ??
( i had enabled debugging mode
i m in administrator mode ...)
It wont say p500
instead it will show numbers in list of devices..
this is your device...
Optimus one
CM 6.5.8
Press THANKS if I helped...
Instead of superoneclick use unlockroot
aspee
command is not showing any device......
?????
i just used unroot.exe...
i started it and clicked on root but it saying no omline device.. start debugging mode..
but debugging mode is already on ...???
S.J said:
i just used unroot.exe...
i started it and clicked on root but it saying no omline device.. start debugging mode..
but debugging mode is already on ...???
Click to expand...
Click to collapse
had a similar problem. install PdaNet app to your computer and it'll install correct adb drivers.
Hi!
I have RN2 with MIUI 16.6.7.0 with root access.
ADB v1.0.32
Win 8.1
If I run "adb devices" when phone is running system, I get response "s/n device" as I should. But when I boot phone to recovery (MI-Recovery 2.0.1) I get "s/n unauthorized".
I have tried rebooting PC and phone, disabling and enabling USB debugging, deleting adbkey and adbkey.pub on PC (only instance was in users/user/.android/), revoking USB debugging authorizations, changing USB ports. Nothing.
The last thing I did:
1. reboot phone to system.
2. developer options > turn developer options on/off > turn debugging on/off <> Revoke USB Debugging Authorization
3. reconnect phone to PC
4. was asked: RSA key fingerprint + always allow from this computer > OK
5. run "adb devices" gives "s/n device"
6. disconnect phone
7. power off phone
8. phone to recovery
9. reconnect phone
10. run "adb devices" gives "s/n unautorized"
11. disconnect phone from USB
12. run "adb kill-server"
13. run "adb start-server"
14. reconnect phone
15. run "adb devices" gives "s/n unautorized"
I guess something is wrong with recovery mode on the device. Any ideas?
Thank you
MK
+ run "adb shell" gives " error: device unauthorized. This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device."
+ from hxxps://android.googlesource.com/platform/system/core/+/d5fcafaf41f8ec90986c813f75ec78402096af2d
"On the device, vendors public keys are installed at build time in /adb_keys. User-installed keys are stored in /data/misc/adb/adb_keys."
On my device user-installed keys are stored in /data/misc/adb/adb_keys. The only other instance of adb_keys is /bin/adb_keys. If it has any relevance.
You need to check in the device the popup, the device ask if you want authorize your computer for connection with adb, remember you need to enable adb debug first with push 7 times on miui version into about device.
In recovery adb isn't available you can enable only the adb transfer from the advance menu.
Namaless said:
You need to check in the device the popup, the device ask if you want authorize your computer for connection with adb, remember you need to enable adb debug first with push 7 times on miui version into about device.
Click to expand...
Click to collapse
Hi!
Thanks a million for your reply. :good:
I did all that already in steps 2, 4 and 5 and it worked. My problem is adb in stock recovery mode.
In recovery adb isn't available you can enable only the adb transfer from the advance menu.
Click to expand...
Click to collapse
Damn I have much to learn (hundreds of pages in a few days and I still dont know anything . So stock recovery doesn't come with ADB access and I am trying to do something that can not be done? ClockworkMod recovery for example should have ADB support if I understand correctly?
I also have that proble my device not connected to phone what I do tell me..
Jay's said:
I also have that proble my device not connected to phone what I do tell me..
Click to expand...
Click to collapse
If problem is PC <> phone then install drivers for your phone on PC.
Or describe your problem better.
Poslano z mojega Redmi Note 2 z uporabo Tapatalk
Does enabling OEM Unlock from developer options (Android 5.1.1) unlocks the bootloader?
If yes then can I directly flash a custom recovery after enabling OEM Unlock?
ayu321 said:
Does enabling OEM Unlock from developer options (Android 5.1.1) unlocks the bootloader?
If yes then can I directly flash a custom recovery after enabling OEM Unlock?
Click to expand...
Click to collapse
No, it only gives you permission to unlock bootloader.
You will need to unlock bootloader using adb.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and your phone will reboot normally.
Augustoandro said:
No, it only gives you permission to unlock bootloader.
You will need to unlock bootloader using adb.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and your phone will reboot normally.
Click to expand...
Click to collapse
thnx for the reply augustonandro ! but i think im doing something wrong , whenever i type the command adb reboot bootloader my device(Galaxy J200G) restarts instead of rebooting to bootloader . So I just went to my stock recovery and chose option "reboot to bootloader" but still it restarted instead of rebooting to bootloader.
Am I doing something wrong?
ayu321 said:
thnx for the reply augustonandro ! but i think im doing something wrong , whenever i type the command adb reboot bootloader my device(Galaxy J200G) restarts instead of rebooting to bootloader . So I just went to my stock recovery and chose option "reboot to bootloader" but still it restarted instead of rebooting to bootloader.
Am I doing something wrong?
Click to expand...
Click to collapse
Try "adb reboot download" command
If u try
Setting>Developer Option>
Now search
OEM Unlock and enable
Ashwinrg said:
Try "adb reboot download" command
Click to expand...
Click to collapse
this command reboots to download mode not bootloader
guys i just found out this thread:https://forum.xda-developers.com/galaxy-j2/development/dev-samsung-galaxy-j2-lte-t3258147 and it says that just enable OEM Unlock and your bootloader will be unlocked. Is it true?
No, as explained above. That just allows the bootloader to be unlocked via ADB/fastboot (unless the bootloader is locked down like many ZTE phones).
Have you tried "adb reboot-bootloader"?
HI...I know after so many years....But i am having some problem considering my nokia 5 phone....In developer option the OEM unlock is greyed out and i cannot unlock it at all(i cannot toggle it on)....Any possible way i can turn it on....Let me know....Thanks in advance
Thebisboss said:
HI...I know after so many years....But i am having some problem considering my nokia 5 phone....In developer option the OEM unlock is greyed out and i cannot unlock it at all(i cannot toggle it on)....Any possible way i can turn it on....Let me know....Thanks in advance
Click to expand...
Click to collapse
It might already be unlocked
Hello Friends,
I have recently Purchased an Oppo F15, I have enabled developer mode, OEM Unlocked, and USB Debugging, with the latest adb drivers installed on my PC.
while I am running the command "adb devices" it returning with the device name I have connected i.e. Oppo F15 but when I am running the command "adb reboot fastboot", "adb reboot-bootloader", "adb reboot bootloader" the device reboots but not going to fastboot, it just reboots in normal mode.
Please help me if I am missing something in this. My device is running with Android version 9.
@Venomiest
Try this commands sequence
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
jwoegerbauer said:
@Venomiest
Try this commands sequence
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
Those are the proper commands
([emoji88]Havoc GSI[emoji88])
Venomiest said:
Hello Friends,
I have recently Purchased an Oppo F15, I have enabled developer mode, OEM Unlocked, and USB Debugging, with the latest adb drivers installed on my PC.
while I am running the command "adb devices" it returning with the device name I have connected i.e. Oppo F15 but when I am running the command "adb reboot fastboot", "adb reboot-bootloader", "adb reboot bootloader" the device reboots but not going to fastboot, it just reboots in normal mode.
Please help me if I am missing something in this. My device is running with Android version 9.
Click to expand...
Click to collapse
The bootloader is blocked by code combination. If you try to see more attentive you'll notice the tiny message on the black screen while rebooting.
Not Working
Alien object
A friend gave me phone to recovery. His son add a lockscreen and forgot it, now after i turn on the phone
"phone locked" try again after 15270 seconds"
So i try to factory reset from recovery menu but there also got "enter a locksceen password"
Is any way to bypass this, restore to defualt by pc or smth ?
I trying to do wipe from pc, using ADB
but see something like this
C:\adb>adb devices
List of devices attached
FU5PJF7SZTO7ZHQS unauthorized
C:\adb>adb shell
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Click to expand...
Click to collapse
It's likely that ADB isn't correctly enabled:- the RSA keys dont match this because probably currently used computer isn't same as computer when ADB got enabled 1st time.
jwoegerbauer said:
It's likely that ADB isn't correctly enabled:- the RSA keys dont match this because probably currently used computer isn't same as computer when ADB got enabled 1st time.
Click to expand...
Click to collapse
So what should i do with this ?
I try other installation of adb-fastboot and got
C:\Windows\ADB-FASTBOOT>adb devices
adb server version (32) doesn't match this client (41); killing...
* daemon started successfully
List of devices attached
FU5PJF7SZTO7ZHQS unauthorized
Click to expand...
Click to collapse
Check and uncheck the USB Debugging option in the device. If that doesn't work unplug and plug in the USB a couple of times.
At some point, the device should show a message box to ask you to authorize the computer. Click yes and then the device will be authorized.
I can;t do that, phone is blocked after reboot i got only "Phone is blocked "Try again after 14950 seconds"
But i don't know the pin to unlock it.
i want my phone restore to factory