Database Develop

MI3 Completely bricked!!!

Guys i have bricked MY mi3 16gb.
I was using Bitti opticancro build with extended partitiion.
as i want to go to miui v6. i flashed stock partition zip
Then i flashed miui stock recovery and tried to flash the miui latest rom
i forgot to rename the rom zip to update .zip so i couldnt insatll the miui rom.
the i tried to flash using fast fastboot mode but it is showing error as remote size too large.
now i am stuck with miui recovery and fastboot error.
pls help me to get back my phone.

If you can enter fastboot mode, then you can flash miui rom manually.
First unzip miui fastboot rom, place adb and fastboot files into the folder you just extracted. (ex. located in cancro_global_images_V6.4.3.0.KXDMICB_4.4_global\images)
And then press shift while in this folder to open terminal, type these one by one.
Code:
fastboot devices
fastboot flash tz tz.mbn
fastboot flash dbi sdi.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot erase boot
fastboot flash misc misc.img
fastboot flash modem NON-HLOS.bin
fastboot flash modem1 NON-HLOS.bin
fastboot flash system system.img
fastboot flash system1 system.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash boot1 boot.img
fastboot flash userdata userdata.img[B] (optional, need backup first, but I recommended to flash this if you want to use gapps)[/B]
fastboot reboot
You're done!
Android ADB Fastboot files is given if you don't have one.https://www.dropbox.com/s/ndud98a4ek3fvxg/Android_ADB_FASTBOOT.zip?dl=0

Or you can just fastboot flash TWRP recovery and then flash whatever you want from USB or something...

1)Install CWM recovery
2) Download restore-stock partition zip file from here http://www.htcmania.com/showpost.php?p=17750021&postcount=144
3) Flash it.
4) Now get in fastboot mode.
5) Get fasboot images from MIUI Forums
6) Flash it via MiFlash or use command line given by 2nd comment
7) Grab a coffee and you will be on miui in no time
8) use miui

Edit: http://xiaomi.eu/community/threads/5-5-8.27542/page-8#post-246332
There is modified flash_all.bat for Mi2, i beleive same works for cancro.
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash partition" && exit /B 1
Add this line after getvar and before flash lines in flash_all.bat and then MiFlash it like usually.

Flash cwm via fastboot, use "fastboot flash recovery recoveryname.img" and don't use this title, its not completely bricked.

Never run stock recovery until u manage to flash a stockrom.. Better remember that.. Save twrp or cwm.. In my case, on last monday, on twrp, i've accidentally wipe internal storage.. Luckily got 6 type of rom in usb-otg..

Fastboot commands for flashing honor 9 lite

Please gve the fastboot command for Oreo for flashing
Boot.img
Recovery.img
System.img
...........................,.......,..........
These comments are not working
Fastboot flash boot
Fastboot flash recovery
Please help me

Curious8 said:
Please gve the fastboot command for Oreo for flashing
Boot.img
Recovery.img
System.img
...........................,.......,..........
These comments are not working
Fastboot flash boot
Fastboot flash recovery
Please help me
Click to expand...
Click to collapse
The fastboot commands you are executing are lacking the image file and have the incorrect partition target.
Code:
fastboot flash ramdisk "boot-image-filename.img"
fastboot flash recovery_ramdisk "recovery-image-filename.img"
fastboot flash system "system-image-filename.img"
fastboot flash vendor "vendor-image-filename.img"

@Curious8
If you will flash anything - it' a good idea you have FULL-Update from your Build on your PC !
Find FULL-Update with HuaweiFirmwareFinder and download.
Extract with HuaweiExtractor from Update.app (inside Update.zip) 3 img : ramdisk.img, recovery_ramdis.img, system.img
The Extractor do automatic 3 *.img.header. This 6 files copy to your ADB-Folder.
NOW you can flash any developer-rom. If this not work reset your phone to stock-rom with
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
this help for self-repair if
- bootloader unlocked
- FRP unlock
the commands you write is for Android older OREO ! With OREO we have new Partition-Names and new commands.

