Every time I try and run a fastboot command... it just shows the fastboot help menu.
"fastboot devices" = menu
"fastboot recovery c:\recovery-en-goapk-0630-1029.img" = menu
all i ever get is:
--------------------------------
Fastboot version 1.0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
setserial <serial> set the device serial number
setrev <rev> set the device hardware revision
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
-n <page size> specify the nand page size. default:
2048
----------------------------------------------------
i am unlocked.
i am in fastboot mode on my phone
i have used fastboot before to install 2.3.4 and i had zero issues
Anyone know why this could be happening?
no reply yet?
"fastboot flash recovery c:\recovery-en-goapk-0630-1029.img"
nevermind... im an idiot.
DISREGARD!
lol it happens.
i actually figured it out right as you posted a reply. thanks a lot, though!
Writing recovery failed. Any idea????
Good afternoon sirs !
I need some help from you regarding my one action bike.
I recently bought it linked to the telephone operator Claro (BR) which the last update he received was in October 2019 on Android version 9
PSBS29.21-20-7 version.
I can't upgrade to a later version and saw that on this site: https://mirrors.lolinet.com/firmware/moto/troika/official/AMXBR/ has a more current version ending 49-7-1. I wonder how do I install it either via RSD or ADB? Remembering! Need to unlock bootloader? Has anyone ever updated it otherwise?
Diogownz said:
Good afternoon sirs !
I need some help from you regarding my one action bike.
I recently bought it linked to the telephone operator Claro (BR) which the last update he received was in October 2019 on Android version 9
PSBS29.21-20-7 version.
I can't upgrade to a later version and saw that on this site: https://mirrors.lolinet.com/firmware/moto/troika/official/AMXBR/ has a more current version ending 49-7-1. I wonder how do I install it either via RSD or ADB? Remembering! Need to unlock bootloader? Has anyone ever updated it otherwise?
Click to expand...
Click to collapse
How are you! You must first have unlock bootloader and then flash the firmware with adb !!
Polnareff said:
How are you! You must first have unlock bootloader and then flash the firmware with adb !!
Click to expand...
Click to collapse
How are you! Exact! First you unlock the bootloader and then flash the firmware.
1) Install motorola drivers
2) download the adb
3) Extract the firmware in the adb folder
3) Enter fastboot mode on the cell phone (volume down + power)
4) Enter through the system symbol (plus two)
4.1 Put fastboot devices
4.2 copy all this ans paste:
%fastboot% oem fb_mode_set
%fastboot% flash pit diskmap.pit
%fastboot% flash fwbl1 fwbl1.nbl1.bin
%fastboot% flash ldfw_a ldfw.bin
%fastboot% flash ldfw_b ldfw.bin
%fastboot% flash keystorage_a keystorage.bin
%fastboot% flash keystorage_b keystorage.bin
%fastboot% flash bootloader_a bootloader.bin
%fastboot% flash bootloader_b bootloader.bin
%fastboot% flash modem_a modem.bin
%fastboot% flash vbmeta_a vbmeta.img
%fastboot% flash oem_a oem.img
%fastboot% flash oem_b oem_other.img
%fastboot% flash logo_a logo.bin
%fastboot% flash dtbo_a dtbo.img
%fastboot% flash boot_a boot.img
%fastboot% flash system_a system.img_sparsechunk.0
%fastboot% flash system_a system.img_sparsechunk.1
%fastboot% flash system_a system.img_sparsechunk.2
%fastboot% flash system_a system.img_sparsechunk.3
%fastboot% flash system_a system.img_sparsechunk.4
%fastboot% flash system_a system.img_sparsechunk.5
%fastboot% flash system_a system.img_sparsechunk.6
%fastboot% flash system_a system.img_sparsechunk.7
%fastboot% flash system_a system.img_sparsechunk.8
%fastboot% flash system_a system.img_sparsechunk.9
%fastboot% flash system_a system.img_sparsechunk.10
%fastboot% flash system_b system_other.img_sparsechunk.0
%fastboot% flash system_b system_other.img_sparsechunk.1
%fastboot% flash system_b system_other.img_sparsechunk.2
%fastboot% flash vendor_a vendor.img
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% erase ddr
%fastboot% oem fb_mode_clear
%fastboot% reboot bootloader
This is more or less the method ... in the forum it is better explained! don't be scared !!!
Polnareff said:
How are you! Exact! First you unlock the bootloader and then flash the firmware.
1) Install motorola drivers
2) download the adb
3) Extract the firmware in the adb folder
3) Enter fastboot mode on the cell phone (volume down + power)
4) Enter through the system symbol (plus two)
4.1 Put fastboot devices
4.2 copy all this ans paste:
%fastboot% oem fb_mode_set
%fastboot% flash pit diskmap.pit
%fastboot% flash fwbl1 fwbl1.nbl1.bin
%fastboot% flash ldfw_a ldfw.bin
%fastboot% flash ldfw_b ldfw.bin
%fastboot% flash keystorage_a keystorage.bin
%fastboot% flash keystorage_b keystorage.bin
%fastboot% flash bootloader_a bootloader.bin
%fastboot% flash bootloader_b bootloader.bin
%fastboot% flash modem_a modem.bin
%fastboot% flash vbmeta_a vbmeta.img
%fastboot% flash oem_a oem.img
%fastboot% flash oem_b oem_other.img
%fastboot% flash logo_a logo.bin
%fastboot% flash dtbo_a dtbo.img
%fastboot% flash boot_a boot.img
%fastboot% flash system_a system.img_sparsechunk.0
%fastboot% flash system_a system.img_sparsechunk.1
%fastboot% flash system_a system.img_sparsechunk.2
%fastboot% flash system_a system.img_sparsechunk.3
%fastboot% flash system_a system.img_sparsechunk.4
%fastboot% flash system_a system.img_sparsechunk.5
%fastboot% flash system_a system.img_sparsechunk.6
%fastboot% flash system_a system.img_sparsechunk.7
%fastboot% flash system_a system.img_sparsechunk.8
%fastboot% flash system_a system.img_sparsechunk.9
%fastboot% flash system_a system.img_sparsechunk.10
%fastboot% flash system_b system_other.img_sparsechunk.0
%fastboot% flash system_b system_other.img_sparsechunk.1
%fastboot% flash system_b system_other.img_sparsechunk.2
%fastboot% flash vendor_a vendor.img
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% erase ddr
%fastboot% oem fb_mode_clear
%fastboot% reboot bootloader
This is more or less the method ... in the forum it is better explained! don't be scared !!!
Click to expand...
Click to collapse
Thank you I will have to get with you when I got more time. I'm ready to r..t my phone. I'm sure I will need help. Thank you so much.
Are you struggling to install custom roms on this device?
Lots of recovery errors?
Can't boot to any rom?
Don't worry. Fastboot is a good way to avoid such nonsense...
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install any custom rom & miui recovery rom through fastboot
Steps:
1. Extract Fastboot OTA Tool. Put the ROM zip in it's root.
2. Run the flash script.
3. Wait till the script asks for device.
4. Boot device to fastboot & connect.
After Installation, it'll be headed to recovery:
You can format to start fresh (or)
Just boot up, for dirty flash way
Windows users:
Make sure you have usb drivers installed through manual method. This is done only once.
Refer this on how to install them... Download USB Drivers from here.
Linux users: Must have latest python & pip
For Ubuntu distros:
sudo apt install python python-pip
And have an alias into ~/.bashrc or ~/.bash_aliases file:
alias python=python3
For Arch based distros:
sudo pacman -S python python-pip
For Fedora:
sudo dnf install snapd python3.9 python3-pip
For Mac users, make sure you allow img2simg tool from Privacy & Security to work. Or Disable Gatekeeper temperorily.
Thanks to @LoV432 for his auto extraction idea.
& @lyoko_xana to bringup Mac issues.
If you have any trouble using this tool, please feel free to reply here...
Happy flashing
According to the script, it is used exclusively for pure flash.
Can you please make an option for upgrade (dirty flash) as well?
StaryMuz said:
According to the script, it is used exclusively for pure flash.
Can you please make an option for upgrade (dirty flash) as well?
Click to expand...
Click to collapse
It does dirty flash bydefault (caz it doesn't affect data partition). It'll be clean flash only when you wipe from recovery at post install...
I've edited post & clarified this...
this tool doesn't seem to work with xiaomi eu roms
sahbimath said:
this tool doesn't seem to work with xiaomi eu roms
Click to expand...
Click to collapse
Currently, it's only for OTA based roms, that have payload.bin in it.
I'll update the script for eu roms too when I get time.
sahbimath said:
this tool doesn't seem to work with xiaomi eu roms
Click to expand...
Click to collapse
Done adding the scripts for miui roms. Check it out & confirm if that works.
...testing it next time when I upgrade or change rom
Zirila said:
...testing it next time when I upgrade or change rom
Click to expand...
Click to collapse
K
Anybody with the m12.0.11 OTA update for sunny Global?
seunlayi said:
Anybody with the m12.0.11 OTA update for sunny Global?
Click to expand...
Click to collapse
I don't think it's the right place to ask.
but why ?
This adds auto rom extraction to the OTA based script. So you just put the rom zip in the root directory and the script auto extracts it.
Disclaimer: I have no actual knowledge of this so theres a 50/50 chance this might nuke your pc or something
I will try this tool later , it seem promising coz it has dirty flash feature , it is very tiring when the only option is clean flash/no internal data after that
Newer update.
Fastboot_OTA_20210715
Instructions in the main thread.
Changelog (2021-07-15):
- Auto Extraction support (Thanks to @LoV432 for the idea)
- Merged updater script & payload extractions
- Fixed "Partition does not exist" error
- Updated flash instructions for linux & mac
If you have trouble working with fastboot for windows, follow this guide if you're ok installing manually
Script error.
Vendor is entered only as Vendor, not as Vendor_a or Vendor_b.
The script did everything correctly after editing.
tools\fastboot %* delete-logical-partition vendor
tools\fastboot %* create-logical-partition vendor 4096
And then flash to a/b:
tools\fastboot %* flash -w system_a output\system.img
tools\fastboot %* flash system_ext_a output\system_ext.img
tools\fastboot %* flash -w system_b output\system.img
tools\fastboot %* flash system_ext_b output\system_ext.img
tools\fastboot %* flash product_a output\product.img
tools\fastboot %* flash product_b output\product.img
StaryMuz said:
Script error.
Vendor is entered only as Vendor, not as Vendor_a or Vendor_b.
The script did everything correctly after editing.
tools\fastboot %* delete-logical-partition vendor
tools\fastboot %* create-logical-partition vendor 4096
And then flash to a/b:
tools\fastboot %* flash -w system_a output\system.img
tools\fastboot %* flash system_ext_a output\system_ext.img
tools\fastboot %* flash -w system_b output\system.img
tools\fastboot %* flash system_ext_b output\system_ext.img
tools\fastboot %* flash product_a output\product.img
tools\fastboot %* flash product_b output\product.img
Click to expand...
Click to collapse
Fastbootd already capable of retrieving active slot through get-active-slot implicitly & flash it to inactive slot. No need to explicitly declare & flash on a specific slot.
It's mandatory for physical partitions, not for logical partitions.
Also, explicit declaration is a bad practice
I was wrong about Vendor.
I flashed PE+ and the system did not load afterwards.
After editing the following, it worked.
tools\fastboot -w %* flash system_a output\system.img
tools\fastboot %* flash system_ext_a output\system_ext.img
tools\fastboot -w %* flash system_b output\system.img
tools\fastboot %* flash system_ext_b output\system_ext.img
tools\fastboot %* flash product_a output\product.img
tools\fastboot %* flash product_b output\product.img
tools\fastboot %* flash vendor_a output\product.img
tools\fastboot %* flash vendor_b output\product.img
But that's not right either.
I found out that:
Slot B should not flash during an update, only during a full ROM install.
For the update, it is flash to slot A, from where the running system updates itself (running from slot B).
The instructions executed during full flash and update should therefore be adapted to this.
Full flash to both B and A.
Update to A only.
If the update then fails, the system can roll back.
EDIT: scripts
I edited your script to flash only to A and only to B.:
Spoiler: Only to B
@Echo off
cd "%~dp0"
echo This is a recovery rom installation script for Windows
mkdir output
tools\7za.exe x *.zip -aos
if exist payload.bin if not exist output\vendor.img (
echo.
echo Extracting images from the build...
tools\payload_dumper.exe payload.bin
)
if exist dynamic_partitions_op_list (
echo.
echo Decompressing system
tools\bin\brotli.exe -d system.new.dat.br
echo Decompressing system_ext
tools\bin\brotli.exe -d system_ext.new.dat.br
echo Decompressing product
tools\bin\brotli.exe -d product.new.dat.br
echo Decompressing vendor
tools\bin\brotli.exe -d vendor.new.dat.br
echo Unpacking all the images...
tools\bin\sdat2img.exe system.transfer.list system.new.dat output\system.img
tools\bin\sdat2img.exe system_ext.transfer.list system_ext.new.dat output\system_ext.img
tools\bin\sdat2img.exe product.transfer.list product.new.dat output\product.img
tools\bin\sdat2img.exe vendor.transfer.list vendor.new.dat output\vendor.img
)
echo.
echo Checking fastboot version. If it's not v31 or above, you're screwed...!
tools\fastboot %* --version
echo.
echo Flashing stock boot for mojito
fastboot --set-active=a
tools\fastboot %* flash boot_b tools\boot_mojito.img
fastboot --set-active=b
echo Booting to fastbootd
tools\fastboot %* reboot fastboot
fastboot --set-active=a
echo.
echo Removing existing logical partitions only slot B ...
tools\fastboot %* delete-logical-partition vendor_b
tools\fastboot %* delete-logical-partition system_b
tools\fastboot %* delete-logical-partition system_ext_b
tools\fastboot %* delete-logical-partition product_b
echo.
echo Creating new logical partitions...
tools\fastboot %* create-logical-partition vendor_b 4096
tools\fastboot %* create-logical-partition system_b 4096
tools\fastboot %* create-logical-partition system_ext_b 4096
tools\fastboot %* create-logical-partition product_b 4096
echo.
echo Flashing the ROM...
echo Just ignore the below sparse file errors...
tools\fastboot -w %* flash system_b output\system.img
tools\fastboot %* flash system_ext_b output\system_ext.img
tools\fastboot %* flash product_b output\product.img
tools\fastboot %* flash vendor_b output\vendor.img
echo.
echo Flashing boot partitions...
tools\fastboot %* reboot bootloader
tools\fastboot %* flash boot_b output\boot.img
tools\fastboot %* flash vendor_boot_b output\vendor_boot.img
fastboot --set-active=b
echo.
echo Cleaning Stuff...
rmdir /q /s META-INF output
del /f *.img *.br *.dat *.list payload.bin care_map.pb payload_properties.txt dynamic_partitions_op_list
echo.
echo Done. Rebooting to recovery...
timeout 1 > nul
echo ...3...
timeout 1 > nul
echo ..2..
timeout 1 > nul
echo .1.
timeout 1 > nul
tools\fastboot %* reboot recovery
echo Done...
pause
Spoiler: Only to A
@Echo off
cd "%~dp0"
echo This is a recovery rom installation script for Windows
mkdir output
tools\7za.exe x *.zip -aos
if exist payload.bin if not exist output\vendor.img (
echo.
echo Extracting images from the build...
tools\payload_dumper.exe payload.bin
)
if exist dynamic_partitions_op_list (
echo.
echo Decompressing system
tools\bin\brotli.exe -d system.new.dat.br
echo Decompressing system_ext
tools\bin\brotli.exe -d system_ext.new.dat.br
echo Decompressing product
tools\bin\brotli.exe -d product.new.dat.br
echo Decompressing vendor
tools\bin\brotli.exe -d vendor.new.dat.br
echo Unpacking all the images...
tools\bin\sdat2img.exe system.transfer.list system.new.dat output\system.img
tools\bin\sdat2img.exe system_ext.transfer.list system_ext.new.dat output\system_ext.img
tools\bin\sdat2img.exe product.transfer.list product.new.dat output\product.img
tools\bin\sdat2img.exe vendor.transfer.list vendor.new.dat output\vendor.img
)
echo.
echo Checking fastboot version. If it's not v31 or above, you're screwed...!
tools\fastboot %* --version
echo.
echo Flashing stock boot for mojito
fastboot --set-active=b
tools\fastboot %* flash boot_a tools\boot_mojito.img
fastboot --set-active=a
echo Booting to fastbootd
tools\fastboot %* reboot fastboot
fastboot --set-active=b
echo.
echo Removing existing logical partitions only slot A ...
tools\fastboot %* delete-logical-partition vendor_a
tools\fastboot %* delete-logical-partition system_a
tools\fastboot %* delete-logical-partition system_ext_a
tools\fastboot %* delete-logical-partition product_a
echo.
echo Creating new logical partitions...
tools\fastboot %* create-logical-partition vendor_a 4096
tools\fastboot %* create-logical-partition system_a 4096
tools\fastboot %* create-logical-partition system_ext_a 4096
tools\fastboot %* create-logical-partition product_a 4096
echo.
echo Flashing the ROM...
echo Just ignore the below sparse file errors...
tools\fastboot -w %* flash system_a output\system.img
tools\fastboot %* flash system_ext_a output\system_ext.img
tools\fastboot %* flash product_a output\product.img
tools\fastboot %* flash vendor_a output\vendor.img
echo.
echo Flashing boot partitions...
tools\fastboot %* reboot bootloader
tools\fastboot %* flash boot_a output\boot.img
tools\fastboot %* flash vendor_boot_a output\vendor_boot.img
fastboot --set-active=a
echo.
echo Cleaning Stuff...
rmdir /q /s META-INF output
del /f *.img *.br *.dat *.list payload.bin care_map.pb payload_properties.txt dynamic_partitions_op_list
echo.
echo Done. Rebooting to recovery...
timeout 1 > nul
echo ...3...
timeout 1 > nul
echo ..2..
timeout 1 > nul
echo .1.
timeout 1 > nul
tools\fastboot %* reboot recovery
echo Done...
pause
StaryMuz said:
I was wrong about Vendor.
I flashed PE+ and the system did not load afterwards.
After editing the following, it worked.
tools\fastboot -w %* flash system_a output\system.img
tools\fastboot %* flash system_ext_a output\system_ext.img
tools\fastboot -w %* flash system_b output\system.img
tools\fastboot %* flash system_ext_b output\system_ext.img
tools\fastboot %* flash product_a output\product.img
tools\fastboot %* flash product_b output\product.img
tools\fastboot %* flash vendor_a output\product.img
tools\fastboot %* flash vendor_b output\product.img
But that's not right either.
I found out that:
Slot B should not flash during an update, only during a full ROM install.
For the update, it is flash to slot A, from where the running system updates itself (running from slot B).
The instructions executed during full flash and update should therefore be adapted to this.
Full flash to both B and A.
Update to A only.
If the update then fails, the system can roll back.
EDIT: scripts
I edited your script to flash only to A and only to B.:
Spoiler: Only to B
@Echo off
cd "%~dp0"
echo This is a recovery rom installation script for Windows
mkdir output
tools\7za.exe x *.zip -aos
if exist payload.bin if not exist output\vendor.img (
echo.
echo Extracting images from the build...
tools\payload_dumper.exe payload.bin
)
if exist dynamic_partitions_op_list (
echo.
echo Decompressing system
tools\bin\brotli.exe -d system.new.dat.br
echo Decompressing system_ext
tools\bin\brotli.exe -d system_ext.new.dat.br
echo Decompressing product
tools\bin\brotli.exe -d product.new.dat.br
echo Decompressing vendor
tools\bin\brotli.exe -d vendor.new.dat.br
echo Unpacking all the images...
tools\bin\sdat2img.exe system.transfer.list system.new.dat output\system.img
tools\bin\sdat2img.exe system_ext.transfer.list system_ext.new.dat output\system_ext.img
tools\bin\sdat2img.exe product.transfer.list product.new.dat output\product.img
tools\bin\sdat2img.exe vendor.transfer.list vendor.new.dat output\vendor.img
)
echo.
echo Checking fastboot version. If it's not v31 or above, you're screwed...!
tools\fastboot %* --version
echo.
echo Flashing stock boot for mojito
fastboot --set-active=a
tools\fastboot %* flash boot_b tools\boot_mojito.img
fastboot --set-active=b
echo Booting to fastbootd
tools\fastboot %* reboot fastboot
fastboot --set-active=a
echo.
echo Removing existing logical partitions only slot B ...
tools\fastboot %* delete-logical-partition vendor_b
tools\fastboot %* delete-logical-partition system_b
tools\fastboot %* delete-logical-partition system_ext_b
tools\fastboot %* delete-logical-partition product_b
echo.
echo Creating new logical partitions...
tools\fastboot %* create-logical-partition vendor_b 4096
tools\fastboot %* create-logical-partition system_b 4096
tools\fastboot %* create-logical-partition system_ext_b 4096
tools\fastboot %* create-logical-partition product_b 4096
echo.
echo Flashing the ROM...
echo Just ignore the below sparse file errors...
tools\fastboot -w %* flash system_b output\system.img
tools\fastboot %* flash system_ext_b output\system_ext.img
tools\fastboot %* flash product_b output\product.img
tools\fastboot %* flash vendor_b output\vendor.img
echo.
echo Flashing boot partitions...
tools\fastboot %* reboot bootloader
tools\fastboot %* flash boot_b output\boot.img
tools\fastboot %* flash vendor_boot_b output\vendor_boot.img
fastboot --set-active=b
echo.
echo Cleaning Stuff...
rmdir /q /s META-INF output
del /f *.img *.br *.dat *.list payload.bin care_map.pb payload_properties.txt dynamic_partitions_op_list
echo.
echo Done. Rebooting to recovery...
timeout 1 > nul
echo ...3...
timeout 1 > nul
echo ..2..
timeout 1 > nul
echo .1.
timeout 1 > nul
tools\fastboot %* reboot recovery
echo Done...
pause
Spoiler: Only to A
@Echo off
cd "%~dp0"
echo This is a recovery rom installation script for Windows
mkdir output
tools\7za.exe x *.zip -aos
if exist payload.bin if not exist output\vendor.img (
echo.
echo Extracting images from the build...
tools\payload_dumper.exe payload.bin
)
if exist dynamic_partitions_op_list (
echo.
echo Decompressing system
tools\bin\brotli.exe -d system.new.dat.br
echo Decompressing system_ext
tools\bin\brotli.exe -d system_ext.new.dat.br
echo Decompressing product
tools\bin\brotli.exe -d product.new.dat.br
echo Decompressing vendor
tools\bin\brotli.exe -d vendor.new.dat.br
echo Unpacking all the images...
tools\bin\sdat2img.exe system.transfer.list system.new.dat output\system.img
tools\bin\sdat2img.exe system_ext.transfer.list system_ext.new.dat output\system_ext.img
tools\bin\sdat2img.exe product.transfer.list product.new.dat output\product.img
tools\bin\sdat2img.exe vendor.transfer.list vendor.new.dat output\vendor.img
)
echo.
echo Checking fastboot version. If it's not v31 or above, you're screwed...!
tools\fastboot %* --version
echo.
echo Flashing stock boot for mojito
fastboot --set-active=b
tools\fastboot %* flash boot_a tools\boot_mojito.img
fastboot --set-active=a
echo Booting to fastbootd
tools\fastboot %* reboot fastboot
fastboot --set-active=b
echo.
echo Removing existing logical partitions only slot A ...
tools\fastboot %* delete-logical-partition vendor_a
tools\fastboot %* delete-logical-partition system_a
tools\fastboot %* delete-logical-partition system_ext_a
tools\fastboot %* delete-logical-partition product_a
echo.
echo Creating new logical partitions...
tools\fastboot %* create-logical-partition vendor_a 4096
tools\fastboot %* create-logical-partition system_a 4096
tools\fastboot %* create-logical-partition system_ext_a 4096
tools\fastboot %* create-logical-partition product_a 4096
echo.
echo Flashing the ROM...
echo Just ignore the below sparse file errors...
tools\fastboot -w %* flash system_a output\system.img
tools\fastboot %* flash system_ext_a output\system_ext.img
tools\fastboot %* flash product_a output\product.img
tools\fastboot %* flash vendor_a output\vendor.img
echo.
echo Flashing boot partitions...
tools\fastboot %* reboot bootloader
tools\fastboot %* flash boot_a output\boot.img
tools\fastboot %* flash vendor_boot_a output\vendor_boot.img
fastboot --set-active=a
echo.
echo Cleaning Stuff...
rmdir /q /s META-INF output
del /f *.img *.br *.dat *.list payload.bin care_map.pb payload_properties.txt dynamic_partitions_op_list
echo.
echo Done. Rebooting to recovery...
timeout 1 > nul
echo ...3...
timeout 1 > nul
echo ..2..
timeout 1 > nul
echo .1.
timeout 1 > nul
tools\fastboot %* reboot recovery
echo Done...
pause
Click to expand...
Click to collapse
You're wrong about many other things. I don't encourage manual slot selection. Fastboot decides this based on the current active slot...
You shouldn't flash the updates through manual slot selection, that's not how A/B partition scheme works.
It is possible that I did not understand all the processes correctly, but your tool did not work as it should for me with PE+.
Everything that preceded it:
- In a functional old version of PE+, I did an OTA update.
- After a reboot, the system should have updated, but it was left hanging in the system loading (even for tens of minutes).
- So I made a dirty flash using your tool. Without a factory reset, I booted the system, but it still hung in startup. During the flash process, it seemed to me that something was flash only to the A slot, and something to both A and B. This led me to the idea of editing the flash slots manually.
- So I had system, system_ext, product and vendor flashed into both slots. This resulted in the system booting without factory settings. However, the system started as new, without data and settings.
- I then experimented a bit and uploaded using flash to A, then flash to B, different systems. If I ran the last flash A system, it worked. Then I changed the active slot to the first flash B slot and also the second system started. But the other system started updating and performed some action. It kept working. I rebooted into the active A slot again, but the previous A system no longer started.
There must be a bug somewhere in the current use of updates and flash custom ROMs.
StaryMuz said:
It is possible that I did not understand all the processes correctly, but your tool did not work as it should for me with PE+.
Everything that preceded it:
- In a functional old version of PE+, I did an OTA update.
- After a reboot, the system should have updated, but it was left hanging in the system loading (even for tens of minutes).
- So I made a dirty flash using your tool. Without a factory reset, I booted the system, but it still hung in startup. During the flash process, it seemed to me that something was flash only to the A slot, and something to both A and B. This led me to the idea of editing the flash slots manually.
- So I had system, system_ext, product and vendor flashed into both slots. This resulted in the system booting without factory settings. However, the system started as new, without data and settings.
- I then experimented a bit and uploaded using flash to A, then flash to B, different systems. If I ran the last flash A system, it worked. Then I changed the active slot to the first flash B slot and also the second system started. But the other system started updating and performed some action. It kept working. I rebooted into the active A slot again, but the previous A system no longer started.
There must be a bug somewhere in the current use of updates and flash custom ROMs.
Click to expand...
Click to collapse
Everything works for me & the users on telegram support groups too.
For dirty flash to work properly, updated slot also must have the same set of ROM, magisk, kernel, boot, it's modules, etc... That you've used in your last rom
It's always recommended that keep backups of everything especially for this device as A/B is still very new to the developers.
I can't install gapps with all available recoveries, it keeps giving me the not enough space error