Hey!
So I recently bought a Redmi note 3 (SD) Kenzo, and successfully installed the latest official cm13 snapshot, though I am having problems with the rear camera, flash and FP sensor not been recognized/functioning.
(I should note I’ve never rooted, flashed, unlocked boot loader or install custom recovery or anything like this before)
My process was:
Request official permission to unlock, which I received in like 5 mins, then proceeded to successfully unlock with Mi unlock tool.
I then flashed official TWRP 3.0.2-2, but then couldn’t access internal storage due to some encryption thing TWRP was complaining about. I later worked out it was because I was running the latest China Dev MIUI ROM which is marshmallow, and then flashed “cofface_TWRP3_kenzo_p.img”, which worked fine.
I booted up into TWRP just fine, and then proceeded to wipe Dalvik cache, system, data and cache. I then flashed the firmware then latest snapshot build of which is linked here "http://forum.xda-developers.com/redmi-note-3/development/rom-cyanogenmod-13-t3431866". And then flashed open Gapps.
I then booted up which took around 10 minutes or so just fine.
According to Aida64 I have FPC sensor, and looking through root/system/etc/firmware, with no “goodix” to be seen. I don’t know where to look to find info on my rear cam and flash though.
So should I flash “radon kernel” (I don’t entirely know what this will do), did I make a mistake in the process, or something else entirely? Also is my bootloader now locked due to flashing cm13, and can I unlock it again with the Mi unlock tool?
It would be so great if you could help!
(also if more info is needed just let me know)
BukuThatDude said:
I recently bought a Redmi note 3 (SD) Kenzo, and successfully installed the latest official cm13 snapshot, though I am having problems with the rear camera, flash and FP sensor not been recognized/functioning.
Click to expand...
Click to collapse
Bro, you did everything in correct order.
And, to get fp working for you, flash Radon v2.9 and select fpc (or goodix if still doesn't work). Kernel is the sw part which directly interacts with your hw. So, you'll need Kernel Aduitor or any another such app to tweak the kernel settings. AIDA64 should show your cam sensors, afair.
And, if Radon doesn't help then you can flash CM13_RADIOS.zip which you'll find in the "All ROM, Recoveries, add-on zips......." thread.
And, official CM13 doesn't lock your bootloader, the unofficial CM13 from SantoshM does that.
You can unlock your bootloader any no. of times using MiUnlock, and if needed you can check it using the following command in adb and fastboot tool
Code:
fastboot oem device-info
Look for "Bootloader Unlocked - true/false"
As above, flash the latest Radon Kernel. Also do not use the old snapshots of CM13 (they are now months old), nightlies are more stable and much more updated.
sasukay said:
Bro, you did everything in correct order.
And, to get fp working for you, flash Radon v2.9 and select fpc (or goodix if still doesn't work). Kernel is the sw part which directly interacts with your hw. So, you'll need Kernel Aduitor or any another such app to tweak the kernel settings. AIDA64 should show your cam sensors, afair.
And, if Radon doesn't help then you can flash CM13_RADIOS.zip which you'll find in the "All ROM, Recoveries, add-on zips......." thread.
And, official CM13 doesn't lock your bootloader, the unofficial CM13 from SantoshM does that.
You can unlock your bootloader any no. of times using MiUnlock, and if needed you can check it using the following command in adb and fastboot tool
Code:
fastboot oem device-info
Look for "Bootloader Unlocked - true/false"
Click to expand...
Click to collapse
Can the kernel be flashed after the firmware/rom? Will it factory reset the device? If i run into any any issues what part do i wipe and replace in twrp to revert to the previous kernel?
Are you sure you have the Kenzo version?
Maybe you have the Kate version like me
BukuThatDude said:
Can the kernel be flashed after the firmware/rom? Will it factory reset the device? If i run into any any issues what part do i wipe and replace in twrp to revert to the previous kernel?
Click to expand...
Click to collapse
Flashing a kernel is like flashing any add-on zip like bootanimation or some new font and stuff. You don't need to flash the whole ROM or the reqd. firmware.
So, first make a backup of system and boot partition in twrp.
Then, wipe cache and dalvik and then flash the kernel zip. Reboot and done.. First boot may take some time.
And, should you need to revert back to stock, you can restore the backup you made earlier.
sasukay said:
Flashing a kernel is like flashing any add-on zip like bootanimation or some new font and stuff. You don't need to flash the whole ROM or the reqd. firmware.
So, first make a backup of system and boot partition in twrp.
Then, wipe cache and dalvik and then flash the kernel zip. Reboot and done.. First boot may take some time.
And, should you need to revert back to stock, you can restore the backup you made earlier.
Click to expand...
Click to collapse
Thank you, I'll update on how it goes.
sasukay said:
Flashing a kernel is like flashing any add-on zip like bootanimation or some new font and stuff. You don't need to flash the whole ROM or the reqd. firmware.
So, first make a backup of system and boot partition in twrp.
Then, wipe cache and dalvik and then flash the kernel zip. Reboot and done.. First boot may take some time.
And, should you need to revert back to stock, you can restore the backup you made earlier.
Click to expand...
Click to collapse
Yes holy sh*t thank you, both cameras and flash work now, fingerprint doesn't, so i'll try re-flashing it for "goodix" to see if that works.
(also is normal to hear a physical clicking sound next to the flashlight when turned on/off?)
BukuThatDude said:
Yes holy sh*t thank you, both cameras and flash work now, fingerprint doesn't, so i'll try re-flashing it for "goodix" to see if that works.
(also is normal to hear a physical clicking sound next to the flashlight when turned on/off?)
Click to expand...
Click to collapse
Flashing either FPC or goodix radon fingerprint still doesn't work?
BukuThatDude said:
Flashing either FPC or goodix radon fingerprint still doesn't work?
Click to expand...
Click to collapse
Try flashing this
Maybe you have goodix variant. If everything else fails, try goodix patch: https://drive.google.com/file/d/0B3Ji2Mma4WGpaFAweDZNWmVVVms/view
Related
I used to flash new ROM's on my old Galaxy S2 and there was never a issue of bootloader thing and same goes for old Xiaomi phones like redmi 1s.
But recently When xiaomi started locking bootloader , even after unlocking bootloader ,In most of ROM threads there is warning to delete the bootloader file from MIUI recovery ROM and then flash the ROM through recovery as it'll relock the bootloader.
Why does this happen so ?
1) What is the difference between official and unofficial unlocked bootloader ?
2) How much difference does one make if we want to flash all type of ROM's including MIUI , CM ,RR etc ?
3) Is there any way in which bootloader once unlocked , we don't have to worry about getting it relocked by flashing other ROM's like exactly what happens in most other android smartphones after unlocking their bootloader ?
Please clear the above doubts as it's becoming very confusing and irritating on flashing the ROM and what points needed to be kept in mind to avoid bricking the RN3.
Read this thread, my phone was officially unlocked the bootloader and used alka twrp to flash official rom with the ease. No need to do anything, just flashed it, superSU and exposed. Rebooted my phone, done. Only failed on incremental ota update, rebooted phone and received a second ota full rom and always success.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Sent from my Redmi Note 3 using Tapatalk
lack of good/complete tutorials
I believe flashing has always been a tricky job, more or less. The fact of the matter is that (for our device) I see very little complete tutorials in ROM threads, they all focus on the last bit of flashing. Some hazards are being mentioned and in the best case scenario you get a link to a vague solution (cross other forums and boards), never a full tutorial in the starting topic or the second post however. Back in the days you would see full explanations in every ROM thread, first posts were even being reserved for that. Nowadays users are being supposed to know it al which most do not.
Besides from the complete guides I also noticed that whenever something is explained, the explanations themselves are poor in terms of language (grammar as well as vocabulary) causing even more problems for newbies to fully understand what they are up to.
I am ne to the Xiaomi community but I am absolutely not new to flashing, cooking etc. (started back in the days with iPAQ's and so on) but I also had a though time to end up where I am now with a official unlocked phone that is rooted, has a custom recovery and a Xiaomi.eu ROM. MY journey was a long one but I must conclude that none of the steps were a real hazard, but combining everything in a workflow in correct order was a pain in the back.
First thing that came to me was the idea of writing down my experiences in the form of a FULL tutorial, which I might do when I find the time. I am pretty sure this will help many fellow flashers, newbies and pro's, to establish what most of us did.
These were just my two cents.
P.S. One more thing I noticed is that there are a lot of unfinished projects, they do the job that they were needed for, but they do nothing else.
e.g. Why are there so many custom recoveries, are there no developers anymore that can combine them all to one-fits-all ?
timberwolf60 said:
Read this thread, my phone was officially unlocked the bootloader and used alka twrp to flash official rom with the ease. No need to do anything, just flashed it, superSU and exposed. Rebooted my phone, done. Only failed on incremental ota update, rebooted phone and received a second ota full rom and always success.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
That is a lot of If else there
Why we can't just flash any rom after unlocking bootloader officially and always have to fear about bootloader relock again?
If i am not mistaken this situation is in Xiaomi phones right ?
Dust2Dust said:
I believe flashing has always been a tricky job, more or less. The fact of the matter is that (for our device) I see very little complete tutorials in ROM threads, they all focus on the last bit of flashing. Some hazards are being mentioned and in the best case scenario you get a link to a vague solution (cross other forums and boards), never a full tutorial in the starting topic or the second post however. Back in the days you would see full explanations in every ROM thread, first posts were even being reserved for that. Nowadays users are being supposed to know it al which most do not.
Besides from the complete guides I also noticed that whenever something is explained, the explanations themselves are poor in terms of language (grammar as well as vocabulary) causing even more problems for newbies to fully understand what they are up to.
I am ne to the Xiaomi community but I am absolutely not new to flashing, cooking etc. (started back in the days with iPAQ's and so on) but I also had a though time to end up where I am now with a official unlocked phone that is rooted, has a custom recovery and a Xiaomi.eu ROM. MY journey was a long one but I must conclude that none of the steps were a real hazard, but combining everything in a workflow in correct order was a pain in the back.
First thing that came to me was the idea of writing down my experiences in the form of a FULL tutorial, which I might do when I find the time. I am pretty sure this will help many fellow flashers, newbies and pro's, to establish what most of us did.
These were just my two cents.
P.S. One more thing I noticed is that there are a lot of unfinished projects, they do the job that they were needed for, but they do nothing else.
e.g. Why are there so many custom recoveries, are there no developers anymore that can combine them all to one-fits-all ?
Click to expand...
Click to collapse
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
akhil17kr said:
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
Click to expand...
Click to collapse
Xiaomi.eu weekly rom was cooked from cn dev rom, removed Chinese apps and put in Google apps and more European languages. Those who wish to flash it must officially unlocked bootloader.
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Xiaomi.eu weekly rom was cooked from cn dev rom, removed Chinese apps and put in Google apps and more European languages. Those who wish to flash it must officially unlocked bootloader.
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
and What's the difference between officially and unofficially unlocked bootloader ? i have unofficially now , should i officially unlock it ? if it makes flashing procedure easy ?
akhil17kr said:
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
Click to expand...
Click to collapse
Couple of examples: Xiaomi.eu gives me different locales and languages. It also sets default GPS location to Europe instead of Asia which provides a faster GPS fix. It is however behind in development so it doesn't have MIUI 8 yet.
As for the bootloader unlock: I have not looked into that since there is no need. If you follow all the steps in correct order and with correct ROM's official unlocking cannot go wrong. The culprit however is the complete chaos (now I said it) in instructions and tutorials. So I have not looked into the unofficial bootloader unlocking.
Dust2Dust said:
Couple of examples: Xiaomi.eu gives me different locales and languages. It also sets default GPS location to Europe instead of Asia which provides a faster GPS fix. It is however behind in development so it doesn't have MIUI 8 yet.
As for the bootloader unlock: I have not looked into that since there is no need. If you follow all the steps in correct order and with correct ROM's official unlocking cannot go wrong. The culprit however is the complete chaos (now I said it) in instructions and tutorials. So I have not looked into the unofficial bootloader unlocking.
Click to expand...
Click to collapse
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
akhil17kr said:
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
Click to expand...
Click to collapse
I did the same steps above after flashing resurrection remix with cm13 radio,after restoration of miui from twrp Alka backup my fingerprint sensor stopped working bcos the firmware didn't restore and I unchecked that partition so what i did was again.
1) go back to twrp Alka
2) flash the full MIUI 8 rom .zip and rebooted
3) then the fingerprint started working .
So Alka twrp has a bug in Restoration of firmware partition .so be careful and have a full twrp Alka backup and then flash cm13 and firmware
akhil17kr said:
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
Click to expand...
Click to collapse
They look more or less correct, I choose not to go the CM way (yet) since there are still some flaws that I can't live with.
I would try to go to official unlock, whatever it takes. It just looks more solid & safe from what I have been reading so far.
Also I would choose to use an other Recovery:
Official TWRP with F2FS Support
• Based on official TWRP 3.0.2-2 & updated CyanogenMod source
• Adds Support For F2FS based file systems.
• Used for flashing official CyanogenMod 13 based ROMs.
• Users with official unlocked bootloader will have to flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip.
• Users with unofficial unlocked bootloader should strictly not use this TWRP for flashing MIUI Recovery ROM Zip.
That seems optimized for CM the most.
II should tell you that I received the phone two days ago and I am also still catching up on reading.
Add on, taken from the above link:
In case of unofficial unlock:
4. Flashing Official CM13 ROM
• Flash F2FS TWRP & Backup Current ROM.
• Select /data & /cache Partitions & Select Change File System
• Select F2FS & Swipe To Change
• Reboot to Recovery & Factory Reset
• Reboot to Recovery & Flash CM13 Firmware
• Reboot to Recovery & Flash CM13 Zip
• Flash Appropriate GApps Version Zip & Reboot to System
• To Return Back To Any ROM After Flashing CM13, Flash Safe TWRP v2 & Proceed.
First of all, im not very new on android things, but the various type and hardware on kenzo a little bit confuse me.
Okay, i have a 2GB version of kenzo, running MIUI Global stable 8.0.6.0, i want to know if the procedure that i would like to do is right.
1. Unlocking my bootloader (still waiting for the approval)
2. Installing twrp.
Nah for the no 2, do i have to do any additional things or i just reboot it right away after installing twrp? (Im not interested on rooting because i dont need it atm).
3. Flashing the mandatory fw, cm14, and the gapps.
Can i actually flash them all on my current miui version? Or do i have to be on developer or something of a kind?
Thanks for your replies.
It means a lot to me, really.
senaferdy79 said:
First of all, im not very new on android things, but the various type and hardware on kenzo a little bit confuse me.
Okay, i have a 2GB version of kenzo, running MIUI Global stable 8.0.6.0, i want to know if the procedure that i would like to do is right.
1. Unlocking my bootloader (still waiting for the approval)
2. Installing twrp.
Nah for the no 2, do i have to do any additional things or i just reboot it right away after installing twrp? (Im not interested on rooting because i dont need it atm).
3. Flashing the mandatory fw, cm14, and the gapps.
Can i actually flash them all on my current miui version? Or do i have to be on developer or something of a kind?
Thanks for your replies.
It means a lot to me, really.
Click to expand...
Click to collapse
If you don't want to root, then don't flash SuperSU.
And for installing the ROM, first flash the developer ROM.
Download the developer ROM. Go the Updates > Choose Update Package > Choose the Developer ROM and install it.
Then,
Install twrp.
Transfer the CM14 Firmware, ROM, GApps to your Internal Storage.
Reboot to recovery.
Backup your current ROM. (Select everything)
Go to wipe > advanced wipe > choose everything except internal storage and microSD card.
Go to install > flash firmware > then ROM > then GApps.
Reboot
PiyushA01 said:
If you don't want to root, then don't flash SuperSU.
And for installing the ROM, first flash the developer ROM.
Download the developer ROM. Go the Updates > Choose Update Package > Choose the Developer ROM and install it.
Then,
Install twrp.
Transfer the CM14 Firmware, ROM, GApps to your Internal Storage.
Reboot to recovery.
Backup your current ROM. (Select everything)
Go to wipe > advanced wipe > choose everything except internal storage and microSD card.
Go to install > flash firmware > then ROM > then GApps.
Reboot
Click to expand...
Click to collapse
Could you please link the twrp installation thread?
Thanks!
Sure
Ky$h said:
Could you please link the twrp installation thread?
Thanks!
Click to expand...
Click to collapse
Sure buddy. Here you go.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Press thanks if I helped
PiyushA01 said:
If you don't want to root, then don't flash SuperSU.
And for installing the ROM, first flash the developer ROM.
Download the developer ROM. Go the Updates > Choose Update Package > Choose the Developer ROM and install it.
Then,
Install twrp.
Transfer the CM14 Firmware, ROM, GApps to your Internal Storage.
Reboot to recovery.
Backup your current ROM. (Select everything)
Go to wipe > advanced wipe > choose everything except internal storage and microSD card.
Go to install > flash firmware > then ROM > then GApps.
Reboot
Click to expand...
Click to collapse
So there is a must to be on developer rom in order to install cm14?
senaferdy79 said:
So there is a must to be on developer rom in order to install cm14?
Click to expand...
Click to collapse
It is preferred to install Developer ROM and install Pico GApps if you want the VoLTE access. If you don't want, then no need.
Hit the thanks button if it helped. ?
---------- Post added at 11:52 AM ---------- Previous post was at 11:49 AM ----------
Ky$h said:
Could you please link the twrp installation thread?
Thanks!
Click to expand...
Click to collapse
Watch this video: https://youtu.be/0ZOyjEhgZ-8
Install the customised twrp for Redmi Note 3 since it helps to install OTA updates when using MIUI ROMs.
Hit thanks if it helped.
wtf begging for likes?
what does pico gapps have to do with VoLTE?!
its not even needes to be on dev rom, its just recommended to use 6.11.24+ firmware for CM14 thats why... I usually just flash eu rom,epicrom,multirom,miuipro whichever of these, because they never relock BL.
After unlocking the bootloader, install Alka recovery and back up all the partitions before doing anything. Copy the back up to a safe place , you will need it for whenever you mess up.
harishmenace said:
After unlocking the bootloader, install Alka recovery and back up all the partitions before doing anything. Copy the back up to a safe place , you will need it for whenever you mess up.
Click to expand...
Click to collapse
Whats distinguishes alka with the official twrp?
Oscilator said:
wtf begging for likes?
what does pico gapps have to do with VoLTE?!
its not even needes to be on dev rom, its just recommended to use 6.11.24+ firmware for CM14 thats why... I usually just flash eu rom,epicrom,multirom,miuipro whichever of these, because they never relock BL.
Click to expand...
Click to collapse
Im kinda new with this topic, but what rom thats usually cause the relocking issue?
senaferdy79 said:
Whats distinguishes alka with the official twrp?
Click to expand...
Click to collapse
With official recovery you have to flash modified boot.img while flashing MIUI rom, with alka you don't have to. Also alka backs up all the partitions, so you don't have to worry about lost imei or bootloader relocking or any other problem. Just restore the backup and you will be right back from where you started.
Also go through these threads while waiting for your unlock permisssion
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
http://en.miui.com/thread-235865-1-1.html
also, zcx twrp can also backup all partitions + disables dm verity, just like alka does.
only switching from LP to MM or vice versa locks bootloader and flashing fastboot rom via edl does that too. some roms also lock it...
Same here. I too bought a 16gb version. But confused why I need to flash any developer ROM.
Can't I simply flash twrp after unlocking the bootloader officially and then flash any ROM from twrp(while on the MIUI GLOBAL 8.0.6.0 version)??
Any help would be appreciated
Sent from my Redmi Note 3 using XDA-Developers mobile app
Sorry for the intreruption but i also have a question. I was on MIUI 8.0.6.0, after that I wiped and flashed appropriate firmware for CM then CM13 then Gapps. What whould one do if he theoretically want to rollback to miui, is it ok to flash latest miui stable rom on top of cm firmware? I miss too much the camera app which had great slo mo and timelapse features. Im also thinking of updating to CM14, dont know yet...seems buggy. Thanks
richiegrasshopper said:
Sorry for the intreruption but i also have a question. I was on MIUI 8.0.6.0, after that I wiped and flashed appropriate firmware for CM then CM13 then Gapps. What whould one do if he theoretically want to rollback to miui, is it ok to flash latest miui stable rom on top of cm firmware? I miss too much the camera app which had great slo mo and timelapse features. Im also thinking of updating to CM14, dont know yet...seems buggy. Thanks
Click to expand...
Click to collapse
You can always flash the rom image with the flash tool(that works 100 percent). If you want to flash it from recovery than i think you need to flash lazy flasher after flashing the ROM. Give it a try.
10.4.6.0
https://sourceforge.net/projects/xi...MI9TPro_V10.4.6.0.QFKCNXM_v10-10.zip/download
https://androidfilehost.com/?fid=1899786940962588388
10.4.4.0
https://sourceforge.net/projects/xi...MI9TPro_V10.4.4.0.QFKCNXM_v10-10.zip/download
https://androidfilehost.com/?fid=1899786940962575568
10.3.17.0
https://sourceforge.net/projects/xi...MI9TPro_V10.3.17.0.PFKCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=1899786940962570691
10.3.16.0
https://sourceforge.net/projects/xi...MI9TPro_V10.3.16.0.PFKCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=6006931924117926174
10.3.15.0
https://sourceforge.net/projects/xi...MI9TPro_V10.3.15.0.PFKCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=6006931924117913531
10.3.11.0
https://sourceforge.net/projects/xi...MI9TPro_V10.3.11.0.PFKCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=6006931924117900078
10.3.10.0
https://sourceforge.net/projects/xi...MI9TPro_V10.3.10.0.PFKCNXM_v10-9.zip/download
https://androidfilehost.com/?fid=6006931924117899463
New links will be posted here.
10.3.10.0 replaced 10.3.9.0, cos 9.0 was rolled back.
10.3.11.0 added in OP.
Wondering if the stable version have same crashes as weekly ones when playing audio. Have anyone tried?
SafetyNet
Does anybody know if SafetyNet will pass without Root? Does Google Pay work and does Netflix DRM check pass?
hello everyone there is no .eu to be installed with miflash? to unlock the bootloader I have to wait 10 days
There is an issue with youtube vanced jittiring and breaking the speaker and mic atleast for me. Does anyone have the same bugs? I used the non-root root and magisk version of youtube vanced and it still happens. Currently on 10.3.11
I'm using 10.3.11.0 and it's seen as a Mi Mix 2S
Aren't the stable and developer ROM both based of the Chinese rom?
This rom is great.been using it for 3 days. No bugs encountered. Thanks
how to do it
it will need root? or with only bootloader unlocked? any fast guide how can i install it? thanks in advance!
bastianpsycho1 said:
it will need root? or with only bootloader unlocked? any fast guide how can i install it? thanks in advance!
Click to expand...
Click to collapse
No need for root. Just unlock the bootloader, flash twrp ,copy zip to internal storage, boot in recovery(twrp), perform factory reset/clean wipe, then install eu rom
gasmatigas said:
No need for root. Just unlock the bootloader, flash twrp ,copy zip to internal storage, boot in recovery(twrp), perform factory reset/clean wipe, then install eu rom
Click to expand...
Click to collapse
thanks buddy!
narugan26 said:
There is an issue with youtube vanced jittiring and breaking the speaker and mic atleast for me. Does anyone have the same bugs? I used the non-root root and magisk version of youtube vanced and it still happens. Currently on 10.3.11
Click to expand...
Click to collapse
The same bug happened to me when I was able to unlock my K20 pro yesterday. The headphone also does not work as well. Video playback from youtube is like slowmotion and no sound.
Factory reset did not help either.
I guess the developer of this rom does not have the actual device to test before releasing.
Id like to flash the EU ROM, but after unlocking bootloader, flashing TWRP.. all with success I always then boot again in the built in recovery.. and cant access the TWRP, only after I flash it I boot there on the first reboot. After system reboot, the access is gone or is overridden... any suggestions?
Thank you
dave6771 said:
Id like to flash the EU ROM, but after unlocking bootloader, flashing TWRP.. all with success I always then boot again in the built in recovery.. and cant access the TWRP, only after I flash it I boot there on the first reboot. After system reboot, the access is gone or is overridden... any suggestions?
Thank you
Click to expand...
Click to collapse
You need to boot in to TWRP immediately after flashing it and without booting into MIUI first. MIUI will restore recovery if you allow it to boot first. TWRP on first boot will write something that stops MIUI from restoring stock recovery.
After flashing and whilst still in fastboot press and hold volume up and power. Keep both pressed until the phone starts to reboot. Once the phone vibrates release the power button but keep holding the volume up until it boots into TWRP. It's a bit awkward to get right at first. It took me a few attempts to do it right on my first Xiaomi phone.
I got the issue of video on Facebook played in slow motion without sound. A reboot helps but the issue will occur in no time. And occasionally, I can't receive phone calls why it's calling, only missed calls after that.
khoaitaychienvn said:
I got the issue of video on Facebook played in slow motion without sound. A reboot helps but the issue will occur in no time. And occasionally, I can't receive phone calls why it's calling, only missed calls after that.
Click to expand...
Click to collapse
I had the same bug and fixed that myself by simply wiping "system" in twrp and reinstalling the rom.
Give it a try and post a comment here if the bug still persists after doing so.
xuananh94 said:
I had the same bug and fixed that myself by simply wiping "system" in twrp and reinstalling the rom.
Give it a try and post a comment here if the bug still persists after doing so.
Click to expand...
Click to collapse
I thought we shouldnt wipe system as it becomes a semi brick and will require a full flash with Xiaomi tool?
ermacwins said:
I thought we shouldnt wipe system as it becomes a semi brick and will require a full flash with Xiaomi tool?
Click to expand...
Click to collapse
If you have a working TWRP, then wiping system isn't a problem. Your just use TWRP to install whatever ROM you want.
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 ?
Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do