I found the right commands to flash GSI's on Moto G⁵⁰ ibiza
in bootloader's type:
fastboot set_active a
then:
fastboot reboot fastboot
fastboot flash product product.img
fastboot flash system (gsi).img
fastboot flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase userdata
fastboot reboot .....
Related
For Linux, Mac, or Windows users with fastboot installed, those who have need of flashing an individual partition, those for whom Moto Flash Tool fails, those who'd rather use fastboot, etc...here are the fastboot commands translated from the cebu flashfile.xml. These can be used to recover a device when all else fails...usually. For cebu with unlocked bootloader only.
Lolinet firmware link: https://mirrors.lolinet.com/firmware/moto/cebu/
Boot to bootloader (hold power and volume down until bootloader screen), plug into computer, and navigate terminal to directory containing the extracted firmware files. Run the commands one at a time, in order, and watch for "Finished" before running the next:
fastboot oem fb_mode_set
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 erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Now, didn't that feel good? Your phone sure liked it.
TIP: For Linux, commands can easily be made into a bash script and all run with one command.
1. Copy everything in #2, paste into a text file in the same directory as the extracted firmware, and save with a .sh extension (ie. flashfile.sh)
2.
#!/bin/bash
fastboot oem fb_mode_set
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 erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
3. Make file executable:
chmod +x flashfile.sh
4. Execute the script with:
./flashfile.sh
5. Reboot.
Please note these commands may be different from one version to another.
You should always refer to the flash_file.xml or service.xml
Getting flash commands from the .xml
Flashing Commands
Use a batch file for easier flashing
Online FlashFile Converter
sd_shadow said:
You should always refer to the flash_file.xml or service.xml
Click to expand...
Click to collapse
arkansawdave74 said:
translated from the cebu flashfile.xml.
Click to expand...
Click to collapse
I try to always include where I got it or what I made it from. Good lookin out. Thanks, Man!
Deleted
BTW @sd_shadow, my next device after the ocean was the Moto G Stylus (sofiap) and a script wouldn't work with it. I wrongly assumed scripts wouldn't work with devices that use a super partition. I hadn't even thought of trying a script on these more recent Powers with super partitions until you posted this. Sure enough, a script works, so thank you.
after I installed a wrong indian rom my original ROM is NE2215 10 then I upgraded to NE2213 12 and it worked fine then i upgraded to A13 then i wanted to downgrade again then i installed a wrong indian ROM then I tried to get back to NE2213 and I flashed it
but I got stuck in a boot loop now so any help ?
btw my phone isn't bricked and I can go recovery and fastboot
What happens if you recover using the built in recovery??
Wait…what? Try booting the boot file from bootloader
Did you upgrade to the android 13 beta or Indian rom A.13?
g96818 said:
Wait…what? Try booting the boot file from bootloader
Click to expand...
Click to collapse
He's downgraded dude.... Not sure a boot image will help him.... This is a situation that MSM was made for tbh.
Can try the boot image, but for what ? 13 or 12? EU or Indian?
Bit of a mess.
Edit: from the OP, it would seem he's on the EU firmware. But no way to tell what firmware is currently taking up the majority of his devices system between 12 or 13
I would try recovery, but yea sure booting an image shouldn't hurt.
I mean... You said the problem is that you flashed the wrong firmware: if you can boot in recovery and Fastboot, just download and flash the right firmware
g96818 said:
Did you upgrade to the android 13 beta or Indian rom A.13?
Click to expand...
Click to collapse
both android 13 first
AmazDev said:
I mean... You said the problem is that you flashed the wrong firmware: if you can boot in recovery and Fastboot, just download and flash the right firmware
Click to expand...
Click to collapse
I cant find NE2215 the original out of the box firmware
dladz said:
He's downgraded dude.... Not sure a boot image will help him.... This is a situation that MSM was made for tbh.
Can try the boot image, but for what ? 13 or 12? EU or Indian?
Bit of a mess.
Edit: from the OP, it would seem he's on the EU firmware. But no way to tell what firmware is currently taking up the majority of his devices system between 12 or 13
I would try recovery, but yea sure booting an image shouldn't hurt.
Click to expand...
Click to collapse
can you tell me the steps of what to do ?
moro700 said:
can you tell me the steps of what to do ?
Click to expand...
Click to collapse
Hey,
It really depends mate, but for me if I've had a bad flash and my recovery is still intact then I'd boot to my bootloader, then recovery, then just do a full wipe from there, this pops the operating system back in there and gives you a functional OS back..plus you bypass the need to identify what OS is indeed installed meaning you aren't attempting to identify the OS and by and large making a mistake, unless you can categorically identify it, something you may not be able to do without it booting.
Few things to note, I don't know how far the last firmware change you made got to.... So this could fail, but I cannot see it making things worse, I've not a had a problem with this method before but I've not been in the exact situation you're in so there is always an inherent risk.
You could go ahead and attempt to boot the boot image from the last firmware you had in a working state and see if that works, bare in mind I'm saying boot via fastboot, do not flash, I mean boot, if it fails, just reboot and you're back to where you are now.
If that works then fantastic, you're back in business, if not then you could either attempt the recovery wipe like I said OR go down the fastboot a full firmware method.
That should also work but that would be my last thing to do, it would mean extracting a firmware image by image from payload.bin then flashing each image over.
Apparently it's possible via fastboot enhance, but (sorry I know it's not too helpful) I have not had to do this myself, I was going to but recovery wipe worked for me instead.
Hope this helps mate, if you're unsure then let us know before you commit.
moro700 said:
I cant find NE2215 the original out of the box firmware
Click to expand...
Click to collapse
try flashing the downgrade rom, above the post that says WARNING. BOOTLOOP.
Fastboot Enhace
Make sure you check the box that says allow incremental or else it won't let you extract the downgrade rom.
moro700 said:
can you tell me the steps of what to do ?
Click to expand...
Click to collapse
I'm not sure if you can flash the downgrade rom through recovery or not, but you can try the following as a last resort. I am not responsible if you end up breaking your phone and this should only be used as a guide that you need to modify yourself since this script came from a oneplus 9RT fastboot rom.
Code:
@echo off
ECHO ###################
ECHO # Formatting data #
ECHO ###################
fastboot format userdata
fastboot format metadata
@echo off
title OnePlus 9RT Fastboot ROM Installer by abhinavgupta371 and HELLBOY017
ECHO #######################################################################
ECHO # Oxygen OS Flasher For OnePlus 9RT by abhinavgupta371 and HELLBOY017 #
ECHO # updated by Va1d3m #
ECHO #######################################################################
ECHO #################################
ECHO # Flashing firmware into slot A #
ECHO #################################
fastboot --set-active=a
ECHO #################################
ECHO # Flashing bootloader img's #
ECHO #################################
fastboot flash --slot=all boot boot.img
fastboot flash --slot=all modem modem.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
ECHO ##########################
ECHO # Rebooting to fastbootd #
ECHO ##########################
fastboot reboot fastboot
ECHO #################################
ECHO # Flashing fastbootd img's #
ECHO #################################
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cpucp cpucp.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all dtbo dtbo.img
fastboot flash --slot=all engineering_cdt engineering_cdt.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all mdtp mdtp.img
fastboot flash --slot=all mdtpsecapp mdtpsecapp.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all oplus_sec oplus_sec.img
fastboot flash --slot=all oplusstanvbk oplusstanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all qweslicstore qweslicstore.img
fastboot flash --slot=all shrm shrm.img
fastboot flash --slot=all splash splash.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all vm-bootsys vm-bootsys.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
ECHO ###############################
ECHO # Resizing logical partitions #
ECHO ###############################
fastboot delete-logical-partition odm_a
fastboot delete-logical-partition odm_b
fastboot delete-logical-partition system_a
fastboot delete-logical-partition system_b
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition system_ext_b
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot delete-logical-partition vendor_a
fastboot delete-logical-partition vendor_b
fastboot delete-logical-partition my_carrier_a
fastboot delete-logical-partition my_carrier_b
fastboot delete-logical-partition my_company_a
fastboot delete-logical-partition my_company_b
fastboot delete-logical-partition my_engineering_a
fastboot delete-logical-partition my_engineering_b
fastboot delete-logical-partition my_heytap_a
fastboot delete-logical-partition my_heytap_b
fastboot delete-logical-partition my_manifest_a
fastboot delete-logical-partition my_manifest_b
fastboot delete-logical-partition my_preload_a
fastboot delete-logical-partition my_preload_b
fastboot delete-logical-partition my_product_a
fastboot delete-logical-partition my_product_b
fastboot delete-logical-partition my_region_a
fastboot delete-logical-partition my_region_b
fastboot delete-logical-partition my_stock_a
fastboot delete-logical-partition my_stock_b
fastboot delete-logical-partition odm_a-cow
fastboot delete-logical-partition odm_b-cow
fastboot delete-logical-partition system_a-cow
fastboot delete-logical-partition system_b-cow
fastboot delete-logical-partition system_ext_a-cow
fastboot delete-logical-partition system_ext_b-cow
fastboot delete-logical-partition product_a-cow
fastboot delete-logical-partition product_b-cow
fastboot delete-logical-partition vendor_a-cow
fastboot delete-logical-partition vendor_b-cow
fastboot delete-logical-partition my_carrier_a-cow
fastboot delete-logical-partition my_carrier_b-cow
fastboot delete-logical-partition my_company_a-cow
fastboot delete-logical-partition my_company_b-cow
fastboot delete-logical-partition my_engineering_a-cow
fastboot delete-logical-partition my_engineering_b-cow
fastboot delete-logical-partition my_heytap_a-cow
fastboot delete-logical-partition my_heytap_b-cow
fastboot delete-logical-partition my_manifest_a-cow
fastboot delete-logical-partition my_manifest_b-cow
fastboot delete-logical-partition my_preload_a-cow
fastboot delete-logical-partition my_preload_b-cow
fastboot delete-logical-partition my_product_a-cow
fastboot delete-logical-partition my_product_b-cow
fastboot delete-logical-partition my_region_a-cow
fastboot delete-logical-partition my_region_b-cow
fastboot delete-logical-partition my_stock_a-cow
fastboot delete-logical-partition my_stock_b-cow
fastboot create-logical-partition odm_a 1
fastboot create-logical-partition odm_b 1
fastboot create-logical-partition system_a 1
fastboot create-logical-partition system_b 1
fastboot create-logical-partition system_ext_a 1
fastboot create-logical-partition system_ext_b 1
fastboot create-logical-partition product_a 1
fastboot create-logical-partition product_b 1
fastboot create-logical-partition vendor_a 1
fastboot create-logical-partition vendor_b 1
fastboot create-logical-partition my_carrier_a 1
fastboot create-logical-partition my_carrier_b 1
fastboot create-logical-partition my_company_a 1
fastboot create-logical-partition my_company_b 1
fastboot create-logical-partition my_engineering_a 1
fastboot create-logical-partition my_engineering_b 1
fastboot create-logical-partition my_heytap_a 1
fastboot create-logical-partition my_heytap_b 1
fastboot create-logical-partition my_manifest_a 1
fastboot create-logical-partition my_manifest_b 1
fastboot create-logical-partition my_preload_a 1
fastboot create-logical-partition my_preload_b 1
fastboot create-logical-partition my_product_a 1
fastboot create-logical-partition my_product_b 1
fastboot create-logical-partition my_region_a 1
fastboot create-logical-partition my_region_b 1
fastboot create-logical-partition my_stock_a 1
fastboot create-logical-partition my_stock_b 1
ECHO ###############################
ECHO # Flashing logical partitions #
ECHO ###############################
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_manifest my_manifest.img
fastboot flash my_preload my_preload.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
ECHO #######################
ECHO # Rebooting to system #
ECHO #######################
fastboot reboot
pause
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Don't Lock your device bootloader.
1.) First of all you need
laptop,
Usb data cable,
Minimal adb & fastboot setup,
firmware.
MCT ofp extractor tool.
and Your device.
Download below files.
Firmware link:
https://rms01.realme.net/sw/RMX3081export_11_C.19_2022072820470000.zip
MCT OFP extractor tool:
https://drive.google.com/file/d/1-MgGdT9fxi2LtJ1DIOxLVSM67thj9EpG/view?usp=drivesdk
Minimal adb & fastboot setup:
https://ava4.androidfilehost.com/dl/OqBAMk5-7QCuTzL-IhX9ZA/1661345244/10763459528675595887/ADB+&+FASTBOOT.rar
2.) Extract the ofp file package by mct ofp extract tool.
3.) Request to unlock your device bootloader by in-deapth test apk, once approved then you can start deep testing and unlock bootloader.
4.) connect your device with laptop.
5.) Open minimal adb & fastboot terminal.
and flash this images files by below cmd.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash metadata metadata.img
fastboot flash opporeserve2 opporeserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
Note: Flash this only 3 super images
fastboot flash super super.0.c5548a43.img
fastboot flash super super.1.bbada0de.img
fastboot flash super super.2.1400563f.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot
Your device will reboot to system.
Download and extract model specific firmware zip to the fastboot folder.
Enter fastboot by turning the device off and then turning it on using pwr+vol down for few seconds.
If it doesn't turnoff, then let the battery drain out on its own and then retry to enter fastboot.
Execute each of the below commands in the CMD window, one at a time. If you get any errors after executing any of these commands, then don’t leave the process mid-way. Rather continue executing the rest of the commands and then check the results.
Fastboot commandsfastboot erase boot_ab
fastboot flash xbl_ab xbl.elf
fastboot flash xbl_config_ab xbl_config.elf
fastboot flash abl_ab abl.elf
fastboot flash aop_ab aop.mbn
fastboot flash tz_ab tz.mbn
fastboot flash featenabler_ab featenabler.mbn
fastboot flash hyp_ab hypvm.mbn
fastboot flash modem_ab NON-HLOS.bin
fastboot flash bluetooth_ab BTFM.bin
fastboot flash dsp_ab dspso.bin
fastboot flash keymaster_ab km41.mbn
fastboot flash devcfg_ab devcfg.mbn
fastboot flash qupfw_ab qupv3fw.elf
fastboot flash uefisecapp_ab uefi_sec.mbn
fastboot erase imagefv_ab
fastboot flash imagefv_ab imagefv.elf
fastboot flash shrm_ab shrm.elf
fastboot flash multiimgoem_ab multi_image.mbn
fastboot flash cpucp_ab cpucp.elf
fastboot flash qweslicstore_ab qweslicstore.bin
fastboot flash logfs logfs_ufs_8mb.bin
fastboot flash rescue rescue.img
fastboot flash storsec storsec.mbn
fastboot flash spunvm spunvm.bin
fastboot flash rtice rtice.mbn
fastboot flash vendor_boot_ab vendor_boot.img
fastboot flash vm-bootsys_ab vm-bootsys.img
fastboot flash super super.img
fastboot flash cust cust.img
fastboot flash dtbo_ab dtbo.img
fastboot flash vbmeta_ab vbmeta.img
fastboot flash vbmeta_system_ab vbmeta_system.img
fastboot erase metadata
fastboot flash metadata metadata.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot flash boot_ab boot.img
fastboot flash logo logo.img
fastboot set_active a
fastboot reboot
If the device is still boot looping, fastboot -w (as the final option) and repeat all the above commands step-by-step.
Im trying to flash a gsi by nippon but it dont work.
I booted some of them
here is link
A03s https://t.me/nippongsi/7035
A52 https://t.me/nippongsi/6755
S22 https://t.me/nippongsi/6746
etc....
but is useless because audio not works, calls not works (because audio)
and you must use fastbootd for flash
here is how
first you must delete some of dynamic partitions
fastboot reboot fastboot
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition system_ext_b
after that clean up system
fastboot erase system
flash gsi
fastboot flash system "gsi.img"
after that you must flash vbmeta.img and vbmeta_system.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verification flash vbmeta_system vbmeta_system.img
after that reboot to recovery and format userdata
if its not boot for you must disable selinux and important to flash vbmeta and vbmeta_system
good luck
Samuel Ladziansky said:
I booted some of them
here is link
A03s https://t.me/nippongsi/7035
A52 https://t.me/nippongsi/6755
S22 https://t.me/nippongsi/6746
etc....
but is useless because audio not works, calls not works (because audio)
and you must use fastbootd for flash
here is how
first you must delete some of dynamic partitions
fastboot reboot fastboot
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition system_ext_b
after that clean up system
fastboot erase system
flash gsi
fastboot flash system "gsi.img"
after that you must flash vbmeta.img and vbmeta_system.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verification flash vbmeta_system vbmeta_system.img
after that reboot to recovery and format userdata
if its not boot for you must disable selinux and important to flash vbmeta and vbmeta_system
good luck
Click to expand...
Click to collapse
Hello how are you, I would like to be able to install Samsung OneUI on my redmi note 11, however, when executing these commands it generates errors and does not run, is there a way to install this GSI with a recovery and have it work correctly, like waiting for your reply.
Or do you know if there is any custom rom that already has this setting and others of OneUI?
@Kiio28 crdroid has OneUI iconset
I have a question please. how did you boot those roms; When I installed the one for the s22, It boot but I got a warning message saying that there was an internal problem and I contacted the provider; the other 2 I could not install.