Ok, my nexus 7 this morning had just randomly started to not respond to any touch. I restarted the device by turning it off and on again with the power button, and it stuck at Google logo. I can go into bootloader, but not recovery. If I try to go in to recovery, it gets stuck at Google logo again.
The device is stock, didn't even unlock it. Fastboot devices returns the serial number, fastboot oem unlock pops up the screen if I want to proceed, at which point I click no because I don't want to wipe the drive yet. I've tried Nexus Root Toolkit to boot into temporary custom recovery to make a back up, but doesn't work. NRT live log is as follows
-----------------------------------------------------------------------------------------------------------
Information: Rebooting your device into bootloader mode...
fastboot reboot-bootloader
Information: Rebooting your device into bootloader mode...
adb reboot bootloader
Information: Checking Fastboot Status
fastboot devices
Information: Retrying.. Checking Fastboot Status
fastboot devices
05864603 fastboot
Fastboot Status: Device Connected
Information: Booting modified boot.img to enable running privileged commands...
fastboot boot "D:\Android Development\Nexus Root Toolkit 1.7.2\data\Modified_Boot\modified_boot_razor_5.0.1_Information: Waiting for your device...
adb wait-for-device
LRX22C.img"
-------------------------------------------------------------------------------------------------------------
and then times out.
Since i couldn't connect it with my computer with USB debugging on, the drivers might not have installed correctly, although I did try installing the drivers with NRT. Currently my laptop doesn't recognize the device. It does make sound when I connect the device, but it doesn't show up in device manager at all.
Any pointers please?
hello
recently i tried to install android wear 2.0 and i did it and downgrade to 1.5 and everything was perfect and i didn't have any problem with it.
but today i tried reinstall it again so i unpair my watch and i enable dev option and enabled adb debugging and tried adb devices and it showed my device :
and then i enter adb reboot bootloader and my watch went to fastboot menu
and then i didn't enter fastboot oem unlock because i unlocked it last time.
so i opened flash-all on my computer and it stuck on < waiting for device >
i tried fastboot devices and i got nothing, fastboot can't recognize my watch.
so anyone can help me ?
(for adb i use this:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
)
behdad_es said:
hello
recently i tried to install android wear 2.0 and i did it and downgrade to 1.5 and everything was perfect and i didn't have any problem with it.
but today i tried reinstall it again so i unpair my watch and i enable dev option and enabled adb debugging and tried adb devices and it showed my device :
and then i enter adb reboot bootloader and my watch went to fastboot menu
and then i didn't enter fastboot oem unlock because i unlocked it last time.
so i opened flash-all on my computer and it stuck on < waiting for device >
i tried fastboot devices and i got nothing, fastboot can't recognize my watch.
so anyone can help me ?
(for adb i use this:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
)
Click to expand...
Click to collapse
Use the Menu in bootloader mode to reboot to bootloader while it is waiting for device. That should get flash-all. bat to just run.
Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!
Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.
Here is screenshot from minimal adb...
Phone must be in MTP mode.
And here is phone in fastboot
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.
I'm trying to unlock boot loader on my device but, when I reboot into boot loader I don't get an option for "fast boot". The options I do get are to reboot, reboot in download mode, reboot in boot loader, reboot in recovery, and shut down. Any ideas or maybe any precursors I've missed?
fastboot (and adb) needs to be installed and running from your PC, you reboot in to the phones bootloader then from a command prompt or terminal on your pc you issue fastboot commands to your phone which is connected by USB.
No luck
upperdecker said:
fastboot (and adb) needs to be installed and running from your PC, you reboot in to the phones bootloader then from a command prompt or terminal on your pc you issue fastboot commands to your phone which is connected by USB.
Click to expand...
Click to collapse
C:\Users\Delprete>adb reboot downloader
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
is all I got. I downloaded and installed fastboot to the pc. The directions that I'm following from HTCDEV.com say to reboot into download mode and then load fastboot from the phone.
Use the adb and fastboot from here http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have usb debugging and oem unlocking enabled in developer options of your phone.
Once in download mode send the fastboot commands from your pc
Hi, I want to move to a custom ROM on my A2 Lite. But before anything else, I need to backup my phone.
1st step : TWRP recovery.
On the PC, ADB driver is installed. Phone powered and connected, I have no problem to send ADB command to phone. "adb reboot bootloader" for example.
But once the phone is in fastboot (logo on screen), it is not recognized by PC (no driver) and I can"t send Fastboot command.
Any hint ?
Thanks.
Ok, I found a solution.
Downloading Google USB Driver but installation procedure is wrong, I should FORCE it and manually assigne the driver "Android Device / Bootloader" to be able to connect in Fastboot mode.
fastboot oem unlock
-> Reboot with the warning message but wipe all data. It's the only I found to unlock the bootloader :/
fastboot oem edl
-> Not the solution to flash the new ROM
fastboot boot twrp*.img
-> Way better to get the recovery flashed