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
Related
Downloaded and installed ADB. Following tutorial here:
https://www.xda-developers.com/nexus-6p-bootloop-fix/
Specifically:
- Connect your smartphone or tablet to your computer with a USB cable. Change the USB mode to “file transfer (MTP)” mode. Some OEMs may or may not require this, but it’s best to just leave it in this mode for general compatibility.
- In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices
- On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).install adb
- Finally, re-enter the command from step #6. If everything was successful, you should now see your device’s serial number in the command prompt. Yay! You can now run any ADB command on your device! Now go forth and start modding your phone by following our extensive list of tutorials!
https://www.xda-developers.com/install-adb-windows-macos-linux/
I did all the above. But don't see anything from:
C:\ADB>fastboot devices
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
Nexus 6P was plugged into the USB cable on Win10 machine. Am in MTP mode. Most recent Google USB drivers installed.
I have done OEM Unlock in setup|Developer options. I have also turned on USB debugging in same options.
I am [obviously] lost. Anyone know what else I might try?
OK, I have made a little progress messing around on my own. It seems that running from the CMD line in Win 10, ADB command works but Fastboot does not. WHY? Bith are in the same directory.
If I type Fastboot by itself, then I get a list of the associated parameters, which means that the CMD system DOES recognize the Fastboot command.
Now, if I run CMD====> "ADB devices", it looks like my device is recognized and attached (that is my serial# below).
But if I try CMD=====> "Fastboot devices", as the instructions require, I get nothing. And if I try to run the flash job via Fastboot, that does not work either.
==================
C:\ADB>adb devices
List of devices attached
8XV5Txxxxxxxxxxx device
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
===================
Wondering if I need to install the Android SDK on Windows for this process to work?
I Think You need to Redo The process from Step One.
I Heard about This and Never Did An OTA.
If it Persists Try Using A Different PC and If After That It doesn't work Then Yes Android SDK is The last Option.
Sent from my Nexus 6P using Tapatalk
Solved. I needed to add the ADB install directory to the environmental path. Don't quite understand why, but doing so allowed me to get the problem fixed.
Hi, I am new to this and wanna root my phone...
One click method doesn't work....Can any one please help me out???
Well there are no official guide on the XDA forum yet, maybe try kingroot?
Sent from my iPhone using Tapatalk
ghoul99 said:
Hi, I am new to this and wanna root my phone...
One click method doesn't work....Can any one please help me out???
Click to expand...
Click to collapse
Try this:
UNLOCKING BOOTLOADER:
Download Koush Universal adb driver from koushikdutta.com and adb setup.
Install the driver first and install adb after that.
Type n and press Enter when adb setup asks for installing drivers.
After the installation, run command prompt as administrator.
Open File explorer, and navigate to C:\adb
Please take backup of your data before proceeding further.
In C:\adb press Shift+right click and select Open Command Window here.
Enable USB debugging on your phone and connect your phone to pc using USB cable.
Type "adb devices" without quotation marks and press enter.
If it shows some device to be connected, only then proceed further.
Type "adb reboot bootloader" and press enter.
Phone will boot into fastboot mode.
Type "fastboot devices" and press enter.
If it shows some device to be connected, only then proceed further.
Type "fastboot oem unlock" and press enter.
On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type "fastboot reboot" and press enter.
Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
ROOTING:
1. For Kingoroot:
Download and install Kingoroot for PC.
Enable USB debugging on your phone and connect your phone to PC using USB cable.
Open Kingoroot.
Connect your pc to internet.
Kingoroot will detect your phone automatically and in a few seconds the root button will come up, click it and wait until the process completes.
Your phone may reboot several times during the process.
Congrats, you have a rooted phone now.
2. For Dr Fone:
Download and install Dr Fone on your PC.
Enable USB debugging on your phone.
Open Dr Fone and select Root option.
Connect your phone to your PC with USB cable.
Dr Fone will detect your phone in a few minutes.
Click "Root" button and wait.
Congrats, you have a rooted phone now.
Hit thanks if found useful.
I've tried PC method as well and still not rooted. I didn't performed the bootloader unlocking through adb though. There's an option of OEM Unlock under developer options. Is that that a problem?
UOTE=Augustoandro;75771341]Try this:
UNLOCKING BOOTLOADER:
Download Koush Universal adb driver from koushikdutta.com and adb setup.
Install the driver first and install adb after that.
Type n and press Enter when adb setup asks for installing drivers.
After the installation, run command prompt as administrator.
Open File explorer, and navigate to C:\adb
Please take backup of your data before proceeding further.
In C:\adb press Shift+right click and select Open Command Window here.
Enable USB debugging on your phone and connect your phone to pc using USB cable.
Type "adb devices" without quotation marks and press enter.
If it shows some device to be connected, only then proceed further.
Type "adb reboot bootloader" and press enter.
Phone will boot into fastboot mode.
Type "fastboot devices" and press enter.
If it shows some device to be connected, only then proceed further.
Type "fastboot oem unlock" and press enter.
On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type "fastboot reboot" and press enter.
Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
ROOTING:
1. For Kingoroot:
Download and install Kingoroot for PC.
Enable USB debugging on your phone and connect your phone to PC using USB cable.
Open Kingoroot.
Connect your pc to internet.
Kingoroot will detect your phone automatically and in a few seconds the root button will come up, click it and wait until the process completes.
Your phone may reboot several times during the process.
Congrats, you have a rooted phone now.
2. For Dr Fone:
Download and install Dr Fone on your PC.
Enable USB debugging on your phone.
Open Dr Fone and select Root option.
Connect your phone to your PC with USB cable.
Dr Fone will detect your phone in a few minutes.
Click "Root" button and wait.
Congrats, you have a rooted phone now.
Hit thanks if found useful.[/QUOTE]
I've tried PC method as well and still not rooted. I didn't performed the bootloader unlocking through adb though. There's an option of OEM Unlock under developer options. Is that that a problem?
ghoul99 said:
I've tried PC method as well and still not rooted. I didn't performed the bootloader unlocking through adb though. There's an option of OEM Unlock under developer options. Is that that a problem?
Click to expand...
Click to collapse
Just check whether the bootloader is unlocked using fastboot.
Type
fastboot getvar all
Click to expand...
Click to collapse
Augustoandro said:
Try this:
UNLOCKING BOOTLOADER:
Download Koush Universal adb driver from koushikdutta.com and adb setup.
Install the driver first and install adb after that.
Type n and press Enter when adb setup asks for installing drivers.
After the installation, run command prompt as administrator.
Open File explorer, and navigate to C:\adb
Please take backup of your data before proceeding further.
In C:\adb press Shift+right click and select Open Command Window here.
Enable USB debugging on your phone and connect your phone to pc using USB cable.
Type "adb devices" without quotation marks and press enter.
If it shows some device to be connected, only then proceed further.
Type "adb reboot bootloader" and press enter.
Phone will boot into fastboot mode.
Type "fastboot devices" and press enter.
If it shows some device to be connected, only then proceed further.
Type "fastboot oem unlock" and press enter.
On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type "fastboot reboot" and press enter.
Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
ROOTING:
1. For Kingoroot:
Download and install Kingoroot for PC.
Enable USB debugging on your phone and connect your phone to PC using USB cable.
Open Kingoroot.
Connect your pc to internet.
Kingoroot will detect your phone automatically and in a few seconds the root button will come up, click it and wait until the process completes.
Your phone may reboot several times during the process.
Congrats, you have a rooted phone now.
2. For Dr Fone:
Download and install Dr Fone on your PC.
Enable USB debugging on your phone.
Open Dr Fone and select Root option.
Connect your phone to your PC with USB cable.
Dr Fone will detect your phone in a few minutes.
Click "Root" button and wait.
Congrats, you have a rooted phone now.
Hit thanks if found useful.
Click to expand...
Click to collapse
Tried adb setup but shows no devices attached but when tried with my brother's phone it shows devices are connected.
ghoul99 said:
Tried adb setup but shows no devices attached but when tried with my brother's phone it shows devices are connected.
Click to expand...
Click to collapse
Press the "Revoke USB debugging authorization" in Developer Options.
Connect your phone with pc with the phone screen on and unlocked.
The phone will ask for permission, press OK.
Then type "adb devices" in the terminal as directed in the tutorial before.
It will probably show your device.
Augustoandro said:
Press the "Revoke USB debugging authorization" in Developer Options.
Connect your phone with pc with the phone screen on and unlocked.
The phone will ask for permission, press OK.
Then type "adb devices" in the terminal as directed in the tutorial before.
It will probably show your device.
Click to expand...
Click to collapse
Tried but nothing happened. Looks like currently they don't have drivers for this phone. However thanks for your efforts.
I rooted my q452 using the boot.img-patch method for magisk
meghgoswami said:
I rooted my q452 using the boot.img-patch method for magisk
Click to expand...
Click to collapse
Can you tell me the steps or link to any tutorial?
Thanks either way
Yeah, sure -->
You need to have the unsigned boot.img for the q452, download it from here https://drive.google.com/file/d/127pySEIXj-uRyZpWycfRjaihkYgGv9tR/view?usp=sharing
Install the Magisk Manager apk, open it, click on the Install button next to "Magisk is not installed" and then click on Install again.
Then select "Select and Patch a File" and select the unsigned boot.img. Magisk will patch it, and then flash the patched boot image using adb (you need to have an unlocked bootloader). That's it!
meghgoswami said:
Yeah, sure -->
You need to have the unsigned boot.img for the q452, download it from here https://drive.google.com/file/d/127pySEIXj-uRyZpWycfRjaihkYgGv9tR/view?usp=sharing
Install the Magisk Manager apk, open it, click on the Install button next to "Magisk is not installed" and then click on Install again.
Then select "Select and Patch a File" and select the unsigned boot.img. Magisk will patch it, and then flash the patched boot image using adb (you need to have an unlocked bootloader). That's it!
Click to expand...
Click to collapse
Thanks bro!
Can you please tell me the adb commands?
ghoul99 said:
Thanks bro!
Can you please tell me the adb commands?
Click to expand...
Click to collapse
THIS WILL WIPE ALL THE DATA ON YOUR DEVICE, MAKE SURE YOU HAVE A BACKUP OF YOUR DATA
Ok, first you have to enable "OEM unlocking" in the Developer options. The adb commands are-
1. adb devices (to make sure that the device is connected)
2. adb reboot bootloader
3. fastboot devices
4. fastboot flashing unlock OR fastboot oem unlock Then press the volume up button on the phone to unlock the bootloader
5. fastboot reboot bootloader
5. fastboot flash boot boot.img (where boot.img is the unsigned boot.img, you have to put it in the adb folder)
6. fastboot reboot
That's it! Hit the thanks button if I helped you!
meghgoswami said:
I rooted my q452 using the boot.img-patch method for magisk
Click to expand...
Click to collapse
ok
I have Samsung Galaxy Tab S2 that I attempted to root earlier today. I used Odin and CF auto root method. Everything appeared to go fine, until it restarted itself after it was done. When it booted back up, the WiFi was not working. When I turn it on, it is simply stuck on "Turning on...." and nothing happens.
Problem 2: When I connect the tablet to a computer via USB cable, it does not recognize it. I'll hear a chime, so it detects it, but it does not show up in the file explorer. The tablet is set for a MTP USB configuration.
I tried a factory reset, but that did nothing.
I'm not sure what to do now. I do have a micro SD card, so I'm able to move it back and forth from the tablet to my PC to install APKs and other files. I'd like to try flashing a custom ROM to see if that fixes it, but now I'm not rooted. I used the SD card to install a couple of the one click root apps, but they were either unsuccessful, or require an internet connection to use.
I don't know if it's possible to actually install a custom ROM on a device that doesn't have internet access and can't use a USB cable.
If anyone has suggestions as to either of my problems, I'd love to hear it, because as of now I can't do anything with my tablet.
You can try to:
wipe data/cache from recovery and reboot it again to see if the wifi error still exists, or you can flash it again.
You can get and use adb/fastboot, if you haven't already, and check if fastboot (execute fastboot devices in cmd) recognizes your device after the chime sound. If you're lucky and your device is displayed, you can flash it again. All the best!
daphr said:
You can try to:
wipe data/cache from recovery and reboot it again to see if the wifi error still exists, or you can flash it again.
You can get and use adb/fastboot, if you haven't already, and check if fastboot (execute fastboot devices in cmd) recognizes your device after the chime sound. If you're lucky and your device is displayed, you can flash it again. All the best!
Click to expand...
Click to collapse
Thanks. Executing "fastboot devices" returns an empty list, however "ADB devices" returns some sort of serial number with "offline" next to it.
edit: I've been running adb kill-server and adb-start server commands, followed by adb devices, and that will switch the device status from "offline" to "unauthorized". I'm not sure how to fix that. I navigated to my .android folder on my PC and deleted the adbkey file but that didn't help.
In developer settings Enable USB debugging, revoke current USB debug authorizations and allow your PC's fingerprint. You can also enable OEM unlock in case you plan to play with the bootloader and custom ROMs.
Next in cmd after plugging the device in, check if it gets detected: adb devices
If you get the list you've mentioned, execute: adb reboot bootloader
This should boot your device into the fastboot mode where you have full access to your phone, so be careful what you're doing.
If you need more info on fastboot and adb, check out the forums.
Good luck!
daphr said:
In developer settings Enable USB debugging, revoke current USB debug authorizations and allow your PC's fingerprint. You can also enable OEM unlock in case you plan to play with the bootloader and custom ROMs.
Next in cmd after plugging the device in, check if it gets detected: adb devices
If you get the list you've mentioned, execute: adb reboot bootloader
This should boot your device into the fastboot mode where you have full access to your phone, so be careful what you're doing.
If you need more info on fastboot and adb, check out the forums.
Good luck!
Click to expand...
Click to collapse
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
febtober said:
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
Click to expand...
Click to collapse
Have you been asked for a new computer ID to accept after revoking old ones and plugging the device in again?
As long as you don't add new fingerprint of your computer to the device, your device will be unauthorized.
febtober said:
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
Click to expand...
Click to collapse
You need to restock your tablet via odin (to put modem back aka Wifi)
After you restock Install Twrp and install magisk to root, instead of cf-root like you did (this will not breaking the safety net or knox even the modem)
(Note:before install magisk backup your "BOOT" via TWRP)
Y cant i get fastboot drivers to read in Windows 10. I have updated the software to the latest update. Developer options are turned on. USB configuration is set to file transfer. In a regular state Windows 10 readds the phone and I can access the contents of the phone. I opened a power shell (regular and as admin) I typed "adb devices" it reads. (I have enabled advanced reboot.) I use the command "adb reboot-bootloader" in boots to fastboot. Now it loses connection. I Open the Run dialog box by pressing Windows Key+R. Type “devmgmt.msc” besides Android is a yellow triangle, then click Update Driver.A new window will pop up. Select the ‘Browse my computer for driver software’ option. I copied the drivers from the OnePlus 5 folder. Try to install but nothing. This is where in stuck. Please help. Thanks
Have Honda Accord X 2019 Have 8 inch for based on android 6.0.1 Find how on USB debugging find how on adb mode. Now have problem: when I enter "adb devices" the command on the computer. I get a response device number and that the device is not authorized. I would have to confirm on the device usb debug but I think that Honda blocked. I try in Ubuntu Insert key files from your phones that passed authorization. nothing helps. please tell me what else can be done. you can simulate the situation on any phone just by request do not confirm usb debug and try to do something after the command "adb devices".
vikdr said:
Have Honda Accord X 2019 Have 8 inch for based on android 6.0.1 Find how on USB debugging find how on adb mode. Now have problem: when I enter "adb devices" the command on the computer. I get a response device number and that the device is not authorized. I would have to confirm on the device usb debug but I think that Honda blocked. I try in Ubuntu Insert key files from your phones that passed authorization. nothing helps. please tell me what else can be done. you can simulate the situation on any phone just by request do not confirm usb debug and try to do something after the command "adb devices".
Click to expand...
Click to collapse
Try this:
1. Go to the developer options on the phone and click "Revoke USB debugging authorization" if option is present
2. Disconnect device
3. Delete folder %USERPROFILE/.android
4. Re-start ADB server
Code:
adb kill-server
adb start-server
5. Re-connect device
Code:
adb devices
I do this dont help. "unauthorized". You can verify this in your phone just dont confirm usb debuging when ask.
vikdr said:
You can verify this in your phone just dont confirm usb debuging when ask.
Click to expand...
Click to collapse
That your problem, you have to confirm when you connect your device, also make sure u use the latest version of adb, it can be downloaded here: https://developer.android.com/studio/releases/platform-tools
Problem i cant confirm on phone. Need use adb without confirm on phone
Re-create RSA keys
Code:
adb kill-server
adb keygen %USERPROFILE%\.android\keys\adbkey.pub
Thanks. But dont help
vikdr said:
Thanks. But dont help
Click to expand...
Click to collapse
Hi!
How did you solve the problem?
Hi. No