[ROM][STOCK][FASTBOOT][OP7P] Stock Fastboot ROMs for OnePlus 7 Pro/ 7 Pro 5G

Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7 Pro in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
FLASHER ADVANCED GUIDE
flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=294300
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro
OnePlus 7 Pro Persist: https://androidfilehost.com/?fid=6006931924117929081
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (you need to extract images.zip before proceed)
Fastboot Partitions:
Code:
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 boot_a boot.img
fastboot flash boot_b boot.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 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 storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
If you need also persist partition, this is the command:
Code:
fastboot flash persist persist.img
Criticals Partitions, for these you need to boot the TWRP:
Code:
fastboot boot TWRP.img
When you are in TWRP you need to run these commands to push and flash all criticals partitions:
Code:
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
adb push odm.img /sdcard/odm.img
adb shell dd if=/sdcard/odm.img of=/dev/block/bootdevice/by-name/odm_a
adb shell dd if=/sdcard/odm_config.img of=/dev/block/bootdevice/by-name/odm_b
adb push tz.img /sdcard/tz.img
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_a
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_b
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
Thanks to @SaiBork for first time tested
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
​

I know you said not for branded devices, are the partitions different for these devices?
Just wondering if this could be what we need to convert the T-Mobile version and if so if you need tester.

criptix said:
I know you said not for branded devices, are the partitions different for these devices?
Click to expand...
Click to collapse
Yes, sometimes also the rom is different. Actually the branded devices can't use this rom also if they want, because to use this rom you need to have an unlocked bootloader

Yeah figured bootloader would need to be unlocked as well.
If you happen to need testers for the conversion ( if your working on it) let me know.

I just SIM unlocked my T-Mobile variant today, and also applied for my unlock .bin on the OnePlus site!

Thank you! You revived my phone!

zzs001 said:
Thank you! You revived my phone!
Click to expand...
Click to collapse
Perfect, like for others oneplus devices i will continue to support them, if you want to contribute and help me, please consider making a donation, thanks.

I've F-ed my international 7 Pro up, used your flash all, seemed to have work, but stuck in a loop now... Anyone got any suggestions, please?
I was so happy when I found this post, I thought my problems were over, but yeah... apparently not

posedatull said:
I've F-ed my international 7 Pro up, used your flash all, seemed to have work, but stuck in a loop now... Anyone got any suggestions, please?
I was so happy when I found this post, I thought my problems were over, but yeah... apparently not
Click to expand...
Click to collapse
which version you had before use fastboot rom? which fastboot rom did you used?

