Hi everybody,
like i said in the title i can't access the ADB interface on this phone.
It has broken screen and i must retrieve all the data inside, i've tried a lot of workarounds but nothing seems to help.
The phone is locked and usb debugging is disabled so i can't open the folders with Windows and it neither shows as adb device.
If i try to enter in recovery mode pushing VOL UP + POWER initially it appears "ADB INTERFACE" in the device manager but it's not listed in the adb devices on cmd.
After pushing VOL UP + POWER and afterwards two times VOL DOWN it finally enters in the recovery mode (the one before was a sort of pre recovery menu) so it has to connect now with the ADB but it not appears in the cmd adb devices and in the device manager appears now 2 Android generical devices (Android [0] and Android [1]), can u give me a little help please I really don't know what to try next :crying::crying::crying:
Related
Hi
I have got a hero on the cheap currently using an iPhone boot looking to move over.
The hero has a custom rom on it, I would liketo try others. Holding down the home button and powering on just leaves it with the G2 boot screen. Holding down back button and power brings me into fastboot USB. When connected to the mac I am unable to see the device / list it using adb devices. If I boot into the os and connect to the mac not mounting the sdcard I can see the device with adv devices.
I'm trying to install a recovery image, this is proving dificult with not seeing the device in fastboot.
Has anyone any thought/suggestions on to resolve? Or point me in the direction of some threads to read.
Tia
deano
use fastboot devices when in fastboot...
HI,
thanks for the reply, when in fastboot on the device I use fastboot which i have downloaded from the andriod site and put in my "tools" folder when trying to lash a recovery image it just comes back with a prompt saying "waiting for device"
thanks
just to make sure: you turn off the phone, then turn it on again while holding down BACK. this brings you to a screen with a white background and fastboot written somewhere. then you plug in the usb cable and execute "fastboot devices". if it still doesn't recognize your device then you got a problem somewhere, no idea where though. not sure if windows needs drivers or anything for fastboot to work correctly...
Yes that's correct.
Phone is recognize in everything other than when connected by fastboot.
Thanks for your input
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
Hii I have a chinese yxtel g905 android mobile. I have rooted it and changed the build. prop file. After rebooting it the phone is not booting. It is just powering on and immediately after the boot animation is completed it is turning off and it also don't have fastboot mood or recovery option.I have tried this by long pressing all the possible combinations of buttons. So someone tell me friends is there any solution for such a problem?? Like feeding new build. prop file into the device or anything like that.
Some devices show no signs of activity in fastboot mode.
It might look like that the phone is switched off but it would actually be in fastboot mode.
To check, try power + volume up/volume down/both then connect the phone to the PC (with all the necessary tools and drivers) and type
Code:
fastboot devices
Into the command prompt.
It will show a list of all devices that are in fastboot mode and connected to the PC.
If you are able to confirm that the phone is now in fastboot, you can proceed to flash the stock ROM (given that you already have it) to your device.
Sent from my Xiaomi HMNote1W using Tapatalk
Dear,
My Asus Zenpad C7.0
Model ; P01Y (Z170CG)
Android Version 5.0.2
Firmware WW_V12.26.4.61_20160530
No root
fastboot or recovery mode only show a droid robot with green backgroun collour like this video
https://www.youtube.com/watch?v=13yqwMB8kTw
can not detect by pc or laptop device connected and disconnect cotinuos
Battery drain fast, sometime device went restart
Before getting update via OTA everything is fine
Hope someone can help or we must wait until asus release update
Same problem here
I just got an Asus ZenPad C 7.0 and when I do "adb reboot fastboot" or "adb reboot bootloader" I get the green droid screen, but the device does not appear in fastboot or adb, and there are no options when I press the volume keys. I can get into recovery mode by pressing the volume down and power buttons, and then pressing the power button again when the "No Command" screen comes up. Hopefully I will be able to sideload a zip that will fix the problem, I'll let you know if I can get it to work.
Drivers...
justineldracher said:
I just got an Asus ZenPad C 7.0 and when I do "adb reboot fastboot" or "adb reboot bootloader" I get the green droid screen, but the device does not appear in fastboot or adb, and there are no options when I press the volume keys. I can get into recovery mode by pressing the volume down and power buttons, and then pressing the power button again when the "No Command" screen comes up. Hopefully I will be able to sideload a zip that will fix the problem, I'll let you know if I can get it to work.
Click to expand...
Click to collapse
Turns out that when I looked in device manager while the device was in fastboot mode, the device wasn't recognized. Once I manually assigned Google's ADB drivers to the device, it appeared in fastboot and I was able to root and do everything else I wanted.
[/COLOR]
justineldracher said:
I just got an Asus ZenPad C 7.0 and when I do "adb reboot fastboot" or "adb reboot bootloader" I get the green droid screen, but the device does not appear in fastboot or adb, and there are no options when I press the volume keys. I can get into recovery mode by pressing the volume down and power buttons, and then pressing the power button again when the "No Command" screen comes up. Hopefully I will be able to sideload a zip that will fix the problem, I'll let you know if I can get it to work.
Click to expand...
Click to collapse
I had to do this on a windows machine to get it working.
Download Intel usb driver: software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Manually select "Intel Android ADB Interface" for the unrecognized device in Device Manager.
Good luck!
[email protected] said:
[/COLOR]
I had to do this on a windows machine to get it working.
Download Intel usb driver: software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Manually select "Intel Android ADB Interface" for the unrecognized device in Device Manager.
Good luck!
Click to expand...
Click to collapse
it's work !
Thanks
So I'm trying to install this app that needs to run an adb command in order to work. I followed all the instructions (Turn on developer options > turn on USB debugging) but the problem is that my computer doesn't recognize my phone in recovery mode, the weird thing is that it recognizes it while it's turned on. I've tried to look for answers in other threads to no avail so I was hopping that you guys could help me?
@-fg
Wondering why you are booting into Recovery Mode when it comes to execute an ADB command?
Android devices have a feature called Recovery Mode, which allows users to fix some problems in their phones or tablets. It may be useful if you notice that your device is not acting right. Technically, Recovery Mode refers to a special bootable partition, which contains a recovery application installed in it.
REMEMBER: When your device is in Recovery Mode, only physical keys will be accessed, means you have to use Volume Up and Down keys to move up and down and the Power button to confirm an option / command.
Well, the command doesn't work when I execute it with my phone booted up normally, I assumed that I had to go into recovery mode because it's the only way for it to work. Maybe there's another way to execute that command but I don't really know how