Develop Bugs

I think I have bricked my phone?

After a lot of messing about I managed to unlock the bootloader, install TWRP but now it won't boot into the system, TWRP boots into recovery fine, but when trying to boot in system it just idles on this screen.
{
"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"
}
and this is what TWRP looks like but won't let me pick sd card or otg to install mgisk or no verify
is it possible to install custom roms via fastboot instead of having to go down the stock rom path?

Have you installed the official 32 twrp or the 64 bit twrp? have you formatted user data yet in TWRP? if not do a full wipe then flash ROM, GAPPs and reboot

andybr1ggs said:
After a lot of messing about I managed to unlock the bootloader, install TWRP but now it won't boot into the system, TWRP boots into recovery fine, but when trying to boot in system it just idles on this screen.
and this is what TWRP looks like but won't let me pick sd card or otg to install mgisk or no verify
is it possible to install custom roms via fastboot instead of having to go down the stock rom path?
Click to expand...
Click to collapse
Stock rom will not boot if you flash TWRP & select to modify system as clearly explained in my twrp thread
All you need to do is select install then select storage on bottom left - select the storage location you have placed your super user zip
If you haven't got one just connect phone to PC whilst in recovery mode & transfer it over
Or
Format system data cache then reboot to recovery & then flash a custom rom
Also your twrp is out of date - I suggest going to my twrp thread unless you flashing the lineageos 15.1 64bit version then you need the twrp from that thread that supports 64bit rom flashing

TheFixItMan said:
Stock rom will not boot if you flash TWRP & select to modify system as clearly explained in my twrp thread
All you need to do is select install then select storage on bottom left - select the storage location you have placed your super user zip
If you haven't got one just connect phone to PC whilst in recovery mode & transfer it over
Or
Format system data cache then reboot to recovery & then flash a custom rom
Also your twrp is out of date - I suggest going to my twrp thread unless you flashing the lineageos 15.1 64bit version then you need the twrp from that thread that supports 64bit rom flashing
Click to expand...
Click to collapse
thanks for the reply, i managed to get the phone back on stock firmware, so i will follow these comments and double check everything and get the new TWRP thanks again.
(done)
used the format wipe cache advice stopped the error 7

TheFixItMan said:
Stock rom will not boot if you flash TWRP & select to modify system as clearly explained in my twrp thread
All you need to do is select install then select storage on bottom left - select the storage location you have placed your super user zip
If you haven't got one just connect phone to PC whilst in recovery mode & transfer it over
Or
Format system data cache then reboot to recovery & then flash a custom rom
Also your twrp is out of date - I suggest going to my twrp thread unless you flashing the lineageos 15.1 64bit version then you need the twrp from that thread that supports 64bit rom flashing
Click to expand...
Click to collapse
so now i have twrp version 3.2.1.0 is this correct? im also trying to install this but get an error 7
https://forum.xda-developers.com/g5/development/7-1-x-lineageos-14-1-moto-g5-t3611973
im nearly there lol least phone starts up (ps doing this sh** takes my mind off my girlfriend finishing it on christmas eve)

andybr1ggs said:
so now i have twrp version 3.2.1.0 is this correct? im also trying to install this but get an error 7
https://forum.xda-developers.com/g5/development/7-1-x-lineageos-14-1-moto-g5-t3611973
im nearly there lol least phone starts up (ps doing this sh** takes my mind off my girlfriend finishing it on christmas eve)
Click to expand...
Click to collapse
You need to goto
Wipe
Select format data (option on the right)
Reboot to recovery
Select wipe
Advance wipe
Wipe system data cache delvik/art cache
Install
Select rom zip
Install
Select gapps zip (I recommend nano gapps)
Install
Select su add on zip
Wipe art/dalvik cache
Restart
If you still get error 7 you may need to remove the get prop details from the rom zip updater script

is to install this zip
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip

TWRP Recovery For Asus Zenfone Lite L1 (ZA551KL)

