While I was unlocking my atrix and installing Tenfars recovery I saw a list of fastboot commands in the command prompt window. Where can I find this list again?
Thanks
vanstorm said:
While I was unlocking my atrix and installing Tenfars recovery I saw a list of fastboot commands in the command prompt window. Where can I find this list again?
Thanks
Click to expand...
Click to collapse
It would be great if someone could compile a list of fastboot commands for us that haven't used it much.
Here's a start that I found in another forum tread:
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Notable fastboot commands:
fastboot devices - If you don't know anything, this is the ONE thing you have to know.
fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - this will unlock your bootloader - NOTE THIS WILL VOID YOUR NEXUS ONE WARRANTY
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Related
Dear Member,
I'm new to rooring and flashing custom ROMS...
i have a folio 100 and after a lot of googling and hardwork i finally managed to root my device on windows XP.. then i tried to install Jelly Bean / CM10 (4.1.1) Alpha 2 - 27.09.2012 from http://forum.xda-developers.com/showthread.php?t=1864774 and followed the instructions.
initially when i typed fastboot devices i was getting "? fastboot" and rest of the commands returned 0x2 error.
then i treid
fastboot -i 0x955 erase userdata
fastboot -i 0x955 erase system
fastboot -i 0x955 erase cache
fastboot -i 0x955 erase linux
fastboot -i 0x955 erase recovery
till now everything worked like a charm but when i tried to run the last command
fastboot -i 0x955 flash recovery recovery-cwm-6.0.1.4.img
i'm getting error message "unable to load recoveryxxxx.img"
now i treid to reboot the device and its saying "magic value mismatch" please help me out..
Nonlxpe Menteur
leaderrocks said:
Dear Member,
I'm new to rooring and flashing custom ROMS...
i have a folio 100 and after a lot of googling and hardwork i finally managed to root my device on windows XP.. then i tried to install Jelly Bean / CM10 (4.1.1) Alpha 2 - 27.09.2012 from http://forum.xda-developers.com/showthread.php?t=1864774 and followed the instructions.
initially when i typed fastboot devices i was getting "? fastboot" and rest of the commands returned 0x2 error.
then i treid
fastboot -i 0x955 erase userdata
fastboot -i 0x955 erase system
fastboot -i 0x955 erase cache
fastboot -i 0x955 erase linux
fastboot -i 0x955 erase recovery
till now everything worked like a charm but when i tried to run the last command
fastboot -i 0x955 flash recovery recovery-cwm-6.0.1.4.img
i'm getting error message "unable to load recoveryxxxx.img"
now i treid to reboot the device and its saying "magic value mismatch" please help me out..
Click to expand...
Click to collapse
First, download the latest & most stable ROM (at the moment), including the ROM, GAPPS, recovery-cwm-CM10-A3.img & formatsd.zip
http://forum.xda-developers.com/showthread.php?t=1864774
Actually, you just need to flash the recovery through fastboot, other else can done in the recovery.
1. Copy all the ROM, GAPPS & formatsd.zip into your memory card. Then insert it into your Folio.
2. Run command prompt, make sure your tablet is connected with your PC in fastboot mode.
To erase existing/stock recovery. In command prompt, go into the fastboot program folder and type the following commands
Code:
fastboot erase recovery
3. Copy the CWM Recovery into your fastboot adb folder.
To flash CWM Recovery
Code:
fastboot flash recovery recovery-cwm-CM10-A3.img
fastboot reboot
4. Enter Recovery. Before you begin, wipe everything (except external_sd) in the CWM Recovery, after wiped, you can install the 3 zip files one by one. After finish, just reboot system.
Full procedure also stated in the link I provided, please scroll down.
Hope that helps you.
So did above solution help? I had a similar issue, and I resolved it by just booting the recovery image from fastboot, i.e.
Code:
fastboot boot recovery.img
Once you get into recovery you can flash an image which will in most cases flash a recovery image along with it. If not, you can try to flash the recovery image again once you've done a full wipe from the booted recovery.
Download
Lenovo Yoga Book Android 6.0 ROM: androidfilehost.com/?fid=817550096634799507
Intel Flash Utility: 01.org/android-ia/downloads/intel-platform-flash-tool-lite
Custom Recovery: twrp.me/lenovo/lenovoyt_x703f.html
Magisk Root: magiskmanager.com
Flashing ROM
With the yoga book in recovery, either use the intel utility + json files to flash, or these commands to flash with adb tools with the files from the archive. To unlock bootloader, enable dev mode, then settings>developer>oem unlock.
Fastboot Flashing Commands:
fastboot flashing unlock
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Click to expand...
Click to collapse
Set Country Code
how to make Halo Keyboard work. Go into Contacts and create a random one, then type into search ####6020# then set country code. This also fixes the "easyimage-country code" error which causes OTA updates to fail. During your system setup process, if you get constant touchpal errors, go into system settings and disable Touchpal app.
OTA Updates
You should now be able to run thru 5+ OTA updates for a few hours till you're at 7.1. These require a locked boot. If you unlock it, then everytime there's a new update you'll have to unroot and relock.
Root
Download twrp and magisk from the above links
$ fastboot flashing unlock
$ fastboot flash recovery twrp.img
go into advanced sideload
$ adb sideload magisk.zip
To get a full Linux desktop experience with chrome with extensions and dev tools, I recommend the "Linux Deploy" and "Xserver" app to install Ubuntu desktop.
there`s already a thread for this here https://forum.xda-developers.com/yoga-book/how-to/yoga-book-yb1-x90f-android-how-to-flash-t3709930
thread closed
Several users of this excellent terminal had problems erroneously flashing the stock firmware since the fingerprint sensor has completely disappeared from the software options, reading in several forums I realize that there is no solution for the users of moto Z more However, in past generations as MOTO G4 PLUS the same problem occurred, and after months it was discovered that the problem was an error in the lines of the HW partition, which can be solved with an HW partition without errors and the program WINMERGE
https://www.youtube.com/watch?v=o2Pao6lnINg
Reason why, I ask you to please share your HW partition which can be obtained with Partitions Backup & Restore, requires root and can be found in google play, I thank you for your collaboration.
Im XT 1650-03 Build NPLS26.118-20-5-11 December security patch 7.1.1
In the following link is the information that brought me to create this post
https://forum.xda-developers.com/mo...luss-model-changed-to-g4-lost-t3496912/page10
Just popping in from the G4 Plus forums - please, if you try this, that you ensure you do have the hw partition (or a similar partition) before trying. Also, please don't use the partition flashing instructions straight from that thread - Moto Z devices are likely to have a different partition layout than Moto G4/Plus devices. You'll need a Moto Z specific partition layout to have an idea about what partition to pull, edit and flash (whether you're flashing an edited file or an undamaged copy from another device).
Also, those partition flashing commands are quite powerful and have the potential to overwrite other partitions if directed to the wrong partition, which may hard brick your device to the point where you may have to have the motherboard changed. Also, we've seen mixed results from this method, but it's possibly worth trying.
I wish Moto Z users all the best, just be careful.
Here is an unmodified hw partition backup.
Please backup your own partition just in case!
For XT1650-03 - single SIM
contains two hw.img files
unmodified single sim (md5sum 1d779d8b27bce0c1da8d507092ae2d51 hw.img.single.sim)
modified single to dual sim (md5sum 1bb3dde5a66f5ac15be305dda83aa2d0 hw.img.single.to.dual.sim)
edit:
extract on phones internal sdcard, backup and flash with adb shell:
Code:
su
dd if=/dev/block/platform/soc/624000.ufshc/by-name/hw of=/sdcard/hw.img.bak
dd if=/sdcard/hw.img.single.sim of=/dev/block/platform/soc/624000.ufshc/by-name/hw
Run the third command only after the second command has succeeded!
Loader009 said:
Here is an unmodified hw partition backup.
Please backup your own partition just in case!
For XT1650-03 - single SIM
contains two hw.img files
unmodified single sim (md5sum 1d779d8b27bce0c1da8d507092ae2d51 hw.img.single.sim)
modified single to dual sim (md5sum 1bb3dde5a66f5ac15be305dda83aa2d0 hw.img.single.to.dual.sim)
edit:
extract on phones internal sdcard, backup and flash with adb shell:
Code:
su
dd if=/dev/block/platform/soc/624000.ufshc/by-name/hw of=/sdcard/hw.img.bak
dd if=/sdcard/hw.img.single.sim of=/dev/block/platform/soc/624000.ufshc/by-name/hw
Run the third command only after the second command has succeeded!
Click to expand...
Click to collapse
Thnx a lot but dont work for me, im dual sim, after run the comands correctly and flash stock, fingerprint is missing and storage capacity now are of 32 gbs, i reflash my backup u.u
Fingerprint sensor is working again!
I finally managed to get my fingerprint sensor back working. My device is a Moto Z XT1650-03 on reteu channel. Please note, that this procedure updates your phone to Android Oreo 8.0.0! Here is what I've done:
First flash the GRIFFIN_NPLS26.118-20-5-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Stock ROM from firmware.center. I used this bunch of commands to flash with fastboot.
Code:
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash system system.img_sparsechunk.17
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Let the device reboot an do the setup until you get to the homescreen, then shutdown the device.
Download the Android Oreo 8.0.0 OTA from the "Moto Z Android Oreo Update Available -Soak Test- (screenshot)" thread, post #182. If the filename only consists of many random letters, rename it to ota.zip and check with an archiving program if you're able to open that zip file.
Now boot into bootloader and select "Recovery Mode" from the available options.
After some seconds an android icon with the text "No Command" appears. To continue press and hold Power, and at the same time press Volume Up once. Release both buttons after the boot options appear.
Connect your device to the PC and make sure it's listed under ADB with
Code:
adb devices
Select "Apply update from ADB" and push the downloaded ota.zip to the device with
Code:
adb sideload ota.zip
After the update has finished (takes some time), select "Wipe cache partition" to wipe the cache.
Finally select "Reboot system now"
After reboot your fingerprint sensor should be functional again
Specifications without engagement, subject to errors and modifications
Hello,
My A3 was unlocked with root, android 9 February security patch
Randomly Google play service stop working, after deleting cache it was fine.
Again randomly the prone start to act weird, restart it and then appear " Can't load android system. Your data may be corrupt."
The only options are try again and Factory data reset. ( like in the image https://i.redd.it/8nf9k5v33u1z.jpg )
Because i have important information i can't do factory reset so tried to flash stock fastboot rom with miflash.
Fastboot was accessible, BUT after trying to adb devices check it shows- List of devices attached* daemon not running. starting it now on port 5037 ** daemon started successfully * so it was not really able to connect. My Computer does not recognise it as Mi A3.
So after flashing fastboot Android One logo unlocked, appear several time, like blinking 4-5 times, and again jump in to fastboot mode.
First tried to flash V10.3.15.0.PFQEUXM, than V10.3.14.0.PFQEUXM. None of them did the work.
Attaching some logs.
By the way i use MiFlash20181115 it was the latest found
Thank you in advance , BE HAPPY and SAFE
Tried to add before fastboot %* reboot , fastboot $* set_active a , bur the result was the same
1. avoid downgrades, your data might get corrupted and you'll end up with factory reset anyway
2. per the logs it seems that everything flashes correctly, make sure that you have partition A as active (https://forum.xda-developers.com/showpost.php?p=81408355&postcount=2). Type both commands (one will fail) in cmd window with phone connected via fastboot.
_mysiak_ said:
1. avoid downgrades, your data might get corrupted and you'll end up with factory reset anyway
2. per the logs it seems that everything flashes correctly, make sure that you have partition A as active (https://forum.xda-developers.com/showpost.php?p=81408355&postcount=2). Type both commands (one will fail) in cmd window with phone connected via fastboot.
Click to expand...
Click to collapse
Phone is not recognised in cmd, only if use- Install from ADB option from recovery it show the device.
alexandarpb said:
Phone is not recognised in cmd, only if use- Install from ADB option from recovery it show the device.
Click to expand...
Click to collapse
You seem to confuse ADB and Fastboot. Connect mobile in FASTBOOT mode and type in those two commands. If there's an error, paste the output here.
_mysiak_ said:
You seem to confuse ADB and Fastboot. Connect mobile in FASTBOOT mode and type in those two commands. If there's an error, paste the output here.
Click to expand...
Click to collapse
PS C:\Users\Sashko\Desktop\platform-tools> fastboot set_active a
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\Users\Sashko\Desktop\platform-tools> fastboot --set-active=a
C:\adb\fastboot.exe: unknown option -- set-active=a
PS C:\Users\Sashko\Desktop\platform-tools>
alexandarpb said:
PS C:\Users\Sashko\Desktop\platform-tools> fastboot set_active a
usage: fastboot [ <option> ] <command>
...
PS C:\Users\Sashko\Desktop\platform-tools> fastboot --set-active=a
C:\adb\fastboot.exe: unknown option -- set-active=a
PS C:\Users\Sashko\Desktop\platform-tools>
Click to expand...
Click to collapse
Uninstall/remove existing fastboot.exe from all locations on your PC and use the latest version https://developer.android.com/studio/releases/platform-tools
_mysiak_ said:
Uninstall/remove existing fastboot.exe from all locations on your PC and use the latest version https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
From my previous PC i managed to get proper result
C:\Users\PC-1\Desktop\mi a3\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.002s]
Finished. Total time: 0.012s
C:\Users\PC-1\Desktop\mi a3\platform-tools>
Should i now use miflash again to flash the fastboot rom or?
Thank you so much for all your answers!!!
alexandarpb said:
From my previous PC i managed to get proper result
C:\Users\PC-1\Desktop\mi a3\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.002s]
Finished. Total time: 0.012s
C:\Users\PC-1\Desktop\mi a3\platform-tools>
Should i now use miflash again to flash the fastboot rom or?
Thank you so much for all your answers!!!
Click to expand...
Click to collapse
Just start the phone. Re-flash only if it won't boot.
_mysiak_ said:
Just start the phone. Re-flash only if it won't boot.
Click to expand...
Click to collapse
Thank you, you are my saviour, unfortunately my data is gone... but at least it work now.
Thank you for everything
alexandarpb said:
Thank you, you are my saviour, unfortunately my data is gone... but at least it work now.
Thank you for everything
Click to expand...
Click to collapse
I suppose that you already performed the factory reset, but for the future - you could try flashing TWRP first, backup/export data and perform factory reset only after that.
_mysiak_ said:
I suppose that you already performed the factory reset, but for the future - you could try flashing TWRP first, backup/export data and perform factory reset only after that.
Click to expand...
Click to collapse
Definitely, but i was thinking that if the phone is not recognised in adb command it would not be able to do anything with fastboot command. It is nonsense i know...
Thank again, by the way which recovery is better OrangeFox Recovery or TWRP ?
alexandarpb said:
Definitely, but i was thinking that if the phone is not recognised in adb command it would not be able to do anything with fastboot command. It is nonsense i know...
Thank again, by the way which recovery is better OrangeFox Recovery or TWRP ?
Click to expand...
Click to collapse
I haven't used custom recovery for A3 yet, but TWRP would be my first choice if a need occured.
Greetings One Fusion users, after some time of research and testing I'd like to write this guide for you all. The guides online were inconsistent and outdated so the main purpose of this is giving an updated guide.
But. I have to say this, if you follow this guide correctly your phone will be ERASED, you don't need to unlock bootloader or do extra things not mentioned in this guide. Also, I'm not responsible of any damage made to your device.
Part 1: What we need?
1: Minimal ADB and Fastboot: You might know it, or not, if that's the case go and Google it or get it here, thanks goes to @shimp208
Just install it but don't open it yet.
2: Drivers: Get your 32 bits drivers here, and 64 bits drivers here.
Just install 32 bits or 64 bits, depends of your Windows version.
3: Firmware: There's one place of firmwares for all our Moto devices, just click here and you will get a bunch of folders, those are named by your country/region and carrier. To know yours, just go to Settings>About Phone, then you'll see Software Channel, the name in this is the folder you'll be picking in the mentioned website, download the latest one or older if you want to downgrade.
Unzip it wherever you want, just make sure you remember the folder, for practical purposes, unzip it where you installed Minimal ADB and Fastboot before.
4: Your stock USB-A to USB-C cable, USB-C to USB-C might work too but haven't tested.
5: Patience.
Part 2: Barry Allen... I mean The Flash.
Save your data. Seriously, if you don't want to say bye to your data you still can save now.
But if you alredy have backup or you just don't care, let's begin.
1. Open a command promp, go to the folder where you already unzipped your firmware, hold your Shift key and right click on a blank spot of the folder, then click on Open command promp here.
2. Turn off your phone, once off, hold volume down and power buttons until you see the green android, at this point plug in your phone to your computer. On the command promp write
Code:
fastboot devices
If drivers are correctly installed, your serial number will be displayed, if not, your device could be still being recognized, try again in few minutes or reinstall drivers, rebooting PC may help this sometimes.
If your serial number was displayed, you can now proceed to flash the firmware, to ease this thing I will write you the commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot reboot
Just copy (all of them, not one by one) and paste them in the command promp, the flash starts.
After everything got flashed, you will have the last command ready for you to hit enter, and your device will reboot.
Thanks for reading, I hope I've helped you.
Questions are welcome!
just a little tip if you don't see the "Open command prompt here." as you shift+right click.
Click on the PowerShell option, wait until a blue window show up and type start cmd, now the command prompt window will open and you can continue with the command lines.
Does any of you guys know how can I disable the bootloader unlocked screen? I have recently rooted my device and can't find anywhere a way to disable the "bootloader unlocked" screen
and to erase the system partition as is ?, you also need how to install one in the same system partition