Hey, is there anyone using a moto g7 power XT1955-4? If so is it rooted or are you willing/ planning to root it? If yes, then i really need your help. Please let me know if you can help me.
Ballyeet said:
Hey, is there anyone using a moto g7 power XT1955-4? If so is it rooted or are you willing/ planning to root it? If yes, then i really need your help. Please let me know if you can help me.
Click to expand...
Click to collapse
Me bro... See:
xe500linux said:
Whats the difference between fastboot -w and just wiping everything in Twrp? That could have been it.. Syber makes the official Twrp as well so dont know if the one in OP is any different
And theres 4 roms btw, Havoc OS has no thread but its on Syber's androidfilehost. Same rgb/display issues as Lineage though
Click to expand...
Click to collapse
bruh you dont even have to use the fastboot -w or wipe command
CREATOR OF POST: MY F***IN BAD my speak problem was some bs from a blank flash i sorted it now the only bugs i got in some sketchy nav bar
there are apparently these roms as well:
CARBON-CR-7.0-OPAL-UNOFFICIAL-ocean-20191025-1317.zip
Viper-ocean-20191029-v6.7-UNOFFICIAL.zip
XenonHD-191024-Unofficial-ocean.zip
---------- Post added at 09:53 AM ---------- Previous post was at 08:54 AM ----------
FULL GUIDE TO DEBRICK/INSTALL STOCK ROM/REMOVE BAD KEY/INSTALL CUSTOM ROM AND TWRP
ensure your google accounts are removed from the phone and bootloader is unlocked...
boot to bootloader
run cmd prompt
use cd C:\*LOCATION* to go to folder with full STOCK ROM but make sure you have this files in the folder too [adb.exe, fastboot.exe, adbwinapi.dll, adbwinusbapi.dll] from ur minimal adb and fastboot setup. you will also need the recovery file TWRP-ocean-3.3.1-Syber-v2.2_11-02.img in this folder and the logo.bin file to remove the bad key FROM HERE. I suggest you rename to logonew.bin and put in the stock rom folder. you will also want ur RRromzip, the copypartitions.zip, the TWRP INSTALLER, GAPPS & MAGISK ZIP...
no matter what stage u are at other than bricked [after the BLANK FLASH then resume with this guide. if ur stuck bootlooping or have messed anything up start from the stock rom install or you will end up bricking your phone....
ok so in your cmd open in stock rom folder type these commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot-bootloader
when it reboots to bootloader use these commands from the same folder:
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 5
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.2
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.2
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot oem fb_mode_clear
fastboot reboot-bootloader
now use these commands to remove bad key
fastboot flash logo_a logonew.bin
fastboot flash logo_b logonew.bin
now boot the twrp by using
fastboot boot TWRP-ocean-3.3.1-Syber-v2.2_11-02.img
when twrp boots it should show up in ur windows explorer if you have an sd card just drop the files you need on it or you will have to use command adb push copy-partitions-payton.zip /sdcard/
install the copy-partitions-payton.zip
when complete reboot-bootloader
now boot the twrp again by using
fastboot boot TWRP-ocean-3.3.1-Syber-v2.2_11-02.img
now install the rom zip
then the twrp installer zip
reboot-recovery [it auto switches slot]
install gapps and magisk zips
reboot system
you should have ur custom rom and twrp recovery permanently installed now
Thanks for this guide! Does it work with official TWRP?
One more question: I have the RETEU Version, wich zip should i pick? The PPO or the PPOS Version?
thanks in advance!
Part, anyone knows an effective method to lock the bootloader so that I have oem_locked written instead of flashing_locked? You unlocked with a code from the Motorola website, which is the official method. I did not modify anything and blocked it with fastboot oem_lock. From now on, instead of oem_locked, I have flashing_locked written. Re-unlocking with the fastboot oem_unlock command is possible without the use of a code from Motorola. Is it normal? Another interesting and strange thing is that after entering recovery mode and trying to install the update from the sd card, he gets the error that he cannot see the card. If he wants to upload updates via ADB he also gets an error. LMSA rescue flashing also crashes when switching to fastboot mode. In general, in fastboot mode, I should be able to flash the stock without unlocking the bootloader and no, I can do it because I also have an error
C: \ adb> fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical: modem_a: not found
Sending 'modem_a' (81048 KB) OKAY [2.072s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Yesterday I started the phone in edl mode and used blankflash. Then I wanted to flash the stock but had to unlock the bootloader. Or rather, there shouldn't be such a need. I do not know how to bring it to the factory state.
gorbatschoff said:
Part, anyone knows an effective method to lock the bootloader so that I have oem_locked written instead of flashing_locked? You unlocked with a code from the Motorola website, which is the official method. I did not modify anything and blocked it with fastboot oem_lock. From now on, instead of oem_locked, I have flashing_locked written. Re-unlocking with the fastboot oem_unlock command is possible without the use of a code from Motorola. Is it normal? Another interesting and strange thing is that after entering recovery mode and trying to install the update from the sd card, he gets the error that he cannot see the card. If he wants to upload updates via ADB he also gets an error. LMSA rescue flashing also crashes when switching to fastboot mode. In general, in fastboot mode, I should be able to flash the stock without unlocking the bootloader and no, I can do it because I also have an error
C: \ adb> fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical: modem_a: not found
Sending 'modem_a' (81048 KB) OKAY [2.072s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Yesterday I started the phone in edl mode and used blankflash. Then I wanted to flash the stock but had to unlock the bootloader. Or rather, there shouldn't be such a need. I do not know how to bring it to the factory state.
Click to expand...
Click to collapse
All of that happened to me except for the flashing locked and unlocked part, when I first got my phone before it was ever unlocked, it said flash_locked and I unlocked it and then it's flashing_unlocked. Now when I relock it, it goes back to it's original state, as flashing_locked. I get Motorola updates still so that's a plus to me.
Never had to start the phone in edl and hope I never have to.
Never used LMSA, and hope I never have to.
And my suggestion would be unlock the bootloader and flash stock firmware from lolinet and use these commands
↓
fastboot devices
fastboot set_active a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.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_b system_b.img_sparsechunk.0 fastboot flash system_b system_b.img_sparsechunk.1 fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
↑
After that, boot it up for the first time and setup the phone. After seeing the home screen power off and boot to fastboot and lock your bootloader, the reason I say lock it is because there is no better reason to have it unlocked imo ("totally unnecessary, you can do what you want, I'm just trying to help ") because there isn't really a striving development community with ROMs yet. I think here soon there will be once Android 10 releases for this phone .
Thanks for the answer. I've used these commands and of course they work. The phone works but the ADB and recovery problem is still there. And that worries me.
dont work
SnowTalker said:
All of that happened to me except for the flashing locked and unlocked part, when I first got my phone before it was ever unlocked, it said flash_locked and I unlocked it and then it's flashing_unlocked. Now when I relock it, it goes back to it's original state, as flashing_locked. I get Motorola updates still so that's a plus to me.
Never had to start the phone in edl and hope I never have to.
Never used LMSA, and hope I never have to.
And my suggestion would be unlock the bootloader and flash stock firmware from lolinet and use these commands
↓
fastboot devices
fastboot set_active a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.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_b system_b.img_sparsechunk.0 fastboot flash system_b system_b.img_sparsechunk.1 fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
↑
After that, boot it up for the first time and setup the phone. After seeing the home screen power off and boot to fastboot and lock your bootloader, the reason I say lock it is because there is no better reason to have it unlocked imo ("totally unnecessary, you can do what you want, I'm just trying to help ") because there isn't really a striving development community with ROMs yet. I think here soon there will be once Android 10 releases for this phone .
Click to expand...
Click to collapse
dont work
bugy65 said:
dont work
Click to expand...
Click to collapse
The commands?
Hi all, just received and updated the 11.1.6.6 via OTA... but after reboot I'm locked on the two white dots around the one red icons, and the phone doesn't start anymore.. so it's NOT a bootloop, but just blocked situation..
I'm rooted... what can I do to exit from this situation as well?
Just tried with VOL UP + POWER combo, but this casue only a power off, or a new reboot, but the situation doesn't change and the screen still stuck on the dots animation..
EDIT:
Had to resolve with a full wipe factory reset, no other way.
There was another way. You could've downloaded the latest update package onto your PC, used PayloadDumper to extract the payload.bin file found inside the zip file, extracted Android's 'Platform tools' into the output folder of the payload dump and then ran these commands without wiping while your phone is connected in fastboot:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
You'd lose root but your phone would be updated to the latest OS and your data would hold.
You can then follow the root guide to patch the boot.img extracted from the payload file and let magisk do its thing.
Recently i was trying to flash Stag OS when i accidentally flashed the wrong img to the system partition. now I can only boot into fastboot and the Qualcomm Crash Dump Mode. Is there a way out of this? I tried unpacking my payload.bin and flashing each img individually but it took me back to the same error.
I have had this happen to two separate oneplus 9's. My recommendation would be to start trying to run MSM tools from the forums here (both for your correct device and then for other 9 variants, i had the most success using the India 9+ version then running the correct version once the phone was booting again)
I did that and it worked! I was having issues getting into msm mode but then I realized I wasn't supposed to hold the power button. Thanks!
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
LinhBT said:
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
It's not dangerous to use the MSM tool that's made for your device. Manual fastboot flashing is more likely to cause problems due to human error than the MSM is. The MSM is done quicker too.
Hi,
I'll try to follow your tutorial, I have an LE2113 and I only cna boot into Qualcomm Crash Dump Mode, sometimes into bootloader mode.
I tried to follow the tutorials to root the phone, but I didn't do it until my OnePlus6, and the tutorials looks more complicated than in the past, in my opinion, it missed a lot of step for the beginners.
I'll try to find a way to make my phone alive again.
EtherealRemnant said:
It's not dangerous to use the MSM tool that's made for your device. Manual fastboot flashing is more likely to cause problems due to human error than the MSM is. The MSM is done quicker too.
Click to expand...
Click to collapse
I always trust myself more than any other tools But yeah, for some, the tools would be more confort
LinhBT said:
I always trust myself more than any other tools But yeah, for some, the tools would be more confort
Click to expand...
Click to collapse
Yeah I have never had an issue with manual flashing either but all the reports of people bricking and having to use MSM tell me that it's pretty common with OnePlus devices. I saw so many of those reports that I made sure MSM Tool was working before I even unlocked my bootloader lol.
EtherealRemnant said:
Yeah I have never had an issue with manual flashing either but all the reports of people bricking and having to use MSM tell me that it's pretty common with OnePlus devices. I saw so many of those reports that I made sure MSM Tool was working before I even unlocked my bootloader lol.
Click to expand...
Click to collapse
True bro. I used to try in vain lots of MSM build just to find one which can actually works and unbrick my 8T, but if not sahara error, then would be param or else. At last, fastboot saved my ass ))
LinhBT said:
True bro. I used to try in vain lots of MSM build just to find one which can actually works and unbrick my 8T, but if not sahara error, then would be param or else. At last, fastboot saved my ass ))
Click to expand...
Click to collapse
I was kind of surprised at how straightforward it was. I booted up Windows 11, installed the drivers, put the USB cord for my Pixel 3 XL in the USB-C port, put phone in EDL with the key combo, ran MSM. Zero issues either time I have tried it. I was absolutely prepared to have to fight with it.
EtherealRemnant said:
I was kind of surprised at how straightforward it was. I booted up Windows 11, installed the drivers, put the USB cord for my Pixel 3 XL in the USB-C port, put phone in EDL with the key combo, ran MSM. Zero issues either time I have tried it. I was absolutely prepared to have to fight with it.
Click to expand...
Click to collapse
Yeah, after I figured out what happened, then the rest are just like what u said. Turns out that my 8T was having CyberPunk param ( I did tried to convert ) therefore, MSM doesn't recognized it since MSM is specific for each model ))
LinhBT said:
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
I'll try your method, MSM don't work, even on test mode on Windows10. Last chance operation :/ but when I fastboot flash abl abl.img, I have the actual message:
fastboot: error: cannot load 'abl.img': No such file or directory
Click to expand...
Click to collapse
BroenGuiraldson said:
I'll try your method, MSM don't work, even on test mode on Windows10. Last chance operation :/ but when I fastboot flash abl abl.img, I have the actual message:
Click to expand...
Click to collapse
Normally, it's abl.elf bro, depends on the Firm u r using to flash
I'm trying to flash the "OnePlus9Oxygen_22.E.47_OTA_1470_all_2203102118_ad7f1.zip" for my LE2113 version.
I extracted all the img files. How can I know if it's abl.elf instead of abl ? What about the other image flash ?
I tried with the aop and it returns the same error.
In parallel, still trying to detect my phone on MSM :/
LinhBT said:
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
Are you sure this is right? I don't see boot.img in that list.
Z-Blade said:
Are you sure this is right? I don't see boot.img in that list.
Click to expand...
Click to collapse
boot.img dtbo.img ( and sometimes stock recovery.img )you will have to flash before execute this commands, since we will need to boot into fastbootD which only available in wherether boot.img or recovery.img
This guide is for anyones like me that wants to go back to Android 11 from 12.
Prerequisites:
unlocked bootloader
Your phone's Android 11 firmware
Ability to get into fastboot and type commands one at a time hitting ENTER after each line
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
flash bluetooth BTFM.bin
flash dsp dspso.bin
flash logo logo.bin
flash boot boot img
flash vendor_boot vendor_boot.img
flash dtbo dtbo.img
flash super super.img_sparsechunk.0
(This flash took almost 15 seconds to finish. Continue flashing sparsechunk.1 thru sparsechunk.11 one at a time.
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
I had to flash both a & b slots to get this to stick. Disable updates to avoid problems.