Error While try to Flash firmware with MI Flash tool - Redmi Note 8 Pro Questions & Answers

Hi!
When im try to flash the firmware i recive that error:
"failed remote:failed to check sparse crc"
this is the first time i get that error....
any help?
{
"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"
}

Try to override checks by editing the batch command file.
Locate the batch command, open with your text editor, remove everything before something like "fastboot flash *** ***.img", run the command.

Try unofficial mi flash toolv2. It's best and lag free.

kekesed97 said:
Try to override checks by editing the batch command file.
Locate the batch command, open with your text editor, remove everything before something like "fastboot flash *** ***.img", run the command.
Click to expand...
Click to collapse
Hey!
Can u be more specific?
Also its weird....because im used many time the same firmware and i never received this error....
why im reveiving now that error and never in the past???

This is what FLASH ALL.BAT has:
also i want to know why i receiving that error if in the past i never received....
if exist %~dp0images\anti_version.txt (for /f "delims==" %%a in (%~dp0images\anti_version.txt) do (set CURRENT_ANTI_VER=%%a))
if [%CURRENT_ANTI_VER%] EQU [] set CURRENT_ANTI_VER=0
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
set anticheck="antirollback check pass"
if %version% GTR %CURRENT_ANTI_VER% set anticheck="Current device antirollback version is greater than this pakcage"
echo %anticheck% | findstr /r /c:"pass" || @ECHO "Antirollback check error" && exit /B 1
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *begonia" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *begonia" || exit /B 1
fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
fastboot %* erase boot || @ECHO "Erase boot error" && exit /B 1
fastboot %* flash preloader %~dp0images\preloader_begonia.bin || @ECHO "Flash preloader error" && exit /B 1
fastboot %* flash lk %~dp0images\lk.img || @ECHO "Flash lk error" && exit /B 1
fastboot %* flash lk2 %~dp0images\lk.img || @ECHO "Flash lk2 error" && exit /B 1
fastboot %* flash tee1 %~dp0images\tee.img || @ECHO "Flash tee1 error" && exit /B 1
fastboot %* flash tee2 %~dp0images\tee.img || @ECHO "Flash tee2 error" && exit /B 1
fastboot %* flash sspm_1 %~dp0images\sspm.img || @ECHO "Flash sspm_1 error" && exit /B 1
fastboot %* flash sspm_2 %~dp0images\sspm.img || @ECHO "Flash sspm_2 error" && exit /B 1
fastboot %* flash gz1 %~dp0images\gz.img || @ECHO "Flash gz1 error" && exit /B 1
fastboot %* flash gz2 %~dp0images\gz.img || @ECHO "Flash gz2 error" && exit /B 1
fastboot %* flash scp1 %~dp0images\scp.img || @ECHO "Flash scp1 error" && exit /B 1
fastboot %* flash scp2 %~dp0images\scp.img || @ECHO "Flash scp2 error" && exit /B 1
fastboot %* flash logo %~dp0images\logo.bin || @ECHO "Flash logo error" && exit /B 1
fastboot %* flash dtbo %~dp0images\dtbo.img || @ECHO "Flash dtbo error" && exit /B 1
fastboot %* flash spmfw %~dp0images\spmfw.img || @ECHO "Flash spmfw error" && exit /B 1
fastboot %* flash exaid %~dp0images\exaid.img || @ECHO "Flash exaid error" && exit /B 1
fastboot %* flash oem_misc1 %~dp0images\oem_misc1.img || @ECHO "Flash oem_misc1 error" && exit /B 1
fastboot %* flash md1img %~dp0images\md1img.img || @ECHO "Flash md1img error" && exit /B 1
fastboot %* flash cam_vpu1 %~dp0images\cam_vpu1.img || @ECHO "Flash cam_vpu1 error" && exit /B 1
fastboot %* flash cam_vpu2 %~dp0images\cam_vpu2.img || @ECHO "Flash cam_vpu2 error" && exit /B 1
fastboot %* flash cam_vpu3 %~dp0images\cam_vpu3.img || @ECHO "Flash cam_vpu3 error" && exit /B 1
fastboot %* flash audio_dsp %~dp0images\audio_dsp.img || @ECHO "Flash audio_dsp error" && exit /B 1
fastboot %* flash vendor %~dp0images\vendor.img || @ECHO "Flash vendor error" && exit /B 1
fastboot %* flash system %~dp0images\system.img || @ECHO "Flash system error" && exit /B 1
fastboot %* flash cache %~dp0images\cache.img || @ECHO "Flash cache error" && exit /B 1
fastboot %* flash recovery %~dp0images\recovery.img || @ECHO "Flash recovery error" && exit /B 1
fastboot %* flash cust %~dp0images\cust.img || @ECHO "Flash cust error" && exit /B 1
fastboot %* flash vbmeta %~dp0images\vbmeta.img || @ECHO "Flash vbmeta error" && exit /B 1
fastboot %* flash userdata %~dp0images\userdata.img || @ECHO "Flash userdata error" && exit /B 1
fastboot %* flash boot %~dp0images\boot.img || @ECHO "Flash boot error" && exit /B 1
fastboot %* reboot || @ECHO "Reboot error" && exit /B 1