Presenting the TWRP Recovery for Asus Zenfone Lite L1 (ZA551KL) (asus_x00r)(Treble Supported)(Encryption Fixed) ​Disclaimer : I am not responsible for any bricked device, all responsibility bears the user.​
First Unlock Boot-loader using official asus ubl tool - Download UBL App
Team Win Recovery Project (TWRP) is the most famous custom recovery used by the people who like to flash custom roms, patches, flashable zips etc. The latest version is TWRP 3.2.3-0.
Flash zips through otg or Micro sd Cards as device is encrypted , if you format data and decry-pt then the Flashlight (torch) and the Camera will not Work.ENCRYPTION IS FIXED NOW
Installation By PC
1. Install fastboot tools - minimal adb and fastboot
2. Download twrp image and rename it as "twrp.img", then copy it to the Minimal ADB and Fastboot folder
3. Boot the device to fastboot mode - press and hold power button and volume down button
4. Connect device to pc
5. Open command prompt from Minimal ADB and Fastboot
6. Run command " fastboot flash recovery twrp.img "
7. Twrp will be flashed immediately
8. To boot in to twrp run " fastboot boot twrp.img " or disconnect device from pc and press and hold power button and volume up button
9. Device will be booted to twrp
NOW LETS DECRY-PT DATA
*Download the data Decrypt patch Zip :- Download
*Put it in otg (pendrive) or microsd card
*Then in twrp , Go to wipe section in twrp and tap on Format data (Important )
*Do not wipe data partiton , you have to format it
*then flash the Decrypt zip from your sdcard or pendrive
*after flashing wipe caches
*then reboot , and see camera and flashlight is working and Storage in Decrypted
{
"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"
}
Join telegram group for updates​
Downloads:-
1. Minimal Fastboot and Adb
2.TWRP_3.2.3.0_asus_lite_l1
3. Decrypt Patch Download
Device tree
Credits:
@Ashish Gupta1999 (me)
Tester - for testing a lot of builds time to time
if you like my work you can donate me also

Dose it support g cam portrait mode

Yes works fantastic(front cam)

Doesn't work for me. Anyone have a working root method for Asus zenfone live L1?

dexx121 said:
Doesn't work for me. Anyone have a working root method for Asus zenfone live L1?
Click to expand...
Click to collapse
Live l1 and lite l1 is a completely different devices

This TWRP actually partially works for Live L1 (ZA550KL, SD425). The problems are 1) it can't decrypt /data, 2) it fails to mount /xrom (which is inexistent on the Go variant) and 3) no ADB/MTP, but for flashing ROMs/addons, backing up and restoring, it works nicely. Just letting y'all know about it.

AndyYan said:
This TWRP actually partially works for Live L1 (ZA550KL, SD425). The problems are 1) it can't decrypt /data, 2) it fails to mount /xrom (which is inexistent on the Go variant) and 3) no ADB/MTP, but for flashing ROMs/addons, backing up and restoring, it works nicely. Just letting y'all know about it.
Click to expand...
Click to collapse
there is a specific twrp for live l1

Ashish Gupta1999 said:
there is a specific twrp for live l1
Click to expand...
Click to collapse
Can you link me to the one you know of? I just found another one from TWRP Builder, and it did fix most problems, but I still can't use decrypted data (shows "encryption unsuccessful" on boot). And it doesn't expose /vendor either which is a small letdown. <- Fixed by unpacking and editing recovery.fstab.

AndyYan said:
Can you link me to the one you know of? I just found another one from TWRP Builder, and it did fix most problems, but I still can't use decrypted data (shows "encryption unsuccessful" on boot). And it doesn't expose /vendor either which is a small letdown. <- Fixed by unpacking and editing recovery.fstab.
Click to expand...
Click to collapse
Contact me on telegram @yoursenpai1 i will provide you there

it works

Ashish Gupta1999 said:
Contact me on telegram @yoursenpai1 i will provide you there
Click to expand...
Click to collapse
Something gone wrong. System in boot loop. Able to load TWRP through PC. Tried to flash a new ROM but only 2 options (Boot & Recovery) available. Please help

Abhicr said:
Something gone wrong. System in boot loop. Able to load TWRP through PC. Tried to flash a new ROM but only 2 options (Boot & Recovery) available. Please help
Click to expand...
Click to collapse
All I know there is no rom for this device as of now , if you flash a gsi , it. Will definitely show system image option , for now flash stock rom using stock recovery to unbrick

Ashish Gupta1999 said:
All I know there is no rom for this device as of now , if you flash a gsi , it. Will definitely show system image option , for now flash stock rom using stock recovery to unbrick
Click to expand...
Click to collapse
I used a GSI to update from Oreo to Pie. But the TWRP has only 2 options (boot & Recovery) to flash the .img file. However, I did a restore & back with the old Oreo. I want to upgrade my Asus Lite 1 to Pie!! Is there any possibility to get the mobile back to the factory state including recovery? So, that I can begin from one.

