I tried to roll back from 10 to 9 and ended up messing up my fastboot. I can use twrp and adb but in fastboot my computer does not see it at all. I've tried linux and windows.
Is there a fastboot image backup I can flash anywhere?
BlazingBullets said:
I tried to roll back from 10 to 9 and ended up messing up my fastboot. I can use twrp and adb but in fastboot my computer does not see it at all. I've tried linux and windows.
Is there a fastboot image backup I can flash anywhere?
Click to expand...
Click to collapse
Have you tired plugging into the side USB port and running "adb reboot bootloader" ?
Related
I have not received the OTA update to Marshmallow yet and getting impatient so I'm attempting to sideload the update myself. I've installed the SDK and drivers. The device is listed when I use 'adb devices' at the command prompt and it allows me to boot into the bootloader. But from there it disconnects from my computer and I'm not able to push the update to the device. I get "error: device '(null)' not found". Any advice?
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Didgeridoohan said:
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Click to expand...
Click to collapse
Ok, but all the instructions I'm finding online to sideload the OTA say to type "adb sideload [the full name of the file].zip". This is after enter Recovery Mode and select "apply update from adb"
I typed "fastboot devices" and my device came up in the bootloader. I click into Recovery Mode and the computer makes the disconnect sound. That's where I'm cut off.
Have you tried unplugging and plugging in the usb again after entering recovery?
Didgeridoohan said:
Have you tried unplugging and plugging in the usb again after entering recovery?
Click to expand...
Click to collapse
I ended up trying NRT and caused even more problems at first, so I ended up just flashing the update instead of sideloading it. I was freaked out for a while because it was stuck in the boot sequence but as of right now, it's working and I have 6.0.
Yay!
ok, sideloading is for twrp recovery. but thats not needed anymore as you can just move files in and out of twrp without adb. flashing factory images is only via fastboot while you are in bootloader. adb and fastboot are different.
Hello everyone,
I have a MotoG 2014 titan XT1064. It was rooted, bootloader unlocked with CyanogenMod 13 running. But it was crashing all the time, so I decided to change its ROM. I couldn't do it though. When I go to the fastboot menu and try to access the recovery option, it's stuck at the blue teamwin screen. For some reason when I try the normal powerup it doesn't boot anymore, everything I see is a "blue Motorola logo powered by android".
Before it bricked I installed a TWRP app to no avail. Also I've tried installing TWRP via fastboot flash recovery 3.1.1-0 img. First there's a msg "(bootloader) has-slot:recovery: not found" then it says sending recovery, writing recovery OKAY. I downloaded the stock firmware for my version (XT1064_TITAN_RETUAWS....xml). It happens the same thing. When I try to fastboot flash the firmware, it's the same as when I try flashing the TWRP: "has-slot:recovery/boot/system/logo...: not found", then OKAY msgs.
I've no glue of what's going on.
Additional information:
- I use debian stretch
- The cellphone is charging alright
- Fastboot recognizes it but adb doesn't
Thanks a lot anyway! Any help is appreciated
Anyone? I'm still searching for help. Is it hopeless? Do I need some hardware intervention?
Install windows on a virtual machine and run the process
marcelo1998 said:
Install windows on a virtual machine and run the process
Click to expand...
Click to collapse
Thanks for the reply. I have Windows XP on a VirtualBox. So I install adb and fastboot than run the .bat file? Is that it?
Agradeço a ajuda!
imbassahy said:
Thanks for the reply. I have Windows XP on a VirtualBox. So I install adb and fastboot than run the .bat file? Is that it?
Agradeço a ajuda!
Click to expand...
Click to collapse
Yes that's right
Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.
Here's what I'm talking about just in case someone asks
Try installing a stock factory image from fastboot.
runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon
My phone 2 boot to fastboot, can't found fastboot device in my computer. i try reinstall driver, change cable, reboot to fastboot mode. only found QDLoader 9008. my phone is not bricked but boot to fastboot mode, can't found fastboot device.
sorry for the my bad english...(translator)
I had the same issue. What I did was make a live boot disk with FWUL and boot into that. I believe there is an issue with fastboot and Windows 10 Update 2004.
hackthis02 said:
I had the same issue. What I did was make a live boot disk with and boot into that. I believe there is an issue with fastboot and Windows 10 Update 2004.
Click to expand...
Click to collapse
Can confirm it is an issue with Windows 10 v2004, I was driving myself insane with this issue and once I tried it on a computer with an older update everything worked perfectly.
try a different cable.
if you're on linux, run fastboot with sudo
Has anyone tried using adb fastboot on Samsung Galaxy Note 8 recently.
I have tried unsuccessfully to get the fastboot work using Windows and Macbook with the latest Samsung Samsung drivers for fastboot. Even installed the fastboot drivers from Android Development platform but still no luck beyond <waiting for device>.
I read on another forum that Samsung no longer allows fastboot to work with their devices. Is it correct?
Fastboot as I understand it is an extension of Android recovery.
If you have USB Debugging enabled on your device, you should be able to issue commands: adb reboot fastboot
Fastboot commands also work in bootloader.
@V0latyle
Thanks for your reply.
I have USB debugging enabled alongwith the unlocked bootloader, as my device is rooted.
Recently, I was trying to use adb fastboot to flash boot image file of my Samsung device. However, it kept displaying <waiting for device> .
I tried the same command from my MacBook using Android platform tools, but result was still the same.
All adb commands work very well on Windows and MacBook without any hiccups.
Prof_Shekhar said:
@V0latyle
Thanks for your reply.
I have USB debugging enabled alongwith the unlocked bootloader, as my device is rooted.
Recently, I was trying to use adb fastboot to flash boot image file of my Samsung device. However, it kept displaying <waiting for device> .
I tried the same command from my MacBook using Android platform tools, but result was still the same.
All adb commands work very well on Windows and MacBook without any hiccups.
Click to expand...
Click to collapse
The appropriate command to flash /boot would be:
Code:
fastboot flash boot <boot image>