very less internal storage after fastboot flashing rom - Xiaomi Redmi Note 3 Questions & Answers

earlier i had around 25 gb usable but after fastboot flashing the latest dev 6.10.13 fastboot rom i get only 9.5 usable internal storage
please help my model 32gb old model

itzamangarg said:
earlier i had around 25 gb usable but after fastboot flashing the latest dev 6.10.13 fastboot rom i get only 9.5 usable internal storage
please help my model 32gb old model
Click to expand...
Click to collapse
Late reply but for users who face this now..
Just flash the stock miui rom in edl mode and let it boot. Then make all the modifications. I had the issue and fixed it myself

Related

my htc desire 826 has no rom and flashing problem

hi, i am new here. i need emergency help. i have "htc desire w826" which is bought from china mainland. i wanted global rom so i unlocked the bootloader and changed the stock rom (lollipop) by using TWRP. it was working good but the battery was draining so fast. so, i wanted to changed the rom again. i tried another marshmallow rom but it was not stable and doing restart after every few minutes. then i also removed it by using TWRP, but accidentally the TWRP recovery is not working now and the phone is stuck in fastboot option.
i also tried to flash the phone by downloaded few custom roms (OPHCIMG.zip files) through sd card, but every time it says "devices halted due to large image file", even though i formated sd card both ntfs and fat32.
I also tried to connect and flash my phone through computer but unfortunately my pc (in ADB cmd window) can't find my phone!! :crying:
Please guys if anyone there suggest me which can help me, i would be very greatful. thank you
jubair207 said:
hi, i am new here. i need emergency help. i have "htc desire w826" which is bought from china mainland. i wanted global rom so i unlocked the bootloader and changed the stock rom (lollipop) by using TWRP. it was working good but the battery was draining so fast. so, i wanted to changed the rom again. i tried another marshmallow rom but it was not stable and doing restart after every few minutes. then i also removed it by using TWRP, but accidentally the TWRP recovery is not working now and the phone is stuck in fastboot option.
i also tried to flash the phone by downloaded few custom roms (OPHCIMG.zip files) through sd card, but every time it says "devices halted due to large image file", even though i formated sd card both ntfs and fat32.
I also tried to connect and flash my phone through computer but unfortunately my pc (in ADB cmd window) can't find my phone!! :crying:
Please guys if anyone there suggest me which can help me, i would be very greatful. thank you
Click to expand...
Click to collapse
Try flashing twrp again
jubair207;74882401"htc desire w826"
Please guys if anyone there suggest me which can help me said:
Hi , first give me answer on this question
1. Is System status : modified or official or temporary ?
2. Bootloader : Locked / Unlocked ?
3. Secure status: S-On or S-Off ?
4. Are you able to go in RUU mode?
command: fastboot oem rebootRUU
5. Post here you getvar info :
command: fastboot getvar all
6. Did you tried to update from sd card Official firmware ?
Format sd to fat32 , put RUU firmware inside it , make sure your device is OFF and rename that firmware to ruu don't add ruu.zip because it will be double ruu.zip.zip in your windows probably if is your extensions file types is checked , insert sd card , hold vol + and power button together and release once you see boot image , or start HTC it will automatically start flashing .
Click to expand...
Click to collapse

[ROM][Stable] MIUI 11 xiaomi.eu