Abhicr said:
I used a GSI to update from Oreo to Pie. But the TWRP has only 2 options (boot & Recovery) to flash the .img file. However, I did a restore & back with the old Oreo. I want to upgrade my Asus Lite 1 to Pie!! Is there any possibility to get the mobile back to the factory state including recovery? So, that I can begin from one.
Click to expand...
Click to collapse
Well there is a fastboot rom available in my telegram channel of lite l1 check in there

Accidentally deleted the OS and now the mobile isn't even switching on. Any solution for this? Anyway I can install an OS ?

My mobile is ASUS Zenfone Lite L1.

[UNOFFICIAL][TWRP][Recovery] TWRP 3.3.1-0

1 . unlock BootLoader AND Root https://forum.xda-developers.com/v50-thinq/development/lg-v50-temp-root-exploit-via-cve-2020-t4098077
2. Download the required files ( twrp-installer-v3.3.1-V50_ab.zip )
View attachment twrp-installer-v3.3.1-V50_ab.zip
3.Install the corresponding TWRP flash module in Magisk Manager, remember not to restart
The module is one-time, and it will be deleted automatically after TWRP is successfully brushed in
{
"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"
}
4.Re-swipe the Magisk 20.4 card package in Magisk Manager
5.Verify that TWRP is successfully installed
adb reboot recovery
6.Wait for the phone to restart to the TWRP interface, I believe everyone knows what this thing looks like
7.Disable_Dm-Verity can solve the problem of decryption failure after booting

Does this still have the touchscreen issue if you boot from OS to Recovery?

5dprince said:
1 . unlock BootLoader AND Root https://forum.xda-developers.com/v5...g-v50-temp-root-exploit-via-cve-2020-t4098077
2. Download the required files ( twrp-installer-v3.3.1-V50_ab.zip )
3.Install the corresponding TWRP flash module in Magisk Manager, remember not to restart
The module is one-time, and it will be deleted automatically after TWRP is successfully brushed in
4.Re-swipe the Magisk 20.4 card package in Magisk Manager
5.Verify that TWRP is successfully installed
adb reboot recovery
6.Wait for the phone to restart to the TWRP interface, I believe everyone knows what this thing looks like
7.Disable_Dm-Verity can solve the problem of decryption failure after booting
Click to expand...
Click to collapse
Dude. You didn't say to flash magisk again, nor did you credit the author of the twrp. And touchscreen does not work with the adb command, so I do not know why you said to do that instead of the key combo...

Indeed, there are some problems with the touch screen in this TWRP version. Can anyone elaborate on how do I even boot into it with key combination? I've been fiddling with them for about half an hour before I dropped it on the carpet and it booted, and I had exactly one chance to flash everything before a reboot, I'd rather know what I pressed if I ever want to do that again.
UPD: getting into TWRP is almost like on v30: power+volUp, when logo appears you let go of power button and immediately press it again, then proceed to factory reset option which will boot you to TWRP. I'll leave it here in case somebody will google it later.
https://youtu.be/b1lnYdNxVMg

The issue with touch not always working in TWRP is that the stock kernel disables the touch driver when the boot reason is recovery (aka from adb reboot recovery), while via button combo, the reason isnt "recovery", so touch works in TWRP

Is there a way to get twrp image somewhere? If I now have unlocked bootloader, won't I be able to just flash it from fastboot?

Installed it but can't mount my internal storage in TWRP. Anyone else have this issue?

SGCMarkus said:
The issue with touch not always working in TWRP is that the stock kernel disables the touch driver when the boot reason is recovery (aka from adb reboot recovery), while via button combo, the reason isnt "recovery", so touch works in TWRP
Click to expand...
Click to collapse
And what would be the combination of buttons to start the TWRP with active touch functionality? If I install TWRP from fastboot is it different than if I install it from QFIL?

Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.

GeoFX said:
Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.
Click to expand...
Click to collapse
That would be great.

smitra420 said:
Installed it but can't mount my internal storage in TWRP. Anyone else have this issue?
Click to expand...
Click to collapse
See https://forum.xda-developers.com/t/twrp_3-3-1-for-usa.4304847/.

GeoFX said:
Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.
Click to expand...
Click to collapse
is this available yet, for the LM-V500EM?

