hello ,
My brother bought a new RMX2086 and wanted a custom rom on this it , i got it running without a problem for him everything was working fine till he connected the phone and he mistakenly formated the phone storage using UnlockTool using the "Snapdragon" tab.
I Tried reviving it using QFil and Unlocktool but it got no success and the phone only connect into EDL mode 9008.
i tried many firmwares but i got no luck.
but the other day i tried another RMX2086 firmware but the phone is hard hard bricked now , what i mean is the phone is not connecting to the pc anymore No 9008 no Fastboot no nothing it is dead , i read on this forum that SDM855+ has ram over it so i can't dig to ISP pinout.
anyone can help
i think i found the test point for this stupid phone ,
i flashed the same firmware that i used to revive this phone with but i got no EDL without shorting or fastboot , nothing , i have to short it to get 9008 port .
{
"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"
}
FOUND a new way to get 9008 port without shorting , just format data and the phone will connect every time you flash rawprogram0-8.xml ...
hey guys i tried 3 difrrent ofp , extracted them and flashed the firmware using Unlocktool's SDM module , with the help of prog_firehose.mbn from Unlocktool server. the one that came with the firmware does not work .
but the phone is still dead and with the usb plugged in it draws 0.25 to 0.30 Amps
here's the log..
Version:0.9 StartHTML:-1 EndHTML:-1 StartFragment:000128 EndFragment:017079 SourceURL:file%3a%2f%2f
EDL FLASHSelected Model : Realme X3 SuperZoom
Code Name : RMX2086
Operation : Auth Flash
Authenticating... OK
Retrieving data... OK [291.56 KiB]
Initializing data... OK
Waiting for HS-USB QDLoader 9008... COM7
Connecting to device... OK
Writing flash programmer... OK
Connecting to flash programmer... OK
Configuring device... OK
Setting boot LUN1... OK
Firehose config : UFS [Sector:4096] [Target:0] [Host:1048576]
Processing LUN0 - rawprogram0.xml
Writing persist.img [ext4:32 MiB]->persist... OK 0.815s
Writing custom.img [sparse:4.12 MiB]->custom... OK 0.219s
Writing cache.img [sparse:68.17 KiB]->cache... OK 0.107s
Writing metadata.img [sparse:44.07 KiB]->metadata... OK 0.103s
super->super.img is not exists!!!
Writing super.0.3743af72.img [sparse:3.9 GiB]->super... OK 100.494s
Writing super.1.ad242118.img [sparse:2.23 GiB]->super... OK 59.572s
Writing super.2.ad8e3c51.img [sparse:1.01 GiB]->super... OK 26.933s
Writing userdata.img [sparse:345.32 MiB]->userdata... OK 9.409s
Writing gpt_main0.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup0.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch0.xml... OK
Processing LUN1 - rawprogram1.xml
Writing xbl.elf [elf:3.04 MiB]->xbl... OK 0.196s
Writing xbl_config.elf [elf:120.66 KiB]->xbl_config... OK 0.105s
Writing gpt_main1.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup1.bin [raw:20 KiB]->BackupGPT... OK 0.101s
Applying patch1.xml... OK
Processing LUN2 - rawprogram2.xml
Writing gpt_main2.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup2.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch2.xml... OK
Processing LUN3 - rawprogram3.xml
Writing oppo19710.bin [raw:48 bytes]->cdt... OK 0.051s
Writing zeros_5sectors.bin [raw:20 KiB]->ddr... OK 0.102s
Writing gpt_main3.bin [raw:24 KiB]->PrimaryGPT... OK 0.052s
Writing gpt_backup3.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch3.xml... OK
Processing LUN4 - rawprogram4.xml
Writing aop.mbn [elf:196.05 KiB]->aop... OK 0.106s
Writing tz.mbn [elf:3.04 MiB]->tz... OK 0.195s
Writing hyp.mbn [elf:476.88 KiB]->hyp... OK 0.148s
Writing NON-HLOS.bin [fat:140.21 MiB]->modem... OK 3.515s
Writing BTFM.bin [fat:860 KiB]->bluetooth... OK 0.126s
Writing abl.elf [elf:160 KiB]->abl... OK 0.106s
Writing dspso.bin [ext4:64 MiB]->dsp... OK 1.689s
Writing km4.mbn [elf:253.03 KiB]->keymaster... OK 0.108s
Writing boot.img [kernel:96 MiB]->boot... OK 2.368s
Writing cmnlib.mbn [elf:385.75 KiB]->cmnlib... OK 0.113s
Writing cmnlib64.mbn [elf:503.61 KiB]->cmnlib64... OK 0.115s
Writing devcfg.mbn [elf:52.79 KiB]->devcfg... OK 0.103s
Writing qupv3fw.elf [elf:69.07 KiB]->qupfw... OK 0.103s
Writing vbmeta.img [raw:8 KiB]->vbmeta... OK 0.101s
Writing vbmeta_system.img [raw:4 KiB]->vbmeta_system... OK 0.051s
Writing vbmeta_vendor.img [raw:4 KiB]->vbmeta_vendor... OK 0.051s
Writing dtbo.img [raw:24 MiB]->dtbo... OK 0.760s
Writing recovery.img [kernel:80 MiB]->recovery... OK 2.087s
Writing uefi_sec.mbn [elf:122.62 KiB]->uefisecapp... OK 0.104s
Writing imagefv.elf [elf:30.5 KiB]->imagefv... OK 0.102s
Writing dpAP.mbn [elf:13.19 KiB]->apdp... OK 0.101s
Writing dpMSA.mbn [elf:13.19 KiB]->msadp... OK 0.102s
Writing splash.img [raw:516.63 KiB]->splash... OK 0.117s
Writing logfs_ufs_8mb.bin [fat:16 KiB]->logfs... OK 0.102s
Writing storsec.mbn [elf:20.08 KiB]->storsec... OK 0.103s
Writing oppo_sec.mbn [elf:111.52 KiB]->oppo_sec... OK 0.104s
Writing multi_image.mbn [elf:13.3 KiB]->multiimgoem... OK 0.103s
Writing sec_smt.dat [raw:512 bytes]->secdata... OK 0.102s
Writing gpt_main4.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup4.bin [raw:20 KiB]->BackupGPT... OK 0.103s
Applying patch4.xml... OK
Processing LUN5 - rawprogram5.xml
Writing dynamic_nvbk.bin [raw:10 MiB]->oppodycnvbk... OK 0.446s
Writing static_nvbk.bin [raw:10 MiB]->oppostanvbk... OK 0.434s
Writing emmc_fw.bin [raw:4 MiB]->opporeserve1... OK 0.349s
Writing opporeserve2.img [sparse:5.05 MiB]->opporeserve2... OK 0.398s
Writing DRIVER.ISO [raw:22.69 MiB]->DRIVER... OK 0.685s
Writing gpt_main5.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup5.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch5.xml... OK
Rebooting... OK
Total transfer : 7.97 GiB
Transfer Speed : 38.14 MiB/s
UNLOCKTOOL 2023.05.25.0
Elapsed time : 4 minutes 14 seconds
I did everything , i have UnlockTool.
i flashed all these roms :
RMX2086GDPR_11_F.06_2022101321340000.zip
RMX2086GDPR_11_C.13_2022051901570000.zip
RMX2086export_11_C.13_2022051901560000.zip
RMX2086PU_11_A.33_200625_33c9c266.zip
RMX2085export_11_C.13_2022051901550466_2.7z
RMX2081PU_11_A.53_210404_719ee533.zip
RMX2081EU_11_A.52_210404_719ee533.zip
RMX2081PU_11_A.53_210404_719ee533.zip
I extracted all of them , flashed them one by one , one time using Unlocktool , the 2nd time using Qfil after making some changes in Rawprogram3.xml "oppo19711.bin in cdt" and Rawprogram4.xml " sec_smt.dat in secdata ".
I edited Rawprogram.xml and got rid of those weird logs from Port_trace.txt " QFil logs "
I try to keep the battery voltage from being sucked by the phone " i keep it above 3.7V " , the phone always is drawing from 0.20 A to 0.32 A using my usb doctor.
Sometimes QFil won't flash unless i use prog_fwupdate.mbn , prog_firehose.mbn won't work .
The phone won't automatically connect to the pc ''9008" unless you short testpoint , and fix this "sometime" i use Format Storage from UnlockTool , then the phone will automatically get detected by the pc ''9008" eachtime you plug it or unplug it from the pc , it will get recognized without shorting the pins.
Before getting to this point , the phone was working fine i installed a custom rom and everything was ok. when i tried to root it i faced many problems of the phone not booting etc , i used to fix everything just by flashing "RMX2086GDPR_11_C.13_2022051901570000.zip" then the phone will boot without a problem , as a fresh start or something then i start ''rooting and installing custom roms etc ''.
Wow, it looks like you've tried a lot of stuff.
Maybe if you could find the UART interface it could give you some feedback on what's going wrong.
I was just wondering what's in those patch XMLs? (No, this has nothing to do with fixing this, I'm just wondering why they have to do that.)
Renate said:
Wow, it looks like you've tried a lot of stuff.
Maybe if you could find the UART interface it could give you some feedback on what's going wrong.
I was just wondering what's in those patch XMLs? (No, this has nothing to do with fixing this, I'm just wondering why they have to do that.)
Click to expand...
Click to collapse
yeah i don't i know why it had to do that , i mean i didn't find it on the internet or something , i just analyzed the xlm file because of the flash tool giving me errors '' sec.dat not exist " , so i had to dig and find a file named sec_smt.dat so i renamed it to sec.dat , the other one is '' oppo does not exist " so i found the file named " file_sector_offset="0" filename="oppo19696.bin" label="cdt ".
Today i downloaded 3 diff roms " RMX2085 " and mine is " RMX2086" i'm just trying everthing to revive this phone .
is there a paid tool or something like unlocktool " without a dongle " that is the best for Q9008 " SDM " phones ?
i need to try another flashtool , i mean i tried with QFIl and unlocktool only , MSMdownloadtool doesn't work , i installed cert for Codemeter enabled that bomb thing and it didn't start giving me error " packed does not exist " , and some username thing that i don't have and don't want to buy.
Deadmau73 said:
hey guys i tried 3 difrrent ofp , extracted them and flashed the firmware using Unlocktool's SDM module , with the help of prog_firehose.mbn from Unlocktool server. the one that came with the firmware does not work .
but the phone is still dead and with the usb plugged in it draws 0.25 to 0.30 Amps
here's the log..
Version:0.9 StartHTML:-1 EndHTML:-1 StartFragment:000128 EndFragment:017079 SourceURL:file%3a%2f%2f
EDL FLASHSelected Model : Realme X3 SuperZoom
Code Name : RMX2086
Operation : Auth Flash
Authenticating... OK
Retrieving data... OK [291.56 KiB]
Initializing data... OK
Waiting for HS-USB QDLoader 9008... COM7
Connecting to device... OK
Writing flash programmer... OK
Connecting to flash programmer... OK
Configuring device... OK
Setting boot LUN1... OK
Firehose config : UFS [Sector:4096] [Target:0] [Host:1048576]
Processing LUN0 - rawprogram0.xml
Writing persist.img [ext4:32 MiB]->persist... OK 0.815s
Writing custom.img [sparse:4.12 MiB]->custom... OK 0.219s
Writing cache.img [sparse:68.17 KiB]->cache... OK 0.107s
Writing metadata.img [sparse:44.07 KiB]->metadata... OK 0.103s
super->super.img is not exists!!!
Writing super.0.3743af72.img [sparse:3.9 GiB]->super... OK 100.494s
Writing super.1.ad242118.img [sparse:2.23 GiB]->super... OK 59.572s
Writing super.2.ad8e3c51.img [sparse:1.01 GiB]->super... OK 26.933s
Writing userdata.img [sparse:345.32 MiB]->userdata... OK 9.409s
Writing gpt_main0.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup0.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch0.xml... OK
Processing LUN1 - rawprogram1.xml
Writing xbl.elf [elf:3.04 MiB]->xbl... OK 0.196s
Writing xbl_config.elf [elf:120.66 KiB]->xbl_config... OK 0.105s
Writing gpt_main1.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup1.bin [raw:20 KiB]->BackupGPT... OK 0.101s
Applying patch1.xml... OK
Processing LUN2 - rawprogram2.xml
Writing gpt_main2.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup2.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch2.xml... OK
Processing LUN3 - rawprogram3.xml
Writing oppo19710.bin [raw:48 bytes]->cdt... OK 0.051s
Writing zeros_5sectors.bin [raw:20 KiB]->ddr... OK 0.102s
Writing gpt_main3.bin [raw:24 KiB]->PrimaryGPT... OK 0.052s
Writing gpt_backup3.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch3.xml... OK
Processing LUN4 - rawprogram4.xml
Writing aop.mbn [elf:196.05 KiB]->aop... OK 0.106s
Writing tz.mbn [elf:3.04 MiB]->tz... OK 0.195s
Writing hyp.mbn [elf:476.88 KiB]->hyp... OK 0.148s
Writing NON-HLOS.bin [fat:140.21 MiB]->modem... OK 3.515s
Writing BTFM.bin [fat:860 KiB]->bluetooth... OK 0.126s
Writing abl.elf [elf:160 KiB]->abl... OK 0.106s
Writing dspso.bin [ext4:64 MiB]->dsp... OK 1.689s
Writing km4.mbn [elf:253.03 KiB]->keymaster... OK 0.108s
Writing boot.img [kernel:96 MiB]->boot... OK 2.368s
Writing cmnlib.mbn [elf:385.75 KiB]->cmnlib... OK 0.113s
Writing cmnlib64.mbn [elf:503.61 KiB]->cmnlib64... OK 0.115s
Writing devcfg.mbn [elf:52.79 KiB]->devcfg... OK 0.103s
Writing qupv3fw.elf [elf:69.07 KiB]->qupfw... OK 0.103s
Writing vbmeta.img [raw:8 KiB]->vbmeta... OK 0.101s
Writing vbmeta_system.img [raw:4 KiB]->vbmeta_system... OK 0.051s
Writing vbmeta_vendor.img [raw:4 KiB]->vbmeta_vendor... OK 0.051s
Writing dtbo.img [raw:24 MiB]->dtbo... OK 0.760s
Writing recovery.img [kernel:80 MiB]->recovery... OK 2.087s
Writing uefi_sec.mbn [elf:122.62 KiB]->uefisecapp... OK 0.104s
Writing imagefv.elf [elf:30.5 KiB]->imagefv... OK 0.102s
Writing dpAP.mbn [elf:13.19 KiB]->apdp... OK 0.101s
Writing dpMSA.mbn [elf:13.19 KiB]->msadp... OK 0.102s
Writing splash.img [raw:516.63 KiB]->splash... OK 0.117s
Writing logfs_ufs_8mb.bin [fat:16 KiB]->logfs... OK 0.102s
Writing storsec.mbn [elf:20.08 KiB]->storsec... OK 0.103s
Writing oppo_sec.mbn [elf:111.52 KiB]->oppo_sec... OK 0.104s
Writing multi_image.mbn [elf:13.3 KiB]->multiimgoem... OK 0.103s
Writing sec_smt.dat [raw:512 bytes]->secdata... OK 0.102s
Writing gpt_main4.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup4.bin [raw:20 KiB]->BackupGPT... OK 0.103s
Applying patch4.xml... OK
Processing LUN5 - rawprogram5.xml
Writing dynamic_nvbk.bin [raw:10 MiB]->oppodycnvbk... OK 0.446s
Writing static_nvbk.bin [raw:10 MiB]->oppostanvbk... OK 0.434s
Writing emmc_fw.bin [raw:4 MiB]->opporeserve1... OK 0.349s
Writing opporeserve2.img [sparse:5.05 MiB]->opporeserve2... OK 0.398s
Writing DRIVER.ISO [raw:22.69 MiB]->DRIVER... OK 0.685s
Writing gpt_main5.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup5.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch5.xml... OK
Rebooting... OK
Total transfer : 7.97 GiB
Transfer Speed : 38.14 MiB/s
UNLOCKTOOL 2023.05.25.0
Elapsed time : 4 minutes 14 seconds
Click to expand...
Click to collapse
Hi, can you send me link to that tool?
maskalicz said:
Hi, can you send me link to that tool?
Click to expand...
Click to collapse
UnlockTool - Flash - Unlock Bootloader Xiaomi - Without Credit (Find My Phone ON)
unlocktool.net
Related
Hi devs and helpers!!
this is only for indians but if you wish you can help
ok this is a long story let me explain
so first lollipop soak test released and i updated it via keeping the file in sd and phone memory and then i updated it till 22.27.1 then i found that i am stuck on that version i cant do anything so i flashed 5.1 firmware images and then on the bootloader says that hab check failed for system and failed to validate system image so i need the indian retail from flipkart stock 4.4.4 images only if they are 4.4.4 ! AND I CANT UNLOCK THE BOOTLOADER AS THAT IS ANOTHER LONG STORY SO NOW IF ANYONE HAS WHAT I WANT THEN PLZ GIVE AND DONT TELL TO UNLOCK THE BOOTLOADER AND I HAVE TRIED EVERY FIRMWARE EXCEPT (http://forum.xda-developers.com/showthread.php?t=2759495) , the link isnt working and i have also posted on that thread that the link isnt working , So can anyone help me plz???
THANKS!!
Hello,
Have you tried this?
http://forum.xda-developers.com/moto-e/general/xt1022-stock-indian-firmware-t2826480
I hope that helps. Good luck.
Droidriven said:
Hello,
Have you tried this?
http://forum.xda-developers.com/moto-e/general/xt1022-stock-indian-firmware-t2826480
I hope that helps. Good luck.
Click to expand...
Click to collapse
Thankyou very much for responding !! i will try it and tell u tommorow!!:laugh::good::good::good:
Droidriven said:
Hello,
Have you tried this?
http://forum.xda-developers.com/moto-e/general/xt1022-stock-indian-firmware-t2826480
I hope that helps. Good luck.
Click to expand...
Click to collapse
sorry doesnt work:crying:
i need Blur_Version.21.41.20.condor_retaildsds.retaildsdsall.en.03 something like that the xx.xx.xx is not correct:crying:
snehil_dps_6l said:
hi devs and helpers!!
This is only for indians but if you wish you can help
ok this is a long story let me explain
so first lollipop soak test released and i updated it via keeping the file in sd and phone memory and then i updated it till 22.27.1 then i found that i am stuck on that version i cant do anything so i flashed 5.1 firmware images and then on the bootloader says that hab check failed for system and failed to validate system image so i need the indian retail from flipkart stock 4.4.4 images only if they are 4.4.4 ! And i cant unlock the bootloader as that is another long story so now if anyone has what i want then plz give and dont tell to unlock the bootloader and i have tried every firmware except (http://forum.xda-developers.com/showthread.php?t=2759495) , the link isnt working and i have also posted on that thread that the link isnt working , so can anyone help me plz???
thanks!!
Click to expand...
Click to collapse
plzzz someone send firwares plzzzz
You cannot flash any 4.4.4 Firmware Image without Unlocking Bootloader. Follow Bootloader locking Tutorial: http://forum.xda-developers.com/showpost.php?p=52693419&postcount=2
Alternatively, forget about KitKat and flash latest XT1022 Lollipop 5.1 Firmware Image from here: http://forum.xda-developers.com/showthread.php?t=2755857
XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7
It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
You have to unlock the bootloader
MaddySayaji said:
You have to unlock the bootloader
Click to expand...
Click to collapse
if there is a corrupt firmware how can i unlock the bootloader
lost101 said:
You cannot flash any 4.4.4 Firmware Image without Unlocking Bootloader. Follow Bootloader locking Tutorial: http://forum.xda-developers.com/showpost.php?p=52693419&postcount=2
Alternatively, forget about KitKat and flash latest XT1022 Lollipop 5.1 Firmware Image from here: http://forum.xda-developers.com/showthread.php?t=2755857
XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7
It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Hi sir,
im very happy that someone is trying to help me out
all the commands were successful but i have a error "failed to validate system image" in purple color and plus ur older version of 5.1 firmware isnt working its saying (preflash validation failed) (XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.2_cid7_CFC.xml)
here are all the commands as asked (output from command prompt):
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.024s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.712s]
finished. total time: 0.741s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1669 KB)...
OKAY [ 0.088s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 2.071s]
finished. total time: 2.170s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (527 KB)...
OKAY [ 0.067s]
writing 'logo'...
OKAY [ 0.132s]
finished. total time: 0.205s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.396s]
writing 'boot'...
OKAY [ 1.573s]
finished. total time: 1.976s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.409s]
writing 'recovery'...
OKAY [ 1.575s]
finished. total time: 1.998s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (242987 KB)...
OKAY [ 8.533s]
writing 'system'...
OKAY [ 27.242s]
finished. total time: 38.026s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256539 KB)...
OKAY [ 9.150s]
writing 'system'...
OKAY [ 25.751s]
finished. total time: 34.909s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257126 KB)...
OKAY [ 9.087s]
writing 'system'...
OKAY [ 25.306s]
finished. total time: 34.406s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (46232 KB)...
OKAY [ 1.667s]
writing 'modem'...
OKAY [ 3.940s]
finished. total time: 5.614s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.018s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.016s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (648 KB)...
OKAY [ 0.066s]
writing 'fsg'...
OKAY [ 0.130s]
finished. total time: 0.201s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.079s]
finished. total time: 0.082s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.271s]
finished. total time: 0.274s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>
@Snehil_DPS_6l - The solution is to unlock your Bootloader and try fastboot flashing again.
Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* Your warranty will be void if you tamper with any part of your device / software.
Download :
RMX2076PU_A29_fastboot [IN]
RMX2076EU_A28_fastboot [EU]
Fastboot Commands :
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
Latest Fastboot :
Download
Fastboot Images For Other Realme Devices :
Github
Guide to extract Fastboot images from ozip :
Credits :
jamflux
Regards,
acervenky
FAQs
I'm getting the "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it." Error, what should I do now?
Flash the vbmeta using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I'm getting the "Invalid sparse file format at header magic" Error, does that mean that the images are corrupt?
No! Just ignore the error, if you get the "Finished" message it means that the image has been flashed without any issues.
Can I cross-flash images?(CN -> IN & vice versa)
Some users have reported that the images can't be flashed due to different partition sizes, proceed at your own risk!
Regards,
acervenky
hi guys i managed to root on rmx2075e 2076 but the twrp is missing to do a job well done.
RMX2071_11.A.18
from this version
rmx2076eu_a28
Can I upgrade to this version?
smhzhl said:
RMX2071_11.A.18
from this version
rmx2076eu_a28
Can I upgrade to this version?
Click to expand...
Click to collapse
These images are not meant for upgrade/downgrade, use the traditional method of upgrading via realme recovery.
Regards,
acervenky
do you have Fastboot Flashable for rmx2072 x50 pro player?
acervenky said:
These images are not meant for upgrade/downgrade, use the traditional method of upgrading via realme recovery.
Regards,
acervenky
Click to expand...
Click to collapse
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/3 (785109 KB) OKAY [ 20.211s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Error ?
smhzhl said:
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/3 (785109 KB) OKAY [ 20.211s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Error ?
Click to expand...
Click to collapse
same issue, how did u solve it?
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/3 (785109 KB) OKAY [ 20.211s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
my phone is rmx2076 indian version
I did install 2071 ozip from twrp, volte, fingerprint,face unlock didn't work
I'm getting error like that on the top any solutions?
[email protected]:/media/marques/DC6493EB6493C724/Phone related/Realme X50 Pro/fastboot images {stock}/RMX2076PU_A29_fastboot$ fastboot flash boot boot.img
Sending 'boot' (98304 KB) OKAY [ 3.089s]
Writing 'boot' OKAY [ 0.395s]
Finished. Total time: 4.792s
[email protected]:/media/marques/DC6493EB6493C724/Phone related/Realme X50 Pro/fastboot images {stock}/RMX2076PU_A29_fastboot$ fastboot flash dtbo dtbo.img
Sending 'dtbo' (24576 KB) OKAY [ 0.780s]
Writing 'dtbo' OKAY [ 0.088s]
Finished. Total time: 1.328s
[email protected]:/media/marques/DC6493EB6493C724/Phone related/Realme X50 Pro/fastboot images {stock}/RMX2076PU_A29_fastboot$ fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/6 (783296 KB) OKAY [ 55.456s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
[email protected]:/media/marques/DC6493EB6493C724/Phone related/Realme X50 Pro/fastboot images {stock}/RMX2076PU_A29_fastboot$ fastboot flash vbmeta vbmeta.img
Sending 'vbmeta' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.098s
[email protected]:/media/marques/DC6493EB6493C724/Phone related/Realme X50 Pro/fastboot images {stock}/RMX2076PU_A29_fastboot$ fastboot flash vendor vendor.img
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/3 (786285 KB) OKAY [ 24.744s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
[email protected]:/media/marques/DC6493EB6493C724/Phone related/Realme X50 Pro/fastboot images {stock}/RMX2076PU_A29_fastboot$
this is whole cmd logs, vendor and system images give this error
my phone is 2076 but I flashed 2071 through twrp
any solutions??
I got my issue solved
Shreeram02 said:
I got my issue solved
Click to expand...
Click to collapse
How did you resolve it?
Touche said:
How did you resolve it?
Click to expand...
Click to collapse
its quite long one.. I have posted it in guide section
Hi,
Can someone please help me with fix of my P20 lite dual?
I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹
The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly"
Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7
Factory reset and cache wipe did not help.
Any attempt to SD or USB update via recovery failed, always got "Install failed"
So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP.
No luck, phone was in fastboot mode only or bootloops.
Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0)
With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK.
So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"?
Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message.
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Or is there some easy way to flash to official ?
Or did I messed up some system files that need to be fixed?
PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts.
Can be this a problem? (I hope not)
Thank you for any ideas !
hdano said:
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Click to expand...
Click to collapse
HwOTA will won't help you - it cannot identify the device in this state...
(model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB )
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
HwOTA will won't help you - it cannot identify the device in this state...
(model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB )
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-BD 1.0.0.40(log)
OKAY [ 0.011s]
finished. total time: 0.013s
C:\adb>
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE
OKAY [ 0.011s]
finished. total time: 0.013s
C:\adb>
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.022s
C:\adb>
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: The reason of failed input oem_nv_item error!)
finished. total time: 0.018s
C:\adb>
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.021s
hdano said:
any ideas
Click to expand...
Click to collapse
maybe the following will help you:
- Download TWRP Service ROM oeminfo and
Recovery_ramdisk for Oreo
- Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT.
- Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP
- Install TWRP over eRecovery (only read the principle, not download links)
- boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it.
- Go back to the main TWRP's menu, select Reboot and Turn off.
- Use three button combo and try to install Service ROM .
Note: you do everything at your own risk, I hope that's clear
Hi Alf,
thanks for reply,
worked like a charm !
Phone booted in official rom, was working well.
But..
If I try to download OTA update from menu, it shows me update to ANE-LX1 8.0.0.174(C432)-FULL size 2.92GB ,
but after downloading phone shows install error.
I did factory reset and cache clear, same result, can not install.
So I downloaded to SD card latest sw Huawei P20 Lite ( Nova 3e ) ANE-L21 ANE-L01 hw eu Anne-L01 9.1.0.370(C432E7R1P7T8) Firmware EMUI9.1.0 05014YXU [androidhost.ru].zip
but verify goes 5% then 6% then back to 5%, then 6% then shows "install failed"
After attempt to update by *#*#2846579#*#* from menu, phone did the same, 5% 6% 5% 6% "install failed", but after reboot I have attached photo error :-(
Now not booting again, stuck in this error.
So how can I update to some new sw ?
Do I have to use some special version to go higher?
Or is it some other problem?
BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet :-O
hdano said:
BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet
Click to expand...
Click to collapse
Yes, service ROM lock the bootloader , it's normal.
hdano said:
FRP locked,
Click to expand...
Click to collapse
You can unlock FRP manually in Developer options - "Enable OEM unlock".
Run again fastboot commands and post results.
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.009s]
finished. total time: 0.010s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.020s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.012s]
finished. total time: 0.013s
hdano said:
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.009s]
finished. total time: 0.010s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.020s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.012s]
finished. total time: 0.013s
Click to expand...
Click to collapse
Okay, now boot into eRecovery (not Recovery) and select option Download latest version and recovery.
This ***** sucks :-(
hdano said:
This ***** sucks
Click to expand...
Click to collapse
Try to install .174 Service ROM via dload method.
If you get Install failed error again, then you need unlock bootloader (if it's possible) and flash some partitions in fastboot.
You can use this tutorial . Use downloaded .174 ROM. Extract and flash
- kernel
-ramdisk
- recovery_ramdisk
- system
- cust
Note: cust.img can be found in update_ane-L21_hw_eu
Reboot and turn off the phone, then flash .174 Service ROM or try update via eRecovery.
C:\adb>fastboot flash kernel KERNEL.IMG
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.893s]
writing 'kernel'...
OKAY [ 0.388s]
finished. total time: 1.286s
C:\adb>fastboot flash ramdisk RAMDISK.IMG
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.602s]
writing 'ramdisk'...
OKAY [ 0.075s]
finished. total time: 0.681s
C:\adb>fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.208s]
writing 'recovery_ramdisk'...
OKAY [ 0.169s]
finished. total time: 1.381s
C:\adb>fastboot flash system SYSTEM.IMG
target reported max download size of 471859200 bytes
sending sparse 'system' 1/8 (460799 KB)...
OKAY [ 19.946s]
writing 'system' 1/8...
OKAY [ 3.866s]
sending sparse 'system' 2/8 (424020 KB)...
OKAY [ 17.042s]
writing 'system' 2/8...
OKAY [ 2.164s]
sending sparse 'system' 3/8 (458375 KB)...
OKAY [ 18.384s]
writing 'system' 3/8...
OKAY [ 2.219s]
sending sparse 'system' 4/8 (460418 KB)...
OKAY [ 18.557s]
writing 'system' 4/8...
OKAY [ 2.213s]
sending sparse 'system' 5/8 (425536 KB)...
OKAY [ 17.164s]
writing 'system' 5/8...
OKAY [ 2.157s]
sending sparse 'system' 6/8 (457971 KB)...
OKAY [ 19.231s]
writing 'system' 6/8...
OKAY [ 2.855s]
sending sparse 'system' 7/8 (460016 KB)...
OKAY [ 19.003s]
writing 'system' 7/8...
OKAY [ 3.147s]
sending sparse 'system' 8/8 (192362 KB)...
OKAY [ 7.791s]
writing 'system' 8/8...
OKAY [ 1.015s]
finished. total time: 156.792s
C:\adb>fastboot flash cust CUST.IMG
target reported max download size of 471859200 bytes
sending 'cust' (139283 KB)...
OKAY [ 5.096s]
writing 'cust'...
OKAY [ 0.794s]
finished. total time: 5.894s
C:\adb>fastboot reboot
rebooting...
Now the only I can get is this, no way to get in eRecovery
hdano said:
Now the only I can get is this, no way to get in eRecovery
Click to expand...
Click to collapse
Chinese??? Wow...
As I said before,
-Alf- said:
turn off the phone, then flash .174 Service ROM
Click to expand...
Click to collapse
Have you tried bro?
-Alf- said:
Chinese??? Wow...
As I said before,
Have you tried bro?
Click to expand...
Click to collapse
how? I can not get in eRecovery, only that chinese recovery or what it is....
hdano said:
how? I can not get in eRecovery, only that chinese recovery or what it is....
Click to expand...
Click to collapse
Service ROM has nothing to do with eRecovery.
As the bootloader got locked, I had to do the whole procedure again,
Board sw 1.0.0.39 , and
-Alf- said:
Download TWRP Service ROM oeminfo and
Recovery_ramdisk for Oreo
- Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT.
- Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP
- Install TWRP over eRecovery (only read the principle, not download links)
- boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it.
- Go back to the main TWRP's menu, select Reboot and Turn off.
- Use three button combo and try to install Service ROM .
Click to expand...
Click to collapse
But I can not get it to work state, 3 button combo always fails.
Can I just simply flash all needed files by fastboot ot TWRP ?
What are all the necessary files for phone to boot up?
- kernel
-ramdisk
- recovery_ramdisk
- system
- cust
what else?
Can I just simply flash some custom ROM that will boot up after TWRP flash ?
BTW, why it should not be possible to directly flash erecovery from fastboot?
For me worked..
C:\adb>fastboot flash erecovery_ramdisk TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'erecovery_ramdisk' (24790 KB)...
OKAY [ 0.660s]
writing 'erecovery_ramdisk'...
OKAY [ 0.128s]
finished. total time: 0.796s
hdano said:
what else?
Click to expand...
Click to collapse
Nothing.
But keep in mind, that "writing OKAY" does not mean that the file is actually installed (it is too long story to tell why...).
hdano said:
BTW, why it should not be possible to directly flash erecovery from fastboot?
For me worked..
Click to expand...
Click to collapse
Running working stock firmware it's impossible.
hdano said:
Hi,
Can someone please help me with fix of my P20 lite dual?
I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹
The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly"
Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7
Factory reset and cache wipe did not help.
Any attempt to SD or USB update via recovery failed, always got "Install failed"
So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP.
No luck, phone was in fastboot mode only or bootloops.
Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0)
With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK.
So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"?
Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message.
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Or is there some easy way to flash to official ?
Or did I messed up some system files that need to be fixed?
PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts.
Can be this a problem? (I hope not)
Thank you for any ideas !
Click to expand...
Click to collapse
I’ve exactly the same as your issue.
But I’ve no service and dual iemis are right!
What could be the problem, did you solve yours?
Or even were you having same no service issue while you were on this case?
My device originally is nova 3e ANE l-LX1 c185 dual sim and flashed oeminfo for c185 by editing the oeminfo for c432 and by using oeminfo tools.
Also using howta8 to change oeminfo.
It was changed ok to c185 but still no service and software not installed.
I used build 160 because it’s the only have 3 files, it was installed from hisuite document/hisuite/rom folder
RED HYDROGEN ONE
Android 9 ROM packageATTENTION: THIS PROCESS WILL WIPE ALL OF YOUR USER DATA. PROCEED AT YOUR OWN RISK. I am not responsible for your phone.
christian.farmerf provided an updated link to the ROM package. Thank you!The file below has the ADBWinAPI.dll file. https://mega.nz/file/D8UhUITA#fvFHE0tRHaFHqKZW5ikPokp026fhqn0UzOHZx2fzuDA
(Original Link)Here is the original link provided by member @114514Beast.
DOWNLOAD (GOOGLE DRIVE)
source
https://drive.google.com/file/d/1FvuqfC28e7tmVGjGDgCZixVpATKtT2sB/view?usp=sharing
@AumAum here's my thread for the Red Hydrogen One in case you want to help me get it going. Thanks
I have an unlocked AT&T variant but cannot reboot into fastboot. Holding down vol- and power from power-off only results in a looping RED logo.
Any ideas?
If I can get this working, I can dump a stock AT&T 8.0 ROM.
xeper said:
I have an unlocked AT&T variant but cannot reboot into fastboot. Holding down vol- and power from power-off only results in a looping RED logo.
Any ideas?
If I can get this working, I can dump a stock AT&T 8.0 ROM.
Click to expand...
Click to collapse
Try adb reboot bootloader
Mohsin6643 said:
Try adb reboot bootloader
Click to expand...
Click to collapse
Wow I feel dumb.
This worked before, but I didn't have an Android bootloader driver for the phone. :|
Updated the driver while it's in the bootloader and it works!
xeper said:
Wow I feel dumb.
This worked before, but I didn't have an Android bootloader driver for the phone. :|
Updated the driver while it's in the bootloader and it works!
Click to expand...
Click to collapse
Glad to know it all worked out. Bugjaeger for Android, works if you need ADB/Fastboot without a pc.
KlutchApex said:
Here is the best link provided by member @114514Beast.
DOWNLOAD (GOOGLE DRIVE)
source
Android 9 ROM package
ATTENTION: IT WILL WIPE ALL OF YOUR USER DATA
https://drive.google.com/file/d/1FvuqfC28e7tmVGjGDgCZixVpATKtT2sB/view?usp=sharing
Click to expand...
Click to collapse
This file does not contain the ADBWinAPI.dll file, but I have fixed it here:
File on MEGA
mega.nz
I excuted this command in fastboot,.
Fastboot erase modemst1 and same for modemst2.
Now no signal at all and imei is 0.
I have been flashing the phone with ur rom for 2days but not signal nor imei back.
Please, who can share me Qcn file for this phone, i Will be grateful for him.
Saloomy83 said:
I excuted this command in fastboot,.
Fastboot erase modemst1 and same for modemst2.
Now no signal at all and imei is 0.
I have been flashing the phone with ur rom for 2days but not signal nor imei back.
Please, who can share me Qcn file for this phone, i Will be grateful for him.
Click to expand...
Click to collapse
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
KlutchApex said:
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
Click to expand...
Click to collapse
I'm waiting for the file my friend. I hope you upload it as fast as u can.
I'm still waiting for the Qcn file, plz.
KlutchApex said:
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
Click to expand...
Click to collapse
I'm still here waiting for the file
KlutchApex said:
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
Click to expand...
Click to collapse
Friend , are you there? I'm still waiting for the Qcn file or efs back up , plz
KlutchApex said:
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
Click to expand...
Click to collapse
Friend, I'm really in trouble. I can't use my phone anymore. You can save my phone if you upload a dump for modemst1 and modemst2 or efs backup or QCN FILE OR NV .
Saloomy83 said:
Friend, I'm really in trouble. I can't use my phone anymore. You can save my phone if you upload a dump for modemst1 and modemst2 or efs backup or QCN FILE OR NV .
Click to expand...
Click to collapse
Give me your IMEI and other relevant info in a DM and I will send you the corrected files
Saloomy83 said:
I excuted this command in fastboot,.
Fastboot erase modemst1 and same for modemst2.
Now no signal at all and imei is 0.
I have been flashing the phone with ur rom for 2days but not signal nor imei back.
Please, who can share me Qcn file for this phone, i Will be grateful for him.
Click to expand...
Click to collapse
the QCN is included in the ROM
KlutchApex said:
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
Click to expand...
Click to collapse
What were you thinking erasing those partitions? Please follow the instructions correctly
KlutchApex said:
Give me your IMEI and other relevant info in a DM and I will send you the corrected
Click to expand...
Click to collapse
Thank u.
I have solved the problem
KlutchApex said:
the QCN is included in the ROM
Click to expand...
Click to collapse
Where?
Which one.
KlutchApex said:
What were you thinking erasing those partitions? Please follow the instructions correctly
Click to expand...
Click to collapse
Cuz when I was inserting my CDMA sim card , there was no service. I found some posts suggesting erasing these two partitions to solve the problem.
Saloomy83 said:
Im
Click to expand...
Click to collapse
Solved.
Or you can give me the file and I will edit it and add my IMEI and other information.
Hi for those people that doesnt know much;
This is for those that cant enter to fastboot , or hard bricked after update like me.
QFIL ROM FOR RED HYDROGEN ONE (NOT TITANIUM)
ROM
Respective credit in the post
1-To put in edl mode you need to hold volume up and down , with power botom holding;
you will see In device manager Something like this
{
"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"
}
2- you need to Install Qfill. ONLY qfil NOT drivers...
If you install Newest Qfil driver you may see " qualcomm hs usb qdloader 9008 " and your flash will give you errors ,
QFIL Download
Drivers TO solve QUSB_BULK DOWNLOAD
3- You need to disable signature drivers (Windows)
Install manually , updating Qusb_BULK like the image
Here How to install .INF drivers (IN GENERAL)
3- In Qfil You import all files like this
3.1 ONLY select Rawprogram 0 to 3
IF you select the umparsed you will have filehose error.
4. Select Patchs 0 to 4 ... and flash
Who has att stock Rom? Tell me where to download. How to restore the att version?
about device
(bootloader) Model:H1A1000
(bootloader) version-baseband:MPSS.AT.2.0.c4-00933-8998
(bootloader) display-id:H1A1000.007ho.01.01.01r.230
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot getvar current-slot
vendor.img from firmware H1A1000.082ho.01.00.10r.118_userdebug_fastboot
userdata.img from firmware H1A1000.082ho.01.00.10r.118_userdebug_fastboot
I installed TWRP-3.5.0_9-0-V2-Hydrogenone.img
The touch did not work
I took the mouse and OTG and unlocked the screen
Made a backup att firmware
got a bootloop
I mixed up the firmware and vendor in the phone
got a phone with a non-working Wi-Fi
I mixed Boot.img, System.img and Vendor.img from rundom firmware and finaly start the wi-fi.
To launch Wi-Fi, I sewed TWRP-3.5.0_9-0-V2-hydrogenone.img and restored the Vendor section from ATT
then
fastboot erase system_b
fastboot erase vendor_b
fastboot erase userdata
fastboot flash -S 100M system_b PixelExperience_ARM64AB-10.0-20200118-2138-GSI.img
fastboot flash -S 100M vendor_b vendor_118.img
fastboot flash userdata userdata.img
fastboot flash boot magisk_patched_9.pkq1.190118.001_118.img
fastboot rebot
Wi-Fi turned on. The camera works. SIM works
repeated everything for Slot a
bugs:
then phone is off and charging screen light is on.
KlutchApex said:
RED HYDROGEN ONE
Android 9 ROM packageATTENTION: THIS PROCESS WILL WIPE ALL OF YOUR USER DATA. PROCEED AT YOUR OWN RISK. I am not responsible for your phone.
christian.farmerf provided an updated link to the ROM package. Thank you!The file below has the ADBWinAPI.dll file. https://mega.nz/file/D8UhUITA#fvFHE0tRHaFHqKZW5ikPokp026fhqn0UzOHZx2fzuDA
(Original Link)Here is the original link provided by member @114514Beast.
DOWNLOAD (GOOGLE DRIVE)
source
https://drive.google.com/file/d/1FvuqfC28e7tmVGjGDgCZixVpATKtT2sB/view?usp=sharing
Click to expand...
Click to collapse
I FLASH BUT STUCK ON LOGO
EDL FLASH Waiting for HS-USB QDLoader 9008... COM43
Connecting to device... OK
Writing flash programmer... OK
Connecting to flash programmer... OK
Configuring device... OK
Setting boot LUN1... OK
Firehose config : UFS [Sector:4096] [Target:4096] [Host:1048576]
Processing LUN0 - rawprogram0.xml
Writing persist [ext4:32 MiB]->persist [8]... OK 1.102s
Writing system.img [sparse:3.49 GiB]->system_a... OK 152.018s
Writing vendor.img [sparse:565.78 MiB]->vendor_a... OK 21.497s
Writing userdata.img [sparse:5.49 MiB]->userdata... OK 1.222s
Writing gpt_main0.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup0.bin [raw:20 KiB]->BackupGPT... OK 0.103s
Applying patch0.xml... OK
Processing LUN1 - rawprogram1.xml
Writing xbl.elf [elf:2.56 MiB]->xbl_a... OK 0.164s
Writing gpt_main1.bin [raw:24 KiB]->PrimaryGPT... OK 0.105s
Writing gpt_backup1.bin [raw:20 KiB]->BackupGPT... OK 0.103s
Applying patch1.xml... OK
Processing LUN2 - rawprogram2.xml
Writing xbl.elf [elf:2.56 MiB]->xbl_b... OK 0.167s
Writing gpt_main2.bin [raw:24 KiB]->PrimaryGPT... OK 0.106s
Writing gpt_backup2.bin [raw:20 KiB]->BackupGPT... OK 0.104s
Applying patch2.xml... OK
Processing LUN3 - rawprogram3.xml
Writing gpt_main3.bin [raw:24 KiB]->PrimaryGPT... OK 0.054s
Writing gpt_backup3.bin [raw:20 KiB]->BackupGPT... OK 0.103s
Applying patch3.xml... OK
Processing LUN4 - rawprogram_unsparse0.xml
Writing persist [ext4:32 MiB]->persist [8]... OK 0.901s
system_a->system_1.img is not exists!!!
system_a->system_2.img is not exists!!!
system_a->system_3.img is not exists!!!
system_a->system_4.img is not exists!!!
system_a->system_5.img is not exists!!!
system_a->system_6.img is not exists!!!
system_a->system_7.img is not exists!!!
system_a->system_8.img is not exists!!!
system_a->system_9.img is not exists!!!
system_a->system_10.img is not exists!!!
system_a->system_11.img is not exists!!!
system_a->system_12.img is not exists!!!
system_a->system_13.img is not exists!!!
vendor_a->vendor_1.img is not exists!!!
vendor_a->vendor_2.img is not exists!!!
vendor_a->vendor_3.img is not exists!!!
vendor_a->vendor_4.img is not exists!!!
vendor_a->vendor_5.img is not exists!!!
vendor_a->vendor_6.img is not exists!!!
vendor_a->vendor_7.img is not exists!!!
vendor_a->vendor_8.img is not exists!!!
userdata->userdata_1.img is not exists!!!
userdata->userdata_2.img is not exists!!!
userdata->userdata_3.img is not exists!!!
userdata->userdata_4.img is not exists!!!
userdata->userdata_5.img is not exists!!!
userdata->userdata_6.img is not exists!!!
userdata->userdata_7.img is not exists!!!
userdata->userdata_8.img is not exists!!!
userdata->userdata_9.img is not exists!!!
userdata->userdata_10.img is not exists!!!
userdata->userdata_11.img is not exists!!!
userdata->userdata_12.img is not exists!!!
userdata->userdata_13.img is not exists!!!
userdata->userdata_14.img is not exists!!!
userdata->userdata_15.img is not exists!!!
userdata->userdata_16.img is not exists!!!
userdata->userdata_17.img is not exists!!!
userdata->userdata_18.img is not exists!!!
userdata->userdata_19.img is not exists!!!
userdata->userdata_20.img is not exists!!!
userdata->userdata_21.img is not exists!!!
userdata->userdata_22.img is not exists!!!
userdata->userdata_23.img is not exists!!!
userdata->userdata_24.img is not exists!!!
userdata->userdata_25.img is not exists!!!
userdata->userdata_26.img is not exists!!!
userdata->userdata_27.img is not exists!!!
userdata->userdata_28.img is not exists!!!
userdata->userdata_29.img is not exists!!!
userdata->userdata_30.img is not exists!!!
userdata->userdata_31.img is not exists!!!
userdata->userdata_32.img is not exists!!!
userdata->userdata_33.img is not exists!!!
userdata->userdata_34.img is not exists!!!
userdata->userdata_35.img is not exists!!!
userdata->userdata_36.img is not exists!!!
userdata->userdata_37.img is not exists!!!
userdata->userdata_38.img is not exists!!!
userdata->userdata_39.img is not exists!!!
userdata->userdata_40.img is not exists!!!
userdata->userdata_41.img is not exists!!!
userdata->userdata_42.img is not exists!!!
userdata->userdata_43.img is not exists!!!
userdata->userdata_44.img is not exists!!!
userdata->userdata_45.img is not exists!!!
userdata->userdata_46.img is not exists!!!
userdata->userdata_47.img is not exists!!!
userdata->userdata_48.img is not exists!!!
userdata->userdata_49.img is not exists!!!
userdata->userdata_50.img is not exists!!!
userdata->userdata_51.img is not exists!!!
userdata->userdata_52.img is not exists!!!
userdata->userdata_53.img is not exists!!!
userdata->userdata_54.img is not exists!!!
userdata->userdata_55.img is not exists!!!
userdata->userdata_56.img is not exists!!!
userdata->userdata_57.img is not exists!!!
userdata->userdata_58.img is not exists!!!
userdata->userdata_59.img is not exists!!!
userdata->userdata_60.img is not exists!!!
userdata->userdata_61.img is not exists!!!
userdata->userdata_62.img is not exists!!!
userdata->userdata_63.img is not exists!!!
userdata->userdata_64.img is not exists!!!
userdata->userdata_65.img is not exists!!!
userdata->userdata_66.img is not exists!!!
userdata->userdata_67.img is not exists!!!
userdata->userdata_68.img is not exists!!!
userdata->userdata_69.img is not exists!!!
userdata->userdata_70.img is not exists!!!
Writing gpt_main0.bin [raw:24 KiB]->PrimaryGPT... OK 0.054s
Writing gpt_backup0.bin [raw:20 KiB]->BackupGPT... OK 0.104s
Applying patch4.xml... OK
Processing LUN5 - rawprogram_unsparse4.xml
Writing rpm.mbn [elf:228.19 KiB]->rpm_a... OK 0.107s
Writing tz.mbn [elf:1.82 MiB]->tz_a... OK 0.147s
Writing hyp.mbn [elf:264 KiB]->hyp_a... OK 0.109s
Writing pmic.elf [elf:49.94 KiB]->pmic_a... OK 0.104s
Writing NON-HLOS.bin [fat:104.05 MiB]->modem_a... OK 3.764s
Writing BTFM.bin [fat:412 KiB]->bluetooth_a... OK 0.114s
Writing mdtpsecapp.mbn [elf:1.03 MiB]->mdtpsecapp_a... OK 0.128s
Writing mdtp.img [raw:16.98 MiB]->mdtp_a... OK 1.039s
Writing abl.elf [elf:148 KiB]->abl_a... OK 0.098s
Writing keymaster64.mbn [elf:308.66 KiB]->keymaster_a... OK 0.078s
Writing boot.img [kernel:44.34 MiB]->boot_a... OK 1.300s
Writing cmnlib.mbn [elf:221.32 KiB]->cmnlib_a... OK 0.108s
Writing cmnlib64.mbn [elf:292.71 KiB]->cmnlib64_a... OK 0.111s
Writing devcfg.mbn [elf:56.84 KiB]->devcfg_a... OK 0.104s
Writing adspso.bin [ext4:16 MiB]->dsp_a... OK 0.603s
Writing rpm.mbn [elf:228.19 KiB]->rpm_b... OK 0.110s
Writing tz.mbn [elf:1.82 MiB]->tz_b... OK 0.247s
Writing hyp.mbn [elf:264 KiB]->hyp_b... OK 0.110s
Writing pmic.elf [elf:49.94 KiB]->pmic_b... OK 0.105s
Writing NON-HLOS.bin [fat:104.05 MiB]->modem_b... OK 2.989s
Writing BTFM.bin [fat:412 KiB]->bluetooth_b... OK 0.113s
Writing mdtpsecapp.mbn [elf:1.03 MiB]->mdtpsecapp_b... OK 0.128s
Writing mdtp.img [raw:16.98 MiB]->mdtp_b... OK 0.677s
Writing abl.elf [elf:148 KiB]->abl_b... OK 0.108s
Writing keymaster64.mbn [elf:308.66 KiB]->keymaster_b... OK 0.111s
Writing boot.img [kernel:44.34 MiB]->boot_b... OK 2.009s
Writing cmnlib.mbn [elf:221.32 KiB]->cmnlib_b... OK 0.110s
Writing cmnlib64.mbn [elf:292.71 KiB]->cmnlib64_b... OK 0.109s
Writing devcfg.mbn [elf:56.84 KiB]->devcfg_b... OK 0.105s
Writing adspso.bin [ext4:16 MiB]->dsp_b... OK 0.493s
Writing splash.img [raw:10.56 MiB]->splash... OK 0.389s
Writing logfs_ufs_8mb.bin [fat:16 KiB]->logfs... OK 0.104s
Writing storsec.mbn [elf:48.02 KiB]->storsec... OK 0.104s
otafs->otafs_ufs_2gb_1.img is not exists!!!
otafs->otafs_ufs_2gb_2.img is not exists!!!
otafs->otafs_ufs_2gb_3.img is not exists!!!
otafs->otafs_ufs_2gb_4.img is not exists!!!
otafs->otafs_ufs_2gb_5.img is not exists!!!
otafs->otafs_ufs_2gb_6.img is not exists!!!
otafs->otafs_ufs_2gb_7.img is not exists!!!
otafs->otafs_ufs_2gb_8.img is not exists!!!
otafs->otafs_ufs_2gb_9.img is not exists!!!
otafs->otafs_ufs_2gb_10.img is not exists!!!
otafs->otafs_ufs_2gb_11.img is not exists!!!
otafs->otafs_ufs_2gb_12.img is not exists!!!
otafs->otafs_ufs_2gb_13.img is not exists!!!
otafs->otafs_ufs_2gb_14.img is not exists!!!
otafs->otafs_ufs_2gb_15.img is not exists!!!
otafs->otafs_ufs_2gb_16.img is not exists!!!
otafs->otafs_ufs_2gb_17.img is not exists!!!
otafs->otafs_ufs_2gb_18.img is not exists!!!
otafs->otafs_ufs_2gb_19.img is not exists!!!
otafs->otafs_ufs_2gb_20.img is not exists!!!
otafs->otafs_ufs_2gb_21.img is not exists!!!
Writing gpt_main4.bin [raw:24 KiB]->PrimaryGPT... OK 0.104s
Writing gpt_backup4.bin [raw:20 KiB]->BackupGPT... OK 0.104s
Rebooting... OK
Total transfer : 4.43 GiB
Transfer Speed : 23.36 MiB/s
UNLOCKTOOL 2022.10.05.2
Elapsed time : 3 minutes 48 seconds
KlutchApex said:
RED HYDROGEN ONE
Android 9 ROM packageATTENTION: THIS PROCESS WILL WIPE ALL OF YOUR USER DATA. PROCEED AT YOUR OWN RISK. I am not responsible for your phone.
christian.farmerf provided an updated link to the ROM package. Thank you!The file below has the ADBWinAPI.dll file. https://mega.nz/file/D8UhUITA#fvFHE0tRHaFHqKZW5ikPokp026fhqn0UzOHZx2fzuDA
(Original Link)Here is the original link provided by member @114514Beast.
DOWNLOAD (GOOGLE DRIVE)
source
https://drive.google.com/file/d/1FvuqfC28e7tmVGjGDgCZixVpATKtT2sB/view?usp=sharing
Click to expand...
Click to collapse
HOW I RESTORD MY PHONE
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