11.0.7.0
https://sourceforge.net/projects/xi...MICC9Pro_V11.0.7.0.PFDCNXM_v11-9.zip/download
https://androidfilehost.com/?fid=4349826312261699789
11.0.5.0
https://sourceforge.net/projects/xi...MICC9Pro_V11.0.5.0.PFDCNXM_v11-9.zip/download
https://androidfilehost.com/?fid=4349826312261652841
11.0.3.0
https://sourceforge.net/projects/xi...MICC9Pro_V11.0.3.0.PFDCNXM_v11-9.zip/download
https://androidfilehost.com/?fid=4349826312261642073
New links will be posted here.
Can I flash this on a chinese cc9 pro with an unlocked bootloader ?
I think yes.
akakal said:
Can I flash this on a chinese cc9 pro with an unlocked bootloader ?
Click to expand...
Click to collapse
Definitely. It even based on chinese version of MiUI
But does this have all the Google services and apps ?
Yes, it has it all
11.0.4.0 added in OP.
Optimization: Increased system stability
Optimization: Reduced system lag
Anyone has tried? Better than global stable? Today i Will unlock bootlader
Installed xiaomi.eu ROM today, working OK, better,than Global.
Is there any informations about weekly - developer ROM for Mi Note 10 ?
Luko69 said:
Is there any informations about weekly - developer ROM for Mi Note 10 ?
Click to expand...
Click to collapse
IS out now
I unlocked bootloader , flashed orangefox then the xiaomi.eu rom but after reboot it will not go past the loading screen .
Have reflashed it multiple times. Can any tell me where I am going wrong ?
akakal said:
I unlocked bootloader , flashed orangefox then the xiaomi.eu rom but after reboot it will not go past the loading screen .
Have reflashed it multiple times. Can any tell me where I am going wrong ?
Click to expand...
Click to collapse
You might want to try to wipe internal storage first before flashing the .EU.
Question! What's the usual differences between a global Rom and eu Rom?
11.0.5.0 added in OP.
Does this have OTA - Support?
otonieru said:
You might want to try to wipe internal storage first before flashing the .EU.
Click to expand...
Click to collapse
u must format data partition first , not wipe data
and reboot to recovery mode and transfer eu rom to device (when u format data , ur device only have a "FOX" folder)
and flash eu rom and enjoy it.
mingZT said:
u must format data partition first , not wipe data
and reboot to recovery mode and transfer eu rom to device (when u format data , ur device only have a "FOX" folder)
and flash eu rom and enjoy it.
Click to expand...
Click to collapse
How to transfer rom after data wipe?
stavrakas2007 said:
How to transfer rom after data wipe?
Click to expand...
Click to collapse
in recovery mode and use usb connect to pc
ur pc will show ur phone , and copy file from pc to your phone
I'm on Xiaomi eu 10.0.5 stable but Mi Note 10 appears to be shown CC9 pro. So far no issues. Should I mind about it?

Colt OS v5.4 (Android 10)