I was on stock, tried to install twrp, didnt go well (wouldn't mount), and i wanted to wipe data/cache, and mistakenly wiped system as well because i wasnt paying attention. Tried putting the stock recovery, still wouldnt boot due to obvious reasons.... then I found this
Basically I had the 9.5.4 with deleted system when I attempted to use the flash all bat.
GM21BA, european 12gb one, if it makes any difference...

posedatull said:
I was on stock, tried to install twrp, didnt go well (wouldn't mount), and i wanted to wipe data/cache, and mistakenly wiped system as well because i wasnt paying attention. Tried putting the stock recovery, still wouldnt boot due to obvious reasons.... then I found this
Basically I had the 9.5.4 with deleted system when I attempted to use the flash all bat.
GM21BA, european 12gb one, if it makes any difference...
Click to expand...
Click to collapse
So you should use the 9.5.4 fastboot rom, have you used it?

of course.
I am hoping maybe a failed download, so I just redownloaded it and trying again now

posedatull said:
of course.
I am hoping maybe a failed download, so I just redownloaded it and trying again now
Click to expand...
Click to collapse
The process can take a lot of time, just wait until you see something like "presse a key to proceed"

also:
"extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.386s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk..."
tose missing files, is that normal?
downloaded your zip, extracted it, started flash-all.bat, no modifications done whatsoever
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
the zip finishes, no problem,ends with
"writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 153.005s
Press any key to exit..."
and then the phone tries to boot, i get to the spinning 1+ logo, and it stays there for even an hour if i let it...

posedatull said:
also:
"extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.386s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk..."
tose missing files, is that normal?
downloaded your zip, extracted it, started flash-all.bat, no modifications done whatsoever
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
the zip finishes, no problem,ends with
"writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 153.005s
Press any key to exit..."
and then the phone tries to boot, i get to the spinning 1+ logo, and it stays there for even an hour if i let it...
Click to expand...
Click to collapse
so i don't know, try to use the other flashall, you should unpack image.zip and other flashall in the main folder and then you should run the flash-all-fastboot.bat.
If you want you can try to flash the twrp in the boot partition and then try to flash the stock rom through sideload

i've just tried all of them one by one... still bootloop every time

posedatull said:
i've just tried all of them one by one... still bootloop every time
Click to expand...
Click to collapse
do you want to contact me on telegram? Maybe i can help you better

i'm struggling this at work, but i'll be home in about 2hours.
if you could help then, i would seriously appreciate it

posedatull said:
i'm struggling this at work, but i'll be home in about 2hours.
if you could help then, i would seriously appreciate it
Click to expand...
Click to collapse
Yes yes, write me on telegram, the nick is always the same: mauronofrio

hello, how long should it take to first boot after flashing all? I'm waiting for so long...

Question Unlock bootloader Realme 8 Pro?

How to unlock the Realme 8 Pro bootloader?

1. you'd better write in english, to get a broader range of people who understand you question ;-).
2. Also waiting for that ... it's a shame.
Greetz
Kurt

How to unlock bootloader realme 8 5G

Answer from [email protected] from today :
Unlock Bootloader tutorial for Realme 8 Pro RMX3081 is not available as of now.Further, keep following our social media handles and official community portal for the latest updates,

Yeah, we can achieve the bootloader unlock of realme 8 pro. Mine is unlocked. The build number and security patch must be (RMX3081_11_A.44) (November 5,2021)

This is Export rom not the GDPR rom (EU)
Have flashed it and can unlock and flash files via fastboot.
OFP - Original Firmware Project :
Code:
Model Project Project ID Download link
RMX3081 20711 (Project ID-20711)_INDIA,MM,BD,PK RMX3081export_11_A.44 https://fileload.coloros.com/504197RMX3081export_11_A.44_2021110921030235.zip
RMX3081 20712 (Project ID-20712)_PH,VN,KH,-EG,IQ,MY RMX3081export_11_A.44 https://fileload.coloros.com/504198RMX3081export_11_A.44_2021110921100000.zip
RMX3081 20713 (Project ID-20713)_LUX,CH,ES,UK,FR,IT,DE,NL,BE,NO,PT,FIN,CY RMX3081GDPR_11_A.44 https://fileload.coloros.com/504200RMX3081GDPR_11_A.44_2021110921090000.zip
RMX3081 20713 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504199RMX3081export_11_A.44_2021110921060000.zip
RMX3081 20714 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504201RMX3081export_11_A.44_2021110921110000.zip
@Shibu Shaji share us the
getprop ro.build.display.full_id

Yeah, we can achieve the bootloader unlock of realme 8 pro. Mine is unlocked. The build number and security patch must be (RMX3081_11_A.44) (November 5,2021)
StratOS_HTC said:
This is Export rom not the GDPR rom (EU)
Have flashed it and can unlock and flash files via fastboot.
OFP - Original Firmware Project :
Code:
Model Project Project ID Download link
RMX3081 20711 (Project ID-20711)_INDIA,MM,BD,PK RMX3081export_11_A.44 https://fileload.coloros.com/504197RMX3081export_11_A.44_2021110921030235.zip
RMX3081 20712 (Project ID-20712)_PH,VN,KH,-EG,IQ,MY RMX3081export_11_A.44 https://fileload.coloros.com/504198RMX3081export_11_A.44_2021110921100000.zip
RMX3081 20713 (Project ID-20713)_LUX,CH,ES,UK,FR,IT,DE,NL,BE,NO,PT,FIN,CY RMX3081GDPR_11_A.44 https://fileload.coloros.com/504200RMX3081GDPR_11_A.44_2021110921090000.zip
RMX3081 20713 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504199RMX3081export_11_A.44_2021110921060000.zip
RMX3081 20714 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504201RMX3081export_11_A.44_2021110921110000.zip
@Shibu Shaji share us the
getprop ro.build.display.full_id
Click to expand...
Click to collapse
Here is my id : RMX3081export_11_A.44_2021110921030235

Yeah, see it's exported Project ID-20711 and don't have a bootloader locked.
Have flashed it previously and know that.
The GDPR versions of ROM you cannot do almost nothing 4 now.

Oh bro, this is not GDPR version.. After I unlocked my bootloader, i tried to root realme 8 pro with patched boot image from OFP Rom but it's doesn't work for me..
Any thing to say about this?
StratOS_HTC said:
Yeah, see it's exported Project ID-20711 and don't have a bootloader locked.
Have flashed it previously and know that.
The GDPR versions of ROM you cannot do almost nothing 4 now.
Click to expand...
Click to collapse

Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system

Since jour project id is 20711
Guess your PCB shows 0020711*
dial : *#899#
press the PCB num

StratOS_HTC said:
Well let me guide you throught it :
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Click to expand...
Click to collapse
Yeah , tried but nothing seems to be work.
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_sys
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Click to expand...
Click to collapse
Yeah i tried the steps that u said above to ROOT realme 8 pro, but it doesn't work for me... here are the steps that i did.
Fastboot mode
*Fastboot flashing unlock
*Fastboot --disable-verity --disable-verification
flash vbmeta vbmeta.img
*Fastboot flash boot (magisk patched) boot.img
Result : Device went to bootloop. Retrieved from
bootloop by flashing stock boot image that previously extracted from OFP file and now the device is fine.
Also tried this step
Fastboot mode
*Fastboot flashing unlock
*Fastboot --disable-verity --disable-verification
flash vbmeta vbmeta.img
* Fastboot --disable-verity --disable-verification
flash vbmeta_system vbmeta_system.img
*Fastboot --disable-verity --disable-verification
flash vbmeta_vendor vbmeta_vendor.img
*Fastboot flash boot (magisk patched) boot.img
Result : Bootlooped. Retrieved by flashing stock boot image..
And also, i tried to BOOT patched boot image... and it shows
FAILED <remote: unknown command>

ABV is still active.

THX @Shibu Shaji
For showing us the 20711 EXPORT .44 ROM fastboot getvar all infos.
I have also the 20713 GDPR .44 ROM fastboot getvar all infos.
The bootloader in EXPORT is unlocked and is not userspaced.

From green to orange state ... some progress after all ...

It seems your bootloader unlocked? actually how? I think ur AVB is now disabled

StratOS_HTC said:
View attachment 5505451
From green to orange state ... some progress after all ...
Click to expand...
Click to collapse
Wow, how did you do it?

currently via isp ufs access and help of a reversing from a friend.
On bootloop also ...

Oh bro, So what to do next? Is there any other problems with ur partitions after this?

Since EDL is not configured correctly (No kernel driver supported: Operation not supported or unimplemented on this platform) after the firehose programmer sucessfully boot ...
Also QFIL and unimplemented <CONFIGURE> or <SIG> and signed and certed things the only thing to do is via ISP UFS control.
OR possible USB port communication debug via MSM flash.
For EXPORT version have prepared seen action on the screen for this ROM
Code:
Project 20711
RMX3081
Version Flash MSM download tool v.2.0.51 for eMMC/UFS
Rom ofp : RMX3081export_11_A.28_202104090210
Server : India
Use default NV=yes
Reboot on finish=yes
Download Firehose protocol file
Sahara communication succeeded
Boot via firehose
Trying to handshake
Get sign data
Verify data
Getting NV code from server
Failed to get NV code. Default NV code would be used
Firehose GetUfsInfo
Erasing the partition Primarly GPT
Erasing the partition BackupGPT
Erasing the partition userdata
Downloading cdt_engineering_release.img
Erasing partition keystore
Downloading cache.img
Downloading recovery.img
Downloading metadata.img
Downloading userdata.img
Downloading gpt_main0.bin
Downloading xbl.elf
Downloading gpt_main1.bin
Downloading gpt_main2.bin
Downloading aop.mbn
Downloading tz.mbn
Downloading NON-HLOS.bin
Erasing the partition mdtpsecapp
Erasing the partition mdtp
Downloading abl.elf
Downloading dspso.bin
Downloading boot.img
Downloading devcfg.mbn
Downloading vbmeta_vendor.img
Downloading dtbo.img
Downloading imagefv.elf
Downloading oppo_sec.mbn
Downloading dpAP.mbn
Erasing the partition spunvm
Downloading splash.img
Downloading logfs_ufs_8mb.bin
Erasing the partition cateloader
Erasing the partition rawdump
Erasing the partition logdump
Download multi_image.mbn
Erasing the partition catefv
Downloading gpt_main4.bin
Download static_nvbk.bin
Erasing the partition opporeserve1
Downloading emmc_fw.bin
Downloading DRIVER.ISO
Downloading gpt_main5.bin
Restarting
Downloading Firehose protocol file
Sahara communication succeeded
Trying to handshake via Firehose
Configure the settings of Firehose
Get sign data
Verify data
Downloading super partsuper.0
Downloading super partsuper.1
Downloading super partsuper.2
Get basic data
Write patch image to user partition
Restarting
Download succeeded
Get sign data
Verify data
Currently non-implemented/documented also by MSM7125 ?

[GUIDE] Flashing the latest firmware updates to your OnePlus 6T

This guide exists next to [GUIDE] Extracting the latest firmwares from ROM update package and they supplement eachother.
General word about firmware updates:
A lot of people know of the importance and benefits of keeping your device firmware updated, just like you keep your custom ROM updated. If you don't keep them updated, you might not get the best out of your custom ROM (like: more bugs, system stability and performance problems/less speed.. also, vendor components, e.g Qualcomm and other chips, have security patches in the firmware.. "Vendor patch level" vs Android "Security patch level").
Besides incremental firmware updates from each OxygenOS release with a small changelog, too many people are missing out on huge jumps such as that they are running an Android 11 custom ROM, while their firmware was never updated so it remained a firmware originally shipped with an Android 10 (or earlier) OxygenOS release. Staying behind on huge jumps like these, causes the biggest list of problems with stability and performance. Therefore it is advisable to keep your firmware updated, and note that even small incremental updates (based on the same Android version) tend to give performance, security and stability benefits.
Prerequisites
For flashing the latest firmware, you need to have the firmware files (NOT the ROM update .zip file.. but a bunch of .img's) first. You can get them in multiple ways:
- Look for someone on XDA that has shared them, after they extracted the firmwares from the ROM update .zip file. This saves you time, but if you want to do it by yourself then first follow the "Extract firmwares" guide. An example of a reason for doing it yourself is: you want to be sure of the authencity, completeness and integrity of firmware files (that is everything but guaranteed if you DL it from another user)
- Do it yourself, as described above, and for this use the guide linked above
So after this stage, you have the firmware .img files, as required to proceed:
GUIDE STARTS BELOW THIS LINE
1) Get adb and fastboot from https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2) Extract the above (adb and fastboot) to a folder named "FW update". We assume that's the location all of the extracted firmware (.img) files are, like they would be if you followed the "Extract firmwares" guide to get them
So, now that your adb and fastboot are in the same folder as all required firmware files, you can proceed.
3) Actual flashing instructions, a very simple process
Code:
1) Boot to Recovery
2) Enter Fastboot (e.g for LineageOS recovery: "Advanced" > "Enter Fastboot")
3) Connect phone to PC with USB cable
4) Open cmd (command prompt) in your adb / fastboot binaries location folder (in cmd, enter cd [location of your "FW update" folder.. or alternatively copy cmd.exe from system32 to "FW update" folder & open it there),
5) Start flashing..
Enter commands 1 by 1:
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 cmnlib cmnlib.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all LOGO LOGO.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all vendor vendor.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot reboot
Done, now your phone will boot up with the updated firmwares.

What's the command to flash system IMG? Can I use this process to flash A11 update from A9 MSM tool?

Doesn't this give can't flash on critical partitions error? Or am I missing something?