Develop Bugs

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

booting custom kernel

SOLVED: I was using the G980F boot.img instead of G985F image. THANKS everyone
The device won't reboot if I unpack and repack the boot.img on S20
Did someone else here succeed in flashing a new boot.img ? THANKS
Code:
[email protected]:~/GS20_kernel_build$ unpackbootimg -i boot.img
BOARD_KERNEL_CMDLINE androidboot.hardware=exynos990
BOARD_KERNEL_BASE 10000000
BOARD_PAGE_SIZE 2048
[email protected]:~/GS20_kernel_build$ mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz -o boot_repacked.img
[email protected]:~/GS20_kernel_build$ heimdall flash --BOOT ./boot_repacked.img
[...]
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...

modem__ said:
The device won't reboot if I unpack and repack the boot.img on S20
Did someone else here succeed in flashing a new boot.img ? THANKS
Code:
[email protected]:~/GS20_kernel_build$ unpackbootimg -i boot.img
BOARD_KERNEL_CMDLINE androidboot.hardware=exynos990
BOARD_KERNEL_BASE 10000000
BOARD_PAGE_SIZE 2048
[email protected]:~/GS20_kernel_build$ mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz -o boot_repacked.img
[email protected]:~/GS20_kernel_build$ heimdall flash --BOOT ./boot_repacked.img
[...]
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...
Click to expand...
Click to collapse
You need to make a tar file containing the img and flash it with odin. You need a Windows computer for that. Linux won't do sadly

If you don't feel like making a flashable zip file you can just use dd to install it from within TWRP (via terminal on console or ADB) if you have that installed:
dd if=boot_repacked.img of=/dev/block/by-name/boot
No Windows/Odin required.

sjevtic said:
If you don't feel like making a flashable zip file you can just use dd to install it from within TWRP (via terminal on console or ADB) if you have that installed:
dd if=boot_repacked.img of=/dev/block/by-name/boot
No Windows/Odin required.
Click to expand...
Click to collapse
dd always scares me lol.
You sure this works with S20? Even Fastboot fllashing doesn't work so I doubt this will

JanBoyGamer23 said:
dd always scares me lol.
You sure this works with S20? Even Fastboot fllashing doesn't work so I doubt this will
Click to expand...
Click to collapse
My phone wouldn't boot last night after I tried flashing my own boot image and this was how I put the previous one back. It booted right up.

Error While try to Flash firmware with MI Flash tool

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?

Question Fastboot and windows.bat does not work

hi,I am currently trying to install MIUI 12.6 -21.10.27 on my PocoF3.Fasboot ROM with a Windows batch file.
My steps:
1 Unzip the file
2 Start the device in Fastboot and connect to the PC
3 Start the Windows batch file
But nothing is happening. In the file folder are the platform tools for Windows, images and windows fastboot .bat. when I do a fastboot device with cmd, I can see my device.
Is it possibly the cable or missing Windows drivers?

Tried using the MiFlash tool?
Also check similar posts, fe https://forum.xda-developers.com/t/fastboot-rom-tgz-file-into-adb-sideload.4352239/

dirtytwo said:
hi,I am currently trying to install MIUI 12.6 -21.10.27 on my PocoF3.Fasboot ROM with a Windows batch file.
My steps:
1 Unzip the file
2 Start the device in Fastboot and connect to the PC
3 Start the Windows batch file
But nothing is happening. In the file folder are the platform tools for Windows, images and windows fastboot .bat. when I do a fastboot device with cmd, I can see my device.
Is it possibly the cable or missing Windows drivers?
Click to expand...
Click to collapse
try to install device drivers especially fastboot and Qualcomm usb driver

dirtytwo said:
hi,I am currently trying to install MIUI 12.6 -21.10.27 on my PocoF3.Fasboot ROM with a Windows batch file.
My steps:
1 Unzip the file
2 Start the device in Fastboot and connect to the PC
3 Start the Windows batch file
But nothing is happening. In the file folder are the platform tools for Windows, images and windows fastboot .bat. when I do a fastboot device with cmd, I can see my device.
Is it possibly the cable or missing Windows drivers?
Click to expand...
Click to collapse
you could also try:
- disable Windows driver signature check;
How to Enable or Disable Driver Signature Enforcement in Windows 10
How to Enable or Disable Driver Signature Enforcement and Test Mode in Windows 10
www.tenforums.com
- reinstall the drivers; (find the ones that work on the mi flash program);
- move the rom folder to c: \;
- try another usb port, the rear or the 2.0 are better;
- make sure you have enabled usb debug in developer settings and have authorized the pc;
- start the .bat file as administrator;

what I've found so far:
first .bat is from 22.4.21 rom wich works
@Echo off
cd %~dp0
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" exit /B
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *alioth"
if %ERRORLEVEL% neq 0 echo Missmatching image and device & exit /B 1
second .bat is from 27.10.21 which doesn't work
@Echo off
cd %~dp0
set DEVICE=unknown
for /f "tokens=2" %%D in ('platform-tools-windows\fastboot %* getvar product 2^>^&1 ^| findstr /l /b /c:"product:"') do set DEVICE=%%D
if "%DEVICE%" neq "alioth" echo This package is for "alioth" devices; this is a "%DEVICE%". & exit /B 1
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" exit /B 0
so what can i do.

dirtytwo said:
what I've found so far:
first .bat is from 22.4.21 rom wich works
@Echo off
cd %~dp0
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" exit /B
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *alioth"
if %ERRORLEVEL% neq 0 echo Missmatching image and device & exit /B 1
second .bat is from 27.10.21 which doesn't work
@Echo off
cd %~dp0
set DEVICE=unknown
for /f "tokens=2" %%D in ('platform-tools-windows\fastboot %* getvar product 2^>^&1 ^| findstr /l /b /c:"product:"') do set DEVICE=%%D
if "%DEVICE%" neq "alioth" echo This package is for "alioth" devices; this is a "%DEVICE%". & exit /B 1
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" exit /B 0
so what can i do.
Click to expand...
Click to collapse
I see that they have changed the encoding of the installation script, but honestly I don't know why it doesn't work for you, it's weird!
Did you do all the moves I handed you?
Can you try to install it from another pc? (So let's see if the problem is the pc or the rom)
You can also try to re-download it because maybe the package got corrupted.
Also you can try asking for information here:
MIUI 13 Stable Xiaomi.EU [Poco F3, Mi 11x, Redmi K40]
This thread is for discussion about xiaomi.eu stable releases. Weekly releases won't be shared here. MIUI 13 :- Xiaomi.EU 13.0.2.0 (Fastboot ROM) Xiaomi.EU 13.0.3.0 (Fastboot ROM) Xiaomi.EU 13.0.5.0 (Fastboot ROM) Xiaomi.EU 13.0.6.0 (Fastboot...
forum.xda-developers.com
(this is the discussion dedicated to the rom xiaomi.eu)
Or directly to the xiaomi.eu community on the official website, here:
MIUI 12.6 - 21.10.27/28
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
(you must register in order to post).

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