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.
Related
Trying to follow the steps to boot into TWRP using this method:
http://forum.xda-developers.com/smartwatch-3/development/lwx49k-rooting-easy-t3107501
I am able to boot into fastboot and my screen shows "Running Fastboot" but when I issue the command fastboot boot "<filename>" I just get < waiting for device > on my PC.
Any idea what is getting stuck? I factory reset the watch hoping that would solve the issue but no luck. ADB works fine.
You need to load the drivers for fastboot. What os do you have?
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
I tried to upgrade to the newest Android Wear 2.0, however an android logo with an open chest appears on my reboot which i suspect that my watch has been bricked.
I tried flashing back the stock image but it didn't help. Now it's stuck in a bootloop(displaying huawei logo -> android logo -> restart).
Any help regarding this matter is well appreciated.
Currently unable to detect adb on fastboot(able to enter fastboot), only can detect adb on sideload
xMiji said:
I tried to upgrade to the newest Android Wear 2.0, however an android logo with an open chest appears on my reboot which i suspect that my watch has been bricked.
I tried flashing back the stock image but it didn't help. Now it's stuck in a bootloop(displaying huawei logo -> android logo -> restart).
Any help regarding this matter is well appreciated.
Currently unable to detect adb on fastboot(able to enter fastboot), only can detect adb on sideload
Click to expand...
Click to collapse
Not sure if this is your problem, but adb doesn't work in fastboot mode, only fastboot commands do. While in bootloader mode, try "fastboot devices". If that returns okay, flash-all or the fastboot flash commands should work. If not, either your adb/fastboot need to be updated or Windows is detecting your watch as something other than a fastboot device. Someone else suggested this that worked for me when fastboot doesn't work:
- Go to Windows device manager
- find the Android device
- right click and selected update driver
- do the procedure to install the drivers manually
- when the list of drivers appear, select the one that says fastboot
- and done!
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful
i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this
Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?
otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so
Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp
Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.
If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.
”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed（too many links）and "press any key to reboot" showing on my phone's fastboot screen
Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.