Related
Alright, fastboot is useful for development but I am posting it here because it is a general topic and won't be discussing developing.
fastboot is useful because you can test kernel builds without having to worry about it not booting, if it doesn't you just remove battery and it boots normal.
While device is off, hold both volume keys(up and down) and power, keep it held until the device goes black but lit screen. This is the bootloader screen and lets you run fastboot commands.
Another way is to have a rooted S7 and in terminal do the following:
su
reboot recovery (you could do adb reboot recovery from your pc without using terminal on device)
I think razor knows because he mentioned this elsewhere, but in case anyone sees this and tries reboot recovery...
Fastboot is actually
adb reboot bootloader
reboot recovery enters recovery and results in a factory reset
Please tell me more about
xaueious said:
I think razor knows because he mentioned this elsewhere, but in case anyone sees this and tries reboot recovery...
Fastboot is actually
adb reboot bootloader
reboot recovery enters recovery and results in a factory reset
Click to expand...
Click to collapse
Hi brother, i have one s7 here model s7-202u and i try to flash and cant boot...
Always appear on screen about fastboot mode...
And i cant boot this tablet.
tried to install TWRP using these instrucitons
http://forum.xda-developers.com/showthread.php?t=1399023
tried everything i could find but im stuck in the kindlefire flash screen and cant go back or anything...is there anyway i can force the tablet to reboot into the OS? It doesnt connect to adb or anything
u are in fastboot. open a cmd prompt in the same directory your adb is in, and run fastboot commands. since twrp isn't installed, u will need to include -i 0x1949 device code or whatever it is, sorry I'm on my device so I can't type is specifically.
Sent from my HTC Glacier using xda premium
smirkis said:
u are in fastboot. open a cmd prompt in the same directory your adb is in, and run fastboot commands. since twrp isn't installed, u will need to include -i 0x1949 device code or whatever it is, sorry I'm on my device so I can't type is specifically.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
i tried doing that..i looked for all of the fast boot commands and it always says fastboot not a valid command etc etc....i tried an adb shell but that didnt work either..i even tried doing a restore with a thread thats in the general forums
Have you verified that fastboot is in fact on your machine? It should reside in the same folder as adb. Also, have you you either A) added the adb/fastboot folder in your Path or B) CDed into the folder where adb/fastboot resides to run the commands?
yay i got it to work...all i did was put in this
fastboot -i 0x1949 oem idme bootmode 4000
then this
fastboot -i 0x1949 reboot
which i got from here
http://forum.xda-developers.com/showthread.php?t=1398728&page=3
looks like all i had to do was add fastboot to the directory i was using so thanks =)
now i just have to wait for a full charge and i can try the twrp again
I also try to install CM7, but it's dead in recovery, I can't exit recovery now. For I have changed boot mode to "idme bootmode 0x5001", How can I change to normal mode ? When I reboot now, it goes to recovery mode directly.
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
It sounds like you may not have the latest drivers for the Android SDK or ADB toolkit.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
When you are in bootloader, you can use fastboot commands.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
JustPlayingHard said:
When you are in bootloader, you can use fastboot commands.
Click to expand...
Click to collapse
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
RonaldusMagnus said:
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
Click to expand...
Click to collapse
It's not adb fastboot.. It's just fastboot.
teh roxxorz said:
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
Click to expand...
Click to collapse
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
RonaldusMagnus said:
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
JustPlayingHard said:
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
Click to expand...
Click to collapse
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
No worries, it's probably me that's being dense.
That should work fine
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
or plug your phone in (while its booted normally, into its OS)
type: adb reboot bootloader
once phone reboots to bootloader, type: fastboot devices
He must have came from a HTC bc he's looking for the option Fastboot in Bootloader.
Sent from my Nexus 6P using Tapatalk
Thanks for your help everyone. I'm back up and running now. My problems stemmed from a misunderstanding that once in the bootloader I'm already able to execute fastboot commands and didn't need to select a fastboot option from the bootloader. And I had a misunderstood how to execute the fastboot commands from the command prompt.
Many thanks to everyone setting me straight!
Hello guys, i m facing very serious issue with my device. My volume up button not working at all and when i take my phone to service centre they said they dont have cheap( i didnt know what they said) and they refuse to repair to my phone. Now problem is i m also custom rom lover and try many roms time to time but if i accidenlty mess with my phone and it get brick than how i can go into recovery mode at that situation ?? Please help me if any one know how to go into recovery mode pc using commands. Thank u
I do not understand clearly. Do you have now a working custom ROM? Or now you are on brick/bootloop?
If you have working system:
If ADB -like minimal ADB and fastboot- (and all windowsdriver) is installed on your PC. And USB debugging enabled. And you have a working TWRP.img on your computer for example to minimal ad and fastboot folder. Then.
Connect your phone to PC with USB
Open a command prompt or run "minimal ADB and fastboot" prompt on your PC.
Type on PC prompt: adb devices (+enter)
If every driver installed correctly, then your PC will display the ID ot your Phone.
If displays then type: adb reboot bootloader (+enter)
The your phone will reboot in fastboot mode.
If you have fastboot mode:
Type on PC prompt: fastboot devices (+enter)
If every driver installed correctly, then your PC will display the ID ot your Phone.
If displays then type: fastboot boot TWRP.img (if your img file is not TWRP.img then rename it before) (+enter)
If everything is all right, your phone will reboot to recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.5.31.
---------- Post added at 06:57 PM ---------- Previous post was at 06:31 PM ----------
My developer friend said: you need to go a private service, and ask him to full button replace. He think, it will be solve your problem.
I found a description http://en.miui.com/thread-84580-1-1.html
bit I am not sure, that is yours.
Maybe...
小米MIX标准版4GB128GB银色MIUI10中国开发者8.5.31.
Thanks for reply ....by the way i have already installed twrp recovery...and the method u said using command is work when my phone in bootloader mode ? Because i cant go into recovery mode at that situation because my volume up button not work
Yes.
Install to your PC minimal adb and fastboot.
https://www.mediafire.com/file/rz87kfzmljiwne4/minimal_adb_fastboot_v1.4.2.exe/file
As I said, if you have fastboot (bootloader) [little green droid with fastboot word] mode:
Type on PC prompt: fastboot devices (+enter)
If every driver installed correctly, then your PC will display the ID ot your Phone.
If displays then type: fastboot boot TWRP.img (if your img file is not TWRP.img then rename it before) (+enter)
If everything is all right, your phone will reboot to recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.5.31.
Volume strip available online
Thank u so much
Please note - this is a general section post. Not android development section post.