Database Develop

Recovery vs eRecovery

Hi there.
I have been flashing ROMS since ICS (Ice Cream Sandwich) but for the last 18 months I have been a bit disconnected from it.
I am also new to everything Huawei.
I find a lot of times people referring to the eRecovery.
Where does this terminology (eRecovery) differ from the normal recovery, be it stock recovery or TWRP?
Is this eRecovery a Huawei thing or am I missing something?
Thanks in advance.

It is nothing to really worry or even think about. I don't think you can get rid of it or even if you could there is no reason. It's just second recovery which does a different things than the normal stock recovery. I think the eRcovery is needed for the stock update, but normal recovery isn't(not completely sure about this).
It is just good to know that device also has eRecovery, because there are some users who install TWRP and then they boot to eRecovery and then they think the TWRP installation failed.
I don't know is it just huawei thing.
Hope this helps a bit, even though it's a bit messy info.

keikari said:
It is nothing to really worry or even think about. I don't think you can get rid of it or even if you could there is no reason. It's just second recovery which does a different things than the normal stock recovery. I think the eRcovery is needed for the stock update, but normal recovery isn't(not completely sure about this).
It is just good to know that device also has eRecovery, because there are some users who install TWRP and then they boot to eRecovery and the they think the TWRP installation failed.
I don't know is it just huawei thing.
Hope this helps a bit, even though it's a bit messy info.
Click to expand...
Click to collapse
Thanks for the information.
It has definitely given me a much better idea regarding what is eRecovery.
Much appreciated.

it's basically useless on this phone. it will never fetch any package nor restore your device. most people either just keep it and dont bother using it or flash TWRP over it. by having stock recovery as 'recovery' and TWRP as 'recovery2' you can have access to official OTA updates yet still being able to do everything you could do with TWRP

Carkai said:
...by having stock recovery as 'recovery' and TWRP as 'recovery2' you can have access to official OTA updates yet still being able to do everything you could do with TWRP
Click to expand...
Click to collapse
Nice! I am interested in that!
Keeping both recoveries and not loosing OTA sounds good to me.
Have you any idea how to accomplish this please? Any link or for that matter where could I download stock recovery for PRA-LX1?
Thank you!

droidbits said:
Nice! I am interested in that!
Keeping both recoveries and not loosing OTA sounds good to me.
Have you any idea how to accomplish this please? Any link or for that matter where could I download stock recovery for PRA-LX1?
Thank you!
Click to expand...
Click to collapse
flash this as recovery (fastboot flash recovery RECOVERY.img) and this as recovery2 (fastboot flash recovery2 twrp-3.1.1-2-v1-prague.img)

Carkai said:
flash this as recovery (fastboot flash recovery RECOVERY.img) and this as recovery2 (fastboot flash recovery2 twrp-3.1.1-2-v1-prague.img)
Click to expand...
Click to collapse
Thank you!
I was really trying to find the stock recovery for PRA-LX1 from somewhere. Very handy!
Now, having both recoveries flashed, I gather that there will be also the need to unroot when I want to receive OTA or not?

droidbits said:
Thank you!
I was really trying to find the stock recovery for PRA-LX1 from somewhere. Very handy!
Now, having both recoveries flashed, I gather that there will be also the need to unroot when I want to receive OTA or not?
Click to expand...
Click to collapse
nope! you can install OTAs with root and unlocked bootloader (although you have to download and install FULL-OTA packages. basically just clicking three dots when you've received an update and selecting 'download full package' or something like that)

Hello! My Y9 2018 FLA-LX3 uses fastboot flash recovery_ramdisk for TWRP, but it removes stock recovery. Can I flash TWRP to the recovery2/erecovery slot? And if so, what is the command? I have ramdisk, so to flash TWRP I'd use recovery_ramdisk instead of recovery. So, do I use recovery2_ramdisk? Thx!

RustyBl0ck said:
Hello! My Y9 2018 FLA-LX3 uses fastboot flash recovery_ramdisk for TWRP, but it removes stock recovery. Can I flash TWRP to the recovery2/erecovery slot? And if so, what is the command? I have ramdisk, so to flash TWRP I'd use recovery_ramdisk instead of recovery. So, do I use recovery2_ramdisk? Thx!
Click to expand...
Click to collapse
Yes, you can flash TWRP over eRecovery.
Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP:
- Copy TWRP file to the SD card
- Boot in TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- reboot .

-Alf- said:
Yes, you can flash TWRP over eRecovery.
Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP:
- Copy TWRP file to the SD card
- Boot in TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- reboot .
Click to expand...
Click to collapse
Oh thx! But I don't like it bc my goal is to leave stock recovery INTACT. So, I've been also trying to use fastboot to use fastboot boot "TWRP".img That's my goal, even though it hasn't worked. That is my ideal solution. Thx"!

RustyBl0ck said:
Oh thx! But I don't like it bc my goal is to leave stock recovery INTACT. So, I've been also trying to use fastboot to use fastboot boot "TWRP".img That's my goal, even though it hasn't worked. That is my ideal solution. Thx"!
Click to expand...
Click to collapse
And what's stopping you from installing TWRP instead of eRecovery and then installing Recovery back?
No matter what your ideal solution is, this is the only way.

Okay. So, I can an have tried to install TWRP just normally using fastboot flash recovery_ramdisk twrp.img That works, but the issue is that I can't find the stock/original recovery.img to replace it with when I'm finished. I extracted the UPDATE.APP and found a recovery_ramdisk.img. I am kinda scared to try to flash it using the same command for twrp, so I haven-t tried it. Can u pls tell me if I shall do it So in theory, fastboot flash recovery_ramdisk recovery_ramdisk.img

Oh and FYI, that image was extracted from a working UPDATE.app I used for my particular phone and it has always worked, just that it restores EVERYTHING. I just want the recovery back when I finish with TWRP. I-m giving it away and dont want the new owners messing with TWRP, since it can do harm to the phone if misused. Thx!!!

RustyBl0ck said:
. I am kinda scared to try to flash it using the same command for twrp, so I haven-t tried it. Can u pls tell me if I shall do it So in theory, fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Sure, you can flash recovery_ramdisk using command
RustyBl0ck said:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Or, you can flash it in TWRP ("install image" option).

Stuck in Oneplus logo. Can't access recovery. Fastboot working.

Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.

Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.

rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.

Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?

rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can

Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS

rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear

Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here

rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway

Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!

rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..

nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working

Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?

pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer

Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.

przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.

Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.

redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)