Didn't work for me 500N problem of decryption failure after booting, how to disable it?

didn't work for me LM-V500EM after boot twrp asks for decryption password ?

GeoFX said:
Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.
Click to expand...
Click to collapse
I don't think that's possible since this device does not have a separate recovery partition so this patch unpacks the boot ramdisk and injects twrp code there - not doable via fastboot.

antintin said:
Dude. You didn't say to flash magisk again, nor did you credit the author of the twrp. And touchscreen does not work with the adb command, so I do not know why you said to do that instead of the key combo...
Click to expand...
Click to collapse
Exactly. The pictures no longer display and this magisk is different than the latest. Do we leave dmverity checked in magisk?
I rebooted before re flashing magisk again because I've never done this and its mind boggling to have to flash magisk twice (why couldn't it stick the first time or have an obvious option?). Anyway. Anyone know how to reverse the softbootloop these instructions result in!?!

How do I get root back after magisk flashed twrp and lied? When I go to recovery, its stock. Now when I replace boot_a with magisk patched in edl mode bootloop! This worked the first time why doesn't it any longer?

q-killer said:
How do I get root back after magisk flashed twrp and lied? When I go to recovery, its stock. Now when I replace boot_a with magisk patched in edl mode bootloop! This worked the first time why doesn't it any longer?
Click to expand...
Click to collapse
Why would you want TWRP if you weren't going to replace the OS? Go into TWRP and flash something else, with Magisk as well.
For anyone reading, the button combo to get into TWRP is Vold down + power. As soon as LG Logo starts up, you release power for a second then go back to pressing it. Phone will ask if you want to erase data. Select yes, and yes. Phone will boot TWRP.

TPMJB said:
Why would you want TWRP if you weren't going to replace the OS? Go into TWRP and flash something else, with Magisk as well.
For anyone reading, the button combo to get into TWRP is Vold down + power. As soon as LG Logo starts up, you release power for a second then go back to pressing it. Phone will ask if you want to erase data. Select yes, and yes. Phone will boot TWRP.
Click to expand...
Click to collapse
Thanks for this question, and advice on getting to recovery with keys, it's the only way to get touchscreen support in recovery, and it's a good question... unfortunately my phone no longer asks if I want to erase data for some odd reason when accessing recovery... this really tripped me up. I was trying to flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, but it was too late in this instance as system was already encrypted. so the mistake made was that I didn't disable dmverity, which needs to be done either before setup, or directly after first restart. Otherwise system starts encrypting and it seems boot_a is encrypted and can't be directly replaced via qfil, since it causes a bootloop at that point. I wasn't able to access and therefore fix NT-Code issue errors (observed after cross flashing) at this point either, so the key is to first backup or get a copy of vmeta_a and boot_a along with other key files, then flash engineering (eng_abl) in qfil so that fastboot can be accessed and then fastboot --disable-verity --disable-verification flash vbmeta vbmeta_a-v50original.bin, place backed up boot_a on phone, patch with Majisk, copy back to pc, then flash patched boot with qfil or fastboot, Then fastboot flash abl_a abl_a(orig-nonENG).bin, also then restore ftm-original and modem_a/b-original with same method in fastboot or using qfil, rebot then *#*#4636#*#* choose automatic and NR/LTE/CDMA/EcDO/GSM/WCDMA , then append NT errors to /Product/OP/cust_path_mapptings.cfg following format there, and then finally flash twrp via magisk but don't reboot, and then reflash magisk.zip, and reboot. Finally, following guides for adaway, revanced, and wallet hiding should work. There are a ton of steps to this phone, especially sprint version.

i have lg v50 450 verizon model number lm-g850 android version 10 g85020j
does not read sim cards.
How to unlock the bootloader on it and flash it. Thank you !!!

Redmi note 8 wipe all partitions since twrp got bricked

