Related
"This package is for A0001, this device is bacon." Wiped internal storage, cant flash
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
KuranKaname said:
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
Click to expand...
Click to collapse
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
Instead of using adb push metod try to flash stock rom (https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/) and then flash the rom you want.
Good luck!
Note: You will loose twrp, so you have to flash it via fasboot [fastboot flash recovery (recovery name).img]
I'd suggest you to start over with a clean flash of COS13 fastboot factory image. Sounds like you are on a very old base.
Try to reboot TWRP and flash again. Or remove that check string from the updater-script.
download CM11 factory recover tool from my google drive @ https://drive.google.com/open?id=0ByfGPjP5zNYSTDZZcXZpLU44Q00 and install drivers and go to fastboot and plug in the phone and run recovery tool to push default factory image then install whatever CM version you want directly
No updater-script file that I can see
Can't find that file!
Anghirrim said:
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
Click to expand...
Click to collapse
use usb otg, success each time!
setup on ubuntu
Instructions for install on linux (test on ubuntu)
1- install adb :
Code:
$ sudo apt-get install android-tools-adb
2- install fastboot :
Code:
$ sudo apt-get install android-tools-fastboot
3- Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
4- test if the phone is detected with the cmd :
Code:
$ fastboot devices
5- unlock bootloader (/!\ it wipe the phone) :
Code:
$ sudo fastboot oem unlock
6- install TWRP :
- go to the path where is the img
Code:
$ cd path/to/twrp/folder/
- rename the image to twrp.img
Code:
$ mv old_name.img twrp.img
- flash the recovery
Code:
$ sudo fastboot flash recovery twrp.img
/!\ Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually turn it off by pressing and holding power button until it switches off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode. Now that you have a custom recovery, you may continue to the final step. /!\
7- install custom/official ROM with TWRP :
- Wipe > Swipe to Factory Reset
- Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
- Install GApps using same process as ROM, then reboot. (optionnal: the official OnePlus ROM come with GApps pre-installed)
Possible errors with official ROM :
"This package is for device: A0001; this device is bacon" or "This package is for device: OnePlus; this device is A0001" or other similar
==> go into the ROM zip file, in "/META-INF/com/google/android/" there is an "updater-script" file. Open it, locate the expression ' getprop("ro.build.product") == "A0001" ' and replace the "A0001" by the device name you have. Replace the file in the archive. Note : after that, you can't verify the official MD5 !
- example : "This package is for device: A0001; this device is bacon", the ' getprop("ro.build.product") == "A0001" ' become getprop("ro.build.product") == "bacon" '
Sources :
https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
https://forum.xda-developers.com/oneplus-one/help/package-a0001-device-bacon-wiped-t3457766
Oneplus one Oxygen Installation error using TWRP
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
check this post
wirelessindeed.blogspot.com/2017/07/oxygen-installation-error-on-oneplus.html
Update TWRP Recovery
I know this is an old post, so this is here in case anyone finds it in the future and requires help...
My mate asked me to upgrade his OnePlus (original, codename Bacon) and I received this error when upgrading from LineageOS 14.1 to 15.1.
To resolve, its extremely easy - simply upgrade the TWRP recovery. My mate originally had TWRP 3.1.1.0 installed, but the latest weekly LineageOS 15.1 required v3.2.3.0 installed which resolved the error message "This package is for device: bacon, a1001. this device is ."
Either Vol+ and Power to enter bootloader, or from command line:
adb reboot bootloader (with Android USB debugging turned on. You can test for connection using command "adb devices" and if successful it should show your phone's serial number). You will need to trust the computer's connection on your phone. To get to Android USB Debugging, you need to go Settings -> Developer menu options, and if you can't see that: Settings -> About Phone and tap "Build" 7 times for developer mode to appear.
Once phone goes into bootloader mode, type:
fastboot flash recovery "path:\twrp-x.x.x.x-bacon.img" (obviously path is the directory that the recovery is stored in, and x.x.x.x will be replaced with the version you've just downloaded. At time of writing, v3.2.3.0 is the latest. You can always use "fastboot devices" if you used Vol+ and Power to enter bootloader to ensure you have a valid connection, in USB debugging mode on your phone and correct Android adb drivers installed in Windows.
Wait until it's succeeded, and turn off phone. Now go into recovery and try again - and this time you should be good to go!!!
All the above implies your bootloader is unlocked. If you need to unlock your bootloader, there are plenty of instructions telling you how to do this - but HAVE A BACKUP as unlocking your bootloader will do a factory reset on your phone.
Hope this helps someone
......mmmmmm BACON!!!
{ ROOT } Twrp & Magisk Installation in Official Oreo { (N2G47H.7.12.29 (Android O) }
Needed Files :
1. Fastboot Rom
Http://bigota.d.miui.com/7.12.29/tissot_images_7.12.29_20171228.0000.00_8.0_c9a6ea979b.tgz
2. Platform tools
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
3.Twrp recovery
https://androidfilehost.com/?fid=962157660013069602
4.. Twrp Installer
http://www.mediafire.com/file/338o7cl72z52rzz/twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
5. Magisk 15.2
http://www.stechguide.com/download-magisk-v15-2/
Flashing Guide:
Download all the needed files copy magisk zip file in your device.
1. Flash Fastboot rom using Mi flash tool. ( clean install recommended )
2. After flashing, complete setup and other setting.
( Note : Please Skip adding Finger print. if you are added by mistakenly kindly delete your finger print in settings. )
3. Enable oem unlocking & usb debugging in developor options.
4. Extract platform tool in your pc.
5. Paste the downloaded twrp recovery(3) & twrp installer(4) in platform tools folder.
6. Boot your device to fastboot Mode and connect to pc.
7. Open Command Window ( shift + right click ) and enter the following commands
fastboot oem unlock
fastboot boot recovery-3.2.1-1.img
8. Your device will be booting to Twrp. In twrp select Advanced -----> Adb sideload.
9. Type following command in command window
adb sideload twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
10. reboot to recovery.
11. your internal storage is available in twrp now.
12. Flash Magish 15.2 ( strictly use this version )
13. Goto to reboot option in twrp and select your current slot a or b . ( twrp will showing your current slot )
14. reboot system and enjoy.
***** Sorry for my bad english ****
will try soon and will update you.
please let me know if after following this method are we able to install Magisk modules and does it work?
Yes.
Did not work at first. I had installed magisk using patched boot method. Installed twrp using given method. Device was booting into twrp after selecting reboot system. Decided to install magisk again. As I already had magisk installed, tried flashing uninstaller.zip and got an error saying stock boot image was found which means that magisk was uninstalled. Flashed magisk 15.2 and it worked. I was able to boot into system with twrp installed.
Moral : Flashing magisk is a necessary step even if you are already rooted with magisk.
ota updates
after root by this method ..how to install ota updates
navneet1 said:
after root by this method ..how to install ota updates
Click to expand...
Click to collapse
1. Download and flash stock rom (same version that you are currently on) using mi flashtool with save user data option.
2. Your device will be in the same condition (including apps, settings, data etc.) but unrooted.
3. You'll have an ota notification. Install it with normal procedure.
4. Follow the op from step 3.
Apoorv AR said:
Did not work at first. I had installed magisk using patched boot method. Installed twrp using given method. Device was booting into twrp after selecting reboot system. Decided to install magisk again. As I already had magisk installed, tried flashing uninstaller.zip and got an error saying stock boot image was found which means that magisk was uninstalled. Flashed magisk 15.2 and it worked. I was able to boot into system with twrp installed.
Moral : Flashing magisk is a necessary step even if you are already rooted with magisk.
Click to expand...
Click to collapse
Follow the steps with clean flashed rom.
Spk1690 said:
Follow the steps with clean flashed rom.
Click to expand...
Click to collapse
It worked when I flashed Magisk again without loosing any modules or anything.
get block at
adb sideload twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
the first file i downladed got different name and when i put this command they tell me
No such file or directory
@Spk1690 SO this file twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip only for show internal storage?
edit
After enter this command fastboot boot recovery-3.2.1-1.img my device boot into system, not twrp, how to solve?
Does this work on the January Oreo STABLE patch??
KalolParty said:
Does this work on the January Oreo STABLE patch??
Click to expand...
Click to collapse
upp
KalolParty said:
Does this work on the January Oreo STABLE patch??
Click to expand...
Click to collapse
I have tried , it works, but do it on your own risks
root
i have problem. When i try to root phone i get command:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-kitkat sideload method...
adb: pre-kitkat sideload connection failed: no devices/emulators found
what im doing wrong?
Spk1690 said:
6. Boot your device to fastboot Mode and connect to pc.
7. Open Command Window ( shift + right click ) and enter the following commands
fastboot oem unlock
fastboot boot recovery-3.2.1-1.img
8. Your device will be booting to Twrp. In twrp select Advanced -----> Adb sideload.
Click to expand...
Click to collapse
My A1 reboor into system, not into TWRP.
What am I doing wrong?
I've already done all previous steps, and device is unlocked now.
These files are old, a new ones have been released some time ago:
An updated ROM file:
http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
An updated recovery:
https://www.androidfilehost.com/?fid=818070582850498337
Updated TWRP installer:
(check the attachment section)
Updated Magisk 16.0:
(Check the attachment section)
realtebo said:
My A1 reboor into system, not into TWRP.
What am I doing wrong?
I've already done all previous steps, and device is unlocked now.
Click to expand...
Click to collapse
Have you selected the partition you've installed your recovery to?
Because if not, boot the TWRP .img again and switch the partitions.
Reboot afterwards.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
cregen said:
i have problem. When i try to root phone i get command:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-kitkat sideload method...
adb: pre-kitkat sideload connection failed: no devices/emulators found
what im doing wrong?
Click to expand...
Click to collapse
You might want to try this: https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
Check steps 7-10. Read the whole instructions even if they aren't for your ROM. (Skip the copying process and other LOS related stuff.)
I have a problem while flashing twrp on march patch after flashing twrp on both slots android will automatically degrade to February patch ? I'm fed up of trying things please anyone help me
Im new in mi a1, why we need to flash new rom before flash twrp? My rom position on latest update
I'm trying to install LineageOS and then GAPPS on my Pixel XL from TWRP recovery. I'll try to `Advance Wipe` the `/systems` directory and `Format Data`, but I continue to get multiple errors:
Code:
Failed to mount '/system' (Device or resource busy)
Code:
Failed to mount '/vendor' (Device or resource busy)
And
Code:
Unable to wipe 'System'
Code:
Unable to wipe '/system'
If I just continue with `adb sideload lineageos.zip` most of the time it stops about halfway (PowerShell shows `47%`) through and then TWRP shell shows:
Code:
Installing zip file '/sideload/package.zip'
Step 1/2
Step 2/2
I then try to `sideload` the `gapps.zip` file and get another error saying `/system` doesn't have enough space. I've tried sideloading several different gapps versions including their smallest `pico` zip fie of `91.39 MiB`.
I am able to then boot into LineageOS, but no GAPPS show and I'm not able to run any new apps installed via APK without them crashing.
My assumption is that I need to fully wipe `system` and format it, but I've been trying for two days now and still get the above `(Device or resource busy)` errors. Any help would be much appreciated!
Make sure you have the latest tools.
Latest TWRP for marlin is 3.3.0-0
Latest platform-tools is 29.0.1
Not sure what's the cause of this, but if you want to wipe and start fresh I think the best option is reflash the stock factory image that completely wipes everything and restores everything stock.
Then, you can retry wiping the device using the latest TWRP (currently, marlin is 3.3.1-0, the zip is 3.3.0-0, try just boot it and don't flash the zip), flash LOS and then gapps.
Also, as pointed by @post-mortem, make sure you are using the latest adb version when flashing the factory image, just to avoid any potential issue.
Don't use 3.3.1-0. Try 3.3.0-0. I had the same issue.
Why doesn't TWRP Team provide an answer as to why this happens? It appears to affect everyone with the latest official Pixel ROM.
Twrp is for Android pie and has trouble mounting stock Android 10. They have announced this on their website. This shouldn't matter since you're installing lineage. You don't need to wipe system before installing lineage because it installs into the inactive slot. You need to sideload lineage then reboot into recovery to switch slot's. The instructions are on the lineage website.
Did OP manage to solve this issue?
Hi,
I just got a second hand Google Pixel 1 and I ran into some trouble trying to install magisk on it : I keep getting those two error messages in TWRP when flashing the TWRP.zip and magisk.zip :
"Failed to mount system/root (invalid argument)"
"failed to mount vendor (invalid argument)"
The two installations are still considered successful by TWRP but rebooting after flashing the magisk.zip keeps the phone in bootloop.
Any idea how I could fix this please ?
Information on the device and software used :
- android 10 installed on the phone when i got it ;
- bootloader unlocked, usb debugging on ;
- Flashing TWRP with "twrp-installer-3.4.0-0-sailfish" preloaded in the phone and the corresponding img ;
- magisk manager installed and using magisk 20.4 zip preloaded in the phone for flashing ;
- all commands made in cmd.exe from windows 10 computer ;
- adb and google drivers installation all ok.
please ask if I didn't give enough information.
Thanks in advance !
dantafas said:
Hi,
I just got a second hand Google Pixel 1 and I ran into some trouble trying to install magisk on it : I keep getting those two error messages in TWRP when flashing the TWRP.zip and magisk.zip :
"Failed to mount system/root (invalid argument)"
"failed to mount vendor (invalid argument)"
The two installations are still considered successful by TWRP but rebooting after flashing the magisk.zip keeps the phone in bootloop.
Any idea how I could fix this please ?
Information on the device and software used :
- android 10 installed on the phone when i got it ;
- bootloader unlocked, usb debugging on ;
- Flashing TWRP with "twrp-installer-3.4.0-0-sailfish" preloaded in the phone and the corresponding img ;
- magisk manager installed and using magisk 20.4 zip preloaded in the phone for flashing ;
- all commands made in cmd.exe from windows 10 computer ;
- adb and google drivers installation all ok.
please ask if I didn't give enough information.
Thanks in advance !
Click to expand...
Click to collapse
Guide
Do #9 in the guide using the Canary Magisk Manager.
Ok thanks I'll try that !
My new Xiaomi Poco X3 Pro is showing an error screen after some time, like in this post:
https://forum.xda-developers.com/t/cant-load-android-system-lineageos.4314035/
It reads "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device"
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
After the first error screen
- I tapped Try again,
- When the error occurred again, I tapped "Factory data reset," but the error still occurred. The phone is new, no user data is on the phone.
- I booted into recovery and reset all the data I could. When I tap "Format system partition" it throws an error "E: Failed to open /dev/block/dm-0: No such file or directory. System wipe failed."
- Then I repeated the adb sideload. The error occurs again.
- I removed the SIM card, as someone in the forum suggested this could be a problem source. The error still occurs.
What can I do now?
----
Update [2021-12-05 Sun 20:09]
It seems to be a Problem with the GApps Version.
What I did Try so far is:
- Install 03-12-LOS and latest GApps via LOS recovery (didn't work)
- Install 03-12-LOS and latest GApps via TWRP recovery (didn't work)
- install LOS Build from 26-11-2021 without GApps (works)
- Install LOS Build from 26-11-2021 with latest GApps (didn't work)
- Install LOS Build form 26-11-2021 with GApps from 25-11-2021 (works)
Just use TWRP, flash ROM and AFTER flashing ROM Format Data where you have to type "yes". (Format, not Wipe)
Xiaomi Poco X3 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Thanks for the Idea. At the moment it has not solved the problem.
This is what I did:
- Flash TWRP
Code:
fastboot flash recovery TWRP-3.5.2-vayu-Nebrassy-2.img
- copy lineage-18.1-20211203-nightly-vayu-signed.zip and "open_gapps-arm64-11.0-nano-20211204.zip" to the Poco device
- install via "install" option, wipe cache at the end of installation
- Format files (via "Wipe" -> "Format Data" -> type "yes")
- Reboot
After some time of the animated Lineage OS logo, the phone reboots into TWRP.
To me this seems very similar to the Lineage recovery before.
Any ideas what could be wrong?
You probably wiped System or Vendor partition or something, you are not supposed to do that.
Most likely you have to reflash MIUI now first. Make sure it's atleast version 12.5.X.X.
Flashing instructions are really simple, this apply to all ROM's.
FIRST INSTALL?:
Remove any fingerprint, PIN, or password in MIUI
Unlock the bootloader
Transfer ROM to internal storage
Install any suitable recovery
Flash ROM zip file
Do a data wipe in recovery (format data)
Reboot to the system, wait and enjoy
FLASHING UPDATES?:
Download via OTA Updater and let it automatically install; OR
Download an update, transfer to internal/external storage (always check file sha256)
Flash ROM zip and reboot.
Do not wipe anything else or add any additional steps. (maybe except Gapps if ROM doesn't have them included)
ps.
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
Click to expand...
Click to collapse
k3lcior said:
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
Click to expand...
Click to collapse
I followed the LOS Install Guide: https://wiki.lineageos.org/devices/vayu/install But this procedure does not seem to bee the cause (see below).
Download the LineageOS installation package that you would like to install or build the package yourself.
Optionally, download an application package add-on such as Google Apps (use the arm64 architecture).
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. When Xiaomi/POCO/Redmi splash appears, release Power and keep pressed Volume Up until recovery appears.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Click to expand...
Click to collapse
Okay so this is what I did (the part that works):
- I downloaded the latest possible stock ROM from https://www.xda-developers.com/down...ut-several-xiaomi-redmi-mi-poco-devices/#vayu The fastboot ROM is more than 5GB.
- Extract the file "vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea_05cc38de43.tgz"
- then connect the phone via USB cable in fastboot mode and:
Bash:
cd ~/Downloads/vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea
/bin/bash ./flash_all.sh
- The default MIUI starts flawless, as it dit the first time I turned on the phone. So far so good.
What didn't work:
1. I installed the LOS Recovery again and flashed the OS and Gapps. Only after that I did step 3 - formating. The result ist the same bootloop as in the beginning.
2. I flashed the stock MIUI ROM again (which woks fine). Then I flashed TWRP, transfered the OS and GApps file and installed. I did not wipe anything, just used "format data" like above.
In both cases the OS does not start. After a while displaying the LOS-logo the phone reboots to recovery.
What did work:
I downloaded lineage-18.1-20211126-nightly-vayu-signed.zip, one version before the latest verion and the corresponding recovery lineage-18.1-20211126-recovery-vayu.img
I flashed only the OS, and no GApps -- and it launched successfully. Installing with the latest GApps failed again.
Install older gapp, not all gapp is compatible