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
Related
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
I want to unlock my cousin's tab who recently passed away and no one knows the passcode so after some googling i found that you can do it via ADB.
(https://forum.xda-developers.com/showthread.php?t=2620456)
The device successfully connects with my pc but when I execute "adb devices" it shows;
.......................... unauthorized
and running adb shell shows;
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.
With the device locked Im unable to authorize my computer so I decided to search something for that too and found this article where it tells u to pull keys from another device and push it into your locked one while in recovery mode and this is where Im stuck. Whenever Im in recovery mode, adb devices shows nothing so if someone of you could help me would be awesome.
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)
Never actually got it done, But see the last post for a workable solution.
Hi all.
The basics:
Device Samsung Galaxy Tab A SM-T295 android 9 PC WIN 7 PRO
Trying to do this >> https://www.xda-developers.com/change-sms-limit-android/
Started this >>> https://www.xda-developers.com/install-adb-windows-macos-linux/
Got this:
I have the USB DEBUGGUNG turned on.
I get the COMMAND WINDOW open
I enter "adb devices" and I get a result
list of devices attached
Enter again and it doesn't show a serial number.
If command
Code:
adb devices
doesn't bring up any device, then an USB connection isn't successfully established. Read here how to fix it.
If device got successfully connected you get its serial-number entering command
Code:
adb shell getprop ^| grep ro.boot.serialno
jwoegerbauer said:
If command
Code:
adb devices
doesn't bring up any device, then an USB connection isn't successfully established. Read here how to fix it.
If device got successfully connected you get its serial-number entering command
Code:
adb shell getprop ^| grep ro.boot.serialno
Click to expand...
Click to collapse
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
But as a test I will do the following from the other thread:
Type in cmd
adb kill-server
adb start-server
Click to expand...
Click to collapse
A lot of that other thread seems to be directed at LINUX users and the thread starter was working on a rooted device which I do not have.
Going to do this
run cmd as Administrator
Click to expand...
Click to collapse
too.
This looks promising so after the above I will try it:
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
Click to expand...
Click to collapse
Back later
Cut_Right_Sharpening said:
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
But as a test I will do the following from the other thread
Back later
Click to expand...
Click to collapse
OK.
Got this from everything except going into recovery mode.
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb kill-server
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb server
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb shell getprop ^| grep ro.boot.serialno
error: no devices/emulators found
Click to expand...
Click to collapse
Cut_Right_Sharpening said:
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
This looks promising so after the above I will try it:
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
Back later
Click to expand...
Click to collapse
Ok this is what I got in recovery mode on the Tab A
https://drive.google.com/open?id=1SCYtbrZKnnfrkNVP34S-H9Jq0SQHSYqj
Still getting this from the CMD WINDOW
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb shell getprop ^| ro.boot.serialno
error: no devices/emulators found
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>
Click to expand...
Click to collapse
@Cut_Right_Sharpening
Is the device shown with a yellow exclamation mark in the Windows device manager when in recovery mode? If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
BTW:
Wondering why the hell you started the device in recovery mode to access it via ADB? Noone does so, me included.
jwoegerbauer said:
@Cut_Right_Sharpening
Is the device shown with a yellow exclamation mark in the Windows device manager when in recovery mode? If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
BTW:
#1 Wondering why the hell you started the device in recovery mode to access it via ADB? Noone does so, me included.
Click to expand...
Click to collapse
#1 Because that was one of the suggestions by this guy https://forum.xda-developers.com/member.php?u=5498377 in the thread I was sent to by the first poster.
Yes, The SM-T295 has the exclamation mark.
If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
Click to expand...
Click to collapse
With WHAT????
@Cut_Right_Sharpening
This is my last post here: Honestly, I have no lust telling you how to successfully run ADB - this may do others here.
What you should know:
1.
Especially for Samsung devices a device-relevant USB driver for Windows OS provided by Samsung Co.Ltd. exists. Hint: Install the one that matches your device, don't further on make use of the obscure one you've already installed.
2.
ADB needs neither the device to be rooted ( unless you want to perform system relevant operations such as modifying system properties ) nor to be run as Administrator nor something else.
3.
Running Android in recovery mode only is useful if you want to perform system maintenance operations, such as
a) reboot system
b) apply update from SD card
c) apply update from cache
d) wipe data/factory reset
e) backup user data
f) restore user data
Note that on stock recovery the ADB utility only registers that the device is connected. When you try applying adb shell or any other thing you'll get an error: it only accepts adb push commands to the device.
Good luck.
jwoegerbauer said:
@Cut_Right_Sharpening
This is my last post here: Honestly, I have no lust telling you how to successfully run ADB - this may do others here.
Good luck.
Click to expand...
Click to collapse
Well, The link to the Drivers may someday be very useful.
I am going to change the thread line to indicate I have given up. There may be people that have the knowledge to do this, but I suspect Google has been working overtime to make it nearly impossible without rooting and I am not ready to go that far.
Should someone else stumble on this thread, it looks like my solution is going to be HitEmUp APP . Not exactly a fully automatic Bulk mailer, but I think it will work for what I want as long as I stay under the 30 SMS/30Minute limit.
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