What, if any, is the difference between flashing a fastboot miui rom from miflash and just executing the flash script from terminal?
In MiFlash tool, you can re-lock the bootloader.
So there is no actual difference in fastboot using only in extra commands that affects the bootloader.
editheraven said:
So there is no actual difference in fastboot using only in extra commands that affects the bootloader.
Click to expand...
Click to collapse
The above answer is simply incorrect. The only difference between interacting with fastboot through terminal and through miui flash tool is that the latter is a GUI interface.
People seem to forget that fastboot is nothing more than an alternative boot mode to interact with the bootloader (pass commands to it or get a bootloader variables using getvar...etc.).
You can lock the bootloader in terminal by passing the command fastboot oem-lock (which is what you will find at the end of the flash_all_lock script). For more fastboot commands and fuctions, you can type fastboot --help to list all available commands.
Related
Hi, I am relatively familiar with fastboot commands having had many android devices on which I had unlocked the bootloader but I haven't really found clarification on the difference between these commands.
I understand that boot and bootloader are different but how and will wiping one wipe the other as well, I also know that the command fastboot erase bootloader should NEVER be used.
So what is different between boot and bootloader.
Never mind I think I have resolved the issue if anyone else is confused.
Boot is where the kernel and files that the system has to boot are stored whereas bootloader is where the file that boots the boot.img files is.
Once again NEVER use the command fastboot erase bootloader
It's very, very, unfortunate that this happened so early in the life of my new Pixel 2. Here's what I did:
fastboot oem unlock
Device erases and boots normally, power off and boot into bootloader using volume and power.
Flash Android 8.1 beta using flash-all.bat
<Device is stuck in bootloader>
Flash factory Android 8.0 image, same thing
Try "fastboot --set-active=a" followed by "fastboot continue" and "fastboot --set-active b" followed by "fastboot continue", neither worked.
Try entering recovery or download mode from bootloader, neither worked.
I contacted Google support, and they didn't have any suggestions other than an RMA, so a new device should be on the way soon. Given the comments in this thread about using the wrong version of fastboot, I'll point out that I do have the latest version of platform-tools, and my fastboot version is:
Code:
C:\>fastboot --version
fastboot version 3db08f2c6889-android
Installed as C:\android-platform-tools\fastboot.exe
Anyone else have this experience? (I hope not.)
Edit: Okay, thanks to this post, I learned that I flash-all.bat, which uses "fastboot -w update image-*.zip", leads to this condition. However, flashing each img file in the zip archive individually gets the device back to health. Phew.
can you share the .bat file please?
I didn't use a bat script to recover the device, I typed each "fastboot flash <partition> <partition>.img" command by hand. Not the most efficient, but I wasn't expecting to do this more than once.
It's possible you had a bad download, did you attempt to redownload the stock image?
went to OTA Pie.
Bootloader is unlocked, but phone is S-On.
I'd like to TWRP then Magisk.
From Download mode (to install TWRP) I get "command not found" when I enter fastboot flash recovery twrp.img.
What am I doing wrong?
metropical said:
went to OTA Pie.
Bootloader is unlocked, but phone is S-On.
I'd like to TWRP then Magisk.
From Download mode (to install TWRP) I get "command not found" when I enter fastboot flash recovery twrp.img.
What am I doing wrong?
Click to expand...
Click to collapse
Put twrp.img into directory with adb and fastboot files for Win OS.
Command line must be run from directory where you have adb, fastboot and twrp.img.
same for Mac OS. Done this many times over the years. But not working with Pie on U11.
In Bootloader or Download I get: command not found for either fastboot devices or fastboot flash recovery /Users/fritz/Downloads/•\ android/twrp-3.4.img.
But adb works fine.
Showing modified and S-On, both of which I don't think I had with Oreo.
I had the wrong fastboot version. TWRP and Magisk are in.
For anyone looking for the right adb & fastboot tools for Mac OS, the link on this page, even though old, is good.
Android Basics: How to Install ADB & Fastboot on Mac, Linux & Windows
ADB and Fastboot are probably the most essential tools for any Android aficionado. They can do everything from backing up your device to unlocking your bootloader with a few simple steps. This paves the way for many new tweaks and customizations that weren't possible before. The required...
android.gadgethacks.com
OK, so I found an experimental version of TWRP, and I switched the active slot to "B." I thought I switched it back, but apparently not. Now I found "fastboot --set-active=a" command online but it throws an error at me, "unknown option -- set-active=a." Anyone know how to fix this? Do I need an older version of fastboot? A newer version? I'm using "Minimal ADB and Fastboot" 1.4.3 currently. Any help would be awesome.
Also I tried, "fastboot --set-active='a'" with the same result.
HopelesRomantc91 said:
OK, so I found an experimental version of TWRP, and I switched the active slot to "B." I thought I switched it back, but apparently not. Now I found "fastboot --set-active=a" command online but it throws an error at me, "unknown option -- set-active=a." Anyone know how to fix this? Do I need an older version of fastboot? A newer version? I'm using "Minimal ADB and Fastboot" 1.4.3 currently. Any help would be awesome.
Also I tried, "fastboot --set-active='a'" with the same result.
Click to expand...
Click to collapse
Try
Code:
fastboot set_active other
sd_shadow said:
Try
Code:
fastboot set_active other
Click to expand...
Click to collapse
Tried that, it just displayed all the options like if I typed help. So it's a different result. Kind of curious about why it's different.
Got an older version of fastboot, the commands are recognized, but slot-count is 1, and there are no slot suffixes.
OK I GOT IT!!! So I had to:
1. Find firmware from RSA
2. fastboot flash partition gpt.bin
3. fastboot flash motoboot bootloader.img
4. fastboot reboot-bootloader
5. Now RSA reads it, and I was able to do a full recovery via RSA
sd_shadow said:
Try
Code:
fastboot set_active other
Click to expand...
Click to collapse
thanks you
We're trying to install a GSI ROM. We get the error FAILED (remote: 'partition table doesn't exist')
We ran
Code:
fastboot getvar all
and see all of the partition tables listed or at least most of them. We do not see a system partition listed.
Why would this be? If I create one, how would I do that? How would I get the correct size? I'm assuming
Code:
fastboot create-logical-partition [NAME SIZE]
?
Does anyone know if I cannot boot into fastbootd and only boot into fastboot, am I still able to create a partition? It seems this device is boot looped. I haven't been able to boot into recovery. I can only get fastboot and EDL modes. Stock firmware is not available.
Starting with Android 10 fastboot got moved to Android's user-space, what requires this pair of commands
Code:
adb reboot fastboot
fastboot reboot fastboot
to get fastboot working.
xXx yYy said:
Starting with Android 10 fastboot got moved to Android's user-space, what requires this pair of commands
Code:
adb reboot fastboot
fastboot reboot fastboot
to get fastboot working.
Click to expand...
Click to collapse
Thank you for the reply. I do understand that part, however I cannot get into adb. If it is stuck in a bootloop, how can I access adb?
The bootloader is unlocked and oem debugging is on. It is a Moxee M2160 MH-T6000 Qualcomm QM215. We cannot find any stock firmware for it.