so i wanted to update to Android pie so i was just going to flash the stock firmware (7.1.1) and go from there but whenever i execute the command it just shows the black and white razer logo and powered by android so im lost
it shows in fastboot devices but one a use a command it exits download mode
the only command that works is fastboot reboot-bootloader
Related
Hey. I was using a 5.0.1 GPE Rom on my M8 and decided to update both the firmware and the rom to 5.1
I Backed everything up and decided to, as usual, use adb to sideload the firmware to the phone. I did and everything went as expected. After I finished I rebooted to android. I get NFC service stopped working, System UI stopped working and I can't interact with the phone. My thought, well let's go to the recovery and flash a rom I have in my external SD card. No recovery to be found just a android guy belly up with a red ! sign on his belly.
So I thought, I lost my recovery due to the firmware flash, I had happened before, So i went online found a TWRP recovery and went to flash it. Reboot to fastboot USB mode, but then in adb I cannot see the device at all. "adb devices" shows and empty list. I tried my windows 7 laptop to the same result.
Can anyone PLEASE PLEASE help me, I'm kinda freaking out at this point and am running out of options
xsidex said:
..... Reboot to fastboot USB mode, but then in adb I cannot see the device at all. "adb devices" shows and empty list.
Click to expand...
Click to collapse
When in fastboot mode - run command fastboot devices
No adb when in fastboot mode
To flash a recovery (unlocked bootloader)
fastboot flash recovery nameofrecovery.img
ckpv5 said:
When in fastboot mode - run command fastboot devices
No adb when in fastboot mode
To flash a recovery (unlocked bootloader)
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Sometimes some outside thought can be just ridiculasly helpfull when you are stuck in a tiny issue.
Thank you so much Kind sir, my heart rate thanks you aswell.
What a silly mistake
Recently installed cm11, woke up today to phone being unresponsive, try to reboot it and it enters fastboot mode. I searched hours to find a solution but cant seem to find any. Can someone help me out here?
I'm not sure why it went into fastboot mode how did you flash CM11?,
But try to get the phone in to recovery mode by holding the volume up button while powering up, If it works, sideload the update.bin file you want. If it doesn't ask here for the recovery image with your fire os version. Download that, boot the phone into fastboot mode, connect the phone to PC and install the drivers and type the normal way `fastboot -i 0x1949 flash recovery recovery.img` or better yet `fastboot -i 0x1949 boot recovery.img` then sideload the update.bin file.
Hello, I have problem with fastboot mode ealier it was working well but in Minimal Adb and flashboot i seen <waiting for device> so I started checking drivers and after this fastboot mode stopped working. I tried to run fastboot by command adb reboot fastboot but it just reboots phone I need help very fast. [I need fastboot mode to flash CWM on my phone then root it and install cyanogen mod 13 (android 6)]
i was trying to flash the 2.0 update to my watch. i was in command prompt and was typing in the codes then my watch rebooted into recovery i was able to get my watch back into fastboot mode but now adb isnt recognizing my device and the watch doesnt have any software on it what do i do ?!
Same for me what do I do ? Now when I turn on recovery appears for 2 sec then black screen and over and over again looks like I don't have software installed what do I do ?
I also got the same issue I clicked on recover in the bootloader as everytime I tried to run the following step: Execute the flash-all script by typing flash-all.sh or, in the case of Windows, flash-all.bat.
Set up the watch and begin testing it would just say adb does not recognise this command.
I am now stuck in a cycle of not being access the device in ADB to flash say TWRP or get it to even boot, the only thing I can do is get it back to the boot loader.
OK, so the good news is we didn't brick out watches
First thing is first you will need to get back into the watches boot-loader to do this follow the steps below:
1. Hold the power button down until the Huawei logo show's up
2.As soon as the watch vibrates let go of the power button and do one quick short press of the power button again
3. If you did this right the boot-loader should appear if not you will feel another vibration and will have to start over
Now that you are back in the Boot-loader put the watch back on the dock and plug it into your pc. Fire up ADB and fastboot minimal (Get it here: http://forum.xda-developers.com/showthread.php?t=2317790). Install this and drag the contents of the Sturgeon-nvd file you downloaded from the android site (this is the Android Wear 2.0 preview image) into the same folder that the minimal ADB is installed in like so:
http://i.imgur.com/Vw8sUo1.png
Now double click the Flash-all.bat file in the folder and you should see it processing on the ADB window.
Did you unzip the folder and placed it in the ad folder location?
Just an FYI: ADB is not what is used to flash .img files. Its fastboot. When you are in bootloader mode are you in fastboot mode and would use fastboot commands. Its normal for ADB not to see a device in fastboot mode.
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!