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.
Hello, this is my first time in the xda forum, I hope you help me with my situation since I have been trying to solve my problem for several days without any success. Without more to say I tell you my situation:
1 week ago I decided to make a rom flash on my motorola G7 POWER (XT1955-2 RETAIL), so I proceeded to download a rom from youtube, perform the procedure without any problem and when I finish the cell phone restart, until here everything normal. Now I comment the problem arises after the restart of the cell phone, I realized that it did not start and stays in the logo of Motorola and restarted again.
I gave myself the task of checking that it could have failed and I found that when it was flashing they appreciated several errors 1 of them is the following:
C: \ Users \ maxic \ Desktop \ fflanfl \ Motorola_Moto_G7_Power_XT1955_2_ 9.0_CFC_US_181210 \ Firmware> fastboot erase customize
erasing 'customize' ...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.009s
Those are the mistakes I found. I've tried flashing 1 million times with different roms and nothing please I need your help to solve my problem.:crying::crying::crying::crying::crying:
pacomiguel said:
Hello, this is my first time in the xda forum, I hope you help me with my situation since I have been trying to solve my problem for several days without any success. Without more to say I tell you my situation:
1 week ago I decided to make a rom flash on my motorola G7 POWER (XT1955-2 RETAIL), so I proceeded to download a rom from youtube, perform the procedure without any problem and when I finish the cell phone restart, until here everything normal. Now I comment the problem arises after the restart of the cell phone, I realized that it did not start and stays in the logo of Motorola and restarted again.
I gave myself the task of checking that it could have failed and I found that when it was flashing they appreciated several errors 1 of them is the following:
C: \ Users \ maxic \ Desktop \ fflanfl \ Motorola_Moto_G7_Power_XT1955_2_ 9.0_CFC_US_181210 \ Firmware> fastboot erase customize
erasing 'customize' ...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.009s
Those are the mistakes I found. I've tried flashing 1 million times with different roms and nothing please I need your help to solve my problem.:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
There is a G7 Power section
https://forum.xda-developers.com/g7-power
See
https://forum.xda-developers.com/g7-power/how-to/complete-noob-guide-to-rooting-metropcs-t3954986
Download from
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 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_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_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Sent from my ali using XDA Labs
sd_shadow said:
There is a G7 Power section
https://forum.xda-developers.com/g7-power
See
https://forum.xda-developers.com/g7-power/how-to/complete-noob-guide-to-rooting-metropcs-t3954986
Download from
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 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_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_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hello, thanks for the information but I had tried to do that before, the bootloader is locked on my device and there is no way to unlock it in the condition that my cell phone is.
hello guys, i just download the new update for my phone but i cant intsall it, i didnt install any recovery and anything on my phone yet, i tried to install it via adb sideload ota.zip command and not work, i unlocked bootloader and its not worked
Hi,
Try these commands when in fastboot mode.
Maybe you need to relock the bootloader.
Here are the commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
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_b system_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
1. Extract rom.zip and get payload.bin
2. Extract payload_drumper-win64 (attach)
3. Put payload.bin in folder payload_drumper-win64
4. Run payload_dumper.exe
Spoiler: 5.1 Flash Recovery (method #1)
fastboot -w (erase all data)
fastboot flash boot magisk.img
fastboot flash recovery OrangeFox.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
start recovery (key +)
Spoiler: 5.2 Flash recovery (method #2)
fastboot -w
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash recovery OrangeFox.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
fastboot reboot bootloader
start recovery (key +)
Spoiler: bonus - Full script
@Echo off
title Oxygen OS 11/12 OnePlus a/b Fastboot ROM by DKPOST3
ECHO ############################################################################
ECHO # OxygenOS 11/12 FASTBOOT ROM INSTALLER FOR ONEPLUS a/b BY DKPOST3 #
ECHO ##############################
ECHO # SETTING ACTIVE SLOT TO A #
fastboot --set-active=a
ECHO #######################
ECHO # FORMATTING DATA #
fastboot -w
ECHO ###############################
ECHO # FLASHING RECOVERY IMAGE #
fastboot flash recovery recovery.img
ECHO ############################
ECHO # REBOOTING TO FASTBOOTD #
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
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 cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.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 logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
ECHO #################################
ECHO # RESIZING LOGICAL PARTITIONS #
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 my_bigball_a
fastboot delete-logical-partition my_bigball_b
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 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
fastboot create-logical-partition my_bigball_a 1
fastboot create-logical-partition my_bigball_b 1
fastboot create-logical-partition vendor_a 1
fastboot create-logical-partition vendor_b 1
fastboot create-logical-partition product_a 1
fastboot create-logical-partition product_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 odm_a 1
fastboot create-logical-partition odm_b 1#
ECHO # FLASHING LOGICAL PARTITIONS #
ECHO ###############################
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash my_carrier my_carrier.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
fastboot flash my_bigball my_bigball.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash odm odm.img
ECHO ###############
ECHO # REBOOTING #
fastboot reboot
pause
Captured this OTA returning to Android 12 after nearly bricking my T-MOBILE branded N200 and using MSMtool to get back to stock.
https://android.googleapis.com/packages/ota-api/package/f706ca0ab8556311d76c565135816d3873a4a15c.zip
This is a Full OTA for the N200 T-Mobile variant DE2118
This can be used to return to stock from a A11 or A12 fw based custom ROM.
YOU MUST BE ABLE TO ACCESS FASTBOOTD
if you can not access fastbootd, install LineageOS recovery and ensure it is functional before using this method.
First extract fastboot flashable images from the stock OTA.zip using a tool such as theses:
Linux - https://github.com/vm03/payload_dumper
MacOS/Linux/Windows (definitely faster than vm03) - https://forum.xda-developers.com/t/...d-ota-payload-dumper-written-in-rust.4573841/
ensure that the output .img files are in a directory that you can use fastboot commands in (ex. platform-tools)
fastboot reboot fastboot
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 vendor_dlkm_a
fastboot delete-logical-partition vendor_dlkm_b
fastboot delete-logical-partition my_carrier_a
fastboot delete-logical-partition my_carrier_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_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_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_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 system_a 1
fastboot flash system_a system.img
fastboot create-logical-partition system_ext_a 1
fastboot flash system_ext_a system_ext.img
fastboot create-logical-partition product_a 1
fastboot flash product_a product.img
fastboot create-logical-partition vendor_a 1
fastboot flash vendor_a vendor.img
fastboot create-logical-partition odm_a 1
fastboot flash odm_a odm.img
fastboot create-logical-partition my_product_a 1
fastboot flash my_product_a my_product.img
fastboot create-logical-partition my_engineering_a 1
fastboot flash my_engineering_a my_engineering.img
fastboot create-logical-partition my_stock_a 1
fastboot flash my_stock_a my_stock.img
fastboot create-logical-partition my_company_a 1
fastboot flash my_company_a my_company.img
fastboot create-logical-partition my_carrier_a 1
fastboot flash my_carrier_a my_carrier.img
fastboot create-logical-partition my_region_a 1
fastboot flash my_region_a my_region.img
fastboot create-logical-partition my_heytap_a 1
fastboot flash my_heytap_a my_heytap.img
fastboot create-logical-partition my_preload_a 1
fastboot flash my_preload_a my_preload.img
fastboot create-logical-partition my_manifest_a 1
fastboot flash my_manifest_a my_manifest.img
fastboot create-logical-partition my_bigball_a 1
fastboot flash my_bigball_a my_bigball.img
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash core_nhlos_a core_nhlos.img
fastboot flash core_nhlos_b core_nhlos.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash featenabler_a featenabler.img
fastboot flash featenabler_b featenabler.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash imagefv_a imagefv.img
fastboot flash imagefv_b imagefv.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash logo_a logo.img
fastboot flash logo_b logo.img
fastboot flash oplusstanvbk_a oplusstanvbk.img
fastboot flash oplusstanvbk_b oplusstanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash uefisecapp_a uefisecapp.img
fastboot flash uefisecapp_b uefisecapp.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vbmeta_system_a vbmeta_system.img
fastboot flash vbmeta_system_b vbmeta_system.img
fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot --set-active=a
fastboot reboot bootloader
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot -w
Hope this helps someone.
Travisholt92 said:
Captured this OTA returning to Android 12 after nearly bricking my N200and using MSMtool to get back to stock.
https://android.googleapis.com/packages/ota-api/package/f706ca0ab8556311d76c565135816d3873a4a15c.zip
This is a Full OTA
This can be used to return to stock from a A11 or A12 fw based custom ROM.
Recreate a A12 super partition for slot A:
In fastbootd delete all of these listed partitions (including vendor_dlkm if coming from custom ROM)
fastboot create-logical-partition system_a 1
fastboot flash system system.img
fastboot create-logical-partition system_ext_a 1
fastboot flash system_ext system_ext.img
fastboot create-logical-partition product_a 1
fastboot flash product product.img
fastboot create-logical-partition vendor_a 1
fastboot flash vendor vendor.img
fastboot create-logical-partition odm_a 1
fastboot flash odm odm.img
fastboot create-logical-partition my_product_a 1
fastboot flash my_product_a my_product.img
fastboot create-logical-partition my_engineering_a 1
fastboot flash my_engineering_a my_engineering.img
fastboot create-logical-partition my_stock_a 1
fastboot flash my_stock_a my_stock.img
fastboot create-logical-partition my_company_a 1
fastboot flash my_company_a my_company.img
fastboot create-logical-partition my_carrier_a 1
fastboot flash my_carrier_a my_carrier.img
fastboot create-logical-partition my_region_a 1
fastboot flash my_region_a my_region.img
fastboot create-logical-partition my_heytap_a 1
fastboot flash my_heytap_a my_heytap.img
fastboot create-logical-partition my_preload_a 1
fastboot flash my_preload_a my_preload.img
fastboot create-logical-partition my_manifest_a 1
fastboot flash my_manifest_a my_manifest.img
fastboot create-logical-partition my_bigball_a 1
fastboot flash my_bigball_a my_bigball.img
Then flash the zip in fastboot enhanced to flash the rest of the required partitions before rebooting (or use a payload dumper to extract all partitions to flash them manually on Linux)
Hope this helps someone.
Click to expand...
Click to collapse
Just have them flash the ota itself in fastbootd and then fastboot. Does the same thing. This is unnecessarily overly-complicated. To many areas for error.
For those who read this.. do not use this guide. There has been a report of a user (who did it step by step exactly and verified) and ended up bricking their device, use the fastboot enhanced method.
I too have also assisted someone who bricked phone with this guide as it deletes files from copy a & b at the same time and if anything goes wrong or reboot, they are soft bricked and cannot boot to recovery or fastboot!
DisclaimerThe information on this site may contain errors or inaccuracies, and we do not make any warranty or guarantee as to the accuracy of the information. Your warranty will be void if you tamper with any part of your device / software. YOU are choosing to make these modifications. XDA is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
All the best,
xda-developers
Sprunglicious said:
For those who read this.. do not use this guide. There has been a report of a user (who did it step by step exactly and verified) and ended up bricking their device, Either use the fastboot method above.
Click to expand...
Click to collapse
WHAT?! they definitely didn't do it right then. Assuming the user didn't flash the full FW which is how they ended up bricked. I have found NO WAY of simply flashing the OTA (using any recovery or fastboot enhanced) to automatically regenerate the super partition. it doesn't work. This guide however DOES explain exactly how to properly regenerate the super partition and only that.
I will revise the OP when i get the time to include the full flashing instructions for Windows, Linux, Android, and MacOS. Thank you for bringing this to my attention.
Edit: OP instructions are now for Full OTA install with fw flashed to both slots. Hopefully this helps.
scanman0 said:
I too have also assisted someone who bricked phone with this guide as it deletes files from copy a & b at the same time and if anything goes wrong or reboot, they are soft bricked and cannot boot to recovery or fastboot!
Click to expand...
Click to collapse
If the user can get to bootloader then custom recovery such as LineageOS recovery can be flashed to gain Fastbootd permissions to properly reflash the device firmware.
See next post
Sprunglicious said:
For those who read this.. do not use this guide. There has been a report of a user (who did it step by step exactly and verified) and ended up bricking their device, Either use the fastboot method above.
Click to expand...
Click to collapse
scanman0 said:
I too have also assisted someone who bricked phone with this guide as it deletes files from copy a & b at the same time and if anything goes wrong or reboot, they are soft bricked and cannot boot to recovery or fastboot!
Click to expand...
Click to collapse
These comments seem unnecessarily critical and assumptive rather than constructive. Have either of you actually followed the guide or just making assumptions based on what another user reports? I think we all know it's quite easy for folks that don't know what they're doing to mess things up quickly because they aren't paying attention. Let's encourage contributors to continue to post by being supportive. It's okay to question the validity of something but do so constructively please.
I'm happy to report that other than a couple minor issues where a few commands needed the _a/b specification (which OP has fixed already) this guide worked without issue. I just flashed an N200 running LineageOS to stock OOS using the supplied OTA and the linked OTA dumper for macOS (Yes, macOS! did the whole process on my MacBook which was awesome).
@Travisholt92 Thanks for an excellent guide!
CmdrCrichton said:
These comments seem unnecessarily critical and assumptive rather than constructive. Have either of you actually followed the guide or just making assumptions based on what another user reports? I think we all know it's quite easy for folks that don't know what they're doing to mess things up quickly because they aren't paying attention. Let's encourage contributors to continue to post by being supportive. It's okay to question the validity of something but do so constructively please.
I'm happy to report that other than a couple minor issues where a few commands needed the _a/b specification (which OP has fixed already) this guide worked without issue. I just flashed an N200 running LineageOS to stock OOS using the supplied OTA and the linked OTA dumper for macOS (Yes, macOS! did the whole process on my MacBook which was awesome).
@Travisholt92 Thanks for an excellent guide
Click to expand...
Click to collapse
You have failed to note that this guide has been updated since I had commented. As I have said elsewhere, there was no hostility meant by anything above. Simply a warning to those out there. Because having to modify _a or _b are not small acts when it comes to the world of Android Modification. My account may be semi-new, but I have been doing this since the android 4.0 days. as this was a new account created due to losing access to my old account. So let's not even bother trying to get into the credibility argument. It isn't something worth either of our's time.
By all means did I want this to be helpful, but the reality is that there were multiple devices to have been reported to have been ruined, being left with a CDE error. Which means they could not have been recovered with the MSMTools in the wild, as they could not pass the verification check to flash. And during this process there was zero ways to get to fastboot to fix the devices in that manner.
Frankly, due to what had occured, I have been having to pull my own time trying to help these individuals in a situation that I did not cause in the first place, when i could have either been working on my own project and spending time with my family. I have been working on trying to build an ops file to flash with the current MSMTools out currently to eventually get these devices fixed (as they are belonging to normal OEM configuration of the OnePlus Nord N200 (Dre). Not the AA variant. This process has been unsuccessful thus far, meaning we still have paperweights.
The only thing I ask is that some kind of assistance be given to those who followed the improper guide in its' original form. As they deserve that much at the very least.
I am more than happy to help and try and figure something out, as you both can contact me elsewhere as well. Let's talk this out like civilized people and come up with a solution.
Thanks again, and I wish you to continue to live happy lives,
Sprungles/Sprunglicious
Sprunglicious said:
You have failed to note that this guide has been updated since I had commented. As I have said elsewhere, there was no hostility meant by anything above. Simply a warning to those out there. Because having to modify _a or _b are not small acts when it comes to the world of Android Modification. My account may be semi-new, but I have been doing this since the android 4.0 days. as this was a new account created due to losing access to my old account. So let's not even bother trying to get into the credibility argument. It isn't something worth either of our's time.
By all means did I want this to be helpful, but the reality is that there were multiple devices to have been reported to have been ruined, being left with a CDE error. Which means they could not have been recovered with the MSMTools in the wild, as they could not pass the verification check to flash. And during this process there was zero ways to get to fastboot to fix the devices in that manner.
Frankly, due to what had occured, I have been having to pull my own time trying to help these individuals in a situation that I did not cause in the first place, when i could have either been working on my own project and spending time with my family. I have been working on trying to build an ops file to flash with the current MSMTools out currently to eventually get these devices fixed (as they are belonging to normal OEM configuration of the OnePlus Nord N200 (Dre). Not the AA variant. This process has been unsuccessful thus far, meaning we still have paperweights.
The only thing I ask is that some kind of assistance be given to those who followed the improper guide in its' original form. As they deserve that much at the very least.
I am more than happy to help and try and figure something out, as you both can contact me elsewhere as well. Let's talk this out like civilized people and come up with a solution.
Thanks again, and I wish you to continue to live happy lives,
Sprungles/Sprunglicious
Click to expand...
Click to collapse
Even before OP updated it, it worked. I used the original form myself. As far as I can tell the expanded form was an effort to ensure less issues for those who have no business attempting it in the first place. I wouldn’t call that improper.
No one is questioning your “credibility” and I’m not sure why you even feel the need to bring that up because it has no bearing to the conversation. This is about whether you know what you’re doing with Android, but rather whether you can be a decent contributor to the conversation for the benefit of all those involved, the community itself and OP.
As for your other point, you’ve taken it upon yourself to attempt to help people who clearly don’t know what they’re doing, fix their issue. Them screwing things up isn’t on OP and as is the case with anyone who provide guides/info/suggestion on XDA, it’s not their responsibility to fix an issue that happens as a result following them. If that was the case, I doubt we’d have any developers contributing on here.
You might want to rethink how you respond to someone if you’re wanting to be civilized as you indicate. And I know you know how.
Alright. As I have said before, there was no I'll intent behind any of what was said. It was all out there as a disclaimer as some newbies ended up misinterpreting information that had been put. At this point in time, things have been settled in this regard. I appreciate the feedback and am glad the original creator updated the post to have less of misunderstanding.
The message was put there as a "Lets not use this if we don't know what we are doing" kind of announcement if that wasnt already clear. As, at this point, each post would be best written as a step by step so the mass majority of people can understand and get use out of it.
Being understanding of the general public, and how they are going to read something and use it is a skill somebody must use when writing a guide online. As, if it is not a learning tool, then it needs be stated as such. As, the user has gone to the post for reference and instructions.
But again, at this point in time, everything has been updated and has calmed down. The writer and I are on good terms and an understanding on both of ours sides. We both have admitted the wrong and have accepted the good from this situation. So, if you have an issue with me, you have my contact information, let's take it there rather than on some public forum. It's quite inappropriate. Do also note, I did try fmto reach out to the creator before writing the warning in this post.
Sprunglicious said:
Alright. As I have said before, there was no I'll intent behind any of what was said. It was all out there as a disclaimer as some newbies ended up misinterpreting information that had been put. At this point in time, things have been settled in this regard. I appreciate the feedback and am glad the original creator updated the post to have less of misunderstanding.
The message was put there as a "Lets not use this if we don't know what we are doing" kind of announcement if that wasnt already clear. As, at this point, each post would be best written as a step by step so the mass majority of people can understand and get use out of it.
Being understanding of the general public, and how they are going to read something and use it is a skill somebody must use when writing a guide online. As, if it is not a learning tool, then it needs be stated as such. As, the user has gone to the post for reference and instructions.
But again, at this point in time, everything has been updated and has calmed down. The writer and I are on good terms and an understanding on both of ours sides. We both have admitted the wrong and have accepted the good from this situation. So, if you have an issue with me, you have my contact information, let's take it there rather than on some public forum. It's quite inappropriate. Do also note, I did try fmto reach out to the creator before writing the warning in this post.
Click to expand...
Click to collapse
Just stop. You’re replying to a post from over a week ago. I’m aware of what’s taken place since then. Good lord.