Recently I got kinda frustrated with MIUI14 and it's limitations, due to the lower RAM capacity of my Redmi. Trying to install CorvusOS, ArrrowOS and PixelExp, i got a warning, stating that my "system"'partition is too small, but cant be resized. So I'm trying to get TWRP to work, so i can try to resize it and if this doesn't work, at least use it in MIUI to install Magisk.
I've followed the steps from this question thread and this thread by skkk for TWRP, and what I've got to the moment is:
1. If i try to boot the TWRP image by using 'fastboot boot twrp.img', it spits out an error saying that it couldn't send the image to the device, because "file too large", which I think is due to the fact that my device is a 4GB RAM model, but even then, the image is about 200MB (which shouldn't be a problem, imo)2. If I try to (don't ask why) to flash the image using 'fastboot flash boot_a', it says that the file is too large for the partition, or something like this, I don't remember.3. Trying to flash the boot image (haven't tried the Rec image, and I don't need to) using 'fastboot flash recovery' spits an error, that the partition doesn't exist. I could try using the 'rescue' partition, but I'm kinda scared to do so.It's a good time to mention, that I've tried booting the partition in both the bootloader, and in FASTBOOTD mode.
Also, if there isn't a way for me to install TWRP in any way on my device, is there a 'fastboot' command to resize my partition, and if not, how do I deal with this problem?
My device: Redmi Note 10 5G, Camellian with 4GB RAM, running MIUI 14.0.1 EU based on A13.
Just found out that the 2nd thread states, that the flash partition is 'recovery_ab', not 'recovery'. Didn't make a difference tho...
mm just get one of the roms here:
[ROM][12][Camellia/Camellian] PixelExperience [AOSP] (Unofficial)
PixelExperience for Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G (camellia/camellian) What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts...
forum.xda-developers.com
[ROM][12.1][UNOFFICIAL][Camellia/Camellian] crDroid v8.14 [14.04.2023]
***Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com
once you flash boot.img (fastboot flash boot boot.img), reboot into recovery and do factory reset / clear data
ThePhoneUser0 said:
mm just get one of the roms here:
[ROM][12][Camellia/Camellian] PixelExperience [AOSP] (Unofficial)
PixelExperience for Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G (camellia/camellian) What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts...
forum.xda-developers.com
[ROM][12.1][UNOFFICIAL][Camellia/Camellian] crDroid v8.14 [14.04.2023]
***Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com
once you flash boot.img (fastboot flash boot boot.img), reboot into recovery and do factory reset / clear data
Click to expand...
Click to collapse
do not do 'fastboot flash boot_a boot.img'. just 'fastboot flash boot boot.img'
Or get MIUI again to fix the things you've done with MiFlash then try installing Pixel Experience or CrDroid
Thanks a lot, but even without testing I'm positive that the problem WILL remain.
From the first pictures u can see that I've made a folder (on my ext HDD, G: ) with all the Android tools, drivers and every firmware for my device. I've tried and I'm not a fan of crDroid, that's why I was trying Corvus and PE. The links u sent me point to the version I already tried. I could download another one, but frankly speaking, I don't want to, if I can just flash TWRP, and install the latest version. And as we speak of TWRP, I tried flash boot, flash boot_a and boot_b. None of them worked. Booting also didn't work. About the MIUI, I've bricked my device about 2-3 months (i don't remember) and used MiFlash to fix it. From them the only other thing I've done, is upgrade to MI14 and root w/ Magisk. So that shouldn't be a problem either, imo.
What I'm gonna try these days is, I think RedWolf or something, an alt for TWRP. They are all based of of TWRP and are for Note 10 or 10 Pro, but I think that they (at least that image for Note 10) should work.
Edit: the Recoveries I'm gonna try are OrangeFox and PitchBlack. I forgot that the RedWolf (if that's the name) is based up to like Mi 6.
OK, I've tried OrangeFox and now every time I try to boot of of it, it says, and I quote: (Status read failed(too many links)). What does that mean? I tried different cable, different port, checked everything, and it still wouldn't boot. Is it just because of the incompatibility of RN10/10 Pro recovery with 10 5G?
bg0169 said:
1. If i try to boot the TWRP image by using 'fastboot boot twrp.img', it spits out an error saying that it couldn't send the image to the device, because "file too large", which I think is due to the fact that my device is a 4GB RAM model, but even then, the image is about 200MB (which shouldn't be a problem, imo)
Click to expand...
Click to collapse
bg0169 said:
2. If I try to (don't ask why) to flash the image using 'fastboot flash boot_a', it says that the file is too large for the partition, or something like this, I don't remember.
Click to expand...
Click to collapse
camellian boot images are 64MB, thats why the 'partition' cant be flashed with an 200MB image
bg0169 said:
3. Trying to flash the boot image (haven't tried the Rec image, and I don't need to) using 'fastboot flash recovery' spits an error, that the partition doesn't exist. I could try using the 'rescue' partition, but I'm kinda scared to do so.
Click to expand...
Click to collapse
bg0169 said:
Just found out that the 2nd thread states, that the flash partition is 'recovery_ab', not 'recovery'. Didn't make a difference tho...
View attachment 5935395
Click to expand...
Click to collapse
since you tried to flash into the “recovery” partition and it wasn’t present, it’s because the camellian is an A/B slot device, which led to its removal and to the implementation of the recovery into the “boot.img” or "boot" partition.
just as ThePhoneUser0 said, use the "boot.img" images referred in those ROMs. *they work perfectly fine and were made for our device.
[ROM] > https://forum.xda-developers.com/f/poco-m3-pro-redmi-note-10-5g.12315/?prefix_id=33
bg0169 said:
Thanks a lot, but even without testing I'm positive that the problem WILL remain.
Click to expand...
Click to collapse
bg0169 said:
OK, I've tried OrangeFox and now every time I try to boot of of it, it says, and I quote: (Status read failed(too many links)). What does that mean? I tried different cable, different port, checked everything, and it still wouldn't boot. Is it just because of the incompatibility of RN10/10 Pro recovery with 10 5G?
Click to expand...
Click to collapse
about TWRP and your doubt that it will remain, TWRP may work and boot on our device, yes, but it is not recommended to use them.* most of them dont work, and the community has probably dropped it, alternatively using the recoveries from AOSP ROMs here that work like a charm. you just use the recovery for that specific ROM every time to avoid any issues
[ROM] > https://forum.xda-developers.com/f/poco-m3-pro-redmi-note-10-5g.12315/?prefix_id=33
bg0169 said:
What I'm gonna try these days is, I think RedWolf or something, an alt for TWRP. They are all based of of TWRP and are for Note 10 or 10 Pro, but I think that they (at least that image for Note 10) should work.
Click to expand...
Click to collapse
if you are telling that youre going to flash stuff from other devices... ffs dont, and never
the Redmi Note 10 is a complete different device with an completely different socket
bg0169 said:
OK, I've tried OrangeFox and now every time I try to boot of of it, it says, and I quote: (Status read failed(too many links)). What does that mean? I tried different cable, different port, checked everything, and it still wouldn't boot. Is it just because of the incompatibility of RN10/10 Pro recovery with 10 5G?
Click to expand...
Click to collapse
please stop trying to install custom recoveries, they wont work.
bg0169 said:
OK, I've tried OrangeFox and now every time I try to boot of of it, it says, and I quote: (Status read failed(too many links)). What does that mean? I tried different cable, different port, checked everything, and it still wouldn't boot. Is it just because of the incompatibility of RN10/10 Pro recovery with 10 5G?
Click to expand...
Click to collapse
at this point, flash MIUI back with miflash and redo the process, although dont flash random recoveries that you just find on other devices because it wont work.
Thanks, again, @1lopes, you've saved my butt from a lot of problems so far... .
1lopes said:
camellian boot images are 64MB, thats why the 'partition' cant be flashed with an 200MB image
Click to expand...
Click to collapse
Yea, I found out after flashing the twrp.img it said that the partition is some 100-200k bytes or so and when i converted, was about 65MB in total. Hella lot smaller than the image.
1lopes said:
just [email protected] ThePhoneUser0 said, use the "boot.img" images referred in those ROMs. *they work perfectly fine and were made for our device.
[ROM] > https://forum.xda-developers.com/f/poco-m3-pro-redmi-note-10-5g.12315/?prefix_id=33
Click to expand...
Click to collapse
I'm gonna try those later, but does these recovery images have those TWRP-like features, or are they like the MIUI Recovery - just Restart, Halt, Bootloader? I'm also curious, cuz the image i tried for PE was unofficial camellia/camellian for A13 from 18th Feb 2022 and it refused to install, die to the "small system partition size". I'ma try those, you've pointed to, but I'm still skeptical some of them might not work, because of this problem.
1lopes said:
about TWRP and your doubt that it will remain, TWRP may work and boot on our device, yes, but it is not recommended to use them.* most of them dont work, and the community has probably dropped it, alternatively using the recoveries from AOSP ROMs here that work like a charm. you just use the recovery for that specific ROM every time to avoid any issues
Click to expand...
Click to collapse
1lopes said:
if you are telling that youre going to flash stuff from other devices... ffs dont, and never
the Redmi Note 10 is a complete different device with an completely different socket
Click to expand...
Click to collapse
Why is using TWRP so scary? Why isn't it recommended? Also about the RN10, yea, after you said it, I searched on gsmarena.com and found that both devices were using a SD chipset, not a MediaTek. Didn't think of that...
ThePhoneUser0 said:
please stop trying to install custom recoveries, they wont work.
Click to expand...
Click to collapse
ThePhoneUser0 said:
at this point, flash MIUI back with miflash and redo the process, although dont flash random recoveries that you just find on other devices because it wont work.
Click to expand...
Click to collapse
OK, OK, I wont, don't worry. Also I've reinstalled MIUI from fastboot flash commands, w/o MiFlash, cuz it was easier. I'm gonna try those recoveries from the ROMs for camellian.
Quick update: just installed PE for camellian on my phone. Gonna see everything works and send some screenshots when i log on it!
Also to mention to anybody trying this: REMEMBER TO FACTORY RESET! I forgor and had to force restart and go to recovery again... Tho when I first booted up w/o reset, it showed my old wallpaper. I think becausethe recovery updatekeeps the user data untouched.
bg0169 said:
does these recovery images have those TWRP-like features
Click to expand...
Click to collapse
they have useful functions, similiar to MIUI's recovery, those being that you only need. they work like TWRP, but TWRP is more advanced with more functions and options available to the user.
i suppose that you have seen those after flashing PE on your device, those important being ADB sideload, update from SD card, some partitions to wipe and factory reset, probably more that I dont remember
bg0169 said:
Why is using TWRP so scary? Why isn't it recommended? Also about the RN10, yea, after you said it, I searched on gsmarena.com and found that both devices were using a SD chipset, not a MediaTek. Didn't think of that...
Click to expand...
Click to collapse
scary for possibly hard bricking your device. since the recovery image is now implemented into the boot partition, a bad boot image will make your device unbootable.
not recommended due to it having almost no functionality, touch screen not working in every build that has been tried here, and other issues, like limitations/errors to flashing, backups, etc.
bg0169 said:
die to the "small system partition size".
Click to expand...
Click to collapse
for some reason, i also have the same issue from nowhere too after I was trying to flash a GSI last week. this could be with an update Xiaomi did to their firmware, but im completely clueless.
anyways, after you reflashed the firmware, has it been solved? (due to you mentioning that you successfully flashed PE)
Sorry for the late reply. I had some things going on.
Yea, the recovery had features, like reboot to bootloader, apply update, enable adb, and stuff. A bit richer than the MIUI stock one, but still not as advanced.
I'm not sure, if you're asking about the flashing GSI problem, but PE worked absolutely fine, and I haven't tried reflashing something else over.
I won't be trying that very soon, because I wanna keep it as is for some time and see if PE satisfies my needs of service.
all twrp builds for camellia cause a camellian hard brick. even without permanent flash. so it's very important for all users that ure curious to test: DONT DO THIS!!!
Related
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
Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks
Did you flash anything?
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.
VD171 said:
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.
Click to expand...
Click to collapse
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?
jeromeof said:
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?
Click to expand...
Click to collapse
You need to flash the stock MIUI rom again using SPFLASHTOOL.
[GUIDE] How to properly solve the errors of the SP FLASH TOOL for MERLIN ? (Redmi Note 9 / Redmi 10X 4G)
WARNINGS: Keep your backup files safe and secure ! If you can, encrypt them. If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again ! Never try to flash in "format all" mode ! Otherwise, you will LOSE all secure and...
forum.xda-developers.com
jeromeof said:
Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks
Click to expand...
Click to collapse
If you have have adb drivers installed in your pc, try connecting your phone and open power shell. Then try this command.
Code:
adb devices
If it shows the device, then simply command
Code:
adb reboot fastboot
and flash the fastboot rom.
If not works, then follow VD171.
Also you should read threads carefully before flashing anything. Like there a tread about pixelplus UI. And they recommend to force reboot when you see the boot logo. To avoid boot loop.
Good luck
jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Don't flash pixel experience. It's unofficial and it's and old version. I recommend you to flash pixel extended after solving and flashing latest fastboot rom. It's official and provide update every month. This rom is also a pure aosp based Stock rom.
Always read new treads before deciding
Redmi Note 9 ROMs, Kernels, Recoveries, & Other De
Improve your Redmi Note 9's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.
Mobarok_ said:
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.
Click to expand...
Click to collapse
Indonesia V12.0.1.0 precisely (V12.0.1.0.QJOIDXM).
Here, you can find and download the rom: https://xiaomifirmwareupdater.com/miui/merlin/stable/V12.0.1.0.QJOIDXM/
Got the bootloader unlocked..should've read more & implemented over a proper guide.
long story short:
stared with magisk apk..when phone was fine.. then got into bootloop;
quickly downloaded & flashed the global (lime) MIUI V12.0.5.0.QJQMIXM;
installed twrp; should've done this before.
wasn't able to copy anything into internal storage.
Used Twrp to wipe phone.. & flashed the stock_global_miui_(lime)12.0.5 boot.img in fastboot
because twrp was saying "unable to decrypt fbe device" on internal storage
formatted using twrp.
booted properly but setup says device is locked because associated with existing mi account can't open wifi but was able to activate device upon entering password on mobile data setup completes but device restarts frequently & still unable to access wifi
I think it has something to do with "unable to decrypt fbe device"..
should I try flashing custom rom boot img?
please don't ban me..tell if I did something wrong, I'll correct that..
..
Edit:
MiFlash-tool Worked
Flashing other compaitable custom Rom also worked
..
Had twrp wipe the whole phone and the format the partions
& then flashed in fastboot & everything was normal.
..
FBE device encryption is basically storage encryption that prevents dirty flashing miui rom via fastboot.
this can be avoided by implementing proper procedure of magisk & use of lazypatcher.
Thank you so much.. @Cursader & @zoel.fahmi for pointing me in the right direction.. godbless
[solved]
Currently I'm running Miui just like a new device.
I will make another guide thread on rooting systemlessly & flashing other custom rooms... if I succeed I will link it here..
Try to reboot bootloader
then flash twrp
wipe everything and format the data partition
reboot to twrp again
then flash custom rom
If you're flashing miui again, your phone bootloader will be lock again and you need something like lazy2flasher if you wanna keep miui with twrp and magisk etc.
zoel.fahmi said:
Try to reboot bootloader
then flash twrp
wipe everything and format the data partition
reboot to twrp again
then flash custom rom
If you're flashing miui again, your phone bootloader will be lock again and you need something like lazy2flasher if you wanna keep miui with twrp and magisk etc.
Click to expand...
Click to collapse
first of all thank you for taking out the time to read & respond..
I found an article with lazy 2 flasher earlier, I'll look into it..
is there any where I should look to find a suited custom rom for my phone..
xhykari said:
first of all thank you for taking out the time to read & respond..
I found an article with lazy 2 flasher earlier, I'll look into it..
is there any where I should look to find a suited custom rom for my phone..
Click to expand...
Click to collapse
you can use custom rom from Poco M3 since it's used the same SoC (662)
here : https://forum.xda-developers.com/f/poco-m3-roms-kernels-recoveries-other-develop.11969/
check the thread name Poco M3 / Redmi 9T or unified or codename like citrus and lime
whats the difference between Lime, Citrus, & Juice..
Mine is Lime
Juice is Lime & Citrus I think..
So will Juice work on a device which previously ran Lime?
..
basically can I install PixelPlusUi_Juice
or should I first try the lazy2flasher.. & @zoel.fahmi
where do I get lazy2flasher
If anything goes for me (RedmiNote9Pro) i just use miflash to flash original miui and start all over from there, might not be the quickest method but is easy and reliable
Cursader said:
If anything goes for me (RedmiNote9Pro) i just use miflash to flash original miui and start all over from there, might not be the quickest method but is easy and reliable
Click to expand...
Click to collapse
THERE IS AN MI FLASH TOOL too.. :O
whydoinotknowofthis.. What the heck..
can it bypass dm verity as well? like does it apply flash without lazypatcher?
do we need to provide it rom or can it fetch itself?
would you be please share some links for me?
..
xhykari said:
THERE IS AN MI FLASH TOOL too.. :O
whydoinotknowofthis.. What the heck..
can it bypass dm verity as well? like does it apply flash without lazypatcher?
do we need to provide it rom or can it fetch itself?
would you be please share some links for me?
Click to expand...
Click to collapse
If the bootloader unlocked and you can go into fastboot you can flash stock rom and It's just like it came from the store! Here you have link for your convinience: https://c.mi.com/oc/miuidownload/detail?guide=2
MiFlash-tool Worked..
(its the best tool for bringing mi devices from rom mess back to scratch new)
Flashing other Rom also worked..(pixelui)
juice = lime + citrus (works for both)
Thank you so much.. @Cursader & @zoel.fahmi for pointing me in the right direction..
Long story short: I tried to install a GSI so I installed TWRP and flashed some necessary zips (vbmeta, mutidisabler, ...) from different sources and the GSI, but maybe it was a bad idea to follow multiple sources, because the phone was bootlooping when I tried to reboot into system. I then wiped everything and reflashed everything but that didn't fix it. After meddlilng around for a while, I was able to get into the download mode, so I thought of flashing the factory firmware with Heimdall. I used samloader and downloaded the supposedlly correct firmware (M215FXXU2BUH6/M215FODM2BUI1/M215FDDU2BUH1/M215FXXU2BUH6, region is BKD). When I was adding the files, I found out that I was missing the following files:
md5.img (MD5HDR)
efs.img (EFS)
sec_efs.img (SEC_EFS)
nad_fw.bin (NAD_FW)
param.bin (PARAM)
steady.bin (STEADY)
uhuh.bin (UHCFG)
blcmd.bin (BLCMD)
spu.img (SPU)
ul_key.bin (UL_KEYS)
nad_refer.bin (NAD_REFER)
dqmdbg.img (DQMDBG)
There were other partitions, but no files were listed for them, so I think they are not supposed to be flashed. There were also two different "fota.zip" files, but I didn't know what to do with them. Anyway, I flashed the other files, but the phone started bootlooping with the bootloader unlocked warning screen. I locked the bootloader from the download mode and tried again but no luck. I tried reflashing everything again, but the flashing stopped halfway with the message "super.img blocked by OEM" or something like that. I performed a force reboot with volume down + power and it rebooted into the "Emergency Recovery Function" screen. I reflashed everything again, but this time, without super.img, and it flashed fine, but the same bootloop problem remained. Looking up on the internet, it seems that efs.img has something to do with the IMEIs. I don't have any backup of it. I also don't know how to get the rest of the files (if all of them are even necessary), or what they even do/mean.
Basically, I'm trying to get it back to the factory software, or salvage it in any other way. Does somebody have any idea how to fix it?
Naah... Stuff like this happens to me all the time.
Download this ODIN first: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Then download this firmware: https://samfw.com/firmware/SM-M215F/BKD/M215FXXU2BUG2
Now first a few things:
1. You probably downloaded a engineer firmware that isnt allowed as of now.
2. Heimdall is mostly dead, last I checked. It isnt very wise to use it.
3. LOCKING THE BOOTLOADER IN A UNSTABLE STATE IS FOOLISHNESS. I do not mean to offend anyone, but pls dont do this.
4. I think you are using ErfanGSI/ some other port. These will NOT work. Only phhusson's GSI's have worked for me so far.
So coming back to the topic, Just open up the ODIN and connect up your phone. It will get recognized. If it is not in emergency/ download modes, just hold vol down + power, then press both vol buttons and connect to pc immediately - it will boot into dl mode.
Select the BL, AP, CP and HOME_CSC. Flash these.
It should reboot right back up into stock.
Also, are you using my vbmeta zip from ItsMeKande's thread?
Chill
GuruPrasadAH
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
GuruPrasadAH said:
Also, are you using my vbmeta zip from ItsMeKande's thread?
Click to expand...
Click to collapse
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
newt23 said:
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
Click to expand...
Click to collapse
My to-go answer is always crdroid. Its lightweight, customizable, and comes in variants with gapps, foss and vanilla. The one you're looking for is vanilla. Here's the post where u can find the link
Any official or unofficial lineage OS for Samsung galaxy M21
Hello everyone so I have a Samsung galaxy M21 with One UI 3.1 core. Are there any lineage OS official or unofficial builds for Android 11? If you know please reply to this, thank you in advance!!! 🙏🏾🙏🏾🙏🏾
forum.xda-developers.com
Hmm, it didn't work. I get bootloops...
Did you follow all the instructions given in that thread?
Only if you flash vbmeta, Multidisabler it will boot.
Then too magisk is recommended. The zips are in that thread.
Follow the instructions and let me know. On guy OldNoobOne also successfully flashed and booted a gsi
Let me know if it works
Chill
GuruPrasadAH
For Multidisabler just do a google search one for samsung devices will appear
Here's what I did (stock firmware, unlocked bootloader):
1. Boot into dl mode
2. Flash TWRP and boot into it
3. Wipe > Format data > "yes"
4. Reboot > Recovery
5. Advanced > Terminal
6. "cd external_sd/flash"
7. "super mount system"
8. "super flash system crdrom-v313-210921-arm64-bvZ-lite.img"
9. Install > vbmeta.zip, multidisabler-samsung-3.1.zip"
10. Reboot into system
And I get bootloops. Multidisabler detects Android 10, doesn't find the stock recovery and fails to mount /system. Maybe that's the problem? I'm using this one.
Also try flashing magisk... I dont really understand what is happening to you.
Maybe you set the system as read only? Really not sure.
Also, a ROM might be coming soon
Chill
GuruPrasadAH
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
newt23 said:
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
Click to expand...
Click to collapse
Use Overlay-Fix by dev Yillie. It had worked for me on crd too. You will find Yillie on telegram 'Galaxy M21 Updates' group, download from there.
After the Jan update to crdroid 9 I have been completely unable to load twrp back onto my phone. I have never had any problems with this before, but now after trying for the third time I am stuck in my third bootloop. I have tried 'install current twrp' 'install to ramdisk' and used two different versions of twrp the result is always the same, stuck in fastboot. So first question - is there a way to get out of the bootloop without having to do a third factory reset because they are doing my head in? Second question - is there a way to get twrp installed any more on this rom? I tried changing slots but it makes no difference. Because it is stuck in fastboot I can 'fastboot boot twrp' to do any flashing/wiping that may be necessary, but so far I have only been able to get the phone back with a factory reset. Any help appreciated.
viking777 said:
After the Jan update to crdroid 9 I have been completely unable to load twrp back onto my phone. I have never had any problems with this before, but now after trying for the third time I am stuck in my third bootloop. I have tried 'install current twrp' 'install to ramdisk' and used two different versions of twrp the result is always the same, stuck in fastboot. So first question - is there a way to get out of the bootloop without having to do a third factory reset because they are doing my head in? Second question - is there a way to get twrp installed any more on this rom? I tried changing slots but it makes no difference. Because it is stuck in fastboot I can 'fastboot boot twrp' to do any flashing/wiping that may be necessary, but so far I have only been able to get the phone back with a factory reset. Any help appreciated.
Click to expand...
Click to collapse
I should first try to reflash the firmware for your device. That's something to try first.
Just flash other ROM and wipe data. If doesn't help, flash firmware for your device like @minionguy said.
Update - I got back to a working system without a factory reset by fastbooting twrp going to restore and restoring the boot partition only from my latest twrp backup, so that answers Q1. As for Q2 (how to get twrp installed I still don't know how to do that).
Thanks for the replies btw. I think if that is the only way to install twrp I will have to live without it for now. I know I am not the only one with this problem there have been other reports elsewhere. Somebody suggested sideloading, but I can't find a zip file for the twrp version I am using ( twrp-3.7.0_12-0-spes-A12-dblenk9) and this is the only version I have found that works properly since it successfully decrypts data whereas the other versions I have used don't even bother to try, making them useless.
viking777 said:
Update - I got back to a working system without a factory reset by fastbooting twrp going to restore and restoring the boot partition only from my latest twrp backup, so that answers Q1. As for Q2 (how to get twrp installed I still don't know how to do that).
Thanks for the replies btw. I think if that is the only way to install twrp I will have to live without it for now. I know I am not the only one with this problem there have been other reports elsewhere. Somebody suggested sideloading, but I can't find a zip file for the twrp version I am using ( twrp-3.7.0_12-0-spes-A12-dblenk9) and this is the only version I have found that works properly since it successfully decrypts data whereas the other versions I have used don't even bother to try, making them useless.
Click to expand...
Click to collapse
This is where I borked it myself, and with sideloading. Apparently, the semi-permanent instructions for TWRP on spes should work using twrp-3.7.0.img (96mb) and NOT twrp-3.7.0-12.1-06.11.22.img (128mb), as the latter is the JabiYeff version and is "unable to flash MIUI ROMs due to dynamic partitioning error" as of November 2022. I assume your dblenk9 version is 128mb? You have a link for it? Googling gives only this thread and a couple of Russian sites 4pda.to. I just stayed on the stock crDroid recovery; did the same on my RN10P after this same ROM.
Flash crd9.1 on spes using instructions by LolFlasherNoob with the full MIUI ROM flashed first.
Sheist! said:
This is where I borked it myself, and with sideloading. Apparently, the semi-permanent instructions for TWRP on spes should work using twrp-3.7.0.img (96mb) and NOT twrp-3.7.0-12.1-06.11.22.img (128mb), as the latter is the JabiYeff version and is "unable to flash MIUI ROMs due to dynamic partitioning error" as of November 2022. I assume your dblenk9 version is 128mb? You have a link for it? Googling gives only this thread and a couple of Russian sites 4pda.to. I just stayed on the stock crDroid recovery; did the same on my RN10P after this same ROM.
Flash crd9.1 on spes using instructions by LolFlasherNoob with the full MIUI ROM flashed first.
Click to expand...
Click to collapse
@Sheist!
Thanks for the reply.
Re the dblenk9 twrp, it definitely came from this site somewhere but I can't find the link any more either, nor on the wider internet. The version I use is 96mb and it has worked very well up until the Jan update. Like yourself, I will stay on crdroid recovery for now, but I will attach the dblenk9 twrp version to this post in case you or anyone else is interested. You can still use it for 'fastboot boot twrp' and it does decrypt data so you are not left with 0mb on internal storage like the others I have tried.
NB To anyone who happens across this post whilst looking for twrp versions, If you are on the Jan ota do not try to install this, only fastboot it - unless you enjoy bootloops!
It probably doesn't matter much now, but I managed to find the original post that linked to the dblenk9 twrp this is it:
Any one have OrangeFox Recovery for Redmi Note 11 (spes)?
I am looking for OrangeFox Recovery for RN 11 (spes). Couldn't find anywhere. Anybody build it?
forum.xda-developers.com
It shows how good the search is on this forum because I wasn't even looking for it!