Anti Roll Back - Xiaomi Mi A3 Questions & Answers

Anti Roll Back - Xiaomi Mi A3 Questions & Answers

Plaese if someone can help
i ininstalled magisk because bugs, and it restart and stay on AndroidOne screen
when i tried to reinstall stock i got this
C:\adb>echo "laurel_sprout fastboot flash tools"
"laurel_sprout fastboot flash tools"
C:\adb>set CURRENT_ANTI_VER=0
C:\adb>for /F "tokens=2 delims=: " %i in ('fastboot getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
C:\adb>(set version=0 )
C:\adb>if [0] EQU [] set version=0
C:\adb>set anticheck="antirollback check pass"
C:\adb>if 0 GTR 0 set anticheck="Current device antirollback version is greater than this package"
C:\adb>echo "antirollback check pass" | findstr /r /c:"pass" ||
"antirollback check pass"
C:\adb>fastboot getvar product 2>&1 | findstr /r /c:"^product: *laurel_sprout" || echo Missmatching image and device
product: laurel_sprout
C:\adb>fastboot getvar product 2>&1 | findstr /r /c:"^product: *laurel_sprout" || exit /B 1
product: laurel_sprout
C:\adb>fastboot flash crclist "C:\adb\images\crclist.txt"
Sending 'crclist' (0 KB) OKAY [ 0.003s]
Writing 'crclist' OKAY [ 0.006s]
Finished. Total time: 0.019s
C:\adb>fastboot flash sparsecrclist "C:\adb\images\sparsecrclist.txt"
Sending 'sparsecrclist' (0 KB) OKAY [ 0.007s]
Writing 'sparsecrclist' OKAY [ 0.001s]
Finished. Total time: 0.022s
C:\adb>fastboot flash tz_a "C:\adb\images\tz.mbn" ||
Sending 'tz_a' (1968 KB) OKAY [ 0.074s]
Writing 'tz_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
"Flash tz_a error"
C:\adb>pause
Drücken Sie eine beliebige Taste . . .

It seems that you have locked bootloader "remote: 'Flashing is not allowed in Lock State'".

You cannot use flashtool with locked bootloader. Unlock it first then run flashtool. After flash complete, set boot slot to A, complete the first boot then relock bootloader if you want

Related

Ruu Problem

hey,
i tried to install the RUU for my One X+ because the sd card, wifi network, cell network is inaccsesible right now.
Also the ADB is not accesible, it always returns device not found error. (i double checked everything).
Finally it gets stuck in the way installing:
Code:
<T121536><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T121536>
<T121537><DEBUG><OUT>FA2C7W106219 fastboot</OUT>
</DEBUG></T121537>
<T121537><DEBUG><CMD>fastboot -s FA2C7W106219 getvar boot-mode</CMD>
</DEBUG></T121537>
<T121537><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T121537>
<T121537><DEBUG><CMD>fastboot -s FA2C7W106219 erase cache</CMD>
</DEBUG></T121537>
<T121539><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T121539>
<T121539><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T121539>
<T121539><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T121539>
<T121539><DEBUG>signed rom
</DEBUG></T121539>
<T121539><DEBUG>getImageCount, nHR: 19
</DEBUG></T121539>
<T121539><DEBUG><CMD>fastboot -s FA2C7W106219 flash zip C:\Users\Ike\AppData\Local\Temp\{545A2C96-F188-4ED7-93DD-73E45B96952E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T121539>
<T121709><DEBUG><OUT>sending 'zip' (711478 KB)... OKAY</OUT>
</DEBUG></T121709>
<T121709><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T121709>
<T121709><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T121709>
<T121740><DEBUG><OUT>INFOrom parsing start ...</OUT>
</DEBUG></T121740>
<T121744><DEBUG><OUT>INFOtime: 4297</OUT>
</DEBUG></T121744>
<T121744><DEBUG><OUT>INFOrom parsing finish ...</OUT>
</DEBUG></T121744>
<T121745><DEBUG><OUT>INFOYour memory size = 59640MB, choose rawpt_64g.img</OUT>
</DEBUG></T121745>
<T121745><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>
</DEBUG></T121745>
Any ideas?

iTTerror said:
hey,
i tried to install the RUU for my One X+ because the sd card, wifi network, cell network is inaccsesible right now.
Also the ADB is not accesible, it always returns device not found error. (i double checked everything).
Finally it gets stuck in the way installing:
Code:
<T121536><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T121536>
<T121537><DEBUG><OUT>FA2C7W106219 fastboot</OUT>
</DEBUG></T121537>
<T121537><DEBUG><CMD>fastboot -s FA2C7W106219 getvar boot-mode</CMD>
</DEBUG></T121537>
<T121537><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T121537>
<T121537><DEBUG><CMD>fastboot -s FA2C7W106219 erase cache</CMD>
</DEBUG></T121537>
<T121539><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T121539>
<T121539><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T121539>
<T121539><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T121539>
<T121539><DEBUG>signed rom
</DEBUG></T121539>
<T121539><DEBUG>getImageCount, nHR: 19
</DEBUG></T121539>
<T121539><DEBUG><CMD>fastboot -s FA2C7W106219 flash zip C:\Users\Ike\AppData\Local\Temp\{545A2C96-F188-4ED7-93DD-73E45B96952E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T121539>
<T121709><DEBUG><OUT>sending 'zip' (711478 KB)... OKAY</OUT>
</DEBUG></T121709>
<T121709><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T121709>
<T121709><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T121709>
<T121740><DEBUG><OUT>INFOrom parsing start ...</OUT>
</DEBUG></T121740>
<T121744><DEBUG><OUT>INFOtime: 4297</OUT>
</DEBUG></T121744>
<T121744><DEBUG><OUT>INFOrom parsing finish ...</OUT>
</DEBUG></T121744>
<T121745><DEBUG><OUT>INFOYour memory size = 59640MB, choose rawpt_64g.img</OUT>
</DEBUG></T121745>
<T121745><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>
</DEBUG></T121745>
Any ideas?
Click to expand...
Click to collapse
nevermind forgot to relock bootloader

Teclast T30 T1P3 Root

I downloaded the img from this thread:
https://forum.xda-developers.com/android/general/teclast-t30-t1p2-root-t4001731
I have followed the instructions to install TWRP on my T30 P1T3 and my tablet has the orange status message.
When I boot into recovery mode I am booted by the Android recovery, not the TWRP.
The procedure I have followed is this:
Code:
PS I:\Teclast T30\Rootear\platform-tools> .\adb reboot bootloader
PS I:\Teclast T30\Rootear\platform-tools> .\fastboot devices
0123456789ABCDEF fastboot
PS I:\Teclast T30\Rootear\platform-tools> .\fastboot boot TWRP-3.3.1_Teclast_T30_.img
Sending 'boot.img' (32768 KB) OKAY [ 0.875s]
Booting OKAY [ 0.063s]
Finished. Total time: 1.094s
PS I:\Teclast T30\Rootear\platform-tools> .\fastboot boot TWRP-3.3.1_Teclast_T30_.img
< waiting for any device >
Sending 'boot.img' (32768 KB) OKAY [ 0.885s]
Booting OKAY [ 0.062s]
Finished. Total time: 1.145s
PS I:\Teclast T30\Rootear\platform-tools>
What happened? What I can do? Thanks for the help.

You are only booting from the TWRP image. You need to flash the image to recovery for it to be the default.

Need help... stuck in fastboot

Hi
I was running latest Xiaomi EU rom on custom recovery and unlocked bootloader. Then I downloaded latest rom from Xiaomi.eu (xiaomi.eu_multi_MI10_V12.2.2.0.RJBCNXM_v12-11.zip) and flashed it via phone updater. It restarted into custom recovery, flashed the rom and everything was running fine. I restarted the phone and then it stucked in fastboot.
I tried to enter recovery but it loads fastboot every time.
Tried to install twrp, and it was flashed but when I try to manually enter recovery it loads only fastboot.
I tried this commands:
fastboot flash recovery twrp.img
fastboot boot twrp.img, but the second one won't go through because of the error: Failed to load/authenticate boot image: Load Error.
Please help, I have so many important stuff on my phone

Let this be a lesson to do a backup next time before flashing custom ROM's.
Most likely the TWRP you were using before is not compatible with the latest Xiaomi.EU ROM, and they also mentioned some issues with TRWP's on UMI/CMI/ and some other devices.
Most likely you will need to FORMAT your data, since even if you manage to get into TWRP, you won't be able to do a backup since TWRP's at the moment don't support Decryption on Android 11 ROM's.
Try downloading this TWRP and Flash it.
https://androidfilehost.com/?fid=10763459528675582373
If you manage to boot into TWRP, try flashing the latest Weekly, I SAID WEEKLY, ROM, as you may get a chance of booting without formating your data. If that doesn't work out, then you'll need to Flash the phone again with MI Flash.

@ekin_strops
I had the same problem. I could install your new twrp however i cant see with this twrp any files from the phone. Without this a transfer a new rom to the phone is not possible. The data manager within the MMX Miui 12 is able to see the files, so there is a problem with the twrp.

@ekin_strops
The solution: Flash via fastboot the above TWRP (recovery) and boot to recovery via fastboot.
Take a USB stick (USB OTG C) and copy the new rom (.zip) on it, connect it to the phone and install via recovery from the USB OTG the rom to your phone. Its really easy when you have a USB OTG C stick.

I managed to boot he phone, but my recovery is not working properly (won't mount).
So i tried to flash the new firmware with Miflash and it stops at the end, this is the error:
error: sending vmbeta... CRC error...
I tried to flash umi_eea_global_images_V12.0.6.0.QJBEUXM rom.
Here is the log:
[19:46:39 f5601ffc]:MiFlash 2020.3.14.0
[19:46:39 f5601ffc]:vboytest index:1
[19:46:39 f5601ffc]:idproduct: 53261 idvendor: 6353
[19:46:39 f5601ffc]:Thread id:14 Thread name:f5601ffc
[19:46:39 f5601ffc]:image path:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea
[19:46:39 f5601ffc]:env android path:"C:\Program Files\MiFlash20200314\Source\ThirdParty\Google\Android"
[19:46:39 f5601ffc]:script :\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\flash_all.bat
[19:46:39 f5601ffc]hysical Memory Usage:1699840 Byte
[19:46:39 f5601ffc]:start process id 3068 name cmd
[19:46:39 f5601ffc]:info1:$fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *umi" || echo Missmatching image and device
[19:46:39 f5601ffc]:info1roduct: umi
[19:46:39 f5601ffc]:info1:$fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *umi" || exit /B 1
[19:46:39 f5601ffc]:info1roduct: umi
[19:46:39 f5601ffc]:info1:$if exist D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\anti_version.txt (for /F "delims==" %a in (D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\anti_version.txt) do (set CURRENT_ANTI_VER=%a ) )
[19:46:39 f5601ffc]:info1:$(set CURRENT_ANTI_VER=1 )
[19:46:39 f5601ffc]:info1:$if [1] EQU [] set CURRENT_ANTI_VER=0
[19:46:39 f5601ffc]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s devicename getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
[19:46:39 f5601ffc]:info1:$(set version=1 )
[19:46:39 f5601ffc]:info1:$if [1] EQU [] set version=0
[19:46:39 f5601ffc]:info1:$set anticheck="antirollback check pass"
[19:46:39 f5601ffc]:info1:$if 1 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
[19:46:39 f5601ffc]:info1:$echo "antirollback check pass" | findstr /r /c:"pass" ||
[19:46:39 f5601ffc]:info1:"antirollback check pass"
[19:46:39 f5601ffc]:info1:$fastboot -s devicename erase boot ||
[19:46:39 f5601ffc]:info2:Erasing 'boot' OKAY [ 0.000s]
[19:46:39 f5601ffc]:info2:Finished. Total time: 0.016s
[19:46:39 f5601ffc]:info1:$fastboot -s devicename flash crclist D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\crclist.txt ||
[19:46:39 f5601ffc]:info2:Sending 'crclist' (0 KB) OKAY [ 0.016s]
[19:46:39 f5601ffc]:info2:Writing 'crclist' OKAY [ 0.007s]
[19:46:39 f5601ffc]:info2:Finished. Total time: 0.053s
[19:46:39 f5601ffc]:info1:$fastboot -s devicename flash sparsecrclist D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\sparsecrclist.txt ||
[19:46:39 f5601ffc]:info2:Sending 'sparsecrclist' (0 KB) OKAY [ 0.000s]
[19:46:39 f5601ffc]:info2:Writing 'sparsecrclist' OKAY [ 0.000s]
[19:46:39 f5601ffc]:info2:Finished. Total time: 0.016s
[19:46:39 f5601ffc]:info1:$fastboot -s devicename flash xbl_4 D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\xbl_4.elf ||
[19:46:40 f5601ffc]:info2:Sending 'xbl_4' (3350 KB) OKAY [ 0.116s]
[19:46:40 f5601ffc]:info2:Writing 'xbl_4' OKAY [ 0.134s]
[19:46:40 f5601ffc]:info2:Finished. Total time: 0.265s
[19:46:40 f5601ffc]:info1:$fastboot -s devicename flash xbl_config_4 D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\xbl_config_4.elf ||
[19:46:40 f5601ffc]:info2:Sending 'xbl_config_4' (95 KB) OKAY [ 0.010s]
[19:46:40 f5601ffc]:info2:Writing 'xbl_config_4' OKAY [ 0.005s]
[19:46:40 f5601ffc]:info2:Finished. Total time: 0.042s
[19:46:40 f5601ffc]:info1:$fastboot -s devicename flash xbl_5 D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\xbl_5.elf ||
[19:46:40 f5601ffc]:info2:Sending 'xbl_5' (3373 KB) OKAY [ 0.115s]
[19:46:40 f5601ffc]:info2:Writing 'xbl_5' OKAY [ 0.133s]
[19:46:40 f5601ffc]:info2:Finished. Total time: 0.280s
[19:46:40 f5601ffc]:info1:$fastboot -s devicename flash xbl_config_5 D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\xbl_config_5.elf ||
[19:46:40 f5601ffc]:info2:Sending 'xbl_config_5' (95 KB) OKAY [ 0.011s]
[19:46:40 f5601ffc]:info2:Writing 'xbl_config_5' OKAY [ 0.005s]
[19:46:40 f5601ffc]:info2:Finished. Total time: 0.045s
[19:46:40 f5601ffc]:info1:$fastboot -s devicename flash abl D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\abl.elf ||
[19:46:40 f5601ffc]:info2:Sending 'abl' (204 KB) OKAY [ 0.017s]
[19:46:40 f5601ffc]:info2:Writing 'abl' OKAY [ 0.009s]
[19:46:40 f5601ffc]:info2:Finished. Total time: 0.036s
[19:46:40 f5601ffc]:info1:$fastboot -s devicename flash tz D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\tz.mbn ||
[19:46:40 f5601ffc]:info2:Sending 'tz' (3228 KB) OKAY [ 0.105s]
[19:46:41 f5601ffc]:info2:Writing 'tz' OKAY [ 0.123s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.261s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash hyp D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\hyp.mbn ||
[19:46:41 f5601ffc]:info2:Sending 'hyp' (434 KB) OKAY [ 0.018s]
[19:46:41 f5601ffc]:info2:Writing 'hyp' OKAY [ 0.022s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.070s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash devcfg D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\devcfg.mbn ||
[19:46:41 f5601ffc]:info2:Sending 'devcfg' (47 KB) OKAY [ 0.010s]
[19:46:41 f5601ffc]:info2:Writing 'devcfg' OKAY [ 0.000s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.022s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash storsec D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\storsec.mbn ||
[19:46:41 f5601ffc]:info2:Sending 'storsec' (19 KB) OKAY [ 0.002s]
[19:46:41 f5601ffc]:info2:Writing 'storsec' OKAY [ 0.000s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.022s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash bluetooth D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\BTFM.bin ||
[19:46:41 f5601ffc]:info2:Sending 'bluetooth' (412 KB) OKAY [ 0.020s]
[19:46:41 f5601ffc]:info2:Writing 'bluetooth' OKAY [ 0.018s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.060s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash cmnlib D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\cmnlib.mbn ||
[19:46:41 f5601ffc]:info2:Sending 'cmnlib' (382 KB) OKAY [ 0.020s]
[19:46:41 f5601ffc]:info2:Writing 'cmnlib' OKAY [ 0.018s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.048s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash cmnlib64 D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\cmnlib64.mbn ||
[19:46:41 f5601ffc]:info2:Sending 'cmnlib64' (496 KB) OKAY [ 0.022s]
[19:46:41 f5601ffc]:info2:Writing 'cmnlib64' OKAY [ 0.020s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.060s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash modem D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\NON-HLOS.bin ||
[19:46:48 f5601ffc]:info2:Sending 'modem' (220348 KB) OKAY [ 6.662s]
[19:46:56 f5601ffc]:info2:Writing 'modem' OKAY [ 8.239s]
[19:46:56 f5601ffc]:info2:Finished. Total time: 14.929s
[19:46:56 f5601ffc]:info1:$fastboot -s devicename flash dsp D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\dspso.bin ||
[19:46:58 f5601ffc]:info2:Sending 'dsp' (65536 KB) OKAY [ 1.990s]
[19:47:01 f5601ffc]:info2:Writing 'dsp' OKAY [ 2.450s]
[19:47:01 f5601ffc]:info2:Finished. Total time: 4.469s
[19:47:01 f5601ffc]:info1:$fastboot -s devicename flash keymaster D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\km4.mbn ||
[19:47:01 f5601ffc]:info2:Sending 'keymaster' (244 KB) OKAY [ 0.012s]
[19:47:01 f5601ffc]:info2:Writing 'keymaster' OKAY [ 0.012s]
[19:47:01 f5601ffc]:info2:Finished. Total time: 0.041s
[19:47:01 f5601ffc]:info1:$fastboot -s devicename flash logo D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\logo.img ||
[19:47:01 f5601ffc]:info2:Sending 'logo' (24704 KB) OKAY [ 0.751s]
[19:47:02 f5601ffc]:info2:Writing 'logo' OKAY [ 0.924s]
[19:47:02 f5601ffc]:info2:Finished. Total time: 1.701s
[19:47:02 f5601ffc]:info1:$fastboot -s devicename flash featenabler D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\featenabler.mbn ||
[19:47:02 f5601ffc]:info2:Sending 'featenabler' (84 KB) OKAY [ 0.006s]
[19:47:02 f5601ffc]:info2:Writing 'featenabler' OKAY [ 0.002s]
[19:47:02 f5601ffc]:info2:Finished. Total time: 0.036s
[19:47:02 f5601ffc]:info1:$fastboot -s devicename flash misc D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\misc.img ||
[19:47:03 f5601ffc]:info2:Sending 'misc' (8 KB) OKAY [ 0.008s]
[19:47:03 f5601ffc]:info2:Writing 'misc' OKAY [ 0.001s]
[19:47:03 f5601ffc]:info2:Finished. Total time: 0.042s
[19:47:03 f5601ffc]:info1:$fastboot -s devicename flash aop D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\aop.mbn ||
[19:47:03 f5601ffc]:info2:Sending 'aop' (197 KB) OKAY [ 0.014s]
[19:47:03 f5601ffc]:info2:Writing 'aop' OKAY [ 0.009s]
[19:47:03 f5601ffc]:info2:Finished. Total time: 0.037s
[19:47:03 f5601ffc]:info1:$fastboot -s devicename flash qupfw D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\qupv3fw.elf ||
[19:47:03 f5601ffc]:info2:Sending 'qupfw' (52 KB) OKAY [ 0.010s]
[19:47:03 f5601ffc]:info2:Writing 'qupfw' OKAY [ 0.003s]
[19:47:03 f5601ffc]:info2:Finished. Total time: 0.028s
[19:47:03 f5601ffc]:info1:$fastboot -s devicename flash uefisecapp D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\uefi_sec.mbn ||
[19:47:03 f5601ffc]:info2:Sending 'uefisecapp' (120 KB) OKAY [ 0.009s]
[19:47:03 f5601ffc]:info2:Writing 'uefisecapp' OKAY [ 0.006s]
[19:47:03 f5601ffc]:info2:Finished. Total time: 0.026s
[19:47:03 f5601ffc]:info1:$fastboot -s devicename flash multiimgoem D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\multi_image.mbn ||
[19:47:03 f5601ffc]:info2:Sending 'multiimgoem' (32 KB) OKAY [ 0.009s]
[19:47:03 f5601ffc]:info2:Writing 'multiimgoem' OKAY [ 0.002s]
[19:47:03 f5601ffc]:info2:Finished. Total time: 0.022s
[19:47:03 f5601ffc]:info1:$fastboot -s devicename flash super D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\super.img ||
[19:47:27 f5601ffc]:info2:Sending sparse 'super' 1/8 (757789 KB) OKAY [ 22.849s]
[19:47:27 f5601ffc]:info2:Writing 'super' OKAY [ 0.001s]
[19:48:05 f5601ffc]:info2:Sending sparse 'super' 2/8 (786430 KB) OKAY [ 38.005s]
[19:48:05 f5601ffc]:info2:Writing 'super' OKAY [ 0.001s]
[19:48:48 f5601ffc]:info2:Sending sparse 'super' 3/8 (785877 KB) OKAY [ 42.735s]
[19:48:48 f5601ffc]:info2:Writing 'super' OKAY [ 0.000s]
[19:49:36 f5601ffc]:info2:Sending sparse 'super' 4/8 (784134 KB) OKAY [ 48.626s]
[19:49:36 f5601ffc]:info2:Writing 'super' OKAY [ 0.001s]
[19:50:25 f5601ffc]:info2:Sending sparse 'super' 5/8 (786140 KB) OKAY [ 48.351s]
[19:50:25 f5601ffc]:info2:Writing 'super' OKAY [ 0.001s]
[19:51:07 f5601ffc]:info2:Sending sparse 'super' 6/8 (786201 KB) OKAY [ 42.274s]
[19:51:07 f5601ffc]:info2:Writing 'super' OKAY [ 0.002s]
[19:51:49 f5601ffc]:info2:Sending sparse 'super' 7/8 (778180 KB) OKAY [ 42.125s]
[19:51:49 f5601ffc]:info2:Writing 'super' OKAY [ 0.000s]
[19:52:29 f5601ffc]:info2:Sending sparse 'super' 8/8 (544992 KB) OKAY [ 39.887s]
[19:52:29 f5601ffc]:info2:Writing 'super' OKAY [ 0.000s]
[19:52:29 f5601ffc]:info2:Finished. Total time: 326.263s
[19:52:29 f5601ffc]:info1:$fastboot -s devicename flash vbmeta D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\vbmeta.img ||
[19:53:00 f5601ffc]:info2:Sending 'vbmeta' (8 KB) FAILED (remote: 'Error: Last flash failed : CRC Error')
[19:53:00 f5601ffc]:info2:fastboot: error: Command failed
[19:53:00 f5601ffc]:info1:"Flash vbmeta error"
[19:53:00 f5601ffc]:begin FlashDone
[19:53:00 f5601ffc]:error:Sending 'vbmeta' (8 KB) FAILED (remote: 'Error: Last flash failed : CRC Error')
[19:53:00 f5601ffc]rocess exit.
[19:53:00 f5601ffc]:flashSuccess False
[19:53:00 f5601ffc]:isFactory False CheckCPUID False
[19:53:00 f5601ffc]:before:flashSuccess is False set IsUpdate:True set IsDone True
[19:53:00 f5601ffc]:after:flashSuccess is False set IsUpdate:false set IsDone true

@ elvirr:
What did I tell you above????? Do not flash any rom whwn you are using the above TWRP.3.4.0 via ADB or fastboot. You MUST flash the rom via USB OTG.
Boot to the twrp, format data (you see nothing, wait for a minute or two), boot again to recovery, connect to USB OTG with the rom on it. Install from USB OTG., clean cach and boot to system.

elvirr said:
Hi
I was running latest Xiaomi EU rom on custom recovery and unlocked bootloader. Then I downloaded latest rom from Xiaomi.eu (xiaomi.eu_multi_MI10_V12.2.2.0.RJBCNXM_v12-11.zip) and flashed it via phone updater. It restarted into custom recovery, flashed the rom and everything was running fine. I restarted the phone and then it stucked in fastboot.
I tried to enter recovery but it loads fastboot every time.
Tried to install twrp, and it was flashed but when I try to manually enter recovery it loads only fastboot.
I tried this commands:
fastboot flash recovery twrp.img
fastboot boot twrp.img, but the second one won't go through because of the error: Failed to load/authenticate boot image: Load Error.
Please help, I have so many important stuff on my phone
Click to expand...
Click to collapse
I've been having this same problem all week trying to install the Global recovery ROM. Unfortunately the only way I was able to get my phone to boot normally again was to flash the 12.0.1 fastboot ROM using the MiFlash tool

@pascha46
You can flash any region ROMs via Fastboot.
In my opinion I have never been able to get MiFlash tool to work. Much easier to just use Fastboot and flash the stock region ROM manually

hello good morning,
I have the same problem ...
it's blocked in fastboot, when connecting to the pc says unrecognized device.
help please

Same issue here. Phone is not recognised by PC, I don't what to do. Flashtool doesn't see the device. Goddamn Android 11

daleksi said:
Same issue here. Phone is not recognised by PC, I don't what to do. Flashtool doesn't see the device. Goddamn Android 11
Click to expand...
Click to collapse
Next time, stay away from things that you didn't understand 100 percent. Try this tool - very suitable for beginners: https://www.xiaomitool.com/V2/
Good luck. No backup - no mercy.

Problem described below is solved. Found out that the problem was a missing/deprecated certificate for the driver installation. Helped getting the newest version of Mi Flash and installing a stock ROM.
----
I also can't boot to anything but this fastboot screen. Tried the beginners tool suggested, but it fails at vbmeta, cf. image.
Tried a few other commands with fastboot, but in general get the following error message:
"FAILED (Write to device failed (Unknown error))" [EDIT: After a hard reboot of the phone, it was possible to write to it again via fastboot. Have an idea what to try now, downloading a ROM for fastboot. But mostly wondering if formatting is safe; might it be impossible to connect to the phone afterwards?]
Guess I should mention that the device is rooted and encrypted.
I don't care too much if I lose all data (probably already happened), but I'd very much appreciate help as to how to get a working phone again. Anyone, please? Is the way forward this usb-c stick plugged into the phone, even though I can't write recovery.img to it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

AllanStig said:
Problem described below is solved. Found out that the problem was a missing/deprecated certificate for the driver installation. Helped getting the newest version of Mi Flash and installing a stock ROM.
----
I also can't boot to anything but this fastboot screen. Tried the beginners tool suggested, but it fails at vbmeta, cf. image.
Tried a few other commands with fastboot, but in general get the following error message:
"FAILED (Write to device failed (Unknown error))" [EDIT: After a hard reboot of the phone, it was possible to write to it again via fastboot. Have an idea what to try now, downloading a ROM for fastboot. But mostly wondering if formatting is safe; might it be impossible to connect to the phone afterwards?]
Guess I should mention that the device is rooted and encrypted.
I don't care too much if I lose all data (probably already happened), but I'd very much appreciate help as to how to get a working phone again. Anyone, please? Is the way forward this usb-c stick plugged into the phone, even though I can't write recovery.img to it?
View attachment 5175947
Click to expand...
Click to collapse
I had the same problem trying to flash any stock ROM with XiaoMiTool, even using the bat File resulted in an error on vbmeta. In the end i tried to flash via console using minimal ADB and Fastboot and hacking the commands into cmd line by line worked fine

pascha46 said:
@ elvirr:
What did I tell you above????? Do not flash any rom whwn you are using the above TWRP.3.4.0 via ADB or fastboot. You MUST flash the rom via USB OTG.
Boot to the twrp, format data (you see nothing, wait for a minute or two), boot again to recovery, connect to USB OTG with the rom on it. Install from USB OTG., clean cach and boot to system.
Click to expand...
Click to collapse
you sir are a genius. Flashing with the older TWRP and using USB worked fine! Just one question: Is updating the ROM over TWRP possible without loosing all data?

elvirr said:
Hi
I was running latest Xiaomi EU rom on custom recovery and unlocked bootloader. Then I downloaded latest rom from Xiaomi.eu (xiaomi.eu_multi_MI10_V12.2.2.0.RJBCNXM_v12-11.zip) and flashed it via phone updater. It restarted into custom recovery, flashed the rom and everything was running fine. I restarted the phone and then it stucked in fastboot.
I tried to enter recovery but it loads fastboot every time.
Tried to install twrp, and it was flashed but when I try to manually enter recovery it loads only fastboot.
I tried this commands:
fastboot flash recovery twrp.img
fastboot boot twrp.img, but the second one won't go through because of the error: Failed to load/authenticate boot image: Load Error.
Please help, I have so many important stuff on my phone
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img

for those still not booted into TWRP

AllanStig said:
Problem described below is solved. Found out that the problem was a missing/deprecated certificate for the driver installation. Helped getting the newest version of Mi Flash and installing a stock ROM.
----
I also can't boot to anything but this fastboot screen. Tried the beginners tool suggested, but it fails at vbmeta, cf. image.
Tried a few other commands with fastboot, but in general get the following error message:
"FAILED (Write to device failed (Unknown error))" [EDIT: After a hard reboot of the phone, it was possible to write to it again via fastboot. Have an idea what to try now, downloading a ROM for fastboot. But mostly wondering if formatting is safe; might it be impossible to connect to the phone afterwards?]
Guess I should mention that the device is rooted and encrypted.
I don't care too much if I lose all data (probably already happened), but I'd very much appreciate help as to how to get a working phone again. Anyone, please? Is the way forward this usb-c stick plugged into the phone, even though I can't write recovery.img to it?
View attachment 5175947
Click to expand...
Click to collapse
Hi there
I have the same error,how did you manage to resolve and what certificate was missing from the driver.If you can help in this .Thanks

jjgvv said:
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
Click to expand...
Click to collapse
I tried this command but again same error
error message:
"FAILED (Write to device failed (Unknown error )
any help appreciated

your emmc is fried

maybe use EDL flash method

Armor x5 Android 10_Q Mt6765 aka Mt6762 ROOT AT LAST!

This 'tutorial' is a quicky for those yet to figure this fone out.
Well it took a bit time for sure, but this is how it went...
No matter what recovery or magisk I tried, nothing worked, all ulefone images with twrp were 64mb in size, where-as mine was 32mb. Betting the 64mb is a/b partioned like the old ambit 250 modems, where half the non-vol was the first boot, the second half a clone of the first half.
No file for the mt6765 worked. In other words, no twrp. instant bootloop every time.
But then I found the ulefone note9 mt6762 recovery, flashed it, booted into recovery, and had root!
Until I rebooted at least. There was no access to the actual fone system however, for in recovery, system, or / has not been mounted, and if it was, it cold not be written to..
Then I had an idea. I tested the root.img from android kitchen by flashing just that direct to the recovery of the fone, and it not only stuck, I could switch off fone, reboot, and what I call an overlaid file system with root presented itself, and before I knew it I had a fake root that worked.
The problem with this fone is that it actually uses mt6762 for booting, booting into mt6765 style, vice versa does not work. The note9 is a 6762 chipset. 32mb in size.
The root.img from android kitchen, flashed to recovery gives the head start, having magisk installed, but sadley, twrp did not show in recovery using the note9 recovery that has a working twrp, and the android kitchen root.img shows no twrp, being magisk'd!
Unlocked bootloader required.
Boot into fastboot.
fastboot flash vbmeta vblankmeta.img
fastboot flash recovery root.img
boot fone, install magisk manager, superuser and busybox apk's, then root checker pro, test and see, by rebooting, it should keep root if you set su to boot via busybox, AND superuser.
Now if someone wants to make this for this actual fone, with the correct file versions for this fone, I'll post my latest stock recovery, along with the files I used. All files as far as I know came from here, I have done nothing to them.
The actual Files are: Armor x5 Android 10_Q root.zip is actually a 7z file renamed to zip to upload here, i use 7z, and dont install winzip, and the password for both is Re-Kr8, used in order to prevent google tampering.
The zip contains vblankmeta.img and root.img taken from android kitchen, hope they dont mind auld folks like me helping this way...
The origional is recovery from unrooted fone taken from stock firmware, android 10 Q for ulefone armor x5.
Have a nice day.

And I found this somewhere so will leave it here for those who want true root on the ulefone device, I'm too sore with slow paralysis to keep working at this...
Android Q system_app writes persist.sys by default. The system property SEliux permission
When debugging Settings.apk by myself.
It was discovered that as a platform system signature application, there was no permission to sign a custom persist.st_nfc_debug system property.
It can be modified to the name beginning with persist.sys.
Although in the end, I said:
persist.st_nfc_debug ubject_r:system_prop:s0
Get it done.
why is that?
This step by step tracks SeLinux permission protection in Android.
The same is because the system authorizes persist.sys. by default and classifies it into system_prop.
alps/system/sepolicy/private/property_contexts
persist.log.tag ubject_r:log_tag_prop:s0
persist.mmc. ubject_r:mmc_prop:s0
persist.netd.stable_secret ubject_r:netd_stable_secret_prop:s0
persist.sys. ubject_r:system_prop:s0
persist.sys.safemode ubject_r:safemode_prop:s0
persist.sys.fflag.override.settings_dynamic_system ubject_r:dynamic_system_prop:s0
So where is system_prop defined?
It belongs to property_type and core_property_type.
alps/system/sepolicy/public/property.te
79 type shell_prop, property_type, core_property_type;
80 type system_boot_reason_prop, property_type;
81 type system_prop, property_type, core_property_type;
82 type system_radio_prop, property_type, core_property_type;
83 type system_trace_prop, property_type;
84 type test_boot_reason_prop, property_type;
Authorization, the last line below, set_prop(system_app, system_prop).
alps/system/sepolicy/private/system_app.te
7 typeattribute system_app coredomain;
8
9 app_domain(system_app)
10 net_domain(system_app)
11 binder_service(system_app)
12
13 # android.ui and system.ui
14 allow system_app rootfs:dir getattr;
15
16 # Read and write /data/data subdirectory.
17 allow system_app system_app_data_file:dir create_dir_perms;
18 allow system_app system_app_data_file:{ file lnk_file } create_file_perms;
33 # Write to properties
34 set_prop(system_app, bluetooth_a2dp_offload_prop)
35 set_prop(system_app, bluetooth_audio_hal_prop)
36 set_prop(system_app, bluetooth_prop)
37 set_prop(system_app, debug_prop)
38 set_prop(system_app, system_prop)
So where is this set_prop sacred?
alps/system/sepolicy/public/te_macros
305 #####################################
306 # set_prop(sourcedomain, targetproperty)
307 # Allows source domain to set the
308 # targetproperty.
309 #
310 define(`set_prop', `
311 unix_socket_connect($1, property, init)
312 allow $1 $2roperty_service set;
313 get_prop($1, $2)
314 ')
315
316 #####################################
317 # get_prop(sourcedomain, targetproperty)
318 # Allows source domain to read the
319 # targetproperty.
320 #
321 define(`get_prop', `
322 allow $1 $2:file { getattr open read map };
323 ')
It is a general method of declaration.
So according to this meaning, you can piece together the following permission statement:
allow system_app system_proproperty_service set;
Use the real phone to enter the mobile phone directory to find and verify is the king:
5032E:/system/etc/selinux # grep -rni "allow system_app system_prop".
./Plat_sepolicy.cil:19108allow system_app system_prop (property_service (set)))
./plat_sepolicy.cil:19109allow system_app system_prop ( file (read getattr map open)))
5032E:/system/etc/selinux #
summary:
Just because the Android compilation system has assigned relevant permissions by default, it can be used directly, and custom ones require additional authorization.
Additional tips:
Before adding the compilation in the alps project, the .te file will be compiled and imported into the cil file.
Android Q currently has cil files:
./vendor/etc/selinux/vendor_sepolicy.cil
./vendor/etc/selinux/plat_pub_versioned.cil
./system/etc/selinux/mapping/27.0.cil
./system/etc/selinux/mapping/29.0.cil
./system/etc/selinux/mapping/26.0.cil
./system/etc/selinux/mapping/28.0.cil
./system/etc/selinux/plat_sepolicy.cil
The property_contexts file will be imported into the plat_property_contexts file.
./system/etc/selinux/plat_property_contexts:61ersist.sys. ubject_r:system_prop:s0
./system/etc/selinux/plat_property_contexts:62ersist.sys.safemode ubject_r:safemode_prop:s0
./system/etc/selinux/plat_property_contexts:63ersist.sys.theme ubject_r:theme_prop:s0
./system/etc/selinux/plat_property_contexts:64ersist.sys.fflag.override.settings_dynamic_system ubject_r:dynamic_system_prop:s0
./system/etc/selinux/plat_property_contexts:66ersist.sys.audit_safemode ubject_r:safemode_prop:s0
./system/etc/selinux/plat_property_contexts:81ersist.sys.boot.reason ubject_r:last_boot_reason_prop:s0
./system/etc/selinux/plat_property_contexts:346ersist.sys.dalvik.vm.lib.2 ubject_r:exported2_system_prop:s0 exact string
./system/etc/selinux/plat_property_contexts:347ersist.sys.media.avsync ubject_r:exported2_system_prop:s0 exact bool
And all the files ending with _contexts in Android Q are:
./vendor/etc/selinux/vndservice_contexts
./vendor/etc/selinux/vendor_file_contexts
./vendor/etc/selinux/vendor_hwservice_contexts
./vendor/etc/selinux/vendor_property_contexts
./vendor/etc/selinux/vendor_seapp_contexts
./system/etc/selinux/plat_file_contexts
./system/etc/selinux/plat_service_contexts
./system/etc/selinux/plat_hwservice_contexts
./system/etc/selinux/plat_seapp_contexts
./system/etc/selinux/plat_property_contexts
./sys/fs/selinux/initial_contexts
The service corresponding to the NFC module is in ./vendor/etc/selinux/vendor_file_contexts:
5032E:/ # cat ./vendor/etc/selinux/vendor_file_contexts | grep nfc
/(vendor|system/vendor)/bin/hw/android\.hardware\[email protected]\.1-service ubject_r:hal_nfc_default_exec:s0
/(vendor|system/vendor)/bin/hw/android\.hardware\[email protected]\.2-service ubject_r:hal_nfc_default_exec:s0
/(vendor|system/vendor)/bin/hw/android\.hardware\[email protected]\.0-service ubject_r:hal_nfc_default_exec:s0
/(system\/vendor|vendor)/bin/hw/android\.hardware\[email protected]\.1-service-st ubject_r:hal_nfc_default_exec:s0
/data/nfc_socket(/.*)? ubject_r:nfc_socket:s0
/data/vendor/nfc_socket(/.*)? ubject_r:vendor_nfc_socket:s0
/dev/st21nfc ubject_r:st21nfc_device:s0
5032E:/ #

My journey continues taking the untrodden path's...
I have found how to write to /
But I dont know how it's working.
So please read, and help me root this fone properly so I can keep what I found permanent in my fone.
I know some of you will 'see' with eye's to hear...
I need a twrp for my fone.
So I finally managed to get a working boot image created for my fone, with magisk, this is how I did it:
fastboot flashing unlock_critical
pressed + vol
fastboot flash vbmeta vblankmeta.img
fastboot flash recovery note9recovery.img <-for mt6762
fastboot reboot
As soon as the screen turns off. I have to hold + vol to NOT show recovery/fastboot/normal, choose recovery, but by taking this step, the recovery with magisk is already wiped somehow, depends on the version of android 10-Q, Pro, Latest, boots are slightly different.
The Pro variant is the best to work with.
So I rinse and repeat and flash the note9.img, boot into recovery, keeping + vol pressed until AFTER the point where the stock android recovery menu would kick in.
This boots the fone using the note9.img from recovery!
Voila, so I know I'm in, but I know a wonderfull trick most devs dont know.
This fone is unlocked from shop. It is system-as-root, meaning, root is actually pointless!
To prove it, I'll use root commands WITHOUT magisk, or twrp, or su, by giving this example:
adb shell echo "persist.service.adb.enable=1" >> default.prop
'Read only' bull**** pops up, but when doing:
adb -s *************** shell echo "persist.service.adb.enable=1" >> default.prop (* = your device serial number)
Command completes! WITHOUT MOUNTING ANY SYSTEM!
HOwever, attempting to write with magisk, su etc wont ever work, yeah, in an overlay file system, they will, but what of this? Like I've said in other posts, it's all a mirror image, or in todays speak, overlaid, I wrote of this on surfboard hacker, and a few other sites back in docsis 2 days as a security measure to stop us
uncapping lol...
So I initially do:
adb -s *************** shell echo "persist.service.adb.enable=1" >> default.prop
adb -s *************** shell echo "persist.service.debuggable=1" >> default.prop
adb -s *************** shell echo "persist.sys.usb.config=mtp,adb" >> default.prop
adb -s *************** shell echo "persist.service.adb.enable=1" >> /system/build.prop
adb -s *************** shell echo "persist.service.debuggable=1" >> /system/build.prop
adb -s *************** shell echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
adb -s *************** shell settings put secure install_non_market_apps 1
adb -s *************** shell settings put global adb_enabled 1
adb -s *************** shell settings put global setup_wizard_has_run 1
adb -s *************** shell settings put secure user_setup_complete 1
adb -s *************** shell settings put global activity_starts_logging_enabled 1
adb -s *************** shell settings put global development_settings_enabled 1
adb -s *************** shell settings put secure location_providers_allowed +gps,network
Works wonders huh?
Nah... of course my above commands work, lots of research...
I tried systemrw_1.32 to use any apps etc wanting to write to system, but I noticed while using magisk, some MMblock29 was read only, whereas systemrw_1.32 locked another, making me believe this is actually a pie script, because after testing this, when I rebooted, system was dm-1, not the dm-3 I normally see, and when attempting to system write, No joy, so these two are clashing.
But here's what to watch for: How TO write system is at this point:
I flashed the first mentioned files. Clean slate.
I boot the fone PAST recovery as mentioned, dont go INTO recovery, go PASSED it so fone boots from recovery without reflashing itself with stock, fone starts with a magisk icon on the desktop. kool.
adb shell
su
mount -o remount,rw /
Voila!
Now reboot...
All gone...
Rinse n repeat. Now how to keep this read write access?
1: Magisk in the bootloader will not work will not enable "mount -o remount,rw / " because it's symlinked it's own overlay system.
2: Magisk in the recovery is great to get magisk canary to do your bootloader for you, but the bootloader root will NOT write "mount -o remount,rw / " - only the note9 recovery allows me to "mount -o remount,rw / "
3: The note9 recovery is doing something no other magiskd bootloader or twrp'd recovery can!
4: If you get this, you get me.
Notice none of this is actually about what I need the most?
A twrp recovery 32mb in size, mt6762 or mt6765
Not a magisked boot.img thats supposed to be flashed to recovery..???
Oh and magisk has not done my fone yet, I need to load the note9 recovery just to get what you just read.
When I try magisk on a clean slate, it does nothing.

Sussed it... when the fone booted, I had the note9 magisk appear dulled out on my screen.
adb shell
$
su
sits and waits...
update magisk using canary 23 apk, but do nothing else.
adb shell
$
su
mount -o remount,rw /
do whatever.
Let magisk do it's stuff n reboot
mount -o remount,rw / is now impossible.
Get it?
Recovery can access / with rw access! <- VOILA!
Edit:
Oh, and flashing magisk to recovery is causing the bootloops, as is the confusion over why we'd flash a boot to recovery or recovery to boot, me I try anything, and I bet the note9 is the key to the read only fs, in that it still contains everything in 'A' bootloader, not several...

I propose a new root tool, called ****root.
Input your serial, in your adb -s *************** then the rooting commands no?
the app will run a script to do what I wrote above I can do.
Only with root commands.
Get to it.

Oh, please forgive my serial numbers, but here's the logs:
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash vbmeta vblankmeta.
img
Sending 'vbmeta' (4 KB) OKAY [ 0.022s]
Writing 'vbmeta' OKAY [ 0.008s]
Finished. Total time: 0.053s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash recovery TWRP-3.4.
0-10-full.img
Sending 'recovery' (32768 KB) OKAY [ 0.807s]
Writing 'recovery' OKAY [ 0.517s]
Finished. Total time: 1.350s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot boot recovery
fastboot: error: cannot load 'recovery': No such file or directory
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot boot TWRP-3.4.0-10-full.
img
Sending 'boot.img' (32768 KB) OKAY [ 0.799s]
Booting OKAY [ 0.213s]
Finished. Total time: 1.073s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adb shell
adb.exe: no devices/emulators found
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash vbmeta vblankmeta.
img
Sending 'vbmeta' (4 KB) OKAY [ 0.022s]
Writing 'vbmeta' OKAY [ 0.008s]
Finished. Total time: 0.058s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash boot MyBoot0.img
Sending 'boot' (32768 KB) OKAY [ 0.805s]
Writing 'boot' OKAY [ 0.513s]
Finished. Total time: 1.347s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash recovery MyRecover
y0.img
Sending 'recovery' (32768 KB) OKAY [ 0.803s]
Writing 'recovery' OKAY [ 0.519s]
Finished. Total time: 1.351s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot reboot
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.008s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash boot MyBoot0.img
< waiting for any device >
^C
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adb kill-server
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot devices
3082SH1001004262 fastboot
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash super super.img
fastboot: error: cannot load 'super.img': No such file or directory
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash super super.bin
fastboot: error: cannot load 'super.bin': No such file or directory
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash super super.bin
Sending sparse 'super' 1/23 (131068 KB) OKAY [ 4.468s]
Writing 'super' OKAY [ 2.133s]
Sending sparse 'super' 2/23 (130832 KB) OKAY [ 4.300s]
Writing 'super' OKAY [ 2.132s]
Sending sparse 'super' 3/23 (130841 KB) OKAY [ 4.602s]
Writing 'super' OKAY [ 2.251s]
Sending sparse 'super' 4/23 (130572 KB) OKAY [ 4.410s]
Writing 'super' OKAY [ 2.184s]
Sending sparse 'super' 5/23 (131060 KB) OKAY [ 4.109s]
Writing 'super' OKAY [ 2.068s]
Sending sparse 'super' 6/23 (130700 KB) OKAY [ 4.157s]
Writing 'super' OKAY [ 2.053s]
Sending sparse 'super' 7/23 (130881 KB) OKAY [ 4.182s]
Writing 'super' OKAY [ 2.248s]
Sending sparse 'super' 8/23 (130489 KB) OKAY [ 3.941s]
Writing 'super' OKAY [ 2.277s]
Sending sparse 'super' 9/23 (129252 KB) OKAY [ 4.187s]
Writing 'super' OKAY [ 2.855s]
Sending sparse 'super' 10/23 (128853 KB) OKAY [ 4.071s]
Writing 'super' OKAY [ 3.008s]
Sending sparse 'super' 11/23 (131020 KB) OKAY [ 4.032s]
Writing 'super' OKAY [ 2.070s]
Sending sparse 'super' 12/23 (131068 KB) OKAY [ 4.108s]
Writing 'super' OKAY [ 2.069s]
Sending sparse 'super' 13/23 (131068 KB) OKAY [ 4.073s]
Writing 'super' OKAY [ 2.080s]
Sending sparse 'super' 14/23 (131068 KB) OKAY [ 4.066s]
Writing 'super' OKAY [ 2.053s]
Sending sparse 'super' 15/23 (130348 KB) OKAY [ 4.274s]
Writing 'super' OKAY [ 4.725s]
Sending sparse 'super' 16/23 (131032 KB) OKAY [ 4.043s]
Writing 'super' OKAY [ 2.085s]
Sending sparse 'super' 17/23 (130560 KB) OKAY [ 4.186s]
Writing 'super' OKAY [ 2.126s]
Sending sparse 'super' 18/23 (130900 KB) OKAY [ 4.065s]
Writing 'super' OKAY [ 2.107s]
Sending sparse 'super' 19/23 (130493 KB) OKAY [ 4.069s]
Writing 'super' OKAY [ 2.340s]
Sending sparse 'super' 20/23 (121428 KB) OKAY [ 3.900s]
Writing 'super' OKAY [ 1.933s]
Sending sparse 'super' 21/23 (131068 KB) OKAY [ 4.082s]
Writing 'super' OKAY [ 2.164s]
Sending sparse 'super' 22/23 (131068 KB) OKAY [ 4.102s]
Writing 'super' OKAY [ 2.109s]
Sending sparse 'super' 23/23 (40268 KB) OKAY [ 1.320s]
Writing 'super' OKAY [ 0.649s]
Finished. Total time: 145.206s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.005s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash vbmeta vblankmeta.
img
< waiting for any device >
^C
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adb kill-server
cannot connect to daemon at tcp:5037: cannot connect to 127.0.0.1:5037: No conne
ction could be made because the target machine actively refused it. (10061)
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash boot TWRP-3.4.0-10
-full.img
Sending 'boot' (32768 KB) OKAY [ 0.795s]
Writing 'boot' OKAY [ 0.517s]
Finished. Total time: 1.336s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot reboot TWRP-3.4.0-10-ful
l.img
fastboot: usage: unknown reboot target TWRP-3.4.0-10-full.img
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot boot TWRP-3.4.0-10-full.
img
Sending 'boot.img' (32768 KB) OKAY [ 0.784s]
Booting OKAY [ 0.067s]
Finished. Total time: 0.904s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash vbmeta vblankmeta.
img
Sending 'vbmeta' (4 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.022s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash boot boot.img
Sending 'boot' (32768 KB) OKAY [ 0.791s]
Writing 'boot' OKAY [ 0.514s]
Finished. Total time: 1.321s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash recovery TWRP-3.4.
0-10-full.img
Sending 'recovery' (32768 KB) OKAY [ 0.795s]
Writing 'recovery' OKAY [ 0.510s]
Finished. Total time: 1.322s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
Armor_X5_Q:/ $ su
/system/bin/sh: su: inaccessible or not found
3082SH1001004262 shell echo "persist.service.adb.enable=1" >> default.prop <
/system/bin/sh: can't create default.prop: Read-only file system
082SH1001004262 shell echo "persist.service.debuggable=1" >> default.prop <
/system/bin/sh: can't create default.prop: Read-only file system
082SH1001004262 shell echo "persist.sys.usb.config=mtp,adb" >> default.prop <
/system/bin/sh: can't create default.prop: Read-only file system
o "persist.service.adb.enable=1" >> /system/build.prop <
/system/bin/sh: can't create /system/build.prop: Read-only file system
o "persist.service.debuggable=1" >> /system/build.prop <
001004/system/bin/sh: can't create /system/build.prop: Read-only file system
262 s1|Armor_X5_Q:/ $ adb -s 3082SH1001004262 shell echo "persist.sys.usb.config
o "persist.sys.usb.config=mtp,adb" >> /system/build.prop <
/system/bin/sh: can't create /system/build.prop: Read-only file system
1|Armor_X5_Q:/ $
1|Armor_X5_Q:/ $
082SH1001004262 shell settings put secure install_non_market_apps 1 <
adb -s 3082SH1001004262 shell settings put global setup_wiz/system/bin/sh: adb:
inaccessible or not found
ard_has_run 1
adb -s 3082SH1001004262 shell settings put secure user_setup_complete 1
adb -s 3082SH10010127|Armor_X5_Q:/ $ adb -s 3082SH1001004262 shell settings put
3082SH1001004262 shell settings put global adb_enabled 1 <
s/system/bin/sh: adb: inaccessible or not found
3082SH1001004262 shell settings put global setup_wizard_has_run 1 <
rt/system/bin/sh: adb: inaccessible or not found
s_logg127|Armor_X5_Q:/ $ adb -s 3082SH1001004262 shell settings put secure user_
3082SH1001004262 shell settings put secure user_setup_complete 1 <
/system/bin/sh: adb: inaccessible or not found
ed 1
adb127|Armor_X5_Q:/ $ adb -s 3082SH1001004262 shell settings put global activity
3082SH1001004262 shell settings put global activity_starts_logging_enabled 1 <
-s 3082SH1001004262 shell settings put sec/system/bin/sh: adb: inaccessible or n
ot found
ure location_providers_allowed +gps,network127|Armor_X5_Q:/ $ adb -s 3082SH10010
3082SH1001004262 shell settings put global development_settings_enabled 1 <
/system/bin/sh: adb: inaccessible or not found
ettings put secure location_providers_allowed +gps,network <
/system/bin/sh: adb: inaccessible or not found
127|Armor_X5_Q:/ $ exit
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adb reboot bootloader
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash vbmeta vblankmeta.
img
Sending 'vbmeta' (4 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.026s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash boot MyBoot0.img
Sending 'boot' (32768 KB) OKAY [ 0.794s]
Writing 'boot' OKAY [ 0.510s]
Finished. Total time: 1.320s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot flash recovery MyRecover
y0.img
Sending 'recovery' (32768 KB) OKAY [ 0.794s]
Writing 'recovery' OKAY [ 0.508s]
Finished. Total time: 1.319s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.007s
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adadb shell
'adadb' is not recognized as an internal or external command,
operable program or batch file.
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adb shell
Armor_X5_Q:/ $ su
^C
130|Armor_X5_Q:/ $ mount -o remount,rw /
mount: '/dev/block/dm-1' not user mountable in fstab
1|Armor_X5_Q:/ $ exit
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adb -s 3082SH1001004262 shell ech
o "persist.service.adb.enable=1" >> default.prop
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adb -s 3082SH1001004262 shell ech
o "persist.service.debuggable=1" >> default.prop
adb -s 3082SH1001004262 shell echo "persist.sys.usb.config=mtp,adb" >> default.p
rop
adb -s 3082SH1001004262 shell echo "persist.service.adb.enable=1" >> /system/bui
ld.prop
adb -s 3082SH1001004262 shell echo "persist.service.debuggable=1" >> /system/bui
ld.prop
adb -s 3082SH1001004262 shell echo "persist.sys.usb.config=mtp,adb" >> /system/b
uild.prop
adb -s 3082SH1001004262 shell settings put secure install_non_market_apps 1
adb -s 3082SH1001004262 shell settings put global adb_enabled 1
adb -s 3082SH1001004262 shell settings put global setup_wizard_has_run 1
adb -s 3082SH1001004262 shell settings put secure user_setup_complete 1
adb -s 3082SH1001004262 shell settings put global activity_starts_logging_enable
d 1
adb -s 3082SH1001004262 shell settings put global development_settings_enabled 1
adb -s 3082SH1001004262 shell settings put secure location_providers_allowed +gp
s,network
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adb install MagiskCanary23.0.apk
Performing Streamed Install
Success
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>for x in / /product /vendor; do m
ount -o remount,rw $x; echo "it works! @ $x">$x/test.txt; cat $x/test.txt; rm $x
/test.txt; done
x was unexpected at this time.
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>adb shell
Armor_X5_Q:/ $ su
"it works! @ $x">$x/test.txt; cat $x/test.txt; rm $x/test.txt; done <
'/dev/block/dm-1' is read-only
/system/bin/sh: can't create //test.txt: Read-only file system
cat: //test.txt: No such file or directory
rm: //test.txt: No such file or directory
'/dev/block/dm-0' is read-only
/system/bin/sh: can't create /product/test.txt: Read-only file system
cat: /product/test.txt: No such file or directory
rm: /product/test.txt: No such file or directory
'/dev/block/dm-2' is read-only
/system/bin/sh: can't create /vendor/test.txt: Read-only file system
cat: /vendor/test.txt: No such file or directory
rm: /vendor/test.txt: No such file or directory
1|Armor_X5_Q:/ #
1|Armor_X5_Q:/ # mount -o remount,rw /
'/dev/block/dm-1' is read-only
Armor_X5_Q:/ #
D:\2022 x86\Adb\platform-tools_r31.0.1-windows>

Notice the commands being accepted BEFORE I updated magisk, then what happens?
mount -o remount,rw /
mount: '/dev/block/dm-1' not user mountable in fstab
In effect I need the note9 fstab to enable rw to /
!!!

One last thing I forgot to mention, without twrp, forget twrp.
I made a proper boot image for this fone, that also works when booting it from recovery, when booting from recovery, if in select recovery menu, continuing to press + VOL button, while choosing recovery lol...
And the boot image works with stock recovery!
Sadley, no twrp flashing
So how to get the twrp flashables flashable again?

The above MyBoot.img gives magisked root access flashed to boot.
fastboot flash vbmeta vblankmeta.img
fastboot flash boot MyBoot1.img
fastboot reboot
As for
mount -o remount,rw /
I gave y'all the answer.

Pachacouti said:
One last thing I forgot to mention, without twrp, forget twrp.
I made a proper boot image for this fone, that also works when booting it from recovery, when booting from recovery, if in select recovery menu, continuing to press + VOL button, while choosing recovery lol...
And the boot image works with stock recovery!
Sadley, no twrp flashing
So how to get the twrp flashables flashable again?
Click to expand...
Click to collapse
Sorry for the doubt but is the TWRP Ulefone Note 9 you wrote from this thread?https://forum.xda-developers.com/t/twrp-3-4-0-twrp-for-ulefone-note-9p-helio-p22-mt6762-5.4171433/
You PORTed TWRP img or only flash that img file directly in your device?
If you want I'll compile the TWRP 3.5.2_10 to you. Only send me stock recovery.img & super.img same version from your device.

I'll post the ULEFONE note9.img I used to gain access. The thing is, when I use this, system is writable, but obviously I update magisk, and while rebooting after doing the 'live install' of magisk (works fine to patch a boot that fails... )
My process is this, I can patch an origional boot with magisk after flashing note9 to recovery,
I can then flash the patched boot and it works when flashed to boot, and can use origional recovery, but cant flash magisk'd boot from origional un rooted fone, patched by magisk, so the note9 was my 'backdoor' so to speak...
and the systems all over the place lol.. dynamic is a pain, cant even find my sdcard and kali nethunter magisk modules need zips not git lol...
The note9recovery has something to watch for.. using clean slate, when booting the note9recovery, as fone goes into loading (past recovery) and just before fone goes into gui,
when doing "mount -o remount,rw / " system is actually writable, but cuts off adb when gui gives access!
Magisk somehow wrecks the actual mount -o remount,rw / I have when I first boot, afterwards saying dm-1 or 3 is read only.
Anyway, I'v posted my stock boot and recovery too, if I can see twrp in recovery, I'd be delighted, I lost the plot with all this where's my f'n sdcard, damn dynamic partitioning'!
Oh, and I have a problem, 128gig sdcard, fone says not enough space!
MyBoot1.img posted above is the clean slate magisk'd origional boot WITHOUT twrp, and I can use this to flash to recovery afterwards, in order to boot recovery, but have no twrp... so useless really as recovery, so I flash boot MyBoot1.img just to get a magisk to test lol...
Thanks for your time

lopestom said:
Sorry for the doubt but is the TWRP Ulefone Note 9 you wrote from this thread?https://forum.xda-developers.com/t/twrp-3-4-0-twrp-for-ulefone-note-9p-helio-p22-mt6762-5.4171433/
You PORTed TWRP img or only flash that img file directly in your device?
If you want I'll compile the TWRP 3.5.2_10 to you. Only send me stock recovery.img & super.img same version from your device.
Click to expand...
Click to collapse
Yes it was this I flashed to recovery, it says mt6762, and this was the key, because up until I flashed this, I was flashing mt6765 as per fones claims it is, and getting nowhere, i'm a only...

Soz, posting superimage once zipped...
I may get cut off by my isp, so if its easier for you my firmware is:
P2N2V23A.GQU.Ulefone.EEA.HB.HJ.S8AMABHUYB.0509.V3.01
In the meantime, I noticed when testing twrp ports, a green line flashed just before I get black screen where twrp WOULD show, adb/su works, but no twrp flashing commands, and it crossed my mind I've seen this with the firestick lol, where firesticks were being overlaid with a screen blocking twrp..? No?

Pachacouti said:
Yes it was this I flashed to recovery, it says mt6762, and this was the key, because up until I flashed this, I was flashing mt6765 as per fones claims it is, and getting nowhere, i'm a only...
Click to expand...
Click to collapse
Keep calm and let me time to do correct TWRP to you test after. Time now.

Thank you...
I think uppin the super mite not go down too well with the ee unlimited broadband business class lol, isp, so if I disappear for a while lol...
Ps, origional super.7z.001 was renamed to zip for my ease

Pachacouti said:
Thank you...
I think uppin the super mite not go down too well with the ee unlimited broadband business class lol, isp, so if I disappear for a while lol...
Ps, origional super.7z.001 was renamed to zip for my ease
Click to expand...
Click to collapse
Downloaded recovery.img & super.zip files.
Now I'm creating file test. Maybe 2h after this message.
SYL
Update: Try install recovery.img (TWRP) and if not good so install vbmeta modified.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recovery.img
cmd command:
Code:
fastboot reboot-recovery
Let me know about.

Super! No rush, it's pickled my head enough as it is lol, reading time..

Am impressed... I see twrp in recovery at last.. you are a god send for all those armor x5 punters with the 'a' only partition, next time I see you in the street, i'll buy you a pint, but until then a lucky find will seek you out, respect!!
You should post this as a working twrp, since it's not my work, as twrp was what I actually needed to get stuff done, well appreciated, I'll away test it now

Pachacouti said:
Am impressed... I see twrp in recovery at last.. you are a god send for all those armor x5 punters with the 'a' only partition, next time I see you in the street, i'll buy you a pint, but until then a lucky find will seek you out, respect!!
You should post this as a working twrp, since it's not my work, as twrp was what I actually needed to get stuff done, well appreciated, I'll away test it now
Click to expand...
Click to collapse
Thanks. Not need more than respect.
I just chose you for the attitude of sharing information and the fact that you needed help to progress. Courage is for the few.
I prefer that you share the TWRP file and instructions yourself. So fastboot/fastbootD; encryption and decryption; installation of zips; backup and restore; internal and external storage; anything else is working??
Yes: Enjoy! No: let me know.

lopestom said:
Thanks. Not need more than respect.
I just chose you for the attitude of sharing information and the fact that you needed help to progress. Courage is for the few.
I prefer that you share the TWRP file and instructions yourself. So fastboot/fastbootD; encryption and decryption; installation of zips; backup and restore; internal and external storage; anything else is working??
Yes: Enjoy! No: let me know.
Click to expand...
Click to collapse
Hmm, I learn sumat new every day, thank god aquarius is here lol, anyway, so far, I'm still at some pernikity when it comes to writing system, dm-1 or dm-3 locked, but from what I see and have tested so far, all possibilities using fone before it boot's into gui, system and mnt points work, , my sdcard is very visible at last, and writable, using stock the crappy google file manager would not let me write to sdcard, so you've solved so many headache's in one swoop. I'll write a final tut to show my alternative route's lol, thanks again
Armor x5 Android 10_Q Mt6765 aka Mt6762 ROOT AT LAST!
This 'tutorial' is a quicky for those yet to figure this fone out. Well it took a bit time for sure, but this is how it went... No matter what recovery or magisk I tried, nothing worked, all ulefone images with twrp were 64mb in size, where-as...
forum.xda-developers.com

Question Unbrick the realme GT 2 Pro from hard brick (black screen)

Hello.
I tried to completely update the Taiwanese firmware.
Basically I flashed all the images taken from the OTA to my phone using fastboot.
The OTA is from here: https://forum.xda-developers.com/t/global-eu-collection-of-firmware-files.4478153/
As a result i got hard brick (black screen). Device doesn't respond to presses, nothing happens. The computer (Windows 11) doesn't see the device.
I performed the following steps:
Code:
adb shell getprop ro.product.name
RMX3301
adb shell getprop ro.build.version.ota
RMX3301_11.C.16_1160_202303162143
adb shell getprop ro.build.version.realmeui
v4.0
adb shell getprop ro.build.oplus_nv_id
00011010
Download OTA:
Code:
E:\Programs\Python\Python39\python.exe .\realme_ota\main.py RMX3301 RMX3301_11.C.16_1160_202303162143 4 00011010
PS D:\0my\phone\realme gt 2 pro\tools\realme-ota> E:\Programs\Python\Python39\python.exe .\realme_ota\main.py RMX3301 RMX3301_11.C.16_1160_202303162143 4 00011010
[2023-04-18 17:28:19.988575] I: Load payload for RMX3301 (RealmeUI V4)
[2023-04-18 17:28:19.988575] I: Wait for the endpoint to reply
PS D:\0my\phone\realme gt 2 pro\tools\realme-ota> [2023-04-18 17:28:21.363576] I: Load payload for RMX3301 (RealmeUI V4)
[2023-04-18 17:28:21.363576] I: Wait for the endpoint to reply
[2023-04-18 17:28:22.285462] I: All good
[2023-04-18 17:28:22.285462] I: Let's rock
[2023-04-18 17:28:22.285462] I: Party time
{
"aid": "RMX3301NV1A_11.C",
"androidVersion": "Android 13",
"colorOSVersion": "ColorOS 13.0",
"componentAssembleType": true,
"components": [
{
"componentId": "my_manifest_RMX3301_11.C.16_1160_202303162143.1A.6f9e3487",
"componentName": "my_manifest",
"componentPackets": {
"id": "foreign_my_manifest_RMX3301_11.C.16_1160_202303162143.1A.6f9e3487_1_65790f8f58d286c8d65dff0ada40aee7",
"manualUrl": "https://gauss-componentotacostmanual-sg.allawnofs.com/remove-b1b7f6f4dab72f7d23ae202c7f98e52d/component-ota/23/03/18/71792dbf4bd649ff9346667b1f25017a.zip",
"md5": "65790f8f58d286c8d65dff0ada40aee7",
"size": "5871425918",
"type": "1",
"url": "https://gauss-componentotacostmanual-sg.allawnofs.com/remove-b1b7f6f4dab72f7d23ae202c7f98e52d/component-ota/23/03/18/71792dbf4bd649ff9346667b1f25017a.zip",
"vabInfo": {
"data": {
"extra_params": "metadata_hash:0c395f95f20207df32aaff86ff7e7ea393369f87876bafc4e9bc517a30077095",
"header": [
"FILE_HASH=idmYLwxiV6ELPhR0QcUtIc5EldhrilpDXfSet7/lF4U=",
"FILE_SIZE=5871420318",
"METADATA_HASH=Y4t+f+3X/Taw1VUq6GqA2wuGcWLk2PGtT8IFpR5GW5M=",
"METADATA_SIZE=225231",
"security_patch=2023-03-05",
"security_patch_vendor=2023-03-05",
"oplus_update_engine_verify_disable=0",
"ota_target_version=RMX3301_11.C.16_1160_202303162143",
"oplus_rom_version=V13.0.0",
"oplus_separate_soft=216AC"
],
"otaStreamingProperty": "payload_metadata.bin:2053:225498,payload.bin:2053:5871420318,payload_properties.txt:5871422429:357,metadata:69:997,metadata.pb:1134:852",
"vab_package_hash": "65790f8f58d286c8d65dff0ada40aee7"
}
}
},
"componentVersion": "RMX3301_11.C.16_1160_202303162143.1A.6f9e3487"
}
],
"decentralize": {
"offset": 508,
"round": 28800,
"strategyVersion": "default"
},
"description": {
"firstTitle": "This update integrates the latest Android security patches, fixes some known issues, and improves system performance.",
"panelUrl": "https://gauss-componentotacostmanual-sg.allawnofs.com/remove-b1b7f6f4dab72f7d23ae202c7f98e52d/component-ota/23/03/31/06c848b83adf43b9afa0a61c4e6f0d30.html",
"share": ".",
"url": "https://h5fsf.coloros.com/3adb669b49144103b5afb789182233ec/static/index.html#/about"
},
"googlePatchInfo": "0",
"id": "6426c6bf124eec0115884385",
"isNvDescription": true,
"isRecruit": false,
"isSecret": false,
"noticeType": 0,
"nvId16": "NV1A",
"osVersion": "ColorOS 13.0",
"otaVersion": "RMX3301_11.C.16_1160_202303162143",
"paramFlag": 1,
"parent": "ota",
"realAndroidVersion": "Android 13",
"realOsVersion": "ColorOS 13.0.0",
"reminderType": 0,
"rid": "d937f577-0f8f-40f5-8bef-d376dbb8138d",
"securityPatch": "2023-03-05",
"securityPatchVendor": "2023-03-05",
"silenceUpdate": 0,
"status": "published",
"versionCode": 1160,
"versionName": "RMX3301_11_C.16",
"versionTypeH5": "Official version"
}
Flashed all images to phone.
Code:
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash abl abl.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop aop.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop_config aop_config.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash bluetooth bluetooth.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash boot boot.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash cpucp cpucp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash devcfg devcfg.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dsp dsp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dtbo dtbo.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash engineering_cdt engineering_cdt.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash featenabler featenabler.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash hyp hyp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash imagefv imagefv.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash keymaster keymaster.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash modem modem.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_bigball my_bigball.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_carrier my_carrier.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_engineering my_engineering.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_heytap my_heytap.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_manifest my_manifest.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_product my_product.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_region my_region.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_stock my_stock.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm odm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm_dlkm odm_dlkm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplusstanvbk oplusstanvbk.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplus_sec oplus_sec.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash product product.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash qupfw qupfw.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash recovery recovery.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash shrm shrm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash splash splash.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system system.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system_ext system_ext.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash tz tz.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefi uefi.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefisecapp uefisecapp.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta vbmeta.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_system vbmeta_system.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_vendor vbmeta_vendor.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor vendor.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_boot vendor_boot.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_dlkm vendor_dlkm.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl xbl.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_config xbl_config.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_ramdump xbl_ramdump.img
."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" --disable-verity --disable-verification flash vbmeta vbmeta.img
Flashing logs.
Code:
PS C:\Users\PeyVodka> cd D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash abl abl.img
Sending 'abl' (216 KB) OKAY [ 0.009s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop aop.img
Sending 'aop' (256 KB) OKAY [ 0.010s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash aop_config aop_config.img
Sending 'aop_config' (16 KB) OKAY [ 0.003s]
Writing 'aop_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash bluetooth bluetooth.img
Sending 'bluetooth' (1788 KB) OKAY [ 0.063s]
Writing 'bluetooth' OKAY [ 0.006s]
Finished. Total time: 0.193s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash boot boot.img
Sending 'boot_b' (196608 KB) OKAY [ 6.557s]
Writing 'boot_b' OKAY [ 0.342s]
Finished. Total time: 7.086s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash cpucp cpucp.img
Sending 'cpucp' (152 KB) OKAY [ 0.006s]
Writing 'cpucp' OKAY [ 0.001s]
Finished. Total time: 0.119s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash devcfg devcfg.img
Sending 'devcfg' (56 KB) OKAY [ 0.004s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dsp dsp.img
Sending 'dsp' (65536 KB) OKAY [ 2.328s]
Writing 'dsp' OKAY [ 0.188s]
Finished. Total time: 2.627s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash dtbo dtbo.img
Sending 'dtbo' (24576 KB) OKAY [ 0.864s]
Writing 'dtbo' OKAY [ 0.076s]
Finished. Total time: 1.044s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash engineering_cdt engineering_cdt.img
Sending 'engineering_cdt' (1024 KB) OKAY [ 0.066s]
Writing 'engineering_cdt' OKAY [ 0.004s]
Finished. Total time: 0.196s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash featenabler featenabler.img
Sending 'featenabler' (92 KB) OKAY [ 0.005s]
Writing 'featenabler' OKAY [ 0.001s]
Finished. Total time: 0.129s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash hyp hyp.img
Sending 'hyp' (1356 KB) OKAY [ 0.057s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash imagefv imagefv.img
Sending 'imagefv' (72 KB) OKAY [ 0.004s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash keymaster keymaster.img
Sending 'keymaster' (360 KB) OKAY [ 0.013s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash modem modem.img
Sending 'modem_b' (296436 KB) OKAY [ 11.736s]
Writing 'modem_b' OKAY [ 0.579s]
Finished. Total time: 12.465s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_bigball my_bigball.img
Sending sparse 'my_bigball' 1/2 (786428 KB) OKAY [ 24.105s]
Writing 'my_bigball' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_carrier my_carrier.img
Sending 'my_carrier' (328 KB) OKAY [ 0.016s]
Writing 'my_carrier' FAILED (remote: '(my_carrier_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_engineering my_engineering.img
Sending 'my_engineering' (328 KB) OKAY [ 0.011s]
Writing 'my_engineering' FAILED (remote: '(my_engineering_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_heytap my_heytap.img
Sending 'my_heytap' (775220 KB) OKAY [ 33.016s]
Writing 'my_heytap' FAILED (remote: '(my_heytap_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_manifest my_manifest.img
Sending 'my_manifest' (404 KB) OKAY [ 0.016s]
Writing 'my_manifest' FAILED (remote: '(my_manifest_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_product my_product.img
Sending 'my_product' (507464 KB) OKAY [ 20.867s]
Writing 'my_product' FAILED (remote: '(my_product_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_region my_region.img
Sending 'my_region' (3544 KB) OKAY [ 0.153s]
Writing 'my_region' FAILED (remote: '(my_region_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash my_stock my_stock.img
Sending sparse 'my_stock' 1/2 (786428 KB) OKAY [ 24.981s]
Writing 'my_stock' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm odm.img
Sending sparse 'odm' 1/2 (786428 KB) OKAY [ 34.161s]
Writing 'odm' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash odm_dlkm odm_dlkm.img
Sending 'odm_dlkm' (340 KB) OKAY [ 0.012s]
Writing 'odm_dlkm' FAILED (remote: '(odm_dlkm_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplusstanvbk oplusstanvbk.img
Sending 'oplusstanvbk' (2776 KB) OKAY [ 0.095s]
Writing 'oplusstanvbk' OKAY [ 0.007s]
Finished. Total time: 0.214s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash oplus_sec oplus_sec.img
Sending 'oplus_sec' (328 KB) OKAY [ 0.012s]
Writing 'oplus_sec' OKAY [ 0.002s]
Finished. Total time: 0.124s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash product product.img
Sending 'product' (12516 KB) OKAY [ 0.465s]
Writing 'product' FAILED (remote: '(product_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash qupfw qupfw.img
Sending 'qupfw' (52 KB) OKAY [ 0.003s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.613s]
Writing 'recovery' OKAY [ 0.176s]
Finished. Total time: 3.905s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash shrm shrm.img
Sending 'shrm' (68 KB) OKAY [ 0.003s]
Writing 'shrm' OKAY [ 0.001s]
Finished. Total time: 0.114s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash splash splash.img
Sending 'splash' (528 KB) OKAY [ 0.018s]
Writing 'splash' OKAY [ 0.002s]
Finished. Total time: 0.131s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system system.img
Sending 'system' (678708 KB) OKAY [ 29.067s]
Writing 'system' FAILED (remote: '(system_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash system_ext system_ext.img
Sending sparse 'system_ext' 1/2 (786428 KB) OKAY [ 25.175s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash tz tz.img
Sending 'tz' (3712 KB) OKAY [ 0.133s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefi uefi.img
Sending 'uefi' (3080 KB) OKAY [ 0.133s]
Writing 'uefi' OKAY [ 0.007s]
Finished. Total time: 0.255s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash uefisecapp uefisecapp.img
Sending 'uefisecapp' (168 KB) OKAY [ 0.007s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta vbmeta.img
Sending 'vbmeta' (12 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.123s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.127s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vbmeta_vendor vbmeta_vendor.img
Sending 'vbmeta_vendor' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_vendor' OKAY [ 0.001s]
Finished. Total time: 0.118s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor vendor.img
Sending 'vendor' (650424 KB) OKAY [ 29.825s]
Writing 'vendor' FAILED (remote: '(vendor_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (196608 KB) OKAY [ 6.615s]
Writing 'vendor_boot' OKAY [ 0.326s]
Finished. Total time: 7.058s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash vendor_dlkm vendor_dlkm.img
Sending 'vendor_dlkm' (144052 KB) OKAY [ 5.430s]
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_b) No such partition')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl xbl.img
Sending 'xbl' (1080 KB) OKAY [ 0.056s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_config xbl_config.img
Sending 'xbl_config' (140 KB) OKAY [ 0.006s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" flash xbl_ramdump xbl_ramdump.img
Sending 'xbl_ramdump' (788 KB) OKAY [ 0.026s]
Writing 'xbl_ramdump' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807>
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807> ."E:/Programs/Android/SDK-platform-tools_r33.0.3-windows/platform-tools/fastboot" --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (12 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.112s
PS D:\Download\Browser\firmware\TAIWAN_71792dbf4bd649ff9346667b1f25017a\extracted_20230418_174807>
I took the phone apart and got to the test points as described in this post: https://forum.xda-developers.com/t/solved-edl-test-points.4471613/#post-87186865
To short-circuit them and put them into EDL Mode.
I checked the voltage with a voltmeter, it is ~1.8v and 0v. Everything seems to be fine and should work.
But my device is still not detected by the computer (Windows 11).
Any idea how to solve this problem?
I'm not sure what the exact cause is. I didn't think that flashing all the firmware images would be a very bad idea. And as far as I know EDL mode should remain available for me in any case.
And what could be causing the problem?
The only thing that seems strange from flashing logs is that this time boot was written to boot_b for some reason. Before that it usually went to boot_a. I'm not sure if this could have corrupted boot.

Okay. I was able to put the device into EDL mode. I soldered the test points to short it. Because the device seems to exit EDL mode every few seconds. Exactly as noted in these messages:
[Solved] EDL test points
Hi guys, i am looking for some help as my Realme GT2 Pro is dead bricked (ie. no response to buttons + usb) I was able to open the back cover but i am not sure which are the correct test points for EDL mode. Below is the picture of the...
forum.xda-developers.com
[Solved] EDL test points
Hi guys, i am looking for some help as my Realme GT2 Pro is dead bricked (ie. no response to buttons + usb) I was able to open the back cover but i am not sure which are the correct test points for EDL mode. Below is the picture of the...
forum.xda-developers.com
So, I got the firware RMX3301export_11_A.06_2022020500280000 from https://realmefirmware.com/realme-gt-2-pro-firmware/
What do I have to do next to flash the device free of charge myself?

A bit late now, but if you have a chance it's helpful to make a backup copy before you go flashing.
If your Firehose loader for EDL is unrestricted you can do it as a whole device and/or by partition.
Did you try before: fastboot flashing unlock_critical
Have you got a Firehose loader and gotten an EDL client to work yet? (Either the Python or mine.)

Renate said:
A bit late now, but if you have a chance it's helpful to make a backup copy before you go flashing.
If your Firehose loader for EDL is unrestricted you can do it as a whole device and/or by partition.
Did you try before: fastboot flashing unlock_critical
Have you got a Firehose loader and gotten an EDL client to work yet? (Either the Python or mine.)
Click to expand...
Click to collapse
I have no access to fastboot. Fastboot does not see my device after it became a hard brick.
I have not tried Firehose or other EDL clients. I tried opening QFIL. There I see that my device is recognized as qualcomm hs-usb qdloader 9008.
I have no idea what to do next.

I've never used QFIL. I don't have any interest in it.
If you use bkerler's Python you could replace the Windows Vcom driver with the Zadig driver.
If you use my client you must replace the Windows Vcom driver with the Zadig driver.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My stuff is in my sig.

Renate said:
I've never used QFIL. I don't have any interest in it.
If you use bkerler's Python you could replace the Windows Vcom driver with the Zadig driver.
If you use my client you must replace the Windows Vcom driver with the Zadig driver.
View attachment 5892303
My stuff is in my sig.
Click to expand...
Click to collapse
Okay. I'm going to try bkerler's Python now.
How do I see the solution to my problem:
1. I need to overwrite boot.img in boot_a with the command "edl w boot_a boot.img".
I believe that after that I will transfer my device to soft brick state and be able to boot into recovery mode.
2. In recovery mode, I will be able to use fastboot with my unlocked bootloader to flash the device normally.
Is my plan viable?

PeyVodka said:
Is my plan viable?
Click to expand...
Click to collapse
Sure.
Still, flashing with EDL, fastboot, dd, whatever all do the same stuff.

Renate said:
Sure.
Still, flashing with EDL, fastboot, dd, whatever all do the same stuff.
Click to expand...
Click to collapse
I'm a little confused trying to install bkerler's edl on Windows 11:
I am following the installation instructions for windows.
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Code:
PS D:\Download\Browser\firmware\edl-3.52.1\edl-3.52.1> python3 setup.py build
running build
running build_py
running egg_info
writing edl.egg-info\PKG-INFO
writing dependency_links to edl.egg-info\dependency_links.txt
writing requirements to edl.egg-info\requires.txt
writing top-level names to edl.egg-info\top_level.txt
reading manifest file 'edl.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*' under directory 'Loaders'
adding license file 'LICENSE'
writing manifest file 'edl.egg-info\SOURCES.txt'
running build_scripts
error: file 'D:\Download\Browser\firmware\edl-3.52.1\edl-3.52.1\Loaders\fhloaderparse.py' does not exist
There are no loaders for realme in the repository. What is this loader, where can I get the loader in my case?
GitHub - bkerler/Loaders: EDL Loaders
EDL Loaders. Contribute to bkerler/Loaders development by creating an account on GitHub.
github.com

PeyVodka said:
I'm a little confused trying to install bkerler's edl on Windows 11:
Click to expand...
Click to collapse
Lol. Now you know why I wrote a native Windows version.
I have less dependencies and admittedly, less features.

Renate said:
Lol. Now you know why I wrote a native Windows version.
I have less dependencies and admittedly, less features.
Click to expand...
Click to collapse
Yes, I understand. In general, the situation is familiar to me.
Will this allow me to overwrite boot_a with boot.img from OTA firmware according to my plan?
How to do this with your tool?
Is it:
Code:
edl.exe /w /pboot_a boot.img
In this case, I will be happy to use your tool.
EDL Utility

PeyVodka said:
Is it:
Click to expand...
Click to collapse
Yup, that should do it.
You'll need a Firehose loader.
There might be one in the QFIL stuff.
There might be one in the bkerler GitHub.
Identify what you've got with edl.exe /l

Renate said:
Yup, that should do it.
You'll need a Firehose loader.
There might be one in the QFIL stuff.
There might be one in the bkerler GitHub.
Identify what you've got with edl.exe /l
Click to expand...
Click to collapse
Okay.
I reinstalled driver for my device via Zadig.
Downloaded your tool and execute:
Code:
PS D:\Download\Browser\firmware> .\edl.exe /l
Found EDL 9008
Serial: $SERIAL$
Received unexpected 04 command
PS D:\Download\Browser\firmware> .\edl.exe /l
Found EDL 9008
Resetting Sahara
Could not read device
Did i do something wrong?

PeyVodka said:
Did i do something wrong?
Click to expand...
Click to collapse
That all looks good.
The Sahara protocol is very brittle (and stupid).
If an attempt at communication has occured but failed, the device will be in la-la land.
Do a clean reset.
(Which is what edl.exe was trying to do, but the implementations of Sahara are all different.)
Actually, it could be flakey communication too. Check your cables and ports.
Edit: Mmm, it could be that this needs some authorization.
In which case you can only do this with the RealMe tools.
You should try the bkerler too. You can leave it on Zadig for that.

Renate said:
That all looks good.
The Sahara protocol is very brittle (and stupid).
If an attempt at communication has occured but failed, the device will be in la-la land.
Do a clean reset.
(Which is what edl.exe was trying to do, but the implementations of Sahara are all different.)
Actually, it could be flakey communication too. Check your cables and ports.
Edit: Mmm, it could be that this needs some authorization.
In which case you can only do this with the RealMe tools.
You should try the bkerler too. You can leave it on Zadig for that.
Click to expand...
Click to collapse
I tried bkerler edl on Ubuntu. It got stuck on this message:
Code:
edl --serial
Capstone library is missing (optional).
Keystone library is missing (optional).
No module named 'Cryptodome'
Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.
main - Trying with no loader given ...
main - Waiting for the device
Detected 0x5c6:0x9008 device at: /dev/ttyUSB0
main - Device detected :)
sahara - Protocol version: 3, Version supported: 1
main - Mode detected: sahara
"it could be that this needs some authorization."
Could this have something to do with the information in this post?:
[No auth collection] Realme No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Realme has blocked offline flashing with authentication required to flash their device. This files will ultimately help you to fix the authorisation issue and hence unbrick your Realme device via EDL mode...
forum.xda-developers.com

PeyVodka said:
It got stuck on this message
Click to expand...
Click to collapse
Normally you should be able to get beyond this point with any device.
The authorization comes in Firehose, not Sahara.
Could you try (after a reset): edl.exe /l /v
See, a custom PBL would be unexpected thing.

Your tool.
I've tried several times, it keeps giving these messages one after another.
Code:
PS D:\Download\Browser\firmware> ./edl.exe /l /v
Found EDL 9008
USB maximum packet: in=512, out=512
Received 01 command
Received 0b command
Received 0e command
Serial: $SERIAL$
Received 04 command
Sahara exec command 2 unsupported
Received 04 command
Received unexpected 04 command
PS D:\Download\Browser\firmware> ./edl.exe /l /v
Found EDL 9008
USB maximum packet: in=512, out=512
Resetting Sahara
Could not read device
PS D:\Download\Browser\firmware> ./edl.exe /l /v
Could not find EDL device
Here I was told that there is currently no Firehose for my device.
[No auth collection] Realme No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Realme has blocked offline flashing with authentication required to flash their device. This files will ultimately help you to fix the authorisation issue and hence unbrick your Realme device via EDL mode...
forum.xda-developers.com

Renate said:
I've never used QFIL. I don't have any interest in it.
If you use bkerler's Python you could replace the Windows Vcom driver with the Zadig driver.
If you use my client you must replace the Windows Vcom driver with the Zadig driver.
View attachment 5892303
My stuff is in my sig.
Click to expand...
Click to collapse
By the they, how do I roll back the changes made by Zadig? From WinUSB.sys driver to qcusbser.sys
UPD: Ok. I've just deleted it via Windows Device Manager.

PeyVodka said:
Code:
Sahara exec command 2 unsupported
Click to expand...
Click to collapse
Well, that is strange. I've run into that before on some other Chinese stuff.
Apparently they never burned a HWID or disabled the querying of it.
I'm quite sure that Qualcomm would never make a custom PBL for anybody.
I don't know if they disabled querying of the hash too.

Everyone, support this post on realme's website. Let's make Realme release private recovery tools via EDL mode to the public!
So we can experiment with our purchased devices and not pay money for something we could always do for free!
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!
c.realme.com

Renate said:
Well, that is strange. I've run into that before on some other Chinese stuff.
Apparently they never burned a HWID or disabled the querying of it.
I'm quite sure that Qualcomm would never make a custom PBL for anybody.
I don't know if they disabled querying of the hash too.
Click to expand...
Click to collapse
My dear friend and g0d-tier researcher M3ik Shizuka was able to "spell" offline access to both obfuscated tools. I couldn't believe my eyes.
Indeed, now that I connected my device in MsmDownloadTool, it stopped exiting EDL mode every few seconds. However, to enter EDL mode, I still had to solder test points. According to the status information and logs, I was finally able to connect via Sahara.
Unfortunately, for some stages of verification and data download, the MsmDownloadTool requires authorization with the servers. Apparently, MsmDownloadTool is really the official leaked tool.
Realme Login Tool makes a GET request to check the OPT code on api2.realmelogin.com.
I am not competent in this, but I hope that knowledgeable people can figure out from the log if there is anything useful that we can learn from sniffing the COM port. So that we can eventually use this to interact with the device via EDL mode with other tools.
MsmDownloadTool logs:
Code:
=========================================================
| Msm Download Tool V2.0.67 for eMMC/UFS
|
| Build Data: Nov 2 2021
| Build Time: 20:12:20
=========================================================
[PID:10472] [TID:15296] [2023-04-21 21:16:32::0323] Start log...
[PID:10472] [TID:15296] [2023-04-21 21:16:32::0468] mac:MAC_ADDRESS
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0680] Path:D:\RMX3301export_11_A.06_2022020500280000\RMX3301export_11_A.06_2022020500280000.ofp
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0804] Project:PROJECT_CODE, Compatible:
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0805] Strorage type: UFS
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Mode:After-sales
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Filter Metadata is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Binding Metadata is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Download Config is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Download Config Signed is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Support Reset is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Cloud Flag is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Multi Project is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Erase Oder is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] WO3 is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] UFS is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] SV is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] NV is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] VC is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] OCDT is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Root is FALSE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Secsmt is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] Support FC is TRUE
[PID:10472] [TID:15296] [2023-04-21 21:19:37::0810] -------------------
[PID:10472] [TID:11916] [2023-04-21 21:19:47::0425] Device Remove: \\?\USB#VID_05C6&PID_9008...
[PID:10472] [TID:11916] [2023-04-21 21:20:28::0540] Device Arrival: \\?\USB#VID_05C6&PID_9008...
[PID:10472] [TID:11916] [2023-04-21 21:20:28::0541] Friendly Name: Qualcomm HS-USB QDLoader 9008 (COM5)
[PID:10472] [TID:15296] [2023-04-21 21:20:35::0046] Click Button Refresh
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0202] Click Button Start, mode:After-sale, project:PROJECT_CODE
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] IsPackImage is true
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] FactoryLine is false
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] BootOnly is false
[PID:10472] [TID:15296] [2023-04-21 21:20:46::0203] DisableBootWizard is false
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Download start
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Set download status ,current status: COM_DOWNLOAD.
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Open the serial device
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0206] [COM5] Open the serial device retry = 1
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0239] [COM5] Set Sahara file ok��sahara file: prog_firehose_ddr.elf.
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0254] [COM5] Attempting to send a Sahara message for communication
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0254] [COM5] Downloading Firehose protocol file via Sahara protocol
[PID:10472] [TID:13348] [2023-04-21 21:20:46::0811] [COM5] Sahara communication succeeded
[PID:10472] [TID:13348] [2023-04-21 21:20:51::0138] [COM5] filename=ChainedTableOfDigests_PROJECT_CODE_persist_no_userdata_no
[PID:10472] [TID:13348] [2023-04-21 21:20:52::0166] [COM5] Trying to handshake via Firehose communication
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0294] [COM5] Configure the settings of Firehose communication data transmission
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0389] [COM5] Get sign data
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0574] [COM5] ID:CHIP_ID, B:enable
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0574] [COM5] old_sw_name_sign:OLD_SW_NAME_SIGN, new_sw_name_sign:NEW_SW_NAME_SIGN
[PID:10472] [TID:13348] [2023-04-21 21:20:53::0575] [COM5] Verify Data
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0361] [COM5] FirehoseCheckRSP is ERROR, hr=1
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0361] [COM5] Rsp:
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: verify failed." /></data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0362] [COM5] Verify pass
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0363] [COM5] Current download task end,elapsed time:416s.
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0363] [COM5] Upload download result. chip id: CHIP_ID, result: 1, project: PROJECT_CODE
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0373] [COM5] Upload download result failed.
[PID:10472] [TID:13348] [2023-04-21 21:27:42::0373] [COM5] Close the serial device
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0406] [COM5] Download failed
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0406] [COM5] Determine whether to upload the download info
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0406] [COM5] compress file, retry time is 4
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0514] [COM5] compress file success
[PID:10472] [TID:13348] [2023-04-21 21:27:45::0515] [COM5] start to upload
[PID:10472] [TID:15296] [2023-04-21 21:28:49::0756] Click Button Stop

Better Mobile App

welcome