How to reset firmware

so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help

Um, i think ur in the wrong category

thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)

Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions

thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .

thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too

Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help

Magisk. How to install on Nuu Tab8?

Hey, new here and not necessarily new to rooting but haven't done so in some years...but...was just wondering if anyone can help me with a problem? Got a cheap Nuu Tab8 tablet yesterday and I'm trying to install it on my device but I'm not able to find the install option when I'm in recovery mode??
I download the manager for magisk, the zip filez I have the twrp app....but I can't figure out what to do?? Can anyone please help?I attached a pic to show my only options when in recovery.
Thanks!

That's the stock Android recovery. If you want to use a custom recovery you'll need to first install TWRP, if it's available for your device. Otherwise you'll need to get the boot image and patch that with the Magisk app before flashing it to your device.
https://topjohnwu.github.io/Magisk/install.html

Didgeridoohan said:
That's the stock Android recovery. If you want to use a custom recovery you'll need to first install TWRP, if it's available for your device. Otherwise you'll need to get the boot image and patch that with the Magisk app before flashing it to your device.
https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
I have the twrp app and it's still not showing up...I'm not sure what to do..?

Not the TWRP app, the TWRP recovery image. For example, on my OnePlus 5T I'd download the image from the TWRP website and then flash with
Code:
fastboot flash recovery twrp.img
It's far from certain that TWRP is available for your device though.

Didgeridoohan said:
Not the TWRP app, the TWRP recovery image. For example, on my OnePlus 5T I'd download the image from the TWRP website and then flash with
Code:
fastboot flash recovery twrp.img
It's far from certain that TWRP is available for your device though.
Click to expand...
Click to collapse
I'm gonna check what I can do and my options here. I haven't rooted for years and I think I used that stupid kingoroot app before so I never got this deep. After I get the file, what would be my next step?

Sounds like you need to read up a bit on the basics... Search the web a bit.
How to use fastboot would be a good start, and also how to get a copy of your boot image if TWRP isn't available for your device.

Question Stuck in fastboot after trying to install PixelExperience :(

Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/rosemary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.

OK nevermind I successfully got the phone booting again with miflash tool by reflashing an official firmware...

Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/t/twrp-on-android-12.4522273/), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Click to expand...
Click to collapse
Hope it helps! ; D

dona3000 said:
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/ros mary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
Click to expand...
Click to collapse
Did u make sure ur on Miui 12.5.16.0.RKLMIXM?

I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s

fol!s said:
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
Click to expand...
Click to collapse
Greetings!
As this phone has an MTK processor, we don't really have a recovery image, it's stored in the boot img I suppose. That link, you can download the official rom to this. DISCLAIMER: There are two types of ROMs listed here, one type is fastboot, that you need now in order to flash it through a computer for example. The another type is the recovery rom, that you can flash from recovery like a magisk package, or anything flashable zip, or with adb sideload.
https://mifirm.net
You should choose global if you are in Europe, but it's suitable for devices in the US or USA probably, ony feature differences are here between an EEA and Global rom.
Also, if you install pixel experience recovery, you can install the firmware by going into recovery, and do it via sideload. Or, you can try flashing the rom with TWRP (tutorial linked below), but then you won't able to install updates automatically.
One question: Did you checked in OEM unlocking in developer options before flashed PE?
Hope it helps!

Yeah, I did checked the oem unlocking. I think the reason why i failed because my bootloader probably updated and I forgot to check. You need bootloader version 12.5.16.0.RKLMIXM to install the pixel experience. Also thank for help

Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/members/gurtnyi.11842195), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Hope it helps! ; D
Click to expand...
Click to collapse
Can I do that on newer firmware or should I roll back to version 12.5.16.0.RKLMIXM? And if I roll back then I need to unlock device again?

I think you can. I've flashed it successfully on the latest version too. Currently I don't use PE but it was good for me.
Well, regarding to the unlock, it's not a big deal, you don't have to wait 168h again, once you've firstly unlocked your device, you can re-unlock it again, and again, no matter how many times, you don't have to wait a lot again.
But depending on how you rollback it,
I mean, with xiaomi flasher (i think that's its name) you can choose between clean all and lock, save userdata, and clean all, but in the first case, it'll lock back the bootloader. With SP flash tool (if you need, I can provide a link for the modified version of it, that doesn't require an auth file, but if fails, you need a python script, I can link that too), as I remember it won't lock back the device, but I'm not a 100% sure
Hope it helps!

Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.

raven17a said:
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
Click to expand...
Click to collapse
Corrected, thank you!

Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.

raven17a said:
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
Click to expand...
Click to collapse
Happy to hear that!
By the way, yes, pe recovery is better for sideloading, or eventually any not stock recovery. Also, if you install PE recovery, you can apply updates automatically, and in the future you won't need to flash it manually.