roberto_1986 said:
Hey!
Can u be more specific?
Also its weird....because im used many time the same firmware and i never received this error....
why im reveiving now that error and never in the past???
Click to expand...
Click to collapse
Don't use flash all. It will erase all the partition, including your data.
I was away from my computer so sorry if my answer is vague.
Erase everything before "fastboot erase boot || bla bla bla". It basically overriding checks.

kekesed97 said:
Don't use flash all. It will erase all the partition, including your data.
I was away from my computer so sorry if my answer is vague.
Erase everything before "fastboot erase boot || bla bla bla". It basically overriding checks.
Click to expand...
Click to collapse
Well ty but idk whats happened but i received another error but i was able to install the firmware on my phone and the weird thing is that was already unlocked it....then im flash again the firmware and i was able to install without problem

anyc solution on flash preloader error?

Related

Android Pay not working?

So I'm on the M5s Plus and Android Pay doesn't work.
Does Pay work on the Mi5s?
When attempting to add a card, error says:
Android Pay can't be used
Google is unable to verify that your device or the software running on it is Android compatible
MIUI Global 8.0.1.0
Check your version again, there is no 8.0.1.0. Official release is 8.0.10.0, "global custom rom" is 8.0.10.0.0. If you have the second one, there it probably doesn't work because your bootloader is unlocked.
If you indeed have the rare original Chinese/English ROM, then go into settings -> connections -> NFC and there somewhere (I sadly don't yet have the phone) you have to switch from MI Pay to the other possible setting. Then it should work.
hey thanks for the input. Am definitely on 8.0.1.0 here.
i tried your suggestion and switched the nfc pay method but that didn't help so it must be detecting something in the rom. this is rather curious
Oohh you're a Plus user, didn't read that when I replied the first time. Yeah there the software releases are different. Your SIM card is payment enabled? I needed a new sim card when I tried this the last time here, but not with Android Pay, as we don't have that yet here.
Anyway found this: http://en.miui.com/forum.php?mod=viewthread&tid=402053&extra=&highlight=android+pay&page=2
Sounds like there is a bug in the new Global Release of MIUI official
Here the official manual on how to enable it: http://en.miui.com/thread-405166-1-1.html
I have Mi5s plus on same Global Rom. I had to lock boot loader for android pay to work.
Sent from my iPad using Tapatalk
How to relock the bootloader? I try to use "fastboot oem lock" to relock the bootloader. After reboot the phone, the bootloader is still unlock. What's wrong? I am using Xiaomi Mi 5s.
You can relock in miflash, but I don't know if that works without flashing it.
I compared the two .bat files (flash_all.bat and flash_all_lock.bat) and the difference is this:
fastboot %* flash userdata %~dp0images\userdata.img || @ECHO "Flash userdata error" && exit /B 1
fastboot %* erase devinfo || @ECHO "Erase devinfo error" && exit /B 1
I don't exactly know what those commands do, so I wouldn't execute them!
The .sh file has those differences:
fastboot $* erase devinfo
if [ $? -ne 0 ] ; then echo "Erase devinfo error"; exit 1; fi
So for me it looks like the erase devinfo file is the re-lock command, not sure why that should do it tough.
In MiFlash you could try this command flash_all_except_storage.bat. That would flash your phone again, but should not delete your apps and data, but I'm not entirely sure
I also tried to use flash_all_lock.bat to flash the global ROM. After flashing the ROM successfully, the unlock status shown by "fastboot oem device-info" is true also. I think the boot loader is also unlocked, and I can't pass the CTS profile test so that I can't use Android Pay.
patoberli said:
You can relock in miflash, but I don't know if that works without flashing it.
I compared the two .bat files (flash_all.bat and flash_all_lock.bat) and the difference is this:
fastboot %* flash userdata %~dp0images\userdata.img || @ECHO "Flash userdata error" && exit /B 1
fastboot %* erase devinfo || @ECHO "Erase devinfo error" && exit /B 1
I don't exactly know what those commands do, so I wouldn't execute them!
The .sh file has those differences:
fastboot $* erase devinfo
if [ $? -ne 0 ] ; then echo "Erase devinfo error"; exit 1; fi
So for me it looks like the erase devinfo file is the re-lock command, not sure why that should do it tough.
In MiFlash you could try this command flash_all_except_storage.bat. That would flash your phone again, but should not delete your apps and data, but I'm not entirely sure
Click to expand...
Click to collapse
That's weird. I unlocked my phone (to be able to flash global rom) and then flashed it with the lock option and it passes the CTS test.
Chinese stable rom(MIUI 8.0.22) not working with android pay and octopus card

[Help] Flashing fastboot ROM (China Dev 7.6.8), cannot flash crclist.txt

I have tried 2 version of MiFlash :
7.4.25 gave me "Length cannot be less than zero error", so I changed to MiFlash Beta as has been suggested here
My PC definitely reckon the device in fastboot mode. fastboot devices showed the device is detected. It's just both version of MiFlash failed to recognize it.
I have tried to Update Driver on "Android Bootloader Interface". Out of 4 similar options I have tried (see attached pic), it doesn't make MiFlash recognize the phone. I have also tried to "search automatically" for updated driver.
MiFlash still doesn't recognize the phone.
second pic :
adb devices from the system -> recognized
fastboot devices from fastboot mode -> recognized
but MiFlash didn't detect the device.
So I'm kinda stuck. Any suggestion?
I'm using Win7 SP1, Official TWRP 3.1.1, and Xiaomi.eu ROM 7.5.19
If your device is recognized in fastboot /device manager then I guess it's a Mi flash problem. Try other Mi flash version. Maybe will do the trick.
Additional attempts I have tried :
- Install Mi PC Suit manager : nope, Mi PC Suite manager can't detect the device
- fastboot oem edl : command prompt says OKAY, but the device is turned off
- Because the adb and fastboot in MiFlash's Source\ThirdParty\Google\Android folder can't detect my device, I tried to replace them with the working adb and fastboot. Executing adb and fastboot via cmd can detect my device, but MiFlash still can't detect the device.
Tried to install MiFlash on my laptop, got the phone detected. But flashing China Dev 7.6.8 has problem
If I go with clean all but save user data, I got this from the log
Code:
[20:57:25 a3f1f00c]:MiFlash 2017.4.25.0
[20:57:25 a3f1f00c]:image path:C:\Mi6ROM\sagit
[20:57:25 a3f1f00c]:env android path:"C:\Mi6\XiaoMiFlash\Source\ThirdParty\Google\Android"
[20:57:25 a3f1f00c]:script :C:\Mi6ROM\sagit\flash_all_except_storage.bat
[20:57:26 a3f1f00c]:Physical Memory Usage:147456 Byte
[20:57:26 a3f1f00c]:$fastboot -s a3f1f00c getvar product 2>&1 | findstr /r /c:"^product: *sagit" || echo Missmatching image and device
[20:57:26 a3f1f00c]:product: sagit
[20:57:26 a3f1f00c]:$fastboot -s a3f1f00c getvar product 2>&1 | findstr /r /c:"^product: *sagit" || exit /B 1
[20:57:26 a3f1f00c]:product: sagit
[20:57:26 a3f1f00c]:$set CURRENT_ANTI_VER=1
[20:57:26 a3f1f00c]:$for /F "tokens=2 delims=: " %i in ('fastboot -s a3f1f00c getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
[20:57:26 a3f1f00c]:$(set version=1 )
[20:57:26 a3f1f00c]:$if [1] EQU [] set version=0
[20:57:26 a3f1f00c]:$if 1 GTR 1 (
[20:57:26 a3f1f00c]:echo current device antirollback version is greater than this pakcage
[20:57:26 a3f1f00c]: exit /B 1
[20:57:26 a3f1f00c]:)
[20:57:26 a3f1f00c]:$fastboot -s a3f1f00c erase boot ||
[20:57:26 a3f1f00c]:erasing 'boot'...
[20:57:26 a3f1f00c]:eek:KAY [ -0.000s]
[20:57:26 a3f1f00c]:finished. total time: -0.000s
[20:57:26 a3f1f00c]:$fastboot -s a3f1f00c flash crclist C:\Mi6ROM\sagit\images\crclist.txt ||
[20:57:26 a3f1f00c]:target reported max download size of 536870912 bytes
[20:57:26 a3f1f00c]:sending 'crclist' (0 KB)...
[20:57:26 a3f1f00c]:eek:KAY [ 0.000s]
[20:57:26 a3f1f00c]:writing 'crclist'...
[20:57:26 a3f1f00c]:error:FAILED (remote: update crc list failed)
[20:57:26 a3f1f00c]:"Flash crclist error"
[20:57:26 a3f1f00c]:error:FAILED (remote: update crc list failed)
[20:57:26 a3f1f00c]:process exit.
[20:57:26 a3f1f00c]:flashSuccess False
[20:57:26 a3f1f00c]:isFactory False CheckCPUID False
[20:57:26 a3f1f00c]:before:flashSuccess is False set IsUpdate:True set IsDone True
[20:57:26 a3f1f00c]:after:flashSuccess is False set IsUpdate:false set IsDone true
If I go with clean all, I got this
Code:
[21:00:53 a3f1f00c]:MiFlash 2017.4.25.0
[21:00:53 a3f1f00c]:image path:C:\Mi6ROM\sagit
[21:00:53 a3f1f00c]:env android path:"C:\Mi6\XiaoMiFlash\Source\ThirdParty\Google\Android"
[21:00:53 a3f1f00c]:script :C:\Mi6ROM\sagit\flash_all_except_storage.bat
[21:00:53 a3f1f00c]:Physical Memory Usage:147456 Byte
[21:00:53 a3f1f00c]:$fastboot -s a3f1f00c getvar product 2>&1 | findstr /r /c:"^product: *sagit" || echo Missmatching image and device
[21:00:53 a3f1f00c]:product: sagit
[21:00:53 a3f1f00c]:$fastboot -s a3f1f00c getvar product 2>&1 | findstr /r /c:"^product: *sagit" || exit /B 1
[21:00:53 a3f1f00c]:product: sagit
[21:00:53 a3f1f00c]:$set CURRENT_ANTI_VER=1
[21:00:53 a3f1f00c]:$for /F "tokens=2 delims=: " %i in ('fastboot -s a3f1f00c getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
[21:00:53 a3f1f00c]:$(set version=1 )
[21:00:53 a3f1f00c]:$if [1] EQU [] set version=0
[21:00:53 a3f1f00c]:$if 1 GTR 1 (
[21:00:53 a3f1f00c]:echo current device antirollback version is greater than this pakcage
[21:00:53 a3f1f00c]: exit /B 1
[21:00:53 a3f1f00c]:)
[21:00:53 a3f1f00c]:$fastboot -s a3f1f00c erase boot ||
[21:00:53 a3f1f00c]:erasing 'boot'...
[21:00:53 a3f1f00c]:eek:KAY [ 0.002s]
[21:00:53 a3f1f00c]:finished. total time: 0.002s
[21:00:53 a3f1f00c]:$fastboot -s a3f1f00c flash crclist C:\Mi6ROM\sagit\images\crclist.txt ||
[21:00:53 a3f1f00c]:target reported max download size of 536870912 bytes
[21:00:53 a3f1f00c]:sending 'crclist' (0 KB)...
[21:00:53 a3f1f00c]:eek:KAY [ 0.000s]
[21:00:53 a3f1f00c]:writing 'crclist'...
[21:00:53 a3f1f00c]:error:"Flash crclist error"
[21:00:53 a3f1f00c]:"Flash crclist error"
[21:00:53 a3f1f00c]:error:"Flash crclist error"
[21:00:53 a3f1f00c]:process exit.
[21:00:53 a3f1f00c]:flashSuccess False
[21:00:53 a3f1f00c]:isFactory False CheckCPUID False
[21:00:53 a3f1f00c]:before:flashSuccess is False set IsUpdate:True set IsDone True
[21:00:53 a3f1f00c]:after:flashSuccess is False set IsUpdate:false set IsDone true
Notice that crclist being sent is empty (0 KB), but the path (C:\Mi6ROM\sagit\images\crclist.txt) is correct.
Here's the content of crclist.txt
Code:
CRC-LIST
cmnlib 0x7d88792d
storsec 0x35f86924
keymasterbak 0x372ec484
cust 0xc1e5c6bc
abl 0xb36e450d
misc 0xd8f49994
pmicbak 0x8512f438
keymaster 0x372ec484
bluetooth 0x796c778e
cmnlib64 0xd2b02789
logo 0x57035ea1
cmnlib64bak 0xd2b02789
rpm 0x630680f
hypbak 0xf7b9a0a0
userdata 0xf671e3a1
tz 0x794c524a
recovery 0xb0584b02
cmnlibbak 0x7d88792d
ablbak 0xb36e450d
cache 0xc7fcb051
boot 0x430e7a99
xblbak 0xd1d418e2
dsp 0xaa1f8735
tzbak 0x794c524a
hyp 0xf7b9a0a0
xbl 0xd1d418e2
splash 0xe75e093d
rpmbak 0x630680f
modem 0x39d79144
pmic 0x8512f438
devcfg 0x2ccefd3b
Phone couldn't enter system, good thing I backed up boot, recovery, and EFS in TWRP, so that's easily got solved.
Anyway, any idea what can I do to solve this crclist error?
I'm wondering if my target reported max download size 536870912 bytes is actually an error.
This guy said it's an error. But from my log, it doesn't say it's an error.
Maybe I should try the other version of MiFlash (Beta) for this? :/

I need two .img

Does anyone have both
userdata.img
And the
aboot.img
If so the downloads for them will be great please and thank you.
Just download the latest firmware from the official source and extract the needed files.
https://en.miui.com/download-354.html
InfinityXDA said:
Does anyone have both
userdata.img
And the
aboot.img
If so the downloads for them will be great please and thank you.
Click to expand...
Click to collapse
Since you asked for the aboot, I guess you ask for 9.6.11.0...
Here it is: aboot and userdata
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
thorin0815 said:
Just download the latest firmware from the official source and extract the needed files.
https://en.miui.com/download-354.html
Click to expand...
Click to collapse
There´s no aboot included...
Voodoojonny said:
There´s no aboot included...
Click to expand...
Click to collapse
fastboot %* flash aboot_a %~dp0\images\emmc_appsboot.mbn || @ECHO "Flash aboot_a error" && exit /B 1
fastboot %* flash aboot_b %~dp0\images\emmc_appsboot.mbn || @ECHO "Flash aboot_b error" && exit /B 1
Taken from the flash_all.bat and the file images\emmc_appsboot.mbn is definately inside the archive.
thorin0815 said:
fastboot %* flash aboot_a %~dp0\images\emmc_appsboot.mbn || @ECHO "Flash aboot_a error" && exit /B 1
fastboot %* flash aboot_b %~dp0\images\emmc_appsboot.mbn || @ECHO "Flash aboot_b error" && exit /B 1
Taken from the flash_all.bat and the file images\emmc_appsboot.mbn is definately inside the archive.
Click to expand...
Click to collapse
strange... But under images, there´s no aboot.img - only if you extract ota´s, but not inside the fastboot rom image folder...
Voodoojonny said:
strange... But under images, there´s no aboot.img - only if you extract ota´s, but not inside the fastboot rom image folder...
Click to expand...
Click to collapse
It's just not named aboot, nevertheless it's there.
Voodoojonny said:
Since you asked for the aboot, I guess you ask for 9.6.11.0...
Here it is: aboot and userdata
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
There´s no aboot included...
Click to expand...
Click to collapse
After flashing got the system is destroyed I will fix it later though

Question Is there any salvation from this?

Hello guys, I created this account because I think I have bricked my Poco F3 badly, but you guys may know how to recover from 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"
}
How did I get here:
This is the first time I try to install a custom rom on any Android phone, nevertheless I followed tutorials step by step on how to unlock the device (I waited 136 hours as instructed) and then I was able to install TWRP first to RAM, and then as a recovery tool as stated in the tutorial I followed. I tried installing LineageOS following this tutorial (in Spanish) but it got seemingly stuck at "step 2/2" stating: "to flash additional zips please reboot recovery", so then I rebooted but this is where things spiraled out of control... After rebooting I was greeted by LineageOS boot logo animation, but it didn't do boot even after 10 minutes, so then I attempted to reboot in recovery by pressing Vol Up+Power, but was greeted by a Recovery tool by LineageOS instead of TWRP, which didn't let me do anything, so then I though "maybe I should do a factory reset and start all over", after which the whole thing wiped.
Now when rebooting it always takes me to LineageOS recovery tool, but now my PC won't recognize the device as storage, it just recognizes it as "Android Bootloader Interface", but CMD doesn't recognize it anymore...
Any idea how to fix this mess? I'm kinda desperate at this point
donwload sdk platform tools
extract it
in file explorer url type cmd it will show cmd
hold power and volume down to your phone to boot it into fastboot
connect phone to pc
type in the opened cmd, fastboot devices
if your devices showed in cmd we can repair it back
try also downloading xiaomi flash tool latest and open the software click drivers on the upper right corner install all 5 drivers and try connecting your phone see if its detected on your device manager
Thank you for your quick response, cmd finally detected my phone, I got Mi Flash Tool but it got me a weird message in after installing drivers:
(hopefully it means it was successful) and it detects it as well!
Edit: Not sure what to do next, monkey brain tells me I should probably try installing TWRP again and see if it detects it as storage to try again and install LineageOS? Unless I can do that with Mi Flash Tool instead
HBMHD said:
Thank you for your quick response, cmd finally detected my phone, I got Mi Flash Tool but it got me a weird message in after installing drivers:
View attachment 5470215
(hopefully it means it was successful) and it detects it as well!
Click to expand...
Click to collapse
its in chinese character dont worry it is successful hahaha
go flash your stock rom before installing and perfecting your custom recovery and roms take note: before flashing stock rom tick clean flash dont flash it if its clean flash and relock bootloader
disregard my stock rom my phone is global variant choose your designated variant to flash
khazzey said:
disregard my stock rom my phone is global variant choose your designated variant to flash
Click to expand...
Click to collapse
Mine is too, I'm downloading it right now, will take a while.
This may be a silly question and idk if you know the answer of, but will my phone keep charging even if it's in Fastboot mode? It has been on for a few hours since attempting to fix and I don't want it to die in the middle of installing the stock rom, the damn thing won't turn off, every time I hold the power button it just turns on again into that LineageOS recovery tool
HBMHD said:
Mine is too, I'm downloading it right now, will take a while.
This may be a silly question and idk if you know the answer of, but will my phone keep charging even if it's in Fastboot mode? It has been on for a few hours since attempting to fix and I don't want it to die in the middle of installing the stock rom, the damn thing won't turn off, every time I hold the power button it just turns on again into that LineageOS recovery tool
Click to expand...
Click to collapse
it will definitely charge like the speed of micro usb like 2.0 amperes in fastboot only it charges too slow but it will keep your phone still alive dont worry after you flashed stock rom it will go back normal 33W
before i forgot you cant flash your stock rom, you need to install notepad ++ edit the extracted rom batch file clean flash all bat remove the first script, stop the editing for the first fastboot word you read to avoid anti rollback protection of xiaomi
khazzey said:
before i forgot you cant flash your stock rom, you need to install notepad ++ edit the extracted rom batch file clean flash all bat remove the first script, stop the editing for the first fastboot word you read to avoid anti rollback protection of xiaomi
Click to expand...
Click to collapse
I'm waiting for my file to download again to check that batch file... What I downloaded was "miui_ALIOTHGlobal_V12.5.4.0.RKHMIXM_76076865ce_11.0.zip" which I think it's a file meant for TWRP as it says "Recovery" and not Fastboot (which I didn't know was strictly different), I'm downloading the Fastboot version from here that has the same name as yours now, and then I'll see if I can figure out how to remove a script from a batch file; I was so not prepared for this, but I'm learning slowly lol.
Thank you for the explanations and warnings, I'll keep you and possible readers posted.
HBMHD said:
I'm waiting for my file to download again to check that batch file... What I downloaded was "miui_ALIOTHGlobal_V12.5.4.0.RKHMIXM_76076865ce_11.0.zip" which I think it's a file meant for TWRP as it says "Recovery" and not Fastboot (which I didn't know was strictly different), I'm downloading the Fastboot version from here that has the same name as yours now, and then I'll see if I can figure out how to remove a script from a batch file; I was so not prepared for this, but I'm learning slowly lol.
Thank you for the explanations and warnings, I'll keep you and possible readers posted.
Click to expand...
Click to collapse
thats the right rom you are downloading now the fastboot one after that extract it to drive C: of your pc in able to detect it from xiaomi flash after you downloaded and extracted it go back here i am going to teach you how to edit fastboot command line to avoid anti rollback
khazzey said:
thats the right rom you are downloading now the fastboot one after that extract it to drive C: of your pc in able to detect it from xiaomi flash after you downloaded and extracted it go back here i am going to teach you how to edit fastboot command line to avoid anti rollback
Click to expand...
Click to collapse
Finally, that took a while; I see the "flash_all.bat" file after extracting.
HBMHD said:
Finally, that took a while; I see the "flash_all.bat" file after extracting
Click to expand...
Click to collapse
edit it with notepad ++ save the first fastboot comand line upto last. then flash it ticking clean flash youre good to go
khazzey said:
edit it with notepad ++ save the first fastboot comand line upto last. then flash it ticking clean flash youre good to go
Click to expand...
Click to collapse
Sorry I got a bit lost there, what do I edit in Notepad++? Do I remove something or do I copy the first line and move it?
This is what's inside the batch file:
Code:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *alioth" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *alioth" || exit /B 1
::check anti_version
if exist %~dp0images\anti_version.txt (for /f "delims==" %%a in (%~dp0images\anti_version.txt) do (set CURRENT_ANTI_VER=%%a))
if [%CURRENT_ANTI_VER%] EQU [] set CURRENT_ANTI_VER=0
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
set anticheck="antirollback check pass"
if %version% GTR %CURRENT_ANTI_VER% set anticheck="Current device antirollback version is greater than this pakcage"
echo %anticheck% | findstr /r /c:"pass" || @echo "Antirollback check error" && exit /B 1
fastboot %* erase boot_ab || @echo "Erase boot_ab error" && exit /B 1
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1
fastboot %* flash xbl_ab %~dp0images\xbl.elf || @echo "Flash xbl_ab error" && exit /B 1
fastboot %* flash xbl_config_ab %~dp0images\xbl_config.elf || @echo "Flash xbl_config_ab error" && exit /B 1
fastboot %* flash abl_ab %~dp0images\abl.elf || @echo "Flash abl_ab error" && exit /B 1
fastboot %* flash tz_ab %~dp0images\tz.mbn || @echo "Flash tz_ab error" && exit /B 1
fastboot %* flash hyp_ab %~dp0images\hyp.mbn || @echo "Flash hyp_ab error" && exit /B 1
fastboot %* flash devcfg_ab %~dp0images\devcfg.mbn || @echo "Flash devcfg_ab error" && exit /B 1
fastboot %* flash storsec %~dp0images\storsec.mbn || @echo "Flash storsec error" && exit /B 1
fastboot %* flash bluetooth_ab %~dp0images\BTFM.bin || @echo "Flash bluetooth_ab error" && exit /B 1
fastboot %* flash cmnlib_ab %~dp0images\cmnlib.mbn || @echo "Flash cmnlib_ab error" && exit /B 1
fastboot %* flash cmnlib64_ab %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64_ab error" && exit /B 1
fastboot %* flash modem_ab %~dp0images\NON-HLOS.bin || @echo "Flash modem_ab error" && exit /B 1
fastboot %* flash dsp_ab %~dp0images\dspso.bin || @echo "Flash dsp_ab error" && exit /B 1
fastboot %* flash keymaster_ab %~dp0images\km41.mbn || @echo "Flash keymaster_ab error" && exit /B 1
fastboot %* flash logo %~dp0images\logo.img || @echo "Flash logo error" && exit /B 1
fastboot %* flash featenabler_ab %~dp0images\featenabler.mbn || @echo "Flash featenabler_ab error" && exit /B 1
fastboot %* flash aop_ab %~dp0images\aop.mbn || @echo "Flash aop_ab error" && exit /B 1
fastboot %* flash qupfw_ab %~dp0images\qupv3fw.elf || @echo "Flash qupfw_ab error" && exit /B 1
fastboot %* flash uefisecapp_ab %~dp0images\uefi_sec.mbn || @echo "Flash uefisecapp_ab error" && exit /B 1
fastboot %* flash multiimgoem_ab %~dp0images\multi_image.mbn || @echo "Flash multiimgoem_ab error" && exit /B 1
fastboot %* flash super %~dp0images\super.img || @echo "Flash super error" && exit /B 1
fastboot %* flash misc %~dp0images\misc.img || @echo "Flash misc error" && exit /B 1
fastboot %* flash vbmeta_ab %~dp0images\vbmeta.img || @echo "Flash vbmeta_ab error" && exit /B 1
fastboot %* flash dtbo_ab %~dp0images\dtbo.img || @echo "Flash dtbo_ab error" && exit /B 1
fastboot %* flash vbmeta_system_ab %~dp0images\vbmeta_system.img || @echo "Flash vbmeta_system_ab error" && exit /B 1
fastboot %* erase metadata || @echo "Erase metadata error" && exit /B 1
fastboot %* flash userdata %~dp0images\userdata.img || @echo "Flash userdata error" && exit /B 1
fastboot %* flash cust %~dp0images\cust.img || @echo "Flash cust error" && exit /B 1
fastboot %* erase imagefv_ab || @echo "Erase imagefv_ab error" && exit /B 1
fastboot %* flash imagefv_ab %~dp0images\imagefv.elf || @echo "Flash imagefv_ab error" && exit /B 1
fastboot %* flash rescue %~dp0images\rescue.img || @echo "Flash rescue error" && exit 1
fastboot %* flash spunvm %~dp0images\spunvm.bin || @echo "Flash spunvm error" && exit /B 1
fastboot %* flash vendor_boot_ab %~dp0images\vendor_boot.img || @echo "Flash vendor_boot_ab error" && exit /B 1
fastboot %* flash logfs %~dp0images\logfs_ufs_8mb.bin || @echo "Flash logfs error" && exit /B 1
fastboot %* flash boot_ab %~dp0images\boot.img || @echo "Flash boot_ab error" && exit /B 1
fastboot %* set_active a || @echo "Set active error" && exit /B 1
fastboot %* reboot || @echo "Reboot error" && exit /B 1
remove the first 10 lines
you shold save the fastboot erase boot_ab upto fastboot reboot
just save this only
dont forget to tick clean flash only dont lock your bootloader
update me if flashing is done

How To Guide [LINUX/ALL-IN-ONE] How to flash an .ofp firmware with QDL (Qualcomm Device Loader)

DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE
- Only git and unlocked bootloader are needed.
- I recommend that you make a backup of your device before carrying out any operations (by QFILhelper or other).
- If you want to flash a different firmware/region, you need to adapt the command.
- This command has been tested and works. One user even tested a version downgrade (from C09 to C08) and it worked.
- I don't know if firmware downgrade (for example from F06 to C13) works.
- At the end, you will have "Waiting for EDL device" : switch off the device, hold down the 2 volume buttons and connect it to the PC USB port.
- The flash will last between 30 and 40 minutes.
- At the end of the installation, the device will automatically restart, try to boot the system and then load Realme UI recovery.
- Wipe data and the device will boot successfully into the system.
- Many thanks to ogree from 4pda.to
All-in-one command (download/make/extract/merge/flash/...) to flash RMX3363GDPR_11_C.13 (EUEX region) in EDL (Emergency DownLoad) mode :
Code:
mkdir qdl_flash && cd qdl_flash && git clone https://github.com/bkerler/oppo_decrypt && mv ./oppo_decrypt/ofp_qc_decrypt.py ./ofp_qc_decrypt.py && mv ./oppo_decrypt/requirements.txt ./requirements.txt && rm -rf oppo_decrypt && pip3 install -r requirements.txt && wget https://rms01.realme.net/sw/RMX3363GDPR_11_C.13_2022121304390000.zip && unzip RMX3363GDPR_11_C.13_2022121304390000.zip && rm RMX3363GDPR_11_C.13_2022121304390000.zip && mv ./RMX3363GDPR_11_C.13_2022121304390000/RMX3363GDPR_11_C.13_2022121304390000.ofp ./RMX3363GDPR_11_C.13_2022121304390000.ofp && rm -rf RMX3363GDPR_11_C.13_2022121304390000 && mkdir extracted && python3 ofp_qc_decrypt.py RMX3363GDPR_11_C.13_2022121304390000.ofp extracted && rm ./RMX3363GDPR_11_C.13_2022121304390000.ofp ofp_qc_decrypt.py requirements.txt && git clone https://git.codelinaro.org/linaro/qcomlt/qdl && mv qdl qdl_source && cd qdl_source && make && cd .. && mv ./qdl_source/qdl ./qdl && rm -rf qdl_source && mv qdl ./extracted/qdl && cd extracted && git clone https://github.com/anestisb/android-simg2img && cd android-simg2img && make && cd .. && mv ./android-simg2img/simg2img ./simg2img && rm -rf android-simg2img && simg2img super.0.b39af986.img super.1.5e90d442.img super.2.a2462fd8.img super.img && rm prog_firehose_ddr.elf super.0.b39af986.img super.1.5e90d442.img super.2.a2462fd8.img super.2.09ba91b0.img super.2.98a4bcf9.img simg2img && sudo systemctl stop ModemManager && sudo ./qdl --debug --storage ufs prog_firehose_ddr_fwupdate.elf rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml

Categories

Resources