Hi all,
I have managed to install the following vanilla ROM on my Huawei P20 lite.
ColtOS-v5.4-10-Unofficial-20200103-arm64-ab-vanilla.img
So far it's going good but I've got 3 issues that I can't get info on with this ROM.
As far as I could see Android 10 OS has changed file systems. So my exFAT SD card won't work (needs to be formatted?). This card is only a couple of months old so it's not broken. It was working when I had EMUI 9.1 running yesterday. The OS says "there is an issue with your SD card". I go into the menu and it asks me to format said card. I have done this 4 times already but nothing changes. After the format the OS still gives the error that the SD card is faulty. Also when I connect my phone to my Win 10 PC only the Internal storage is picked up, not the SD card at all.
Then the other issue I have is getting TWRP to run. I have the following TWRP image that I tried to flash. When I do flash it and I reboot nothing happens and the phone boots to normal eRecovery.
TWRP image:
twrp-3.4.0-0-anne.img
Latly I have read read on the Colt OS XDA forum that one can not report errors of the OS if you are running Magisk. Is Magisk supported at all with this OS? Can I use SuperSU maybe instead of Magisk to get root working maybe?
For anyone who is going to respond, I say thank you
MayhemIam said:
Hi all,
I have managed to install the following vanilla ROM on my Huawei P20 lite.
ColtOS-v5.4-10-Unofficial-20200103-arm64-ab-vanilla.img
So far it's going good but I've got 3 issues that I can't get info on with this ROM.
As far as I could see Android 10 OS has changed file systems. So my exFAT SD card won't work (needs to be formatted?). This card is only a couple of months old so it's not broken. It was working when I had EMUI 9.1 running yesterday. The OS says "there is an issue with your SD card". I go into the menu and it asks me to format said card. I have done this 4 times already but nothing changes. After the format the OS still gives the error that the SD card is faulty. Also when I connect my phone to my Win 10 PC only the Internal storage is picked up, not the SD card at all.
Then the other issue I have is getting TWRP to run. I have the following TWRP image that I tried to flash. When I do flash it and I reboot nothing happens and the phone boots to normal eRecovery.
TWRP image:
twrp-3.4.0-0-anne.img
Latly I have read read on the Colt OS XDA forum that one can not report errors of the OS if you are running Magisk. Is Magisk supported at all with this OS? Can I use SuperSU maybe instead of Magisk to get root working maybe?
For anyone who is going to respond, I say thank you
Click to expand...
Click to collapse
Try Magisk-phh :
https://androidfilehost.com/?fid=4349826312261812699
You can try also SuperSu:
https://mega.nz/#!Zgc3VaBZ!K6_N35ex3HiNp6UAPq7nz_h3EDuuVQcLpYR0-kg56bQ
And TWRP by Askuccio:
https://mega.nz/#!EsdTgYqZ!2QX9wgAhA653Dp2MkDTLPHa3tmFdNqmC5CDDHB-7f5Y
-Alf- said:
Try Magisk-phh :
https://androidfilehost.com/?fid=4349826312261812699
You can try also SuperSu:
https://mega.nz/#!Zgc3VaBZ!K6_N35ex3HiNp6UAPq7nz_h3EDuuVQcLpYR0-kg56bQ
And TWRP by Askuccio:
https://mega.nz/#!EsdTgYqZ!2QX9wgAhA653Dp2MkDTLPHa3tmFdNqmC5CDDHB-7f5Y
Click to expand...
Click to collapse
Hi Alf man!
Thank you for the suggested links. I tried flashing the TWRP provided but nothing happens.
I have gone back to EMUI 9.1 and I can pickup the sd card. So I have no idea why it keeps telling me the sd card is corrupt Alf.
From what I have read, there are 2 partitions, one active the other not, for easier upgrading etc. So it seems I have to specify which partition to flash the provided TWRP? Is there a post on xda that I am missing in trying to install TWRP on Android 10?
MayhemIam said:
Hi Alf man!
Thank you for the suggested links. I tried flashing the TWRP provided but nothing happens.
I have gone back to EMUI 9.1 and I can pickup the sd card. So I have no idea why it keeps telling me the sd card is corrupt Alf.
From what I have read, there are 2 partitions, one active the other not, for easier upgrading etc. So it seems I have to specify which partition to flash the provided TWRP? Is there a post on xda that I am missing in trying to install TWRP on Android 10?
Click to expand...
Click to collapse
Well after flashing back to EMUI 9.1 I tried again, this time flashing TWRP first (twrp-3.4.0-0-anne.img) ....the other TWRP you suggested booted into TWRP but then it would reboot shortly after. Then I formated my sd card to fat32. After that I flashed Colt OS, then I reinstalled stock recovery, rebooted and ColtOS was working but it was installed on my SD card and not my main storage?
So now I am back on EMUI 9.1 but I can't access my storage on my PC. If I switch to "transfer file" only a cd-rom pops up in My Computer on Win 10. So I managed to screw up my entire storage :crying:
Well EMUI 9.1 is running though. My internal storage is encrypted
MayhemIam said:
Well after flashing back to EMUI 9.1 I tried again, this time flashing TWRP first (twrp-3.4.0-0-anne.img) ....the other TWRP you suggested booted into TWRP but then it would reboot shortly after. Then I formated my sd card to fat32. After that I flashed Colt OS, then I reinstalled stock recovery, rebooted and ColtOS was working but it was installed on my SD card and not my main storage?
So now I am back on EMUI 9.1 but I can't access my storage on my PC. If I switch to "transfer file" only a cd-rom pops up in My Computer on Win 10. So I managed to screw up my entire storage :crying:
Well EMUI 9.1 is running though. My internal storage is encrypted
Click to expand...
Click to collapse
Hi, just a few notes:
- As I wrote earlier, availability of custom ROMs for Kirin devices is scarce.
- Note that the "AB" in GSIs is not the same thing as physically having AB partitions .
"AB" in GSIs means SAR - system-as-root ( P20 lite which runs on EMUI 9.1).
A common misconception is that having Project Treble support and A/B partition support are related to one another, but that’s not actually the case. Having one does not imply the other. P20 Lite supports Project Treble AB, yet is an A-only device ( does not support Seamless Updates).
- if your phone is running Oreo, install a-only version.
-Alf- said:
Hi, just a few notes:
- I gave you in P.M. TWRP tips but you are still using 3.4.0-0 . Okay, it 's your choice.
- As I wrote earlier, availability of custom ROMs for Kirin devices is scarce. Some GSI Custom roms on Huawei devices require the .img file to be installed from fastboot :
fastboot erase userdata
fastboot flash system Colt-xxxx-xxxx.img
- Note that the "AB" moniker in GSIs is not the same thing as physically having AB partitions .
AB" in GSIs means system-as-root.
A common misconception is that having Project Treble support and A/B partition support are related to one another, but that’s not actually the case. Having one does not imply the other. P20 Lite supports Project Treble, yet is an A-only device ( does not support Seamless Updates).
- Install Service ROM and recover your phone (don't wait until it's too late ).
Click to expand...
Click to collapse
Ok thank you very much for your insight Alf.
I was having issues with that specific TWRP, that's why I tried a different one. But per your instructions, I will 100% go ahead and install Service ROM as suggested!
Thank you so very much Alf! Now I understand a bit more one the partitions.
-Alf- said:
Hi, just a few notes:
- I gave you in P.M. TWRP tips but you are still using 3.4.0-0 . Okay, it 's your choice.
- As I wrote earlier, availability of custom ROMs for Kirin devices is scarce. Some GSI Custom roms on Huawei devices require the .img file to be installed from fastboot :
fastboot erase userdata
fastboot flash system Colt-xxxx-xxxx.img
- Note that the "AB" moniker in GSIs is not the same thing as physically having AB partitions .
AB" in GSIs means system-as-root.
A common misconception is that having Project Treble support and A/B partition support are related to one another, but that’s not actually the case. Having one does not imply the other. P20 Lite supports Project Treble, yet is an A-only device ( does not support Seamless Updates).
- Install Service ROM and recover your phone (don't wait until it's too late ).
Click to expand...
Click to collapse
Hi Alf,
So I tried to follow your advice. I downloaded the following .zip file mentioned in your earlier post.
ANE-L01 8.0.0.136(C432) Firmware Android 8.0.0 EMUI 8.0.0 05014YXX.zip
I unzipped that file, and afterwards I tried flashing it first with the dload method, which only gave an error exclamation on eRecovery. I know I need to downgrade first from 9.1.0 and I have looked through XDA posts now but I haven't managed to do it. I have also tried via HiSuite and it gives me the option to downgrade, which I did, and then the phone restarted into TWRP recovery ( it seems I did not flash stock recovery before the HiSuite downgrade).
Ok...it seems I have to relock my bootloader before I try and downgrade to EMUI 8. If there are any steps I am missing please help.
Thank you!
MayhemIam said:
I know I need to downgrade first from 9.1.0 .
Click to expand...
Click to collapse
Where did you get this information ??? If you are running EMUI 9.1, you have to flash Service ROM for EMUI 9.1. Don't try downgrade to Oreo using Oreo Service ROM, it may brick your phone.
Download links (Service ROMs for C432 EMUI 9.1):
https://androidhost.ru/Xch
https://androidhost.ru/Xc1
https://androidhost.ru/Xar
It doesn't matter which one you choose.
-Alf- said:
Where did you get this information ??? If you are running EMUI 9.1, you have to flash Service ROM for EMUI 9.1. Don't try downgrade to Oreo using Oreo Service ROM, it may brick your phone.
Download links (Service ROMs for C432 EMUI 9.1):
https://androidhost.ru/Xch
https://androidhost.ru/Xc1
https://androidhost.ru/Xar
It doesn't matter which one you choose.
Click to expand...
Click to collapse
Ok thank you Alf, I will try with the provided info. Thank you! I was reading through XDA but couldn't find a answer. After I tried to do a downgrade via HiSuite and it failed as well as the dlaod method, I tried again to do a downgrade via HiSuite and the info in the app stated that my phone should not be unlocked.
Thank you for the help Alf!
Ok, I tried flashing via dload method as well as the service menu Alf. Didn't work. So I flashed it manually via fastboot. It installed the service ROM as you suggested I do.
The one I flashed was
Huawei P20 Lite ANE-LX1 ANE-L21 hw eu HLRCF Anne-L21 9.1.0.278(C432E6R1P7T8) Firmware EMUI9.1.0 05014YWN.zip
Current build number 9.1.0.278(C432E6R1P7)
What is the next step Alf? What makes a service ROM special? I tried looking on interwebs but couldn't find any info.
MayhemIam said:
Ok, I tried flashing via dload method as well as the service menu Alf. Didn't work. So I flashed it manually via fastboot. It installed the service ROM as you suggested I do.
The one I flashed was
Huawei P20 Lite ANE-LX1 ANE-L21 hw eu HLRCF Anne-L21 9.1.0.278(C432E6R1P7T8) Firmware EMUI9.1.0 05014YWN.zip
Current build number 9.1.0.278(C432E6R1P7)
What is the next step Alf? What makes a service ROM special? I tried looking on interwebs but couldn't find any info.
Click to expand...
Click to collapse
Ok, got a post on XDA, you need Service ROM to go back to Android 8.
The dload method, does it matter what the sd card's name is in the OS? Must it be sd_card?
OK the dload method does not work. I see that once you properly load a Service ROM, your device locks automatically and then one can proceed to flashing back to Oreo. I take it when the Service ROM is loaded correctly and one boot into fastboot mode the device should say "Phone Locked" "FRP Unlock"?
MayhemIam said:
Ok, got a post on XDA, you need Service ROM to go back to Android 8.
Click to expand...
Click to collapse
Dude it's you choice. As I said, downgrade to lower EMUI version via dload method may brick your phone. it's possible (and safely!) via HiSuite (with locked bootloader) only, or using HuRupdater 0.4 & TWRP .
Our conversation is useless, it's time to end it. Good Luck!
-Alf- said:
Dude it's you choice. As I said, downgrade to lower EMUI version via dload method may brick your phone. it's possible (and safely!) via HiSuite (with locked bootloader) only, or using HuRupdater 0.4 & TWRP .
Our conversation is useless, it's time to end it. Good Luck!
Click to expand...
Click to collapse
Thank you Alf. You were very helpful!