Bien...
I was trying to flash the EU rom on my Redmi Note 8, but I did wype to all the partitions, until that moment I had informed myself about how to flash, how to root and use twrp, but the issue of the partitions still did not know, I selected all the partitions except data and sd and I did wype, in the end my cell phone was completely bricked, I try to turn it on and for a period of less than half a second, I get the Redmi logo, below it says Powred by Android and above I get a padlock open indicating that the bootloader is unlocked, then I get a screen with the message "System has been destroyed" and then it turns off, unless I put it to load, in that case it enters the bootloop state, I cannot enter the recovery but yes I can enter fastboot, I tried to flash it through My Flash Tool and ADB, the problem is that the computer recognizes that the bootloader is unlocked, but when flashing it, a message appears that the bootloader It is locked, so flashing it is not an option, for that reason, I assume that the testpoint method for flashing by EDL would not work either.
That happened three weeks ago, at first I did not know the reason for the problem, later I learned more, I will not make that mistake again, but I am interested in knowing if there is a software solution; I would be interested in being able to download all the partitions and install them on my cell phone using the computer, I don't know if any of those who read this have the opportunity to find the partitions and share them here, I don't know if it is a realistic option, but I have hope, I saw that That solution worked with a OnePlus 3 and that's why I'm looking for information about my cell phone. The only other option I can think of is to change the motherboard, but it's very expensive and with that money, I'd better buy another cell phone.
By the way, my cell phone was in very good condition despite having used it for a year, it was very well cared for and I had no problems with both software and hardware, the reason why I was trying to change to the EU rom is because the Global version was to be a decaf version of the update.
I hope that someone can help to find a solution. Thanks for your understanding.

Diego_Arturo said:
Bien...
I was trying to flash the EU ...
Click to expand...
Click to collapse
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended

loopypalm said:
wiping partition is not a problem in RN8, i wipe all the time before flashing roms ...
download the attached file or use your own adb/vbmeta
reboot to fastboot mode (hold power and Vol -)
choose :
2. Fix "The system has been destroyed"
or (if you have the files)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
reboot to recovery and flash orangefox , it will reboot again to recovery
check the option :
"aggressive stock recovery deactivation"
if you still want "sh*tui" use recovery flashable zip, not fastboot zips ...
but i highly recommend using custom roms
if you want A10 use RRos or MSM ext or AEX
A11 is still not that good, but if you still want A11 use Xtended XR or POSP
a clean flash is always recommended
Click to expand...
Click to collapse
I understand what you are saying, the problem is that I deleted all the partitions (/ boot, / system, / misk, and several others that I do not remember), the only ones that I did not delete were sd and data. I read that if you delete the boot partition, you should not restart the cell phone, you must flash a rom with the boot partition, if you don't, the cell phone will not start the operating system
Another thing: I didn't flash any ROMs, twrp didn't read my storage well and couldn't find the .zip file of the EU rom, I just wipe and reboot without flashing anything. I do not know why the cell phone still detects the system for a very brief moment before showing that the system has been destroyed, the problem is that it does not start. And when I try to flash the original ROM, the computer detects that the bootloader is unlocked, but when flashing I get an error saying that it is locked, it occurs to me that possibly the bootloader was one of the first things to be erased, but it was not completely erased Maybe the kernel or ramdisk was deleted and after that everything stopped and the cell phone just bricked, I don't know if I'm correct.

Diego_Arturo said:
I understand what you say, the problem is that I did wipe to all partitions, (/ boot, / system, / recovery, / cache, / misc and several others that I do not remember), I just did not wipe to SD and data partitions. I understand that if you delete the boot partition you must have a ROM ready that comes with a boot partition, or else you would be left with a hardbrick. What I don't know is if I can force the installation of all partitions.
Click to expand...
Click to collapse
-how did you wipe recovery ? did you use flashtool or something ?
-all roms now comes with boot img (boot partition is where the kernel files are stored) , so no problem wiping it (same for dalvik/cache/system/vendor/data)
yes, you can flash img files of partitions using fastboot (if that what you mean with force install a partition)
-what you should try now is reinstalling twrp 1st

nteresting ... It reassures me to know that I don't need to search for the partitions separately and only need to flash the ROM, although I am concerned about the same problem when flashing. I tried to flash using Mi Flash Tool, ADB and XiaoMi Tool V2, but it is always the same problem, it detects the unlocked bootloader, but when flashing it gives me an error.
I deleted all the partitions from TWRP, it was weird, because the videos didn't show many of the partitions that came out for me, that's why I don't remember them. Before doing wipe I made a copy of everything in case something went wrong, but in the end everything went wrong ...
Now that I remember, I deleted the partitions because when I tried to do anything, I got red letters and TWRP wouldn't let me do anything, when I deleted them the letters turned blue.
It seems to me that I tried to install TWRP from XiaoMi Tool v2 although I don't remember correctly, I will try and write again.

