My Redmi Note 7 recently broke and the screen was not responsive and had no display. But it was still booting at that time. I can feel the vibrations when placing my finger on the fingerprint scanner.
USB Debugging was enabled, but my computer was not authorized.
I tried to generate adb key from my computer so that it would be authorized by my phone.
I entered recovery on my phone and used adb to push the adb_keys.pub into the /data/misc/adb directory.
After that, I rebooted the phone via the command 'adb reboot', but every time, it just reboots to the recovery. I know this by using 'adb get-state'.
I took the logcat and attached them here. Hopefully someone can help me. Thanks!
Related
Hi,
I ran into a problem with my Nexus 4, the plan was to unlock the bootloader using my mac and fastboot. (used this as information but didn't follow it step by step, youtube.com/watch?v=fHZJ2f6JLw0)
I turned off the phone and went into the bootloader with volume down + power button. From here i used "fastboot devices" to secure that i was able to communicate with the phone. My device showed up together with an error message saying "ERROR: could not get pipe properties nexus 4".
Before doing any more i wanted to understand what this message meant so I searched the web without any success. I booted up my android, turned on usb debugging and used "adb devices". This time only my devices showed up and no error messages. I used the "adb reboot boatloader" to access the bootloader once again.
I still had the same error message with "flashboot devices" as before.
From here i didn't do anything more, I may have disconnected the usb from the computer while the terminal window was open and the phone in bootloader but without running any command from fastboot.
So I didn't run "fastboot oem unlock" or anything else.
I turned off the phone and tried to access the bootloader one more time with the volume down + power button. It didn't respond to this any more and nothing happened, the device just stayed turn off.
I turned on the phone and tried to use adb to access the bootloader but now when running the "adb devices" it just responds "-bash: adb: command not found".
I have tried to restore the phone thru the android setting meny without any success. The phone is working fine without any problem except i cant access the bootloader or use adb.
So I desperately need help from you guys. :crying:
Have any of you heard of this problem before?
Regards Rasmus
I have to change my statement.
Actually I succeeded rooting and installing CWM recovery using a win7 computer together with Nexus4 toolkit.
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
To access bootloader i have to go thru the toolkit and this can be an issue in case i flash a bad rom or kernel and can access android usb debugging.
Is it possible to restore the bootloader?
rallanand said:
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
Click to expand...
Click to collapse
Are you holding the down volume and pressing the power button?
What OS is the computer that you are using? If you have reset the device, make sure that USB debugging is checked again. I know it sounds dumb, but a lot of times it's the simplest things we forget. Once you factory reset your device, it resets everything.
If you are on Windows 7, make sure you are starting the command prompt from the same location your adb is installed. If you are on Ubuntu or another Linux distro, please let me know which one. This seems like it should be an easy fix for you, but a little more info is needed. Thanks!
Hi xda community,
I have always sideloaded the OTA in recovery using a Windows machine. Yesterday, I tried to use my Chromebook running Ubuntu. I can see my device when Android is up and running (meaning Android is running and not in recovery or bootloader) by typing "adb device" using the terminal within Ubuntu. The problem I'm having is not being able to see my device when in Recovery mode and selecting the sideload adb mode.
$adb devices
List of devices attached
<---------this line is blank
$adb sideload update.zip
error: device not found
I've made sure /etc/udev/rules.d/51-android.rules are configured. I also checked the post regarding .android/adb_usb.ini but this is only for the Nook and should not apply to the Nexus 6P.
I also tried adb kill-server and adb start-server with no luck.
I've read post about being able to see the device in fastboot. I tried this as well and can't see the device either. My device does not have an unlocked bootloader but this should not matter. The device doesn't need to be for a sideload. This worked in Windows with no issues. You might ask, what is the problem then? I just want it to work in Ubuntu.
Does anyone have any suggestions on how I can fix this?
Thank you in advance for just reading.
After some more searching I found a suggestion to run the following command and it fixed my problem:
/etc/init.d/udev restart
http://android.stackexchange.com/questions/58187/adb-can-discover-devices-but-not-fastboot
My Acer Chromebook 11 only has two ports: 2.0 and 3.0 USB. I noticed the device would not show up after typing in "lsusb" which would normally show the Google device. I unpluged the USB cord from the 2.0 and plugged it into the 3.0. I read another post online stating this sometimes causes the problem.
When in fastboot I can type "fastboot devices" and "adb devices" in recovery and my device now shows up.
I hope this helps someone. Thank you all.
Mods feel free to close out this thread.
Hi all!
First of all I would like to give small heads up - I've been searching XDA and web for two days and ended with no working solution.
Situation:
Suddenly my Nexus 7 (2012) just died. No charging signs, nothing. So i tried Google described and random hardware resets using buttons with no luck.
I ended with situation:
device is not turning on - no screen flickering, not even small amount of pixel light visible,
ADB - no devices found,
fastboot - no diveces found,
nvflash - only my GeForce PC card found
when I connect device to PC I have to hold power button for ~10sec and there I hear "boing" (USB dev. disconnected), "boing" (USB device connected) sounds.
device is visible as APX device with "!" mark
I've tried:
hardware reset by pressing: power button, power+volume's buttons for different amount of time,
taking back and disconnecting battery,
using different software to discover device,
editing driver .inf file to recognize my device as ADB device. It did but still no visibility via ADB or fastboot (URL: http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/),
read and tried to use things from: http://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495.
No result at all...
One more - when I unplug and then plug in battery while having back taken I can hear sound that something is "running".
Please help!
@kepisty89 You can check here. Install the driver and check your device is detecting or not, actually you've a fried bootloader.
Tahnk you @DutchMan_1990, I tried this and now ended with my device recognized as "Asus Transformer Prime APX Interface". Nothing else happened.
Any ideas?
kepisty89 said:
Tahnk you @DutchMan_1990, I tried this and now ended with my device recognized as "Asus Transformer Prime APX Interface". Nothing else happened.
Any ideas?
Click to expand...
Click to collapse
Hi, kepisty89...
Unfortunately, APX mode is generally never good news .
It usually indicates that the Nexus 7's bootloader has either become corrupted or has been erased, and effectively hardbricking the device.
-----
See here, for a post I wrote for another XDA member with similar issues to yours, back in December 2014, where I elaborate further on this problem.
-----
I suspect your Nexus 7 will require a motherboard replacement .
Rgrds,
Ged.
I have similar issue, but mine I can get to bootloader but that's it, if I try to power it on all I get is the Google and unlock padlock, can't get to recovery, but my device is seen via fastboot ADB Wugfresh NRT, but as soon as I try to write to it ie flash files or try to restore device, ADB locks up, and when it says rebooting device my nexus tries to reboot but I get a black screen and Wugfresh says waiting for device, I have to force reboot bootloader hold power button vol down for NRT to see it again in fastboot. I can also boot tempery recovery via NRT but when I select mount it pops up on PC but I can't copy anything to it, also it says I have no OS installed.
Sent from my Nexus 6 using Tapatalk
Hello Everyone,
I have an issue with my nexus 6p screen all of a sudden being unresponsive to touch. The big error on my part was not setting up my videos and images to automatically backup. So now what i'm trying to do is unlock the phone using ADB and a usb cable but haven't had any luck. I've gotten as far as listing my devices, which show up an unauthorized and seem I can only authorize it from my phone. Q1. is this true? Could there be any other way to authorize my phone, or am I out of luck and my data is kaput? I've also tried an OTG cable but it doesn't load since i'm guessing the OS has to fully load for the cable work.
Do I have any choice on saving my data with a USB cable and command line or can someone suggest a tool that would help me out of this situation?
Put it into fastboot/download mode and flash the latest TWRP recovery.
Use TWRP's file manager or ADB Pull commands to pull your data off. Use ADB push to push a new ROM image and flash over everything except userdata (back it up just in case).
Hello all,
I recently dropped my phone, shattering the screen and rendering the LCD useless. I need to use my phone to access some important messages, so I am trying to use Android Control to emulate my phone until I can get a new one. The problem is I didn't have USB debugging turned on when I dropped it. To fix that, I am trying to use ADB and recovery mode to turn it on, but ADB can't/won't recognize my device. I have installed the universal adb driver and my phone shows up in the device manager, but when I run "adb devices" in the command prompt, nothing comes up. Any help is much appreciated!
Thanks!
lonshlon said:
Hello all,
I recently dropped my phone, shattering the screen and rendering the LCD useless. I need to use my phone to access some important messages, so I am trying to use Android Control to emulate my phone until I can get a new one. The problem is I didn't have USB debugging turned on when I dropped it. To fix that, I am trying to use ADB and recovery mode to turn it on, but ADB can't/won't recognize my device. I have installed the universal adb driver and my phone shows up in the device manager, but when I run "adb devices" in the command prompt, nothing comes up. Any help is much appreciated!
Thanks!
Click to expand...
Click to collapse
Did you have TWRP installed? (Unlocked bootloader?)
If not, I don't know of any way to turn on ADB.
If TWRP is installed you boot into recovery and you are good.
tech_head said:
Did you have TWRP installed? (Unlocked bootloader?)
If not, I don't know of any way to turn on ADB.
If TWRP is installed you boot into recovery and you are good.
Click to expand...
Click to collapse
Unfortunately I don't have TWRP installed
Unfortunately I don't have TWRP installed
No USB debugging and no twrp and no LCD ....
That's a no go.