Xiaomi RN3PSE Kate bootloop whatever I flash

Hi,
My favourite phone is the Xiaomi Redmi note 3 Pro SE with Lineage OS 13 (Yes marshmallow).
I got a new one that was in endless bootloop and I planned to get it working.
I don't know if the bootloader has been unlocked and how (last time I checked it was written locked), if a custom ROM as been flashed or anything that could been done on it before I get it.
After many tries I first succeed to install LineageOs 13 on it, what I remember:
I go to fastboot mode
I go to edl mode
I flashed it with an old MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. (This is the way to get a recovery with no need to unlock bootloader)
I started it directly to TWRP recovery mode (to be sure TWRP will stay it I guess?) changed the language and checked OTA checkbox in parameters
I started this old official ROM once (to get the full storage capacity)
I discovered it was a 16GB ROM / 2GB RAM version instead a 32GBROM / 3GB RAM I previously knowed
I restarted to TWRP recovery mode
I wiped david/cache
I flashed the last knowed LineageOS 13 for this phone: https://forum.xda-developers.com/re...ageos-13-0-t3533744/post83687823#post83687823
I wiped david/cache
I flashed the last radeon kerned on it
I wiped david/cache
I restarted it to LineageOS 13
I restarted to TWRP recovery mode, changed the language and checked OTA checkbox in parameters
I flashed magisk (sytemless)
I wiped david/cache
I restarted it to LineageOS 13
I could use it install a lot of things, was happy with it
Before succeeding I tried a lot of combinations of official ROM/TWRP/MiFlash versions and this couple was the only one working.
Other MiFlash versions don't detect the phone in edl mode
But 2 weeks later, just after installing a new app, the phone sudently reboots and I got stuck in bootloop again...
I could go to recovery one time, I selected reboot system, now I can't go to recovery anymore
I still can go to fastboot mode and edl mode, and I can flash a ROM, but whatever I flash I can't go away from bootloop.
What could the new bootloop come from?
Is my installation sequence good?
Why only this combination of official ROM/TWRP/MiFlash versions was working?
Why can't I start a ROM anymore after a new flash?
Why can't I go to the recovery anymore after a new flash?
How to check if the emmc memory is defective (I got no error while flashing)?
Thanks for reading, hope someone still cares on this old great phone
Sorry for my bad English
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
JD. A said:
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
Click to expand...
Click to collapse
Thanks for your answer.
The last app before bootloop was a sms/mms backup app on google store I get through Aurora.
I tried to flash the stock ROM (old one) kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 but it doesn't start, always bootloop.
I have no option to wipe on the only miflash version that detect my phone in edl : the 2016.04.01.0 64 bit version. so I choose flash all data/storage include, but still bootloop.
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
JD. A said:
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
Click to expand...
Click to collapse
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
ROUGE13 said:
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
Click to expand...
Click to collapse
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
JD. A said:
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
Click to expand...
Click to collapse
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
ROUGE13 said:
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
Click to expand...
Click to collapse
I'm not home this weekend so I can't say for sure. gismoZ recommends using the 8.0.2 firmware or something like that can't remember, but the latest works just fine on my kate. The latest miflash is from 20200314 and just get the latest global rom and try to flash it.
I tried with an other windows computer, I successfully used last MiFlash version
But now, whatever I flash, ROM version or recovery version, it stay in bootloop when I power it.
I expect the eMMC memory to be faulty but why doesn't I have any error while flashing?
How to be sure this comes from the eMMC chip?
Some people have successfully changed it on the mediatek version of the phone:
https://fr-fr.facebook.com/16816505...c-kmvtu-done/1821360108117225/?_fb_noscript=1
https://translate.google.com/transl.../03/service-hp-xiaomi-redmi-mi-note-mati.html
If I go on this solution I have some questions before:
Must the eMMC chip be programmed before soldering it?
If not, can I program it with MiFlash once soldered?
If not, have I to use some special touch/contact on the mainboard to program it?
How to be sure of the chip model to buy?
Will the chip come already balled? Or have I to ball it before soldering it on mainboard?
Could I buy a 32GB chip instead 16GB original one?
Something else to test before going on this crazy last chance solution?
I bought a EDL flash cable, but I think I don't need it on this phone, I alway success to go to EDL mode from fastboot mode with a small batch script.
Hello ,
Any chance I could get an answer anymore or is my problem too specific maybe?

