Hi everyone, sorry for my bad english but i sure we can help me to find a PIXEL EXPERIENCE fluid rom for my Xiaomi Mi 11 Lite 5G (8+128).
I searched the entire internet to find the rom but none of that are good for myself.
FCsperimentx said:
Hi everyone, sorry for my bad english but i sure we can help me to find a PIXEL EXPERIENCE fluid rom for my Xiaomi Mi 11 Lite 5G (8+128).
I searched the entire internet to find the rom but none of that are good for myself.
Click to expand...
Click to collapse
you have to take GSI rom here..
You can check my personal PE 12.0 build, been using it for 2 weeks and it works alright not 100% perfect.
Releases · aurotones/renoir
Contribute to aurotones/renoir development by creating an account on GitHub.
github.com
Ho un grosso problema sul mio dispositivo: quando provo a installare una rom personalizzata lo smartphone si blocca sul bootloop e I install again the stock miui con MIFlashTool.
I tried everything but the smartphone still have this problem.
FCsperimentx said:
Ho un grosso problema sul mio dispositivo: quando provo a installare una rom personalizzata lo smartphone si blocca sul bootloop e I install again the stock miui con MIFlashTool.
I tried everything but the smartphone still have this problem.
Click to expand...
Click to collapse
i updated install instructions. Also don't forget you must be on MIUI 12.5.7 firmware base.
I downloaded MIUI 12.5.7 but everything is the same.
Now when i write .\adb reboot fastboot the phone reboot itself on FASTBOOTD.
I tried everything but nothing just change because the xiaomi’s stuck on bootloop.
FCsperimentx said:
I downloaded MIUI 12.5.7 but everything is the same.
Now when i write .\adb reboot fastboot the phone reboot itself on FASTBOOTD.
I tried everything but nothing just change because the xiaomi’s stuck on bootloop.
Click to expand...
Click to collapse
You downloaded MIUI 12.5.7 is a good start but you could have alternatively download and flash only the firmware base which is only about 100MB. Also I see the instructions were not 100% clear, hope this will be clear enough for you. Also before you do, backup your files!
1. You supposed to go into bootloader, not fastboot.
Code:
adb reboot bootloader
2. Flash boot.img and vendor_boot.img files through fastboot command on your PC.
Code:
fastboot flash boot_ab ./boot.img
fastboot flash vendor_boot_ab ./vendor_boot.img
3. Now you need to go into recovery mode. It should say pixel experience recovery on top of the screen.
Code:
fastboot reboot recovery
4. Select Apply update -> Apply from ADB.
5. Now sideload the zip file through adb command on your PC
Code:
adb sideload ./PixelExperience_renoir-***.zip
6. You may need to format your data so it will boot properly.
Above commands are examples but might be different on your type of operating system you're using, so take them as example, not the exact command that will guaranteed to work.
If you're still having problem then, there's underlying problem that i'm not aware of and hope someone else will help you to flash it.
Hi, I don't get it I tried everything can't make it work. I finally flashed vendor_boot, and booted on TWRP 3.6.1_11-0 in order to manage to side load on Renoir, and I get this error all time (with the 12 and 12 plus official release of pixel experience) as on the picture.
Could you help me, it's been 6 month I don't manage to installé any pixel experience on this phone. First time I' m stuck with a smartphone ever ... Official/gsi nothing works, I only manage to flash the MIUI ROM and lineage os....
I'm desperate .
Eightkiller said:
Hi, I don't get it I tried everything can't make it work. I finally flashed vendor_boot, and booted on TWRP 3.6.1_11-0 in order to manage to side load on Renoir, and I get this error all time (with the 12 and 12 plus official release of pixel experience) as on the picture.
Could you help me, it's been 6 month I don't manage to installé any pixel experience on this phone. First time I' m stuck with a smartphone ever ... Official/gsi nothing works, I only manage to flash the MIUI ROM and lineage os....
I'm desperate .
Click to expand...
Click to collapse
TWRP doesn't support Android 12 yet, you need LineageOS or Pixel Experience recovery to sideload.
Edit: Follow instructions here: https://wiki.pixelexperience.org/devices/renoir/install/
aurotones said:
TWRP doesn't support Android 12 yet, you need LineageOS or Pixel Experience recovery to sideload.
Edit: Follow instructions here: https://wiki.pixelexperience.org/devices/renoir/install/
Click to expand...
Click to collapse
Thx for your answer the problem is I can't manage to boot on pixel experience recovery as shown in the tutorial. It says ok when I flash but I can only get to fastboot. And when I just try to fastboot boot 'myrecovery.img', it just rebbotsyto fastboot. That's why I tried to boot on TWRP which works without any trouble :s
Eightkiller said:
Thx for your answer the problem is I can't manage to boot on pixel experience recovery as shown in the tutorial. It says ok when I flash but I can only get to fastboot. And when I just try to fastboot boot 'myrecovery.img', it just rebbotsyto fastboot. That's why I tried to boot on TWRP which works without any trouble :s
Click to expand...
Click to collapse
TWRP will never work but while you're on TWRP your base should be on V12.5.7.0.RKIEUXM, flash that first in TWRP and then maybe try flash boot.img and vendor_boot.img and go to recovery mode. Without it you will never be able to install. Please give me details what your phone is, is it 5G variant with renoir codename?, is it global or china?, did it had MIUI 12.5 or 13?, these informations are necessary.
aurotones said:
TWRP will never work but while you're on TWRP your base should be on V12.5.7.0.RKIEUXM, flash that first in TWRP and then maybe try flash boot.img and vendor_boot.img and go to recovery mode. Without it you will never be able to install. Please give me details what your phone is, is it 5G variant with renoir codename?, is it global or china?, did it had MIUI 12.5 or 13?, these informations are necessary.
Click to expand...
Click to collapse
It had MIUI 12.x and it is a "eu" phone, I tried to flash the V12.5.7.0.RKIEUXM (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0) from twrp it's not working with the same errors messages. I don't really know what to do, i managed to put back my 12.6 beta stock miui from "xiaomi.eu_multi_MI11Lite5G_21.7.7_v12-11-fastboot" version.
When i'm stuck i'm forced to install this back to not be stuck on fastboot loop. I found a "renoir_eea_global_images_V12.5.7.0.RKIEUXM_20220105.0000.00_11.0_eea" fastboot version but the installation is not working (would you have one working from my config ?).
I also tried to flash the firmware (fw_renoir_miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0 ~104mo) which gave me an "orange" fastboot instead of the fastboot with the funny character. And tried to install the recovery from pixel after but still stuck on fastboot.
Hope it will help you a bit more to help me
Eightkiller said:
It had MIUI 12.x and it is a "eu" phone, I tried to flash the V12.5.7.0.RKIEUXM (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0) from twrp it's not working with the same errors messages. I don't really know what to do, i managed to put back my 12.6 beta stock miui from "xiaomi.eu_multi_MI11Lite5G_21.7.7_v12-11-fastboot" version.
When i'm stuck i'm forced to install this back to not be stuck on fastboot loop. I found a "renoir_eea_global_images_V12.5.7.0.RKIEUXM_20220105.0000.00_11.0_eea" fastboot version but the installation is not working (would you have one working from my config ?).
I also tried to flash the firmware (fw_renoir_miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0 ~104mo) which gave me an "orange" fastboot instead of the fastboot with the funny character. And tried to install the recovery from pixel after but still stuck on fastboot.
Hope it will help you a bit more to help me
Click to expand...
Click to collapse
i feel like your partition is messed up by TWRP so my advice is clean flash V12.5.7.0 fastboot rom with method of "flash_all.bat" on windows, "flash_all.sh" on linux i forgot the filenames but there's also method with lock in the name which you should avoid and then never touch or install TWRP as it's a bit unstable even with Android 11 roms, now you flash boot.img and vendor_boot.img provided by Pixel Experience through bootloader that only spells fastboot, no extra letter at the end.
This is important, Rebooting into bootloader and fastboot is different, when you do 'adb reboot fastboot' it will show fastbootd with orange text which something you should avoid, instead do 'adb reboot bootloader' or by vol down + power button and flash those 2 files.
If you still having problems try changing your boot slot by
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
And then
Code:
fastboot reboot recovery
If you still having problems, then head over to this telegram group and get help from ROM maintainer: https://t.me/arixelogroup
The Official build Pixel Experience is now available for renoir
It works perfectly on my device
PE for renoir
RGB39 said:
The Official build Pixel Experience is now available for renoir
It works perfectly on my device
PE for renoir
Click to expand...
Click to collapse
Attention that, Don't flash miui13 before flashing pe, or your wlan won't work.
aurotones said:
i feel like your partition is messed up by TWRP so my advice is clean flash V12.5.7.0 fastboot rom with method of "flash_all.bat" on windows, "flash_all.sh" on linux i forgot the filenames but there's also method with lock in the name which you should avoid and then never touch or install TWRP as it's a bit unstable even with Android 11 roms, now you flash boot.img and vendor_boot.img provided by Pixel Experience through bootloader that only spells fastboot, no extra letter at the end.
This is important, Rebooting into bootloader and fastboot is different, when you do 'adb reboot fastboot' it will show fastbootd with orange text which something you should avoid, instead do 'adb reboot bootloader' or by vol down + power button and flash those 2 files.
If you still having problems try changing your boot slot by
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
And then
Code:
fastboot reboot recovery
If you still having problems, then head over to this telegram group and get help from ROM maintainer: https://t.me/arixelogroup
Click to expand...
Click to collapse
Thx, but that's what i'm trying to do since yesterday, but i don't manage to fresh install 12.5.7.0 with the fastboot rom i found (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0
I always get errors when i run the flash_all.bat, saying that my rom is more recent than the one i'm trying to flash. I tried to delete the "if statement" checking for the versions, but seems to mess up with the "directories name" after.
Would you have some link or place where i can get a working 12.5.7.0 with fastboot install ? I'll try it properly from this one.
Thanks in advance.
Eightkiller said:
Thx, but that's what i'm trying to do since yesterday, but i don't manage to fresh install 12.5.7.0 with the fastboot rom i found (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0
I always get errors when i run the flash_all.bat, saying that my rom is more recent than the one i'm trying to flash. I tried to delete the "if statement" checking for the versions, but seems to mess up with the "directories name" after.
Would you have some link or place where i can get a working 12.5.7.0 with fastboot install ? I'll try it properly from this one.
Thanks in advance.
Click to expand...
Click to collapse
Use XiaoMiFlash
Download Official Xiaomi Mi Flash Tool All Versions
xiaomimiflashtool.com
or fastboot v29.0.5
Download Platform Tools for Android SDK Manager
Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net
mitanyan98 said:
Use XiaoMiFlash
Download Official Xiaomi Mi Flash Tool All Versions
xiaomimiflashtool.com
or fastboot v29.0.5
Download Platform Tools for Android SDK Manager
Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net
Click to expand...
Click to collapse
Thx for your answer, as i was saying: same error with mi flash tool (look the screenshot)
And if i comment the "checking parts" inside the .bat files, i get directories error on windows: it does not seem to check properly my direcotries name
for example a line is like this:
fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
the %~dp0images seems to be my path, but it's not taken properly into accoutn, seems to have " quote problems with the path
Edit: I had to double quote " the path inside the script as my path was having spaces inside
Thx for you help, I managed to install it, the only problem was to properly install 12.5.7 After succeding that everything worked as it should
RGB39 said:
Attention that, Don't flash miui13 before flashing pe, or your wlan won't work.
Click to expand...
Click to collapse
So that's why... so many hours wasted trying to get Wi-Fi to work. I had the "fantastic idea" of flashing the official global miui (renoir_global_images_V13.0.4.0.SKIMIXM_20220412....) prior to installing DotOS and when wi-fi did not work, flashed Pixel Experience...
And I'm pretty sure flashing miui 12.x will trigger ARB and brick the phone. Right?
Related
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
_____________________________________________________________________________________________
UPDATE: The cell phone was completely downloaded. I plugged it into the computer and was able to enter Fastboot mode. So again I have TWRP for OREO.
But I still have a boot loop of "Error MODE". Any idea how to fix it?
TWRP 8 Oreo https://ibb.co/nEn5HS
Error MODE https://ibb.co/mrErrn
Aspiranteh said:
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock oem xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
Sorry bad english.
Click to expand...
Click to collapse
try to flash stock recovery then try force upgrade method.
h30_u10 said:
try to flash stock recovery then try force upgrade method.
Click to expand...
Click to collapse
Edit:
I can flash the recovery stock however, I don't know if in android OREO I can install full firmware through a folder (dload) on the SD card. Is there a similar way as in Nougat and earlier versions of android?
Try to flash your rom with twrp and install magisk before trying to boot into rom. Magisk patch boot.img and remove many security/error check when booting to rom.
rhaavin said:
Try to flash your rom with twrp and install magisk before trying to boot into rom. Magisk patch boot.img and remove many security/error check when booting to rom.
Click to expand...
Click to collapse
I'll give it a try. The problem is that the Rom Oreo I have is not flash for TWRP. I have searched but I still can't find an Oreo ROM that can be flashed by TWRP.
I found this method: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
that I think can work. However, it is for Mate 9, so I have to replace the files with those of Mate 10 lite and rename them as if they were Mate 9. Although I'm not sure what I should extract from Update.app to rename.
If someone could guide me, I'd be very grateful.
If that doesn't work, I will try this other method I found by browsing the forums. [ Chuckles]
https://forum.xda-developers.com/showpost.php?p=75628230&postcount=71
Any contribution is welcome.
Translated with www.DeepL.com/Translator
I stucked on the same or very similar fastboot screen, phones OS was oreo, here is why it happened:
I tried to use command fastboot flash recovery TWRP3.1.1.img
It will always show Failure message.
Then on this kind XDA forum I came to know that the recovery location is changed in oreo to
recovery_ramdisk I flashed with: fastboot flash recovery_ramdisk TWRP3.1.1.img
And thus reached the same fastboot error screen you have posted.
Workaround was: Get the update.app file from the update zip files (I used HWOTA method
to upgrade to Oero when my device was already soft bricked). So used update extractor
to pull out UPDATE.APP file form the biggesst update zip file from HWOTA folder,
but first u have to go to settings and disable header check sum option otherwise it will show error.
So I pulled out the proper stock recovery file named like: recovery_ramdisk.img
I used command: fastboot flash recovery_ramdisk revcovery_ramdiskimg
Now I got the stock recovery that I can use to wipe data and do factory reset.
So if you can come to this point, may be after factory reset you would be able to get it back.
Good luck.
Fix Error (SOLVE)
I can say from experience that the same thing happened to me, and the only thing you have to do is wait until your phone has a 0% charge, leaving the screen turned on with the error.
When that happens, connect the original cable to the PC and connect it in Fasboot mode, unlock the bootloader if you do not have it, then install the firmware of it ... with the HWOTA tool that you will see in one of the posts in this section ... you will have to have the three corresponding files of the same one ... the UPDATE, DATA, DATAPUBLIC and follow the steps in the post of HWOTA ... and you will relive your team.
Greetings ... I hesitate to answer for the difference of time and my work ... Greetings from Panama
Aspiranteh said:
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
_____________________________________________________________________________________________
UPDATE: The cell phone was completely downloaded. I plugged it into the computer and was able to enter Fastboot mode. So again I have TWRP for OREO.
But I still have a boot loop of "Error MODE". Any idea how to fix it?
TWRP 8 Oreo https://ibb.co/nEn5HS
Error MODE https://ibb.co/mrErrn
Click to expand...
Click to collapse
usman400 said:
I stucked on the same or very similar fastboot screen, phones OS was oreo, here is why it happened:
I tried to use command fastboot flash recovery TWRP3.1.1.img
It will always show Failure message.
Then on this kind XDA forum I came to know that the recovery location is changed in oreo to
recovery_ramdisk I flashed with: fastboot flash recovery_ramdisk TWRP3.1.1.img
And thus reached the same fastboot error screen you have posted.
Workaround was: Get the update.app file from the update zip files (I used HWOTA method
to upgrade to Oero when my device was already soft bricked). So used update extractor
to pull out UPDATE.APP file form the biggesst update zip file from HWOTA folder,
but first u have to go to settings and disable header check sum option otherwise it will show error.
So I pulled out the proper stock recovery file named like: recovery_ramdisk.img
I used command: fastboot flash recovery_ramdisk revcovery_ramdiskimg
Now I got the stock recovery that I can use to wipe data and do factory reset.
So if you can come to this point, may be after factory reset you would be able to get it back.
Good luck.
Click to expand...
Click to collapse
I also uploaded to OREO by HWOTA like you, I managed to do it without problems, all functional. Then I don't remember why but I decided to give wipes and that's when my problem started.
Yes, recovery_ramdisk was already in consideration.
I even flashed:
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash kernel kernel.img
fastboot flash system system.img
fastboot reboot
but I can't get it to start just throw that "MODE ERROR" at me, I don't think system is completely installed :/ /
emorenoebultron said:
I can say from experience that the same thing happened to me, and the only thing you have to do is wait until your phone has a 0% charge, leaving the screen turned on with the error.
When that happens, connect the original cable to the PC and connect it in Fasboot mode, unlock the bootloader if you do not have it, then install the firmware of it ... with the HWOTA tool that you will see in one of the posts in this section ... you will have to have the three corresponding files of the same one ... the UPDATE, DATA, DATAPUBLIC and follow the steps in the post of HWOTA ... and you will relive your team.
Greetings ... I hesitate to answer for the difference of time and my work ... Greetings from Panama
Click to expand...
Click to collapse
Yes, I really think this is the solution but it's only posted HWOTA and not HWOTA8 for Mate 10 lite... If there was only one HWOTA8 for our equipment, I'm sure I could fix it .
Aspiranteh said:
I also uploaded to OREO by HWOTA like you, I managed to do it without problems, all functional. Then I don't remember why but I decided to give wipes and that's when my problem started.
Yes, I really think this is the solution but it's only posted HWOTA and not HWOTA8 for Mate 10 lite... If there was only one HWOTA8 for our equipment, I'm sure I could fix it .
Click to expand...
Click to collapse
hmmm since I am all set with Oreo update and its working and I am not a very advanced user in flashing etc.
So am not going to any further thing until proper oreo update comes
But I was thinking at a point, why not go through existing HWOTA script, change the commands where recovery
is referred, (change recovery to recovey_ramdisk in any fastboot command found inside script), then running it to
try luck.
Also I think TWRP for mate 10 lite for Oreo version was made available a few days ago in this forum, search it
usman400 said:
hmmm since I am all set with Oreo update and its working and I am not a very advanced user in flashing etc.
So am not going to any further thing until proper oreo update comes
But I was thinking at a point, why not go through existing HWOTA script, change the commands where recovery
is referred, (change recovery to recovey_ramdisk in any fastboot command found inside script), then running it to
try luck.
Also I think TWRP for mate 10 lite for Oreo version was made available a few days ago in this forum, search it
Click to expand...
Click to collapse
Forgive my ignorance but what would be the script to edit, I downloaded the HWOTA again to modify it but I don't really know which file to modify. :confuso:
** @vovan1982 Hi, excuse me. I saw you post HwOTA for Mate 10 lite, do you know if there are any options for HwOTA8? Thank you very much in advance!
Aspiranteh said:
Forgive my ignorance but what would be the script to edit, I downloaded the HWOTA again to modify it but I don't really know which file to modify. :confuso:
** @vovan1982 Hi, excuse me. I saw you post HwOTA for Mate 10 lite, do you know if there are any options for HwOTA8? Thank you very much in advance!
Click to expand...
Click to collapse
If you can enter to trwp8, I can try to give you my backup of oreo mate 10. The problem for the script is, I think, the recovery push by vovan1982 is not comptatible with the aero installed, and when you are in twrp8, usb cable don't work!
gmbengue said:
If you can enter to trwp8, I can try to give you my backup of oreo mate 10. The problem for the script is, I think, the recovery push by vovan1982 is not comptatible with the aero installed, and when you are in twrp8, usb cable don't work!
Click to expand...
Click to collapse
If I have access to Twrp8, if you could share your backup with me I would be very grateful! :fingers-crossed:
Aspiranteh said:
If I have access to Twrp8, if you could share your backup with me I would be very grateful! :fingers-crossed:
Click to expand...
Click to collapse
I'm in L21. like I see, your model is L03. If you confirm that it's good I'll try to upload it. If someone can help for what to backup. It's too big (ramdisk, kernel, product, product image, cust, cust image,system, vendor, vendor image, version and version image)
gmbengue said:
I'm in L21. like I see, your model is L03. If you confirm that it's good I'll try to upload it. If someone can help for what to backup. It's too big (ramdisk, kernel, product, product image, cust, cust image,system, vendor, vendor image, version and version image)
Click to expand...
Click to collapse
If you please. If that's what you ask in MediaFire, there are 10 GB free to upload to the cloud. I know your help will help someone else at some point. . Thx.
file name is shell inside the folders find it or edit the .bat file to know where is the shell located
but if this is something new 4u then ask some one with little knowledge of MS DOS commands or shell scripts to edit it for u
Aspiranteh said:
If you please. If that's what you ask in MediaFire, there are 10 GB free to upload to the cloud. I know your help will help someone else at some point. . Thx.
Click to expand...
Click to collapse
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Lords, I have news for you. After many attempts I couldn't fix my "ERROR MODE", so I blocked the Bootloader and went to the shop to make my warranty effective... The technician believed my history that the phone was blocked after an update that appeared to me through OTA and will enforce my warranty because the phone presented "Factory Errors"... XD. Well, that's it, I've got my cell phone working again. Thank you all for your help.
gmbengue said:
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Click to expand...
Click to collapse
Maybe if you upload the backup you can help someone else in the future. Thank you very much for your willingness to help me. :good::fingers-crossed:
Urgent ordi 8.0 failed
gmbengue said:
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Click to expand...
Click to collapse
Bonjour
J'ai exactement le même problème.
Tu pourrais me donné le backup de ton mate 10 ton envie , s'il te plait.
Je serrais usurper heureux si tu pouvais m'aider.
Merci d'avance.
Je m'excuser ne parle pas anglais .
Up
RobotGuerrier said:
Bonjour
J'ai exactement le même problème.
Tu pourrais me donné le backup de ton mate 10 ton envie , s'il te plait.
Je serrais usurper heureux si tu pouvais m'aider.
Merci d'avance.
Je m'excuser ne parle pas anglais .
Click to expand...
Click to collapse
XDA Forum rules
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator.
Flashing Pixel Experience ROM and AOSP Extented returns to fastboot mode, but flashing Lineage os is Working in my poco f1.
Please help
What PE Rom did you flash? Version matters. What vendor-firmware do you have on your fone? Version also matters. What are you using to flash PE? Version matters as well. We'll need the answers to these questions to be able to help you out.
Same problem flashing pixel experience returns to fastboot
Yea same problem with me flashing pixel experience returns to fastboot. I tried the 22/07/2019 and one more older build both after flashing returned to fastboot. Vendor firmware is miui version 10.3.6. I flashed using official twrp version.
PavanGowdaV said:
Yea same problem with me flashing pixel experience returns to fastboot. I tried the 22/07/2019 and one more older build both after flashing returned to fastboot. Vendor firmware is miui version 10.3.6. I flashed using official twrp version.
Click to expand...
Click to collapse
go for Vendor firmware 9.6.27-9
https://mirror.akhilnarang.me/MIUI/beryllium/
and do a CLEAN FLASH
dirty flash on 10.3.6 gives bootloops or fastbtoot bot
Explain the steps
I am on stock ROM now version 10.36 . Can you tell me the complete steps to install pixel experience on my phone.
PavanGowdaV said:
I am on stock ROM now version 10.36 . Can you tell me the complete steps to install pixel experience on my phone.
Click to expand...
Click to collapse
If you are on stock now then you problem should be fixed.
Just unlock bootloader if it's unlocked an flash TWRP and install the desired rom.
The boot-up to fastboot issue happens when the vendor firmware got corrupted somehow and the only solution I found to fix it is flash back to stock and then reflash the custom rom.
PavanGowdaV said:
I am on stock ROM now version 10.36 . Can you tell me the complete steps to install pixel experience on my phone.
Click to expand...
Click to collapse
this is how I flash(ed) my rom(s)
1. in fastboot flash recovery first or
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\<username>\Desk
top\twrp-3.3.1unofficial.img
boot it up using command line in adb
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot C:\Users\<username>\Desk
top\twrp-3.3.1unofficial.img
i use this twrp 3.3.3-1 unofficial, the official one always give me TOUCH screen issues on twrp
https://mega.nz/#F!bdwQVIyK!OWNLH72HNT-ecmC-vAVmPw ( dev by https://t.me/MODsPOCOF1/68 )
from sd/external otg flash...
2.vendor firmware 9.6.27.9 from https://mirror.akhilnarang.me/MIUI/beryllium/ (if you are on miui10.3.6) you must download this version - i used vendor10.3.6 but somehow i noticed battery drainage higher! don't know why! but I tried 3 times on two different roms! vendor image 9.6.27-9 words best
3. custom Rom of your flavor! I ALWAYS use HAVOC! for me Havoc is next to stockrom
4. GAPPS (opengapps.org) (take Micro & disable pixel launcher later if you wana use custom Rom's given launcher
5. opitmus drunk kernel ( I flash this kernel, found it very stable and batter + 4g connectivity effecient) but if you are happy with your custom rom's given kernel! skip this step!
6. flash Magisk19.3,
7. wipe cache / delvik and reboot in to system! , first boot may goto bootloop but eventually you will see WELCOME Prompt!
USEFULL APPS WHICH I ALWAYS CARRY
1. MIGRATE - IF Today you wana move to different rom and don't wana loose/redownload your apps and don't wana loose you settings just make snapshopt (upto 2gb) for next time and flash it in twrp before no6.
https://play.google.com/store/apps/details?id=balti.migrate&hl=en
2. VideoDer (not on playstore) (search on apkmirror) A tool to fetch video from every possible site on web (doesn't work on tiktok)
3. magicbox (similar to netflix)
Does anyone have a guide on how to root a Xiaomi Redmi Note 10? I’m a novice Android user so any help will be appreciated. Thanks
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Slim K said:
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Click to expand...
Click to collapse
Thanks mate. Will wait for the phone to be unlocked then will try these steps.
hello, I followed the whole procedure and the phone only reboots in bootloop or after several reboots it brings me back to Fastboot
Slim K said:
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Click to expand...
Click to collapse
what about vbmeta?
0purple said:
what about vbmeta?
Click to expand...
Click to collapse
I do not understand the question
0purple said:
what about vbmeta?
Click to expand...
Click to collapse
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
titifayls said:
I do not understand the question
Click to expand...
Click to collapse
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Slim K said:
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Click to expand...
Click to collapse
precisely I did not take magisk v22 but v21, moreover I have exactly the same version as the first poster is 12.0.1 RKGEUXM.
To root I took the boot.img from version 12.0.2, was it an error?
I tried to reflash the original boot.img file from v12.0.2 but still in bootloop
I can not find anywhere where to take my original version yet up to date v12.0.1
@titifayls The original poster had version
V12.0.1.0.RKGMIXM (Global) while you claim to have downloaded
V12.0.2.0.RKGEUXM (European) which are not interchangeable. If you want to use either global or eu. Then you would need to flash the full firmware, you can't flash the boot.img from EU to ROM of global. It won't boot.
If you don't really remember which version came with your device, then reply to me again and I can give you further instructions. Tell me which OS are you using to access fastboot and if you want to preserve your data.
Slim K said:
@titifayls The original poster had version
V12.0.1.0.RKGMIXM (Global) while you claim to have downloaded
V12.0.2.0.RKGEUXM (European) which are not interchangeable. If you want to use either global or eu. Then you would need to flash the full firmware, you can't flash the boot.img from EU to ROM of global. It won't boot.
If you don't really remember which version came with your device, then reply to me again and I can give you further instructions. Tell me which OS are you using to access fastboot and if you want to preserve your data.
Click to expand...
Click to collapse
ha , sorry indeed I may have made a mistake, now I don't remember my exact version, it seemed to me that it was EU but in 12.0.1
I use ABD in fastboot and yes I would like to keep all my data that I did not save before wanting to root: /
I bought the phone on aliexpress, I am French, can I look on the box if I have any info on the version?
titifayls said:
ha , sorry indeed I may have made a mistake, now I don't remember my exact version, it seemed to me that it was EU but in 12.0.1
I use ABD in fastboot and yes I would like to keep all my data that I did not save before wanting to root: /
I bought the phone on aliexpress, I am French, can I look on the box if I have any info on the version?
Click to expand...
Click to collapse
I asked if you're using windows or linux to connect to your phone. About losing data, maybe a clean flash could be required, but trying first won't hurt.
Here is how you do it: (you can use the downloaded fastboot firmware, because your device is unlocked, so region differences won't matter that much when flashing full firmware):
Inside that .tgz archive (that you unarchived) you'll find a script called flash_all_except_data_storage.bat for windows or flash_all_except_data_storage.sh for linux. (Do not use the flash_all_lock.bat/.sh script or risk a hard brick, so read carefully this time!!!!)
Connect your device in fastboot mode and open a CMD/Terminal where those scripts and the rest of the firmware files are. Use fastboot devices to make sure device is recognized.
If it is, then type in fastboot followed by dragging and dropping the flash_all_except _data_storage.bat to your CMD/terminal and press Enter. The process should begin automatically. If you get an error, make sure to have typed a space after the fastboot command and before the dropped script.
If it takes a long time during flash of super, don't panic!! Super.img is a very big file
Done!
If it still bootloops after that, then use the flash_all.bat script (will factory reset your phone and delete data)
It doesn't matter, it gives me the list of commands but doesn't launch anything
Wouldn't it be better to put fastboot flash?
don't bother, I'll take miflash, it'll be easier
I delivered an eea_global_images_V12.0.2.0.RKGEUXM rom with miflash by putting flash_all_except_data_storage.
I recovered everything at startup, my applications everything, so I redid the manipulation for the root and now everything works, perfect
thank you
I did the above process successfully.
Also if new update comes out, the process must be done again (not including the unlocking part of course).
The ROMs are posted here
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Slim K said:
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Click to expand...
Click to collapse
so if i use latest magisk v22.1 , do i have to disable something like vbmeta.img or not ? or it is onli Mi Series that need to disable vbmeta.img ?
how to see how many hours left to unlock the phone ? i kinda forgot about it, it is my 1st MIUI device beside Xiaomi Mi A1
pihpih95 said:
so if i use latest magisk v22.1 , do i have to disable something like vbmeta.img or not ? or it is onli Mi Series that need to disable vbmeta.img ?
Click to expand...
Click to collapse
Only MI series need that. You should not have to do that. Also yes, I meant to say that 22.0 stable magisk can make the patched boot.img unbootable. Using the 22.1 canary is the way to go.
pihpih95 said:
how to see how many hours left to unlock the phone ? i kinda forgot about it, it is my 1st MIUI device beside Xiaomi Mi A1
Click to expand...
Click to collapse
You would need to connect your phone in fastboot mode and use MI unlock tool again. It'll tell you how many hours left. Usually, you just need to wait exactly one week or 168 hours.
Slim K said:
Only MI series need that. You should not have to do that. Also yes, I meant to say that 22.0 stable magisk can make the patched boot.img unbootable. Using the 22.1 canary is the way to go.
You would need to connect your phone in fastboot mode and use MI unlock tool again. It'll tell you how many hours left. Usually, you just need to wait exactly one week or 168 hours.
Click to expand...
Click to collapse
about mi unlock tool , what version that show how many hours left ? i use latest version and it show nothing on the tool , if i remember correctly the oldest version show the time remaining to unlock , sorry if i mistaken something here >.<
pihpih95 said:
about mi unlock tool , what version that show how many hours left ? i use latest version and it show nothing on the tool , if i remember correctly the oldest version show the time remaining to unlock , sorry if i mistaken something here >.<
Click to expand...
Click to collapse
I used the latest as well. Most of the time, it errors out and I can't see the time left, but sometimes it works. Don't forget, you're giving them your imei for the freedom of your phone. Those imei's must be stored on Chinese servers and the tool must query those servers to get any info, depending on your country it may not work at all.
My experience with using an older tool has been very bad, the time was extended to 2 weeks instead of one on an another Xiaomi device. Avoid doing that and wait the requested time first.
After following the instruction my phone keeps rebooting.
I tried the flash_all.bat without success. What could I do?
SO finally I successfully rooted with TWRP and root access.thanks to all developers @Eastw1ng @TheMalachite
Following are all download links combined in one post Also there are two threads like unlocking boot loader and twrp but there are some steps are not mentioned which we must need to understand so see the video tutorial at the end of thread.
If you have issues please post comment I will try to solve at my best
NOTE: REMOVE ALL PASSWORD AND PINS ON PHONE BEFORE FLASHING TWRP
All data will be erased so keep backup
Download:
Latest new twrp 3.7 official:
Download twrp-3.7.0_11-0-denniz.img
Download page for twrp-3.7.0_11-0-denniz.img
dl.twrp.me
Vbmeta image:
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Mediatek USB VCom drivers:
MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip
drive.google.com
ADB AND FASTBOOT DRIVERS(WHEN FASTBOOT NOT DETECTING ONLY)
adb - platform tools v30.0.5.zip | by abdyasar for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
magisk v24 zip:
Download Magisk Zip 24.2 Latest Version For Android 2022
Magisk Zip is a flashable file that is used to install Magisk Root on android phones. This Magisk Zip 24.3 latest version can be installed/flashed using
magiskapp.com
magisk 23 apk:
Magisk 23.0 APK Download by topjohnwu - APKMirror
Magisk 23.0 APK Download by topjohnwu - APKMirror Free and safe Android APK downloads
www.apkmirror.com
CMD COMMNADS HIT ENTER:
1)detect adb devices:
adb devices
2)Reboot to bootloader mode:
adb reboot bootloader
3)To detect FASTBOOT devices:
fastboot devices
4)To OEM unlock:
fastboot flashing unlock
5)To flash Vbmeta image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
6) flash twrp image:
fastboot flash recovery recoveryname.img
7)Reboot from FASTBOOT mode to recovery:
fastboot reboot recovery
If you have any issue follow this tutorial correctly
This worked great! Only problem I had was unlocking the bootloader and flashing TWRP without booting up caused the stock recovery to overwrite it again for some reason. After repeating the steps after unlocking it worked. Also, if you have the same problem as me with Magisk being unable to bypass the safety net, try this:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
I wish I found this before I sunk hours into learning what build prop editing is
Kenaestic said:
This worked great! Only problem I had was unlocking the bootloader and flashing TWRP without booting up caused the stock recovery to overwrite it again for some reason. After repeating the steps after unlocking it worked. Also, if you have the same problem as me with Magisk being unable to bypass the safety net, try this:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
I wish I found this before I sunk hours into learning what build prop editing is
Click to expand...
Click to collapse
I already mentioned in the video regarding re-writing of STOCK recovery. For that when we reboot after typing
fastboot reboot recovery
Immediately press volume down+ power button till you saw the recovery name at the bottom om the phone screen and leave the phone it will boots to twrp that's it.
What is vbmeta.ing?
pankspoo said:
I already mentioned in the video regarding re-writing of STOCK recovery. For that when we reboot after typing
fastboot reboot recovery
Immediately press volume down+ power button till you saw the recovery name at the bottom om the phone screen and leave the phone it will boots to twrp that's it.
Click to expand...
Click to collapse
It did boot to TWRP with just the command, though. It just didn't save it for some reason. Still no major problem or anything. Your guide worked in the end and I'm happy ! However I noticed GPS is terrible now for some reason. When I'm on WiFi there's no problems but as soon as I go on mobile data: my weather app can't refresh anymore, Google Maps thinks I'm 50 meters from my actual location and the GPS is always turned 90 degrees away from forward. Is this a common problem?
Kenaestic said:
It did boot to TWRP with just the command, though. It just didn't save it for some reason. Still no major problem or anything. Your guide worked in the end and I'm happy ! However I noticed GPS is terrible now for some reason. When I'm on WiFi there's no problems but as soon as I go on mobile data: my weather app can't refresh anymore, Google Maps thinks I'm 50 meters from my actual location and the GPS is always turned 90 degrees away from forward. Is this a common problem?
Click to expand...
Click to collapse
Root doesn't have to do with these things anymore please check any other app is causing issue
Worked like a charm on a DN2103 OxygenOS v11.3 phone.
Thank you.
@pankspoo how to handle OTA updates? Updater doesn't work anymore with TWRP.
Can I use this titorial for A11?
It
8vasa8 said:
Can I use this titorial for A11?
Click to expand...
Click to collapse
Its the same Process to follow with A11
Cerveza said:
@pankspoo how to handle OTA updates? Updater doesn't work anymore with TWRP.
Click to expand...
Click to collapse
Crested video
Cerveza said:
@pankspoo how to handle OTA updates? Updater doesn't work anymore with TWRP.
Click to expand...
Click to collapse
Creted video in how to section
Ciao, ho effettuato il root del mio telefono con questo metodo (https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/ ) come Non sono riuscito a installare TWRP. Ora mi chiedo se posso fare la procedura installando TWRP e poi procedere all'upgrade alla versione A.11. Perderò i miei dati? Grazie
caccola69 said:
Ciao, ho effettuato il root del mio telefono con questo metodo (https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/ ) come Non sono riuscito a installare TWRP. Ora mi chiedo se posso fare la procedura installando TWRP e poi procedere all'upgrade alla versione A.11. Perderò i miei dati? Grazie
Click to expand...
Click to collapse
OTA Update process for rooted nord 2 : Any incremental Thread update Latest Feb 2022
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone. They can't able to Flash update through stock settings OR via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth. So here...
forum.xda-developers.com
Use this method to. Upgrade you will not loose data if you already unlocked your bootloadee
pankspoo said:
OTA Update process for rooted nord 2 : Any incremental Thread update Latest Feb 2022
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone. They can't able to Flash update through stock settings OR via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth. So here...
forum.xda-developers.com
Use this method to. Upgrade you will not loose data if you already unlocked your bootloadee
Click to expand...
Click to collapse
Thanks for the answer .... as I said I don't have TWRP. When I tried to install it, after restarting the phone, it was no longer accessible. For this I used the other method for root (I didn't understand how to fix TWRP)
What do you advise me to do?
caccola69 said:
Thanks for the answer .... as I said I don't have TWRP. When I tried to install it, after restarting the phone, it was no longer accessible. For this I used the other method for root (I didn't understand how to fix TWRP)
What do you advise me to do?
Click to expand...
Click to collapse
Did you seen the video after flashing twrp using fastboot you need to type
fastboot reboot recovery and hit enter
You will boot in Twrp and its permenant
pankspoo said:
Did you seen the video after flashing twrp using fastboot you need to tyoe
F
fastboot reboot recovery and hit enter
You will boot in. Twrp and its permenant
Click to expand...
Click to collapse
thanks for your patience but I'm afraid to make a mistake
Do I redo the whole procedure described?
CMD COMMNADS HIT ENTER:
1)detect adb devices:
adb devices
2)Reboot to bootloader mode:
adb reboot bootloader
3)To detect FASTBOOT devices:
fastboot devices
4)To OEM unlock:
fastboot flashing unlock
5)To flash Vbmeta image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
6) flash twrp image:
fastboot flash recovery recoveryname.img
7)Reboot from FASTBOOT mode to recovery:
fastboot reboot recovery
caccola69 said:
thanks for your patience but I'm afraid to make a mistake
Do I redo the whole procedure described?
CMD COMMNADS HIT ENTER:
1)detect adb devices:
adb devices
2)Reboot to bootloader mode:
adb reboot bootloader
3)To detect FASTBOOT devices:
fastboot devices
4)To OEM unlock:
fastboot flashing unlock
5)To flash Vbmeta image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
6) flash twrp image:
fastboot flash recovery recoveryname.img
7)Reboot from FASTBOOT mode to recovery:
fastboot reboot recovery
Click to expand...
Click to collapse
Yes correct
pankspoo said:
Yes correct
Click to expand...
Click to collapse
this procedure deleted all my data. I have upgraded the phone to version A.11 and now waiting to figure out how to root
I redid the procedure and in twrp I did a wipe data. I restart twrp and now I see all the memory but I can't copy magisk to the phone and then flash it
Reboot
caccola69 said:
this procedure deleted all my data. I have upgraded the phone to version A.11 and now waiting to figure out how to root
I redid the procedure and in twrp I did a wipe data. I restart twrp and now I see all the memory but I can't copy magisk to the phone and then flash it
Click to expand...
Click to collapse
OEM unlocking always wipes your data no need to mention things again and again.
If you have TWRP first click wipe> format data >yes now reboot back to TWRP again
now click MTP disable and enable it now see if you are able to copy files.
My xiaomi phone is chenese version and the original rom is the official stable version of 12.8. I want to root my phone so I search relative theme on Ada ,as result I have found this thread(https://forum.xda-developers.com/t/rooting-the-mi-11-with-the-latest-xiaomi-eu-rom.4232347/).In this thread everything begin on xiaomi.eu rom,so I install xiaomi.eu rom on this thread .The problem was happened here, when I do as what the thread said download the rom which has matched my phone (I select the stable rom of xiaomi.eu_multi_MI11Lite5G_V12.5.8.0.RKICNXM_v12-11-fastboot.zip) and run the macos_fastboot_first_install_with_data_format.sh file my phone was stuck on fastboot....
phone infomations:
xiaomi 11 lite 5g (renoir)
Click to expand...
Click to collapse
what I have try:
1、boot twrp.img of matched my phone
fastboot boot twrp-3.7.0_11-0-renoir.img
Click to expand...
Click to collapse
but receive the blow error message
downloading 'boot.img'...
OKAY [ 4.397s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.398s
Click to expand...
Click to collapse
2、I search in the google and found this blog which similar with my situation
but still stuck on fastboot......
3、try to flash official rom which matched my phone use miflash tool
but still stuck on fastboot....
I do not know what can I do to take my phone back
Is there has any other methods can make my phone unbrick
Hello, that is an old miui version, i assume you have unlocked bootloader so you may try to install the latest china version wich is 14.0.6.0, you can search it in mifirm.net and try to install it with xiaomi tool v2, and if that does not work, then try again with mi flash.
You can search 'how to unbrick xiaomi with xiaomi tool v2' for more information. Good luck bro
97jota said:
Hello, that is an old miui version, i assume you have unlocked bootloader so you may try to install the latest china version wich is 14.0.6.0, you can search it in mifirm.net and try to install it with xiaomi tool v2, and if that does not work, then try again with mi flash.
You can search 'how to unbrick xiaomi with xiaomi tool v2' for more information. Good luck bro
Click to expand...
Click to collapse
Yes, I have unlocked boot loader.
Thank you for your suggestions ,I will make a try
97jota said:
Hello, that is an old miui version, i assume you have unlocked bootloader so you may try to install the latest china version wich is 14.0.6.0, you can search it in mifirm.net and try to install it with xiaomi tool v2, and if that does not work, then try again with mi flash.
You can search 'how to unbrick xiaomi with xiaomi tool v2' for more information. Good luck bro
Click to expand...
Click to collapse
still stuck on fastboot....
cyberexplorer said:
still stuck on fastboot....
Click to expand...
Click to collapse
flash 12.0.8 stock firmware with fastboot, with clean data,
rayman95 said:
flash 12.0.8 stock firmware with fastboot, with clean data,
Click to expand...
Click to collapse
Thank you for your suggestions which gave me light in dark...
I found here and other relative websites but only found 12.0.8.0 for renoir_eea_global version(eg.renoir_eea_global_images_V12.0.8.0.RKIEUXM_20210419.0000.00_11.0_eea_1e3641e85a.tgz)
But my phone is Chinese version, is that ok?
cyberexplorer said:
Thank you for your suggestions which gave me light in dark...
I found here and other relative websites but only found 12.0.8.0 for renoir_eea_global version(eg.renoir_eea_global_images_V12.0.8.0.RKIEUXM_20210419.0000.00_11.0_eea_1e3641e85a.tgz)
But my phone is Chinese version, is that ok?
Click to expand...
Click to collapse
you should take CHN firmware...or at least global version
rayman95 said:
you should take CHN firmware...or at least global version
Click to expand...
Click to collapse
But I only found 12.0.7 for CN (if you have 12.0.8 for CN please post the link), is ok?
cyberexplorer said:
But I only found 12.0.7 for CN (if you have 12.0.8 for CN please post the link), is ok?
Click to expand...
Click to collapse
normally yes...but take fastboot rom
rayman95 said:
normally yes...but take fastboot rom
Click to expand...
Click to collapse
still stuck on fastboot
cyberexplorer said:
still stuck on fastboot
Click to expand...
Click to collapse
Did you successfully flash - ie, it did not complain about eg Downgrade protection?
Actually, instead of flashing Xiaomi Fastboot ROMs by MiFlash, it is better to un-gzip and un-tar the tgz ROM, and find inside the bat scripts (sh scripts for Linux users)
Choose a script (judge by their names and by inspecting commands) that does not relock BL
Strip some 5-6 lines from the beginning of the script that deal with Downgrade protection (you will easily find it, also, it's usually separated from the rest by an empty line)
Then, run that bat script through Fastboot - this is then the same what MiFlash does (but it takes the original tgz and it uses the Downgrade protection part found in the script)
Btw, you can use this handy app to search through the ROMs:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
---
Btw, once when I had a similar Bootloop (Fastboot mode only) on Lisa (not Renoir) and flashing variozs official Fastboot ROMs did not help, I put my Lisa back to service (8 months ago, since then using it as my daily driver) by successfully flashing Xiaomi.eu Fastboot ROM
zgfg said:
Did you successfully flash - ie, it did not complain about eg Downgrade protection?
Actually, instead of flashing Xiaomi Fastboot ROMs by MiFlash, it is better to un-gzip and un-tar the tgz ROM, and find inside the bat scripts (sh scripts for Linux users)
Choose a script (judge by their names and by inspecting commands) that does not relock BL
Strip some 5-6 lines from the beginning of the script that deal with Downgrade protection (you will easily find it, also, it's usually separated from the rest by an empty line)
Then, run that bat script through Fastboot - this is then the same what MiFlash does (but it takes the original tgz and it uses the Downgrade protection part found in the script)
Btw, you can use this handy app to search through the ROMs:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
---
Btw, once when I had a similar Bootloop (Fastboot mode only) on Lisa (not Renoir) and flashing variozs official Fastboot ROMs did not help, I put my Lisa back to service (8 months ago, since then using it as my daily driver) by successfully flashing Xiaomi.eu Fastboot ROM
Click to expand...
Click to collapse
yeah,i use miflash to flashing rom.and it's successed except the check point error(because not lock)
I open the flash_all.bat with editor only autirollback check but no error
::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
Click to expand...
Click to collapse
I run the flash_all.bat again just now no any error about "downgrade protection",BUT still stuck on fastboot
zgfg said:
I put my Lisa back to service (8 months ago, since then using it as my daily driver) by successfully flashing Xiaomi.eu Fastboot ROM
Click to expand...
Click to collapse
I really not understand how do you flashing xiaomi rom successfully
cyberexplorer said:
I really not understand how do you flashing xiaomi rom successfully
Click to expand...
Click to collapse
It was not the official Xiaomi ROM but let's say debloated Xiaomi.eu ROM (they are based on CN ROMs but made to work internationally)
You can search through the Stable and Weekly ROMs, you can go back from the current A13 to A12 but I'm not sure how was Renoir the Renoir supported
There is always a table in the post #1 which devices we're supported and by what type of ROM (TWRP, Fastboot or hybrid), instructions and links to download
www.xiaomi.eu
zgfg said:
It was not the official Xiaomi ROM but let's say debloated Xiaomi.eu ROM (they are based on CN ROMs but made to work internationally)
You can search through the Stable and Weekly ROMs, you can go back from the current A13 to A12 but I'm not sure how was Renoir the Renoir supported
There is always a table in the post #1 which devices we're supported and by what type of ROM (TWRP, Fastboot or hybrid), instructions and links to download
www.xiaomi.eu
Click to expand...
Click to collapse
oh,i got it. My phone was bricked because of flashing a xiaomi.eu rom which is stable,so only weekly rom maybe worth make a try...
cyberexplorer said:
oh,i got it. My phone was bricked because of flashing a xiaomi.eu rom which is stable,so only weekly rom maybe worth make a try...
Click to expand...
Click to collapse
You should try with a Fastboot type ROM. They usually flash more (deeply) than OTA type Recovery ROMs
zgfg said:
You should try with a Fastboot type ROM. They usually flash more (deeply) than OTA type Recovery ROMs
Click to expand...
Click to collapse
ok, i will make a try
zgfg said:
You should try with a Fastboot type ROM. They usually flash more (deeply) than OTA type Recovery ROMs
Click to expand...
Click to collapse
Unfortunately,still stuck on fastboot
Download rom from https://mifirm.net/model/renoir.ttt#cn
Select China > Fastboot stable.
Extract all content (7zip), again, and again until you see the images folder and the "flash.all.bat" files. Put everything in c:\rom
Download MiFlash20210226, extract also to c:\miflash
Go to fastboot (volume down + power)
Select c:\rom and press Flash.
This WILL work. Good luck.
dwensch said:
Download rom from https://mifirm.net/model/renoir.ttt#cn
Select China > Fastboot stable.
Extract all content (7zip), again, and again until you see the images folder and the "flash.all.bat" files. Put everything in c:\rom
Download MiFlash20210226, extract also to c:\miflash
Go to fastboot (volume down + power)
Select c:\rom and press Flash.
This WILL work. Good luck.
Click to expand...
Click to collapse
I have done this many times, but finally it's still stuck on fastboot