I was trying to understand what is fastboot. And then I got caught into all that bootloader jargon and couldn't differentiate one from the other. So I have a few questions. If someone could make me understand this stuff...I would be really grateful. Thanx guaranteed:laugh:
1. What is fastboot? When I run fastboot commands through cmd...I get <waiting for device>.
2. How to get into fastboot mode...should I boot into bootloader? How?....I possess a Samsung Galaxy R...very similar to the galaxy s2
3. I know how to get into recovery...I'm rooted and have a custom recovery CWM. Is recovery same as bootloader?
4. Then what is download mode....how is it different from bootloader mode or recovery mode?
5. I tried running fastboot commands through cmd by entering recovery and download mode...but got the same message as in point 1. Whats wrong???
The-Droidster said:
I was trying to understand what is fastboot. And then I got caught into all that bootloader jargon and couldn't differentiate one from the other. So I have a few questions. If someone could make me understand this stuff...I would be really grateful. Thanx guaranteed:laugh:
1. What is fastboot? When I run fastboot commands through cmd...I get <waiting for device>.
2. How to get into fastboot mode...should I boot into bootloader? How?....I possess a Samsung Galaxy R...very similar to the galaxy s2
3. I know how to get into recovery...I'm rooted and have a custom recovery CWM. Is recovery same as bootloader?
4. Then what is download mode....how is it different from bootloader mode or recovery mode?
5. I tried running fastboot commands through cmd by entering recovery and download mode...but got the same message as in point 1. Whats wrong???
Click to expand...
Click to collapse
Answers:
1) [Q] What is Fastboot?
[A] Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host via USB. It allows flashing of unsigned partition images. It is disabled in production devices since USB support has been disabled in the bootloader.
2) [Q] How to get into Fastboot Mode?
[A] I have no idea on your specific device, but I would imagine a little Google'ing and you could find the answer. I'm sure it's like any other device: a combination of certian button presses upon reboot or at boot.
3) [Q] Is recovery the same as bootloader?
[A] No. The bootloader, in literal terms, is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. This is one reason that all Android phones have different Custom ROMS developed due to high variance of processing hardware present on the device.
Your recovery is, as in Android, a recovery that refers to the dedicated, bootable partition that has the recovery console installed. A combination of key presses (or instructions from a command line) will boot your phone to recovery, where you can find tools to help repair (recover) your installation as well as install official OS updates. Because Android is open and has the recovery source code available, building a customized version with more and different options is relatively easy as well.
4) [Q] What is download mode?
[A] Download mode is for when you want to flash a new firmware using something like odin, If you update your firmware using kies, kies will automatically put the phone into download mode, if you use odin you have to put the phone into download mode yourself.
5) [Q] I tried running fastboot commands through cmd by entering recovery and download mode...but got the same message as in point 1. Whats wrong???
[A] You're confused as to what the difference is bewteen fastboot and recovery mode are. Hopfeuly, this gave some clarifiaction...
Related
Short version - is it possible to copy files from my phone to my PC using fastboot (or perhaps adb)? The cyanogenmod WIKI for fastboot, among others, imply that you can (under the section Examples -> Manual Nandroid Restore it says "Make a Nandroid backup, and copy the folder off your SD card to your desktop."). Sorry I'm not allowed to post the link due to being a new user, but this is what it says:
"Make a Nandroid backup, and copy the folder off your SD card to your desktop.
cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot"
If it is possible, is "flash" the correct command to be using? The description of the flash command when you run "fastroot help" implies it writes data to the phone, not from the phone to the PC... Unfortunately almost everything I search for around the flash command is examples showing how to load ROMs etc, I can't seem to find anything else that points to it being used to backup data...
[UPDATE] - From what I understand you can't copy files off the phone using fastboot commands, but can using adb - so a few questions:
- Does anyone know why adb wouldn't see my device (when I run "adb devices") but fastboot does (note that I'm on the fastboot screen)?
- Does adb require debugging mode to be on?
[UPDATE-2] - Still can't get adb working, suspect it's because USB debugging isn't enabled (though not sure how I can check?). I did try using fastboot to erase the /cache partition in case the lockout data was stored in there - but this didn't work unfortunately. Looking likely I'll just have to wipe it with fastboot oem unlock
Long version / background info:
Using a Samsung Nexus S with Android 4.1
The other night someone down the pub decided to try to unlock my phone, and apparently got the pattern wrong so many times it's now requiring me to enter my Google account details.
Fine, I enter the username / pass, only it says they're wrong - I know they're correct because I've just confirmed they are by logging into Gmail. It says they're incorrect so quickly that I suspect it's not even connecting to the web to check. The icons at the top imply there is signal, but it looks as though 3G / data is off, and there's no WiFi icon even though I'm sat next to my wireless router. I can't find any way to re-enable WiFi / 3G without first unlocking the phone - which requires a net connection. So I got into Fastboot Mode and selected Recovery and the device looks as though it's doing something (deleting all user data I assumed), but when it starts up it's exactly the same - which implies the user data hasn't been erased.
Then I installed fastboot, and the drivers for the Nexus S.
When I run "fastboot devices" I can see the phone listed, however bizarrely "adb devices" lists nothing.
"fastboot oem unlock" seems to work (the phone prompts me to confirm I want to give root access & delete all user data). I haven't done this yet as I want to see if I can save my data somehow using adb or fastboot commands.
For adb to work, your phone must be booted and USB debugging enabled. In your current situation, as far as I know, a factory reset is the only option.
The phone is either in ADB mode or in Fastboot mode. It can never be in both ADB and Fastboot at the same time. ADB requires the phone is up and running, Fastboot requires the phone is in bootloader mode. ADB requires debugging turned on.
If you unlock your bootloader, you can boot the phone using fastboot and your own recovery image using "fastboot boot myrecovery.img" (notice, no flash keyword here). Booting your device with this recovery image, you can do whatever you like and the image permits, e.g. running ADB and copying files. You'll need this recovery image, though.
Thanks, I did try fastboot with a recovery image, but it currently doesn't work because I need to unlock the bootloader (which will wipe all data anyway). Sounds like I will need to just wipe it
kuisma said:
The phone is either in ADB mode or in Fastboot mode. It can never be in both ADB and Fastboot at the same time. ADB requires the phone is up and running, Fastboot requires the phone is in bootloader mode. ADB requires debugging turned on.
If you unlock your bootloader, you can boot the phone using fastboot and your own recovery image using "fastboot boot myrecovery.img" (notice, no flash keyword here). Booting your device with this recovery image, you can do whatever you like and the image permits, e.g. running ADB and copying files. You'll need this recovery image, though.
Click to expand...
Click to collapse
Facing same issue.
Is there anyway so I could copy userdata.img to my pc and then delete gesture.key file (I am running Lollipop) with NO USB DEBUGGING ON in Fastboot mode.
I have gone through "unpacking and packing .img files"http://forum.xda-developers.com/galaxy-s2/general/ref-unpacking-repacking-stock-rom-img-t1081239
But it is out of my knowledge range can anyone get through it and explain me the same.
Hi! I am in the same situation... ADB not working, only fastboot... Any way to save my data? Do I need to unlock bootloader to install a stock recovery? Thank you!
Hi - I am in exactly same situation as well. I am using Oneplus 8t. Any help is greatly appreciated. thanks
So, if I completely wipe the storage of an android device, would I still be able to enter the Fastboot?
Is fastboot the same thing like bios? Where is fastboot-programm storaged?
Can I actually break the fastboot funktion somehow?
I also would be thankful if you just give me some good links. Thanks.
@GoFurthAndDie
1.
The BIOS of an Android device is the BOOTLOADER.
2.
In Android, FASTBOOT is a special diagnostic and engineering protocol that you can boot your Android device into. While in FASTBOOT, you can modify the file system images from a computer over a USB connection (AKA ADB ).
FASTBOOT is three different things with the same name:
A protocol for communication between your phone hardware and a computer
A software that runs on the phone when in fastboot mode
The executable file on the computer you use to make them talk to each other
3.
FASTBOOT is a Windows app.
jwoegerbauer said:
@GoFurthAndDie
1.
The BIOS of an Android device is the BOOTLOADER.
2.
In Android, FASTBOOT is a special diagnostic and engineering protocol that you can boot your Android device into. While in FASTBOOT, you can modify the file system images from a computer over a USB connection (AKA ADB ).
FASTBOOT is three different things with the same name:
A software that runs on the phone when in fastboot mode
The executable file on the computer you use to make them talk to each other
3.
FASTBOOT is a Windows app.
Click to expand...
Click to collapse
First thing, thank you very much for your answers.
Now I have an other question: if I use Fastboot to boot up TWRP and then use TWRP to wipe all data and all partitions from the intern storage of my android device and reboot it without flash any new ROMs (no /boot partition and all the other partitions), then my smartphone won't funktion any and won't be able to get into the fastboot mode on my phone.
If this happens, what could I do to make this smartphone functional again?
@GoFurthAndDie
Run
Code:
fastboot boot <<twrp.img>>
where <<twrp.img>> is replaced with your TWRP image name. This will boot you back into TWRP and should allow you to use TWRP to install a stock recovery and system partition.
Alternately, run
Code:
fastboot flash recovery <<twrp.img>>
to flash TWRP back to your recovery, and boot into recovery normally.
I have this phone and now it wont boot. Im thinking there is no OS to boot. It tries and says DM varity disabled at top of screen then says software cant be checked for corruption /bootloader unlocked. When in bootloader there is no recovery to boot into as well when plugged into desktop . ADB devices command is not seeing it. So my question is where do I start to install recovery and make PC (adb/fastboot) recognize device. If I could get adb to identify device shouldn't I be able to fastboot boot (twrp-disc.img) then flash twrp.zip then reboot bootloader and flash factory ROM and kernel or custom? Hate if I sound like a noob im learning all I can. Any help is greatly appreciated!
ADB, Fastboot & Recovery are 3 completely things independent from each other:
ADB program deals with Android OS ( folders / files / settings )
Fastboot program deals with device's bootloader
Recovery is a special bootable partition on device, which contains a recovery application installed in it
If
Code:
adb devices
doesn't show you a connected "device" then either USB debugging isnt enabled or Android OS isn't accessable at all or Android's USB service isn't set to "adb"
If
Code:
fastboot devices
doesn't show you device's mode as "fastboot" then device's bootloader isn't accessable at all.
Back to your "issue", well, it's NORMAL, starting from Android Marshmallow on ALL devices with an unlocked bootloader & disabled "dm-verity" will boot with those warning, so nothing to worry about, and , at the moment it's not possibile to remove those warnings.
When Fastboot is working, then you should be able to boot device into a Custom Recovery, of course only if that is at 100% suitable to the device.
Hi!
I'm still on my way ro root my Samsung Tab SM-T725, after upgrading to Android 11. Before Android 9 was on the device, succesfully rooted via Magisk. Updating and keeping the root status didn't work properly, the flashing process in Odin failed. Therfefore I had to flash the latest stock recovery, successfully. So now I have Android 11 on my device but no root. The bootloader is open and USB debugging enabled.
I tried the method described here. But the flashing in Odin failed again. So now I try to follow the instructions on the Magisk website. If I get everything right a processed recovery.img has to be flashed via ADB/Fastboot. That's new to me and I have questions.
- Is fastboot and download/recovery mode the same? Booting to the recovery and following "reboot to bootloader" leads to the turquois "Downloading" window. The same occurs when prompting "ADB reboot fastboot" e. g. Again the mentioned Downloading window shows up, nothing (special) with fastboot. Is that correct?
- Will therefore all fastboot commands not work? And only ADB is possible on my tablet? Is that common for Samsung devices?
- Can the flashing of the patched recovery.img (for Magisk) be done with ADB as well? Instructions always mention fastboot.
- My device doesn't show up in ADB when being in recovery mode. In normal mode it is listed when entering "ADB devices". Trying again in recovery mode the list stays empty - and all other commands have no effect. Current Samsung and Google USB drivers are installed. How could that be solved? Without ADB (perhaps fastbood) running in download mode I shouldn't be able to flash (and root the device) as planned.
I hope I described everything properly. I'm not that Android expert - but successfully managed to root a couple of devices over the years.
Samsung devices dont know of Fastboot mode. But you can run them in either Recovery or Odin / Download mode or Normal mode.
Running Samsung devices in Download mode you can flash ROM or update system in the Android device. When the Samsung device has entered Download mode, the device will boot from external sources. You can also make the stock ROM replaced in Download mode.
ADB mode is the Normal mode.
In Recovery mode ADB - with some exceptions - isn't working
Because your device is a Samsung one the Google USB drivers are senseless. Remove them to avoid conflicts.
Thanks for the quick and helpful response!
That makes clear why the tablet didn't show up in ADB. And that all rooting efforts for Samsung devices via that way should be obsolete. Strange enough that Magisk doesn't mention this on their instruction site.
So I'll have to try on with flashing a patched AP via Odin - and hope for a solution for my fail-problem.
Hello i wanted to ask about this since i dont see any other thread related to my issue, im trying to install magisk root and im at the stage of accessing fastboot/bootloader, when i go to recovery mode and select "reboot to bootloader" it just restarts the phone, i have tried adb commands didnt work either, same result, just restarts. The "unlock oem" option under developer options is enabled, i could flash another firmware of the same phone with SPD upgrade tool and its still not letting me get into bootloader, (to do this i must press down vol down and connect the usb while the program is on, and it is detected, otherwise it just restarts adb and fastboot tools will not detect it as download mode) any idea or suggestions on how I could root the phone, been thinking about twrp but not sure it would let me install that, looked into many pages about rooting this device and none show anything related maybe its not possible, i saw there are phones with blocked bootloader. the phone is android 9
Have you tried to
- flash the boot.img from the stockfirmware;
- install a recovery (twrp, orangefox, etc.) and rebooted to fastboot from recovery?
wenyendev said:
Have you tried to
- flash the boot.img from the stockfirmware;
- install a recovery (twrp, orangefox, etc.) and rebooted to fastboot from recovery?
Click to expand...
Click to collapse
TWRP and orangefox dont support my phone, there may be something unnoficial for twrp as i search and im not sure i can flash the phone with a specific boot file since to flash i use a single .pac file that contains the rom ill look into this
For now im not able to flash the phone with custom boot.img or recovery.img maybe i need to pack specific files i dont know about i give up for today
Sorry to hear that...
Have you tried the following command?
Apache config:
adb reboot bootloader
wenyendev said:
Sorry to hear that...
Have you tried the following command?
Apache config:
adb reboot bootloader
Click to expand...
Click to collapse
yes both that and adb reboot fastboot just restart the phone
Have you tried the method in the following page?
Hold volume up & power buttons. Otherwise, try volume down & power buttons.
How to get into fastboot and How to exit fastboot ZTE Blade A5 PRO? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
wenyendev said:
Have you tried the method in the following page?
Hold volume up & power buttons. Otherwise, try volume down & power buttons.
How to get into fastboot and How to exit fastboot ZTE Blade A5 PRO? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
Click to expand...
Click to collapse
This is not my phone model, its zte blade a5 plus 2020, vol up and power restarts the phone normally