I HAVE ADVANCES!
I flashed the partitions one by one because Flash Tool still does not let me flash the ROM, on one occasion I flashed the system, but in the end it did not finish flashing, I still got the error "System has ben destroyed", I kept flashing partitions but there was no Result, in the end I flashed the system again and when it finished flashing, the error system has ben destroyed no longer appeared, now my cell phone is in a permanent bootloop state with the redmi logo, but it already lets me enter TWRP, I can't flash it from the computer, I'm going to try to get an SD card and flash it from recovery, I'm going to try to flash the EU ROM, but it's already a breakthrough, I don't have a hard brick anymore.

Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
I thank you very much for helping me find a solution, I hope this helps someone else and this serves me as my experience, I managed to solve a serious problem that I made and you helped me ... Thank you very much.

Diego_Arturo said:
Solved !!!
My computer detected the storage of my cell phone, so I transferred the .zip file from the EU ROM to my cell phone and from TWRP I flashed it. Now I have MIUI 12.6 with Android 11 and I have a weekly OTA update pending. I didn't get TWRP cleared, so I won't have to flash it again.
Click to expand...
Click to collapse
Glad it work for you ^........^ !
all sensors are working fine ?
Diego_Arturo said:
Thank you very much.
Click to expand...
Click to collapse
you know what to do
{
"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"
}

For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.

Diego_Arturo said:
For now everything seems to be going well, I notice a little lag, but it seems to be normal, also a big update came compared to the version it had before bricking, also, I had already seen that it is normal for the cell phone to go a little Lagged after an update and that resolves itself over time. If it's some EU ROM bug, no problem, weekly updates are coming. I will continue to use it and write my experience.
Thank you very much for your help.
Click to expand...
Click to collapse
Miui roms are resource hungry and lag is not their only problem , battery and performance are also affected ...
i think you should try custom roms

First, I didn't want to, I preferred to wait, but seeing how slow the cell phone was and how fast the battery was draining, I felt that the best in the long run would be to install a ROM that did not consume so many resources, so I installed the latest version of Pixel Experience. I have to say that I did not expect anything from this ROM, I just expected fluidity and more battery, but in the end I liked it. I personally like MIUI, but I think that Pixel Experience could extend the life of my cell phone. I will continue using it and possibly in the future I will return to MIUI to see how it goes.

Question Unable to install Custom rom on mi 11 lite 13.0.7.0 SKOINXM

Hi,
Everytime I try to install recovery device stucks in fastboot screen the only way to get out of it is to install miui thru mi flash
Guide me through how to install custom rom on miui 13.0.7.0
Thanks in advance

Crazymods said:
Hi,
Everytime I try to install recovery device stucks in fastboot screen the only way to get out of it is to install miui thru mi flash
Guide me through how to install custom rom on miui 13.0.7.0
Thanks in advance
Click to expand...
Click to collapse
Installed the correct firmware before flashing.
for example for this rom
https://forum.xda-developers.com/t/rom-12-1-official-pixelos-aosp-stable-15-08-2022.4392297/
This firmware
https://sourceforge.net/projects/pixelos-releases/files/twelve/lisa/firmware/
Most often it is global or CN firmware.

NOSS8 said:
Installed the correct firmware before flashing.
for example for this rom
https://forum.xda-developers.com/t/rom-12-1-official-pixelos-aosp-stable-15-08-2022.4392297/
This firmware
https://sourceforge.net/projects/pixelos-releases/files/twelve/lisa/firmware/
Most often it is global or CN firmware.
Click to expand...
Click to collapse
Thanks for the quick reply
I wanted to install CorvusOs also tried but failed, everytime I try to install recovery it mess ups my firmware

Crazymods said:
Thanks for the quick reply
I wanted to install CorvusOs also tried but failed, everytime I try to install recovery it mess ups my firmware
Click to expand...
Click to collapse
Can you post the rom link?

NOSS8 said:
Can you post the rom link?
Click to expand...
Click to collapse
Thread '[SHARED] CorvusOS 4.0-L v12.1 - UNOFFICIAL | Android 12L. Vanilla/GApps | Updated: 2022/08/22' https://forum.xda-developers.com/t/...12l-vanilla-gapps-updated-2022-08-22.4484681/