Detailed Guide for Flashing ROMs in POCO X3 / NFC (Karna & Surya)

Custom ROMs are one of the best things about Android. One of the best things about the openness of the Android platform is that if you're unhappy with the stock OS, you can install one of many modified versions of Android (called ROMs) on your device. A new ROM can bring you the latest version of Android before your manufacturer does, or it can replace your manufacturer-modded version of Android with a clean, stock version. But with the introduction of the dynamic partition flashing Custom ROMs are a bit tricky. In this post, I will run you through the steps of flashing Custom ROMs on your Poco X3.
Pre-requisites:
Unlocked Bootloader
Custom Recovery
Note:- Always create a backup of your important files before flashing.
Steps:-
From MIUI to Custom ROM
Encrypted
Copy the Custom ROMs zip to your sdcard or your OTG flash drive.
Boot to the recovery.
Flash the required firmware mentioned for the ROM.
Reboot your recovery.
Flash the Custom ROM.
And then format data [**This will wipe your internal storage**]
Reboot (Flash magisk if you want root after the first boot)
Decrypted
Flash this decrypted vendor
Flash the custom rom
Format data and reboot
From Custom ROMs to Another Custom ROM
Encrypted
**Backup your internal storage, incase something gets wrong**
Remove your lockscreen password
Boot to the recovery
Wipe Data, Cache and Dalvik Cache
Flash Custom ROM
Reboot
** If the device bootloops Format Data **
Decrypted
*If your device is encrypted*
Flash the decrypted vendor
Flash the custom rom
Format data and reboot
*If your device is already decrypted*
Wipe data and cache
Flash rom
Reboot
Notes:-
For encrypted people
Always create a backup of your internal storage.
Format data while upgrading from one android version to another.
Downgrading firmware may also require data format
Moving from Gapps build to non-gapps build or vice versa also requires fata format
For decrypted people
You don't need to flash the decrypted vendor everytime unless you come from miui
The vendor will not work on miui
All credits to POCO X3 Developers & Custom ROM Community.
Regards,
Polvolt
You saved me. I had properly unlocked bootloader, flashed OrangeFox but then I did the wipes and also mistakely formated data, so I couldn't send files from PC to phone to flash the custom rom.
Guess I could've just used the usb otg at this point, but I reflashed MIUI with a script, and reflashed OrangeFox and now I'm good to go.
I thought current custom recoveries don't check for rollback protection (yet)?
It's probably safe to be flashing stock firmwares via custom recovery if you are sure you know what you're doing. But this guide seem to appeal to new comers. Should we suggest they stick to using Mi Flash tool for flashing stock firmwares as it has rollback protection checks?
Or am I just out of the loop and this is no longer the case with custom recoveries for surya/karna?
Thanks for the guide btw. Greatly appreciated.
I miss manually flashing each partition files via fastboot like when I was on my Nexus devices and my Essential PH-1. I have not seen a guide that recommends or even teaches us to flash partitions manually.
payas0 said:
I thought current custom recoveries don't check for rollback protection (yet)?
It's probably safe to be flashing stock firmwares via custom recovery if you are sure you know what you're doing. But this guide seem to appeal to new comers. Should we suggest they stick to using Mi Flash tool for flashing stock firmwares as it has rollback protection checks?
Or am I just out of the loop and this is no longer the case with custom recoveries for surya/karna?
Thanks for the guide btw. Greatly appreciated.
I miss manually flashing each partition files via fastboot like when I was on my Nexus devices and my Essential PH-1. I have not seen a guide that recommends or even teaches us to flash partitions manually.
Click to expand...
Click to collapse
Yes it is safe to flash stock fw via custom recovery. ARB hasn't been implemented on surya yet.
Well manual flashing each partition using fastboot on surya is much more complicated. Dynamic partition work differently. In short one have to boot to fastboot than boot to fastbootd than you can flash rom
Are you sure it's not enabled? After running fastboot getvar anti, I get anti: 2 and I just bought the phone without doing any upgrades. Unless this alone doesn't mean that ARB is enabled?
Mckol said:
Are you sure it's not enabled? After running fastboot getvar anti, I get anti: 2 and I just bought the phone without doing any upgrades. Unless this alone doesn't mean that ARB is enabled?
Click to expand...
Click to collapse
No only if you get "anti:4" itmeans ARB is enabled, otherwise feel free to downgrade via fastboot.
Kineceleran said:
No only if you get "anti:4" itmeans ARB is enabled, otherwise feel free to downgrade via fastboot.
Click to expand...
Click to collapse
Seems you're wrong. This XDA article states other way:
"
How to find current rollback index
Reboot to fastboot mode
Enter the following command: fastboot getvar anti
If the output is blank, then anti-rollback has not yet been enabled. If you get a number in the output, then that’s your current rollback index."
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
How about from MIUI Global to MIUI EU ? I've found a 12.0.7.0, not sure but it seems to be EU rom, right?
Hello
I'm new to Xiaomi phones! For the love of God someone tell me how do I flash roms on my poco x3 nfc Note ( I've been flashing roms for years but not Xiaomi phones ). What ever I flash it works but after I attempt to flash another rom files in sd card get corrupt and I format data that doesn't gonna do anything! So please someone tell me how do I flash roms on this phone. My phone is encrypted I was on MIUI global
ayad.phonex said:
Hello
I'm new to Xiaomi phones! For the love of God someone tell me how do I flash roms on my poco x3 nfc Note ( I've been flashing roms for years but not Xiaomi phones ). What ever I flash it works but after I attempt to flash another rom files in sd card get corrupt and I format data that doesn't gonna do anything! So please someone tell me how do I flash roms on this phone. My phone is encrypted I was on MIUI global
Click to expand...
Click to collapse
I suppose you do have already unlocked bootloader and installed recovery? if no, please do, if yes try this guide or read this post
I'm having trouble because I flashed the vendor and it does not work in my version (QJGMIXM) and 4g internet does not work. I need help to fix because I can't find original vendor file or return to MIUI. HELP!!!!!
biliterror said:
I'm having trouble because I flashed the vendor and it does not work in my version (QJGMIXM) and 4g internet does not work. I need help to fix because I can't find original vendor file or return to MIUI. HELP!!!!!
Click to expand...
Click to collapse
Use any fastboot stock ROM and MiFlash tool to restore your phone...or flash any custom recovery and use it to flash any recovery stock ROM to restore your phone.
I have 6 days to wait for unlocking the device. I can't wait to get rid of the Mi UI mess and bloat. I haven't had to do a complicated (for me) phone flash process like this since a Motorola phone in 2014. I have a a few questions:
1- Do I need to add/install adb drivers to my WIN10 PC? I came across win adb drivers for the POCO in my search for Windows PC drivers. Which version of adb is needed for Win10? I currently have abd my laptop, but I can't determine the version.
2- Installing the recovery - I see the steps some have posted with TWRP versions, but I'm not really clear on this. Do I go to the folder with TWRP in it and then use a command prompt from there? TWRP or Orange Fox and what version? The posts are confusing.
3- I'd like to have the easiest rom flash for my first go at this phone. I would appreciate a recommendation for which rom might be the best one to start with. I will be want gapps as part of the process, but could flash afterwards if its better that way. Is Arrow OS or Havoc a good choice?
Sorry for all the questions.
Thanks
If i flash a newer Firmware (.7) over the decrypted vendor (.5), is my phone encrypted again?
Grusel said:
If i flash a newer Firmware (.7) over the decrypted vendor (.5), is my phone encrypted again?
Click to expand...
Click to collapse
if you'll flash 12.0.7 vendor from this thread, then no
Is this the right way?
Flash the CustomRom and after flash format Data?
Not first format Data and than flash Customrom?
My plan after bootloader Wait time is flash the Miui Eu Rom.
What ist the right way?
trutta said:
Is this the right way?
Flash the CustomRom and after flash format Data?
Not first format Data and than flash Customrom?
My plan after bootloader Wait time is flash the Miui Eu Rom.
What ist the right way?
Click to expand...
Click to collapse
Flashing ROM and Format data is the usual way....
I now. But the chronologie was another. First Format data, then flash Rom.
Usually in all my old device while flashing roms I have to wipe system data cache then I just flashed the rom, it's my first Xiaomi device I am confused as hell , should i never have to wipe system partition ? , Is flashing firmware necessary everytime ? Are there any risks associated with decrypted vendor ?please guide me I am not noob but these things are completely new to me
Device storage partition schemes have changed and are now dynamic, so previous procedures don't apply anymore. Closely follow your ROM developer instructions in order to avoid bricking your device.
Dynamic Partitions | Android Open Source Project
source.android.com
Brother, i have Karna (Indian) one with me. I got update to latest MIUI 12.0.8, after updating i unlocked the bootloader and flashed twrp, but it dint wrok, then had to flash OFox. RN i am on latest lineageOS 17.1. I am having network issues. Someone at the telegram group told me to flash the firmware along with the vendor of 12.0.5 MiUi as he also suffered the same kind of network issue i am having.
but the problem is i am unable to find the Vendor n firmware of 12.0.5. Can you please help me ?

Categories

Resources