Related
Hey All, kind of a weird situation here.
My Mi 8 (Chinese Ver. 64GB, 6GB Ram) after updating to 9.9.3 and playing around with Pixel Experience 10, now has constant problems/hitches/crashes connecting to Wifi and Data or getting service overall. This happens with Sim in or out of Phone.
I have tried clean flashing both 9.9.3 and latest global using the fastboot method, clean flashing Xiaomi.eu using TWRP, formatting Data, Deleting Data,System,Cache, Boot partitions and Reflashing stock, as well as flashing just the Vendor from 9.9.3 after clean flashing Xiaomi.eu 9.9.3.
I have attached some screenshots (look at status bar) and some logcats of the Searches Modem and Sim
Help?
Try to flash persist.img in twrp (wzsx150 ex). Take that image from a stable or a dev China rom.tgz
...
mar.ur said:
Try to flash persist.img in twrp (wzsx150 ex). Take that image from a stable or a dev China rom.tgz
Click to expand...
Click to collapse
Just tried flashing the persist image from 9.9.3 and problem still exists. I also tried the one from the latest Stable 10.3.6 and it completely stopped working instead of intermittently even after clean installing 10.3.6 rom. maybe older version?
JvaOneShotzXprX said:
Just tried flashing the persist image from 9.9.3 and problem still exists. I also tried the one from the latest Stable 10.3.6 and it completely stopped working instead of intermittently even after clean installing 10.3.6 rom. maybe older version?
Click to expand...
Click to collapse
It should be ok after flashing with Miflash. You can try flash fastboot ROM with Miflash ones again or flash firmware ( it includes modem ) in twrp.
mar.ur said:
It should be ok after flashing with Miflash. You can try flash fastboot ROM with Miflash ones again or flash firmware ( it includes modem ) in twrp.
Click to expand...
Click to collapse
Can you link me to that? The Mi Flash tool i'm using causes my pc an error?
JvaOneShotzXprX said:
Can you link me to that? The Mi Flash tool i'm using causes my pc an error?
Click to expand...
Click to collapse
https://www.xiaomiflash.com/download/
Flash last China Dev or stable ROM and uncheck clean all and lock. Use clean all only
mar.ur said:
https://www.xiaomiflash.com/download/
Flash last China Dev or stable ROM and uncheck clean all and lock. Use clean all only
Click to expand...
Click to collapse
Issue still there, I don't know what to do any more.
JvaOneShotzXprX said:
Issue still there, I don't know what to do any more.
Click to expand...
Click to collapse
Do you have IMEI? Ehat about wi-fi and Bluetooth? Did you try another sim card?
mar.ur said:
Do you have IMEI? Ehat about wi-fi and Bluetooth? Did you try another sim card?
Click to expand...
Click to collapse
It happens with or without Sim card. Any Sim I insert does the same. And yes, both Sim slots have an IMEI.
I just tried flashing 9.8.15 persist.img and then flashing 9.8.15 with Xiaomi Flash and it seems to be working so far (no hangups for the last 30 mins) but we'll see if the problem comes back because it all seems fine until a couple of hours later.
mar.ur said:
Do you have IMEI? Ehat about wi-fi and Bluetooth? Did you try another sim card?
Click to expand...
Click to collapse
(( It keeps happening! I'm convinced my phone went bad and I want to die. I'm broke so I can't afford to replace my phone .
Here's a video if that helps :'(
https://drive.google.com/file/d/1-BGRyaZAxmN1laRyrCBHucf6DqWmBNV-/view?usp=drivesdk
Help?
I'll gladly donate to whomever can fix this for me
You have missed out some info for me to help.
1. On twrp ? Version ?
2. Have you tried wipe / format data in twrp ?
3. Try to install a stable version of global rom
4. After done all the above and still the same issue then enter engineering mode and look at the network settings there and report here.
JvaOneShotzXprX said:
I'll gladly donate to whomever can fix this for me
Click to expand...
Click to collapse
This is strictly a software issue, you have encrypted, deleted or corrupted the images in your persist partition.
Flashing a rom will do absolutely nothing to fix this issue.
This issue is resolved 3 different ways, i have several posts on this. The absolute best/fastest method is to restore persist images from a TWRP recovery backup.
You need to use one of these versions of TWRP : https://forum.xda-developers.com/showpost.php?p=79908339&postcount=116
method 1
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Note use an older fastboot version of Global stable if you own a Global device. if you own a Chinese device, use the chinese fastboot rom...Not recovery rom it has to be a fastboot rom and the older versions have the persist images separated,
Global Rom with persist images : https://xiaomifirmware.com/download/11879/
China Rom with persist images : https://xiaomifirmware.com/download/12207/
Method 2 : Restore persist images from a TWRP backup, do you have one?
Method 3 : Use the flashbat method of restoring your phone, the phone must be linked to your Miui account.
Let me know if any of these steps helped. Relax, this will definitely be resolved.
tsongming said:
This is strictly a software issue, you have encrypted, deleted or corrupted the images in your persist partition.
Flashing a rom will do absolutely nothing to fix this issue.
This issue is resolved 3 different ways, i have several posts on this. The absolute best/fastest method is to restore persist images from a TWRP recovery backup.
You need to use one of these versions of TWRP : https://forum.xda-developers.com/showpost.php?p=79908339&postcount=116
method 1
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Note use an older fastboot version of Global stable if you own a Global device. if you own a Chinese device, use the chinese fastboot rom...Not recovery rom it has to be a fastboot rom and the older versions have the persist images separated,
Global Rom with persist images : https://xiaomifirmware.com/download/11879/
China Rom with persist images : https://xiaomifirmware.com/download/12207/
Method 2 : Restore persist images from a TWRP backup, do you have one?
Method 3 : Use the flashbat method of restoring your phone, the phone must be linked to your Miui account.
Let me know if any of these steps helped. Relax, this will definitely be resolved.
Click to expand...
Click to collapse
Tried all methods above except restoring a backup as I didn’t have one. No dice.
dvdfreak said:
You have missed out some info for me to help.
1. On twrp ? Version ?
2. Have you tried wipe / format data in twrp ?
3. Try to install a stable version of global rom
4. After done all the above and still the same issue then enter engineering mode and look at the network settings there and report here.
Click to expand...
Click to collapse
1. Twrp 3.3.1-0607 and also tried 3.2.4 and Orange fox on 3.3.0
2.Yes, many many times. I have to format data (typing in yes) everytime I switched from Chinese dev to Xiaomi.eu when I flashed via the Xiaomi flash tool. (Bat flash method)
3. Have tried installing every Dev, China Stable, Global Dev (old ofc), and Global Stable along with all of their respective persist partitions. Even tried flashing persist+ROM in EDL.
4. Pics below. All pics below are with the SIM card removed. It has been for a week without SIM card.
I'm pretty sure I'm screwed. Random reboots as well.
JvaOneShotzXprX said:
Tried all methods above except restoring a backup as I didn’t have one. No dice.
Click to expand...
Click to collapse
Sorry to hear that you are having difficulty.
Unfortunately backup persist images are unique to your device., and need to match up exactly with the device hardware. So do not attempt to restore someone else's TWRP persist backup it absolutely will NOT resolve your issue.
Try this method , it should finally resolve your issue, if it fails try it again and if if it fails. Start over , reread and try again.
Note Use Google Translate: http://4pda.ru/forum/index.php?showtopic=906971&view=findpost&p=77405784
Hi,
I have the same problem. Did you find any solution?
Thanks in advance.
tsongming said:
This is strictly a software issue, you have encrypted, deleted or corrupted the images in your persist partition.
Flashing a rom will do absolutely nothing to fix this issue.
This issue is resolved 3 different ways, i have several posts on this. The absolute best/fastest method is to restore persist images from a TWRP recovery backup.
You need to use one of these versions of TWRP : https://forum.xda-developers.com/showpost.php?p=79908339&postcount=116
method 1
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Note use an older fastboot version of Global stable if you own a Global device. if you own a Chinese device, use the chinese fastboot rom...Not recovery rom it has to be a fastboot rom and the older versions have the persist images separated,
Global Rom with persist images : https://xiaomifirmware.com/download/11879/
China Rom with persist images : https://xiaomifirmware.com/download/12207/
Method 2 : Restore persist images from a TWRP backup, do you have one?
Method 3 : Use the flashbat method of restoring your phone, the phone must be linked to your Miui account.
Let me know if any of these steps helped. Relax, this will definitely be resolved.
Click to expand...
Click to collapse
hello
how can i apply the third method ( Use the flashbat method of restoring your phone, the phone must be linked to your Miui account. )?
and if my brother has the same phone ( mi 8) can i use his pack up?
Hi everyone, I really need some help. Took my phone to I.T shop to have it unlocked and EU rom stable put on. I got my phone back with TWRP on it saying no rom. I know nothing about this kind of thing and now I am stuck. Is there someone who can fix this remotely for me?? Thanks in advance
In twrp Click install and Check in the download folder in case it's not in the root folder, if there is no ROM there you could fix it yourself by flashing the last fastboot ROM from a bat file or cmd line
i think it was 12.5.5 or something like that and then you can update to EU 12.5.12 stable via twrp
AND NEVER USE THAT SHOP AGAIN LOL
speedtripler said:
In twrp Click install and Check in the download folder in case it's not in the root folder, if there is no ROM there you could fix it yourself by flashing the last fastboot ROM from a bat file or cmd line
i think it was 12.5.5 or something like that and then you can update to EU 12.5.12 stable via twrp
AND NEVER USE THAT SHOP AGAIN LOL
Click to expand...
Click to collapse
Thanks for your reply. Could this be done remotely. I really have no idea how to do any of this stuff which is why i first went to a shop. Im happy to pay for a good outcome
Anyone who flashes ROMs could do it in a few minutes via team viewer or something.... But it maybe beneficial to learn for yourself
It's really simple, you've already done the hardest part if you've unlocked the bootloader and installed twrp
Just put the phone in fastboot mode and then plug into PC and click on the bat file
Download: MIUI 12 stable update rolling out to several Xiaomi, Redmi and POCO devices
MIUI 12 stable builds have begun rolling out to several Xiaomi, Redmi, and POCO devices. Head on over for Recovery ROM and Fastboot ROM download links!
www.xda-developers.com
Select your phone and download the MIUI stock ROM. (Do NOT extract it.)
Boot into Twrp and wipe and factory reset.
Move the miui stock rom to the phone.
Select flash and select the zip file.
Swipe to flash
Then download and flash(move to phone, flash) the 'ARM64 Android 11' Gapps(Google apps) https://opengapps.org/
Then reboot.
All data will be lost. If you want to keep your photos and videos, before doing everything, go to twrp , connect the phone to a pc, and move the 'Dcim' folder to the computer side.
If you have a working TWRP, just use it to flash latest EU version, format data, reboot system. Done.
Then if you want to go back to a stock ROM, flash it via fastboot or twrp depending on the ROM format you download.
Sathelp said:
If you have a working TWRP, just use it to flash latest EU version, format data, reboot system. Done.
Then if you want to go back to a stock ROM, flash it via fastboot or twrp depending on the ROM format you download.
Click to expand...
Click to collapse
If he's stuck in twrp how can he download a ROM to flash? I don't think you can transfer files to a phone that doesn't have a ROM to flash via twrp
Fastboot first from a PC cmd maybe the only way to get started
He is asking someone else to do the process he doesn't know anything about these things (and I don't understand why buying a phone to make things like this if not capable). Anyway go on YouTube and check people doing the process, I don't think is difficult watching a guy and copy what he is doing
I am replying to close this thread. He contacted me over telegram. I took a look at his phone and the phone is not being detected in fastboot mode on his pc. Maybe hard bricked or in edl mode. Also his twrp is not accessible. So i suggested him to contact the edl guy and he fixed the phone.
So ask mods to close this thread?
speedtripler said:
If he's stuck in twrp how can he download a ROM to flash? I don't think you can transfer files to a phone that doesn't have a ROM to flash via twrp
Fastboot first from a PC cmd maybe the only way to get started
Click to expand...
Click to collapse
I know it's closed as such but in twrp, I can copy files from pc to phone. He could have done the same. BTW, I'm using the very first twrp that many wouldn't install but my phone is recognised in Windows while in recovery. This might help someone else
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..
Hello! Just created an account in this forum to seek help because this is driving me nuts.
I have a Xiaomi Redmi Note 9 (Merlin) which has no system (Android), but I still can access fastboot and recovery menu, so I went ahead and unlocked the bootloader and flashed MIUI without any issue. To my surprise, when I booted the phone back up, it was like I didn't do anything as it still bootlooped, it didn't even show the MIUI logo, so I tried again; still nothing.
So, I tried the following:
- I followed the guide in this forum for hard-bricked Note 9 phones (https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/), and I can tell the firmware flashes because the starting menu and the fastboot logo changed from the rabbit to FASTBOOT in orange letters, but still no system.
- I flashed stock firmware, but still no system.
- I flashed the MIUI version that the phone came with through fastboot, but still no system
- I tried to flash the newest version of MIUI the phone came with through TWRP using the recovery version, but still no system (and when I try to reboot, TWRP says there is no system)
- I tried installing Pixel Experience to see if MIUI was the issue but, still no system. The phone just keeps bootlooping endlessly.
- I tried running https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt to see if the encryption was the problem, but no progress.
I would appreciate any help to at least have my phone working, even if it's not with MIUI but with a custom ROM. At this point I don't care anymore, just want a useable phone.
Thank you.
Hi. Just flash the whole stock MIUI ROM of your choice and then
In TWRP you must format /data (you did first make a backup of your personal data right?)
Then phone should boot again.
I hope this helps. Good luck!
lebigmac said:
Hi. Just flash the whole stock MIUI ROM of your choice and then
In TWRP you must format /data
I hope this helps. Good luck!
Click to expand...
Click to collapse
I've tried that a couple of times but it's like I didn't do anything, when I reboot I still get no system
bump
bump - really desperate about this matter
I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue
You are using the flash_all.sh script that comes with the stock MIUI firmware right?
well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck!
lebigmac said:
I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue
You are using the flash_all.sh script that comes with the stock MIUI firmware right?
well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck!
Click to expand...
Click to collapse
Yeah, I even tried with other PCs to see if that was the issue. Will try looking in the logs. Thank you!
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!!!