Crazymods said:
Thread '[SHARED] CorvusOS 4.0-L v12.1 - UNOFFICIAL | Android 12L. Vanilla/GApps | Updated: 2022/08/22' https://forum.xda-developers.com/t/...12l-vanilla-gapps-updated-2022-08-22.4484681/
Click to expand...
Click to collapse
Seems this ROM is for Renoir device
{
"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"
}

Think I should flash pixelos

Crazymods said:
Think I should flash pixelos
Click to expand...
Click to collapse
Yeap, try this rom.
Flashing the correct firmware with the TWRP but sometimes it does not work, the method that works 100% is to use Miflash(without relocking the bootloader) and let the phone restart then switch to fastboot mode once arrived at the request of the Xiaomi account.
Install TWRP
Twrp
Wipe/format data type yes
reboot twrp
put the rom in internal storage or use Otg
Flash rom
• After installation complete, Reboot system
if bootloop format data and reboot system.
This method differs from that recommended by the OP but remains the most common one, you can use that of the OP, at your choice.
In any case, formatting the data does not erase the previously installed firmware.
.Use 12 version
https://pixelos.net/download/lisa

NOSS8 said:
Yeap, try this rom.
Flashing the correct firmware with the TWRP but sometimes it does not work, the method that works 100% is to use Miflash(without relocking the bootloader) and let the phone restart then switch to fastboot mode once arrived at the request of the Xiaomi account.
Install TWRP
Twrp
Wipe/format data type yes
reboot twrp
put the rom in internal storage or use Otg
Flash rom
• After installation complete, Reboot system
if bootloop format data and reboot system.
This method differs from that recommended by the OP but remains the most common one, you can use that of the OP, at your choice.
In any case, formatting the data does not erase the previously installed firmware.
.Use 12 version
https://pixelos.net/download/lisa
Click to expand...
Click to collapse
Can you guide more briefly because I messed my os everytime I use adb command

Crazymods said:
Can you guide more briefly because I messed my os everytime I use adb command
Click to expand...
Click to collapse
No ADb command performed.
where are you with the method?

NOSS8 said:
No ADb command performed.
where are you with the method?
Click to expand...
Click to collapse
The moment I type "fastboot flash boot" Drag and drops file I get stuck at bootloop

Crazymods said:
The moment I type "fastboot flash boot" Drag and drops file I get stuck at bootloop
Click to expand...
Click to collapse
Clean flash (coming from a different ROM):
• Reboot to bootloader (fastboot)
• Connect phone to PC
• fastboot flash boot boot.img
• fastboot reboot recovery
• Select Wipe data/factory reset & confirm
• Go back and select Apply update from ADB
• adb sideload PixelOS*.zip
• Flash latest firmware from the link above
• adb sideload fw_lisa*.zip
• After installation complete, Reboot system.
or use my method with twrp.

NOSS8 said:
Clean flash (coming from a different ROM):
• Reboot to bootloader (fastboot)
• Connect phone to PC
• fastboot flash boot boot.img
• fastboot reboot recovery
• Select Wipe data/factory reset & confirm
• Go back and select Apply update from ADB
• adb sideload PixelOS*.zip
• Flash latest firmware from the link above
• adb sideload fw_lisa*.zip
• After installation complete, Reboot system.
or use my method with twrp.
Click to expand...
Click to collapse
Thanks I, ll get back to you

Crazymods said:
Thanks I, ll get back to you
Click to expand...
Click to collapse
In case that doesn't work, detail what you did.

so heres what i did till now
1-i tried to flash twrp and orange fox but unable to boot them i`m stuck at fastboot now

Crazymods said:
so heres what i did till now
1-i tried to flash twrp and orange fox but unable to boot them i`m stuck at fastboot now
Click to expand...
Click to collapse
What command did you use?

NOSS8 said:
What command did you use?
Click to expand...
Click to collapse
"fastboot flash boot" drag and dropped file

Crazymods said:
"fastboot flash boot" drag and dropped file
Click to expand...
Click to collapse
Command is" fastboot boot twrp.img' phone in fastboot mode.
then in Twrp go to Advanced -> flash current TWRP

NOSS8 said:
Command is" fastboot boot twrp.img' phone in fastboot mode.
then in Twrp go to Advanced -> flash current TWRP
Click to expand...
Click to collapse

Rename to twrp.img.
The command from the folder where the img is.
You must have flashed the xiaomi rom first to be on the correct firmware. How did you proceed?