It seems that
Code:
fastboot flashing unlock
and
Code:
fastboot flashing unlock_critical
are the same command.
I've tried wiping all data, using MsmDownloadTool and re-doing every steps, but there's only two options: Unlock or Lock Bootloader.
I want flash some images into some critical partitions, it always says Flashing is not allowed for Critical Partitions. Has anyone succeed unlocking the Critical Partitions on OnePlus 6T?
vungsung said:
It seems that
Code:
fastboot flashing unlock
and
Code:
fastboot flashing unlock_critical
are the same command.
I've tried wiping all data, using MsmDownloadTool and re-doing every steps, but there's only two options: Unlock or Lock Bootloader.
I want flash some images into some critical partitions, it always says Flashing is not allowed for Critical Partitions. Has anyone succeed unlocking the Critical Partitions on OnePlus 6T?
Click to expand...
Click to collapse
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
tech_head said:
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
Click to expand...
Click to collapse
Is there any up-to-dated NetHunter kernal for Oneplus6T?
vungsung said:
I'm trying to flash NetHunter kernel: https://forum.xda-developers.com/oneplus-6t/development/oneplus6-6t-nethunter-kernel-t3900105, which lead me to a github page: https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel. I followed the tutorial in the github page. They say you have to flash patched imgaes list in https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel/blob/master/flash.bat. I run flash.bat, and saw the errors.
Click to expand...
Click to collapse
When I flash ElementalX the boot image is patched via the install.
On this phone, if you have a patched boot image it's not a critical partition.
fastboot flash boot_a/b boot.img (the boot_a/b is for which partition you are flashing).
tech_head said:
When I flash ElementalX the boot image is patched via the install.
On this phone, if you have a patched boot image it's not a critical partition.
fastboot flash boot_a/b boot.img (the boot_a/b is for which partition you are flashing).
Click to expand...
Click to collapse
I don't get it. I do have to flash boot.img, which is not critical, AND below, that some of them are critical.
Code:
fastboot erase boot_a
fastboot erase boot_b
fastboot erase system_a
fastboot erase system_b
fastboot erase radio
fastboot erase radio_a
fastboot erase radio_b
fastboot erase recovery
fastboot erase recovery_a
fastboot erase recovery_b
fastboot erase userdata
fastboot erase userdata_a
fastboot erase userdata_b
fastboot flash abl_a abl.img
fastboot flash aop_a aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash boot_a boot.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash devcfg_a devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash hyp_a hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash modem_a modem.img
fastboot flash oem_stanvbk_a oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash tz_a tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_a xbl.img
fastboot flash abl_b abl.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_b boot.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk_b oem_stanvbk.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_b system.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash xbl_b xbl.img
Or it won't boot...
vungsung said:
I don't get it. I do have to flash boot.img, which is not critical, AND below, that some of them are critical.
Code:
fastboot erase boot_a
fastboot erase boot_b
fastboot erase system_a
fastboot erase system_b
fastboot erase radio
fastboot erase radio_a
fastboot erase radio_b
fastboot erase recovery
fastboot erase recovery_a
fastboot erase recovery_b
fastboot erase userdata
fastboot erase userdata_a
fastboot erase userdata_b
fastboot flash abl_a abl.img
fastboot flash aop_a aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash boot_a boot.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash devcfg_a devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash hyp_a hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash modem_a modem.img
fastboot flash oem_stanvbk_a oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash tz_a tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_a xbl.img
fastboot flash abl_b abl.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_b boot.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk_b oem_stanvbk.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_b storsec.img
fastboot flash system_b system.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash xbl_b xbl.img
Or it won't boot...
Click to expand...
Click to collapse
That is a complete wipe and install.
If you are only installing a kernel and NOT a ROM then that is not correct.
tech_head said:
That is a complete wipe and install.
If you are only installing a kernel and NOT a ROM then that is not correct.
Click to expand...
Click to collapse
I know the correct steps to install kernels or ROMS. The problem is I tried to install OOS official ROM, and install the Nethunter kernel, the kernel won't work at all. So I have to install the patched ROM by flash the patched images inside the ROM one-by-one and then install kernel.
vungsung said:
I know the correct steps to install kernels or ROMS. The problem is I tried to install OOS official ROM, and install the Nethunter kernel, the kernel won't work at all. So I have to install the patched ROM by flash the patched images inside the ROM one-by-one and then install kernel.
Click to expand...
Click to collapse
You indicated you were trying to flash a kernel which is why I said that. Had you said you were trying to flash a complete ROM then I would have said something else.
tech_head said:
You indicated you were trying to flash a kernel which is why I said that. Had you said you were trying to flash a complete ROM then I would have said something else.
Click to expand...
Click to collapse
Sorry, I didn't mean to make you misunderstood. For those find this thread with the same problem, I'd say trying to flash OOS by normal way. Thanks for your help, tech_head!
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
sadatkabir55 said:
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
Click to expand...
Click to collapse
Wrong thread there Glenda. This is the 6T forum.
I got same problem how to fix this???????
vungsung said:
I'm trying to flash NetHunter kernel: https://forum.xda-developers.com/oneplus-6t/development/oneplus6-6t-nethunter-kernel-t3900105, which lead me to a github page: https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel. I followed the tutorial in the github page. They say you have to flash patched imgaes list in https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel/blob/master/flash.bat. I run flash.bat, and saw the errors.
Click to expand...
Click to collapse
That's a pretty old version of that kernel. Here's the up to date version, and you can flash it from recovery without any issues
http://www.mediafire.com/file/fue9i4pzbcp4x6w/NHKernel.zip/file
Jfoster1234 said:
That's a pretty old version of that kernel. Here's the up to date version, and you can flash it from recovery without any issues
http://www.mediafire.com/file/fue9i4pzbcp4x6w/NHKernel.zip/file
Click to expand...
Click to collapse
Alright, thank you for the resource!
have you fixed already bro?
sadatkabir55 said:
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
Click to expand...
Click to collapse
have you fixed?
sadatkabir55 said:
i am using china global oneplus 8. I have unlocked bootloader but i cannot unlock critical partition . i have tried with this code: fastboot flashing unlock_critical
But it is not working ..please help me to unlock critical partition. My phone is bricked....
Click to expand...
Click to collapse
gazitonmoy said:
have you fixed?
Click to expand...
Click to collapse
[CLOSED] Same here, no Idea what to do? Phone bricked and dead. PLEASE HELP US, GUYS
--
EDIT: *lol - I did a "oem lock" and a "oem unlock" again... and suddenly my device behaves as expected again, without needing to "flash-all.bat". Perhaps sometimes I will understand this stuff... :/
tech_head said:
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
Click to expand...
Click to collapse
What does "dd" stand for?
Did you solve this? I have the same issue. Oneplus 8 Pro, got it and installed LineageOS right away which worked, but just wasn't useable, lots of gps stuff not working. So, I wanted to restore the factory ROM. I followed this:
How to Create Fastboot-flashable Factory Image for Any OnePlus Phone
Learn how to create a factory image for any OnePlus phone and flash it using Fastboot. Useful for restoring stock OxygenOS software and unbricking.
www.thecustomdroid.com
Ran through everything fine as far as I could tell the first time, but it wouldn't boot, just kept going back to fastboot.
So, I tried to re-do the steps but upon trying to go through them again, as soon as I get to about the 5th command where I reboot before continuing to flash, it reboots with a Qualcom crash screen. I can still power off and get to fastboot, but if I try to continue the flash steps i get this same error on any of them.
PLEASE HELP! I just got this phone and paid a ton I am going to loose it if I bricked it already.
UPDATE: Forget this. I didn't solve it, but I did manage to at least restore A rom.
tech_head said:
You cannot flash critical the 6T.
You need to dd directly to the media.
What are you wanting to flash to a critical partition.
Click to expand...
Click to collapse
may i know how? i want to flash persist.im for oneplus6t
Related
Hi, my MOTO G7 is bricked, it wont start, not even for the bootloader, even if i hold the power button for 10 seconds, it just doesnt work, it makes a sound when i plug it in the pc, and thats it.
i unlocked bootloader successfuly and it was working fine, i was trying to root the phone using magisk, as one thread in this forum suggested, it wouldnt work, so i decided to flash the stock rom, because the boot.img wasnt working properly.
i downloaded my correct version for my device "OPENCL" on the lolinet webpage that was posted in this forum
and i installed it using the following commands in fastboot:
fastboot getvar max-sparse-size
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
rem fastboot erase modemst1
rem 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 vendor vendor.img_sparsechunk.2
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​
it should have worked, but when i rebooted the phone, it was bricked.
did i miss a step? how can i unbrick it ? i havent been able to find anything online.
Thanks in advance
Are you able to access bootloader by press and hold Vol - while powering on?
Try RETAIL ROM and see the result
Also, try RSDlite to flash if it can recognize your phone
mingkee said:
Are you able to access bootloader by press and hold Vol - while powering on?
Try RETAIL ROM and see the result
Also, try RSDlite to flash if it can recognize your phone
Click to expand...
Click to collapse
no, i can't access bootloader.
I have a rooted G7 that I rooted (unofficial twrp and then Magisk) when it was still at the original January android version. How do I get its android version updated? I've read others
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342/page4
who bricked their phones trying to do this.
Is there a way to safely get the ota updates?
How?
maybeme2 said:
I have a rooted G7 that I rooted (unofficial twrp and then Magisk) when it was still at the original January android version. How do I get its android version updated? I've read others
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342/page4
who bricked their phones trying to do this.
Is there a way to safely get the ota updates?
How?
Click to expand...
Click to collapse
OTA on a rooted device? No. Do the update yourself and save the headache:
1. Download the latest firmware here.
2. Install adb & fastboot
windows:
download
linux:
Code:
sudo apt install adb fastboot -y
if you have Debian/Ubuntu family of OS
download here if you don't
3. Flash with these commands:
Code:
fastboot getvar max-sparse-size
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 dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.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 vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
4. Install TWRP and reroot
Thank you very, very much.
Will I lose my installed apps including Titanium Backup to restore app data?
maybeme2 said:
Thank you very, very much.
Will I lose my installed apps including Titanium Backup to restore app data?
Click to expand...
Click to collapse
If you skip the command:
Code:
fastboot erase userdata
then all your data stays. Do all the other commands.
ptn107 said:
1. Download the latest firmware here.
Click to expand...
Click to collapse
May I ask where this firmware comes from? Is it authentic Moto firmware or extracted and possibly modified?
Thanks again.
Dear friends,
Some time ago there were report about a serious vulnerability in the Snapdragon devices firmware, which have affected multiple users.
As a user of a Lineage OS I can not install the vendor updates, because in this case I will need to re flash all the device twice (once with Oxygen OS and second time back with Lineage OS). To fix this problem I used to extract the individual BLOBS and flash them to the phone.
I have downloaded the latest version of the Oxygen OS and extracted the payload.bin. This file contains all the BLOBs and meta data used to flash the original operation system. The blobs can be easily recovered by using the extract_android_ota_payload from cyxx script and instructions from the corresponding readme file.
Create the virtual environment with the only dependency of extract_android_ota_payload - protobuf:
Code:
pip3 install virtualenv --user
virtualenv proto_env
source proto_env/bin/activate
pip install -U protobuf
Then extract BLOBS:
Code:
python /path/to/extract_android_ota_payload.py path/to/payload.bin output_dir
Create the script to flash all the BLOBs to the phone and save it to flasher.sh
Code:
#!/bin/bash
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.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 fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash india_a india.img
fastboot flash india_b india.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 modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash reserve_a reserve.img
fastboot flash reserve_b reserve.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
echo "\"Invalid sparse file format at header magic\" is not an error you need only to wait"
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
exit 0
Reboot the phone to fastboot mode and flash:
Code:
# Check that we see the device:
flastboot devices
./flasher.sh
This script has successfully updated all the non lineage OS partitions (which are boot.img, dtbo.img, system.img and vbmeta.img).
Though the Trust utility is happy, saying that all the updates were applied successfully, I still have seen several errors, updating the critical sections: keymaster, tz, xbl_config and xbl. I think that Trust only check the vendor partition and does not check others.
Did anybody encountered this kind of problems? Is it critical to update ALL the partitions?
Hi Guys
I bricked my phone because I did something wrong. I need help.
I have a rooted Moto g7 (river) running android pie.
I decided to upgrade it to android 10.
1. I downloaded the latest android 10 version from:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
2. created new C:\adb2021 folder in laptop
obtained latest adb/fastboot from
https://developer.android.com/studio/releases/platform-tools
unziped the zip contents into the new C:\adb2021
3. Connected by cable and turned on phone
4. In a CMD prompt on W10 went to in C:\adb2021
5. adb reboot bootloader
was successful
6. I then ran
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 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 vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase DDR
fastboot flash logo logo.bin
patched_boot.img
fastboot reboot
Problem:
The phone rebooted but is stuck on the
"your device has been unlocked and can't be trusted" screen.
Rebooting just brings me back to this same screen.
I can get to the Android Recovery screens but don't know what to do there.
The fastboot commands I listed above were originally designed for installing android 9. I now see I should have included fastboot flash system system.img_sparsechunk.10
When in the recovery screen "Flastboot Flash mode" I tried to issue from the laptop
C:\ADB2021>adb reboot bootloader
I get
error: no devices/emulators found
Please help. This is my main phone.
How do I recover?
Thanks.
I tried factory reset. And then reboot but it still only goes to the "this device is unlocked....." and stays there.
I really need help.
Hello,
if i use a custom rom and i try to go back to oos. I always need to use msm and flash 11.0.4.4. After this i can update to 11.0.9.9.
If i flash oos like this from fastboot:
Code:
fastboot -w
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 fastboot
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 --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot-bootloader
pause
I mostly end with the qualcomm failsafe mode.
Something i do wrong here? It doesnt matter if i wipe data in recovery first.
Do i need to remove fingerprint or encryption overall first maybe?