Related
I am very confused on how to root RN3 (SD 650).
I need rooting for
- Titanium backup
- Adblock
There are multiple terms and multiple posts. Can any one guide.
What is Kenzo, Kate .... ?
What is global dev/chinese rom?
What I have learnt so far
Step 1 - I need to unlock bootloader. But how ??
Official method - Does it require flashing a new rom? Will I loose data?
Unofficial - Is there any safe method?
Step 2 - Flash recovery
Cofface and ZCX are stable TWRPs. Which one to use.
i unlocked on global stable (so no data loss) no need of dev ROM ( it depends on luck)
try logging in on miunlock tool and micloud with mobile no (as username)only. If it fails try tommorow. repetition can do no good.
I unlocked on stable rom on my first attempt of the day.
my last attempt was weeks ago (primarily because i thought it was a lost cause)
thread http://en.miui.com/thread-280561-1-1.html
zcx for backing up ROMs ,
while updating through zcx to 6.11.24 many had bootloop(easily fixed by miunlock again).
so i updated through cofface no big problem ( the only problem i had was the system launcher was not loading fixed when i installed xposed again) always take backup before updating
first thing first. apply for bootloader unlocking. thn unlock it through mi unlock tool. if u are new to these things thn dont try unofficial methods.
hope this helps.
hyperorb said:
I am very confused on how to root RN3 (SD 650).
I need rooting for
- Titanium backup
- Adblock
There are multiple terms and multiple posts. Can any one guide.
What is Kenzo, Kate .... ?
What is global dev/chinese rom?
What I have learnt so far
Step 1 - I need to unlock bootloader. But how ??
Official method - Does it require flashing a new rom? Will I loose data?
Unofficial - Is there any safe method?
Step 2 - Flash recovery
Cofface and ZCX are stable TWRPs. Which one to use.
Click to expand...
Click to collapse
Welcome to Redmi Note 3 family.
Kenzo or Kate?
Snapdragon standard variant is called as a 'kenzo' and special edition Redmi note 3 with different radios version is called as a 'kate'.
Global/ Chinese?
There are two types of MIUI ROMs.
1. Global
2. Chinese
Difference in these both ROMs is that, you will find some chinese material here and there in chinese ROM. Global is fully in english.
Again there are two subtypes of these two ROMs which are Stable and Dev/Beta. Sometimes Beta/Dev ROM is also called as a 'weekly'.
So basically most of the devices have 4 official MIUI ROMs which are:
1. Global Stable
2. Global Beta or Global Dev
3. Chinese Stable
4. Chinese Beta or Dev
There is no connection between the type of ROM and unlocking bootloader.
Bootloader unlock method?
Since you know there are two methods to unlock the bootloader, I will discuss them one by one.
1. Official
You don't require to flash any latest or dev or chinese ROM to unlock using official method.
First of all you need a persmission from Xiaomi to unlock the bootloader.
Goto http://en.miui.com/unlock/
Login here. The account should be same as the one is on your phone.
Write the reasons for unlocking.
After that Xiaomi will grant you the permission. If you don't receive any SMS from Xiaomi, just check on the above link.
Even if you get the permission its most likely you will not able to unlock nootloader on first attepmt. But don't worry, try again after few days.
Use MiUnlock tool. Once you get the permision, that tool will be available on the above link or you can always download from here http://en.miui.com/unlock/download_en.html
2. Unofficial
I have unlocked my phone by unofficial method 6-7 months ago and I still have no issues at all.
Open this folder https://mega.nz/#F!LUxlHJBC!RK5_8fta4XWAVFqWoWrvjQ
It has everything what you need for unlocking bootloader unofficially.
Just follow this guide and you are good to go: GUIDE
You might have to disable Driver Signature Verification if you are using Windows 8 or higher (google it)
Recovery?
I will suggest you only and only following recoveries:
If you have unlocked your bootloader officially, You must use ZCX only.
If you have unlocked your bootloader unofficially, you must use either Alka or Cofface
Here is a thread where you will find everything about recoveries.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
All download links are in that thread.
Hope this will help! Happy flashing! :fingers-crossed: :highfive:
skad00sh said:
Hope this will help!
Click to expand...
Click to collapse
What are you saying !!! .. This is more than what I could have asked for to start. :good: Many thanks for taking time to compile the information.
One more noob query. I have RN3 3GB 32GB version. Is it special edition or normal?
I am planning to flash unofficially - Recovery - Alka
One question - In your mega folder Kenzounlock.zip was uploaded in Sept. Can I use the "Redmi Note 3 Qualcomm Latest Global Stable Version Fastboot File Download" from http://en.miui.com/a-234.html as replacement.
Many thanks for your help.
hyperorb said:
What are you saying !!! .. This is more than what I could have asked for to start. :good: Many thanks for taking time to compile the information.
One more noob query. I have RN3 3GB 32GB version. Is it special edition or normal?
I am planning to flash unofficially - Recovery - Alka
One question - In your mega folder Kenzounlock.zip was uploaded in Sept. Can I use the "Redmi Note 3 Qualcomm Latest Global Stable Version Fastboot File Download" from http://en.miui.com/a-234.html as replacement.
Many thanks for your help.
Click to expand...
Click to collapse
I have same device. No problrm at all.
'kenzounlock.zip' should be flashed. Only that zip grants you ability to unlock bootloader. Don't flash any other zip.
Don't foget to activate 'OEM Unlocking' from Developer Options
To unlock Developer Options, tap on 'MIUI Version' 7 times.
Developer Options is situated at Settings>Additional Settings.
@skad00sh Unfortunately I moved forward with latest global stable zip.
- Unzip global stable Kenzo zip
- Found the unocked emmc_appsboot.mbn from the forum
- Replaced the file in /images folder
- Miflash (Beta version gave length less than zero error) therefore used MiFlash 20160401
- Flashed rom
- Fastboot mode
- Unlocked boot loader -> Auto reboot
- Had to force fastboot
- Oem device-info tells bootloader unlocked
- Reboot
- Red light blinking while charging
- Rom booted successfully.
Not sure why red light is blinking while charging
Edit :
I was able to use another emmc_appsboot.mbn from http://forum.xda-developers.com/red...nlock-twrp-t3494833/post69484805#post69484805.
Reflashed with replaced file. Now no more blinking red light.
Cofface TWRP from below link worked. Alka did not work.
http://forum.xda-developers.com/redmi-note-3/how-to/tutorial-miui-8-0-1-0-global-stable-t3449039
Rebooting now... Fingers crossed ..
hyperorb said:
@skad00sh Unfortunately I moved forward with latest global stable zip.
- Unzip global stable Kenzo zip
- Found the unocked emmc_appsboot.mbn from the forum
- Replaced the file in /images folder
- Miflash (Beta version gave length less than zero error) therefore used MiFlash 20160401
- Flashed rom
- Fastboot mode
- Unlocked boot loader -> Auto reboot
- Had to force fastboot
- Oem device-info tells bootloader unlocked
- Reboot
- Red light blinking while charging
- Rom booted successfully.
Not sure why red light is blinking while charging
Click to expand...
Click to collapse
So far you have done great!
Congrats!!
Red Light Blinking is common issue on unofficially unlocked bootloader devices.
Its just a firmware issue which can be fixed by flashing proper firmware.
Flash ROM from xiaomi.eu. Those ROMs are very clean and works perfectly with titanium backup. The issue with official MIUI ROM is that every time to try to restore a app from titanium backup, it asks for your permision. It is so annoying. Xiaomi.eu provides clean ROMs. These ROMs are unlocked bootloader friendly. These will not relock your bootloader.
Link for the ROM.
I recommend you to flash this ROM. Updated on 1st December.
In case you want to use current ROM without changing anything, you can flash following MIUI firmware from recovery... and you will be done with that red light thingy!
MIUI Firmware Link
I wonder why you still want to use MIUI when you can taste Nougat 7.1 easily!
In case if you want to use nougat, I will recommend you to use CyanogenMod 14.1, Ressurection Remix, AICP (I felt these ROMs are highly stable than other)
skad00sh said:
So far you have done great!
Congrats!!
Red Light Blinking is common issue on unofficially unlocked bootloader devices.
Its just a firmware issue which can be fixed by flashing proper firmware.
Flash ROM from xiaomi.eu. Those ROMs are very clean and works perfectly with titanium backup. The issue with official MIUI ROM is that every time to try to restore a app from titanium backup, it asks for your permision. It is so annoying. Xiaomi.eu provides clean ROMs. These ROMs are unlocked bootloader friendly. These will not relock your bootloader.
Link for the ROM.
I recommend you to flash this ROM. Updated on 1st December.
In case you want to use current ROM without changing anything, you can flash following MIUI firmware from recovery... and you will be done with that red light thingy!
MIUI Firmware Link
I wonder why you still want to use MIUI when you can taste Nougat 7.1 easily!
In case if you want to use nougat, I will recommend you to use CyanogenMod 14.1, Ressurection Remix, AICP (I felt these ROMs are highly stable than other)
Click to expand...
Click to collapse
Red light issue - [refer to edit in my previous reply. ]It is fixed. I had to use a different bootloader file. It worked with latest global stable.
Recovery I was unable to use Alka recovery (refer to your mega folder) . Had to install Cofface (refer to my previous reply).
EU Roms - My bad. I was not aware of those. Sigh !! so much effort I put. You are right TiBU asks about every single app restore. Besides for some app .. it hanged. I had to force reboot. Can I install these rom using TWRP Cofface recovery??
Nougat - This is my SO's fone. I need a stable daily driver for her. This is a day old phone. May be after sometime I will try 7.1
Honestly, I was very scared with RN3. It was my most confusing rooting. Compared to Moto Defy > Galaxy S3 > OP3 .. which were all very easy to manipulate.. But RN3 ..
Your initial post really paved way for me to move forward. Sincere thanks to you and others who helped me with my queries.
One thing is surprising that Cofface TWRP does not show EFS backup option
Wasn't the MTK variant called hennesy? and the rmn3 pro(sd650) with extra cellular bands called the kate.
Ivanlai said:
Wasn't the MTK variant called hennesy? and the rmn3 pro(sd650) with extra cellular bands called the kate.
Click to expand...
Click to collapse
There are 3 variants in the Redmi Note 3 series
RN3MTK code named "Hennessy" - with Mediatek SoC
RN3SD code named "Kenzo" - (with Qualcomm/SoC is Snapdragon 650), also called "Pro"
RN3SD Special Edition, code named "Kate" - "International version"also called "Special Edition" (Kate variant) of "pro", includes 800 base band (4g in somes isolated areas) and hardware is 2mm higher than kenzo.
Edit: Oops @Ivanlai You wrote the same thing. Looks like I still have lots of confusion . :silly:
Ivanlai said:
Wasn't the MTK variant called hennesy? and the rmn3 pro(sd650) with extra cellular bands called the kate.
Click to expand...
Click to collapse
Oh yeah! I forgot! My bad! MTK version is called as a Hennessy.
Rename that Alka recovery file to 'recovery.img' then copy it to your Minimal ADB and Fastboot folder.
After that open command prompt in that folder and enter following command
Code:
fastboot flash recovery recovery.img
Then alka will be installed.
You can flash EU roms directly from any recovery.
@skad00sh
1) Should I update recovery from Cofface to Alka ? If yes, how fastboot flash or TWRP install?
2) Before installing EU rom, do I need to replace the bootloader file emmc_appsboot.mbn
hyperorb said:
One thing is surprising that Cofface TWRP does not show EFS backup option
Click to expand...
Click to collapse
yes it is. use zcx or alka for backup
edit
if you want to flash another recovery image n ur phone is rooted thn use flashify app to flash any recovery img through your phone
Flash ROM from [URL="https://xiaomi.eu/community/threads/6-12-1.36462/" said:
xiaomi.eu[/URL]. Those ROMs are very clean and works perfectly with titanium backup. Xiaomi.eu provides clean ROMs. These ROMs are unlocked bootloader friendly. These will not relock your bootloader.
Link for the ROM.
I recommend you to flash this ROM. Updated on 1st December.
Click to expand...
Click to collapse
Do i have to replace the emmc_appsboot.mbn from xiaomi.eu ROM or just flash using Cofface TWRP?
Guys..i have redmi note 3 sd 650 miui 8.0.6...how should i install recovery..i wan to try cm roms??so many confusion regarding which is the right recovery to flash on my device...
hyperorb said:
@skad00sh
1) Should I update recovery from Cofface to Alka ? If yes, how fastboot flash or TWRP install?
2) Before installing EU rom, do I need to replace the bootloader file emmc_appsboot.mbn
Click to expand...
Click to collapse
1. Yes use Alka. It has all backup options. You will filnd EFS and other backup options in it. Since you have unlocked officially, use Alka only. An you can install it directly through TWRP install. No issues.
2. No need to replace emmc_appsboot.mbn for EU ROMs. They are specially made for unlocked bootloader devices only. So you can directly flash EU ROMs without any worry.
$lim $hady said:
Do i have to replace the emmc_appsboot.mbn from xiaomi.eu ROM or just flash using Cofface TWRP?
Click to expand...
Click to collapse
No need to replace emmc_appsboot.mbn for EU ROMs. They are specially made for unlocked bootloader devices only. So you can directly flash EU ROMs without any worry.
kitbor said:
Guys..i have redmi note 3 sd 650 miui 8.0.6...how should i install recovery..i wan to try cm roms??so many confusion regarding which is the right recovery to flash on my device...
Click to expand...
Click to collapse
Checkout 4th post of mine in this thread or click below:
http://forum.xda-developers.com/showpost.php?p=69920880&postcount=4
skad00sh said:
1. Yes use Alka. It has all backup options. You will filnd EFS and other backup options in it. Since you have unlocked officially, use Alka only. An you can install it directly through TWRP install. No issues.
Click to expand...
Click to collapse
Ok. Will install Alka.
By the way, I have unlocked unofficially. Hope that is ok.
skad00sh said:
No need to replace emmc_appsboot.mbn for EU ROMs. They are specially made for unlocked bootloader devices only. So you can directly flash EU ROMs without any worry.
Click to expand...
Click to collapse
Thank you.. I flashed the latest 6.12.1 while waiting for the reply got stuck in mi account log in screen.. Clean flashed 6.11.3 and then dirty flashed 6.12.1 and lazy flasher.. Works perfect.. Using Cofface TWRP
I was a Mi A2 user for a while, now I'm moving to Note 9 Pro and I feel a bit lost because of lacking of guides and tools.
I encounter some unexpected issues with disabling phone encryption. In short, I followed the steps I used for my Mi A2, but it seemed only working partially, and I encountered boot loop when upgrading ROM afterwards.
The details are as follow:
I have Note 9 Pro global (joyeuse), originally it was on stock ROM V11.0.5.0.QJZMIXM
After unlocking bootloader, I booted to TWRP with TWRP-3.4.1B-joyeuse-fix.img (from https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ ) and flashed Magisk, then Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip (from https://zackptg5.com/android.php#disverfe )
Everything was fine, I could debloat and disable Xiaomi services, and Google Pay was working (with Magisk Hide and MagiskHide Props Config).
But when entering TWRP again, TWRP requested passcode to decrypt data, that's when I realized the phone was not decrypted. Booting to normal mode, phone Settings showed "Encrypted". But because TWRP was able to decrypt with passcode and could backup as normal, so I ignored it.
When V11.0.7.0.QJZMIXM was released, I backed up /data using TWRP and flashed the new ROM using fastboot without erasing data. Then the phone was in boot loop (it showed redmi logo then vibrated then rebooted)
I flashed back V11.0.5.0.QJZMIXM without erasing data, but it still entered boot loop.
I decided to wipe data (using TWRP and using Wipe menu in XIaomi recovery mode), but boot loop still occurred.
I flashed V11.0.7.0.QJZMIXM again, but this time without keeping data (flash_all.bat), but boot loop still occurred.
I accidentally selected flash all & lock bootloader (in MiFlashTool), then phone could boot up normally. But I lost root, and bootloader was relocked.
Additional info: In a rage, I turned on Developer mode and tapped to bind mi account, and now I have to wait 168hrs to unlock bootloader again.
Questions:
What have I done wrong that the phone entered boot loop even after wiping data?
What's the proper way of using TWRP so that I can backup data and can update ROM in the future without going through this mess again?
HRSE said:
I was a Mi A2 user for a while, now I'm moving to Note 9 Pro and I feel a bit lost because of lacking of guides and tools.
I encounter some unexpected issues with disabling phone encryption. In short, I followed the steps I used for my Mi A2, but it seemed only working partially, and I encountered boot loop when upgrading ROM afterwards.
The details are as follow:
I have Note 9 Pro global (joyeuse), originally it was on stock ROM V11.0.5.0.QJZMIXM
After unlocking bootloader, I booted to TWRP with TWRP-3.4.1B-joyeuse-fix.img (from https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ ) and flashed Magisk, then Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip (from https://zackptg5.com/android.php#disverfe )
Everything was fine, I could debloat and disable Xiaomi services, and Google Pay was working (with Magisk Hide and MagiskHide Props Config).
But when entering TWRP again, TWRP requested passcode to decrypt data, that's when I realized the phone was not decrypted. Booting to normal mode, phone Settings showed "Encrypted". But because TWRP was able to decrypt with passcode and could backup as normal, so I ignored it.
When V11.0.7.0.QJZMIXM was released, I backed up /data using TWRP and flashed the new ROM using fastboot without erasing data. Then the phone was in boot loop (it showed redmi logo then vibrated then rebooted)
I flashed back V11.0.5.0.QJZMIXM without erasing data, but it still entered boot loop.
I decided to wipe data (using TWRP and using Wipe menu in XIaomi recovery mode), but boot loop still occurred.
I flashed V11.0.7.0.QJZMIXM again, but this time without keeping data (flash_all.bat), but boot loop still occurred.
I accidentally selected flash all & lock bootloader (in MiFlashTool), then phone could boot up normally. But I lost root, and bootloader was re-locked.
Additional info: In a rage, I turned on Developer mode and tapped to bind mi account, and now I have to wait 168hrs to unlock bootloader again.
Questions:
What have I done wrong that the phone entered boot loop even after wiping data?
What's the proper way of using TWRP so that I can backup data and can update ROM in the future without going through this mess again?
Click to expand...
Click to collapse
first of all you are not the only one that faces same problems. So chears mate. Next is the TWRP and the lack of stable/working version since i have done quite few phones now i can tell that the TWRP encryption ignore is not persistent and it works while you don't touch the recovery and not booting it up. Upon the boot it triggers the encryption and although he filesystem is not encrypted it still thinks it is.
Solution for now? wait for the fixed version while this is new phone and may take some time to re-code he recovery (find the damn cause of the encryption trigger).
Anyways. I am still thinking to do the fastboot rom mod, root it while it is not flashed and hen flash it while i don't actually need. I just need to remove all the miui/xiaomi stuff, block the damn ADS and root the phone and those things can be done on a pc i am just figuring out the correct way to do i.
The idea about skipping the TWRP came right after i downloaded mi-flash tool and found out that it uses same fastboot mode to flash everything and the file structure of the rom is not packet or something. Img files can be exacted and re-packed again so everything in the image can be modified.
What i really hate is the fact that there is tons of tools for other phones but somehow Xiaomi was skipped in the device selection...
Downloaded unlock tool, nice but limited to only requesting ad unlocking the phones bootloader. Next thing is the flash tool, it is limited to only flashing. There is xiaomi tool v2 that can also install the twrp, and cause the encryption crap or download and install stock or xiaomi.eu...
What i was looking for was the tool that can take the stock, decompress it and allow you to choose the apps you want to be per-installed, add some functions to it, mod bootscreens, pre-root it and eventually pack and flash the damn thing. While you are skipping the recovery procedure you are way safer than with its crap.
Agree with me?
daigtas said:
first of all you are not the only one that faces same problems. So chears mate. Next is the TWRP and the lack of stable/working version since i have done quite few phones now i can tell that the TWRP encryption ignore is not persistent and it works while you don't touch the recovery and not booting it up. Upon the boot it triggers the encryption and although he filesystem is not encrypted it still thinks it is.
Solution for now? wait for the fixed version while this is new phone and may take some time to re-code he recovery (find the damn cause of the encryption trigger).
Anyways. I am still thinking to do the fastboot rom mod, root it while it is not flashed and hen flash it while i don't actually need. I just need to remove all the miui/xiaomi stuff, block the damn ADS and root the phone and those things can be done on a pc i am just figuring out the correct way to do i.
The idea about skipping the TWRP came right after i downloaded mi-flash tool and found out that it uses same fastboot mode to flash everything and the file structure of the rom is not packet or something. Img files can be exacted and re-packed again so everything in the image can be modified.
What i really hate is the fact that there is tons of tools for other phones but somehow Xiaomi was skipped in the device selection...
Downloaded unlock tool, nice but limited to only requesting ad unlocking the phones bootloader. Next thing is the flash tool, it is limited to only flashing. There is xiaomi tool v2 that can also install the twrp, and cause the encryption crap or download and install stock or xiaomi.eu...
What i was looking for was the tool that can take the stock, decompress it and allow you to choose the apps you want to be per-installed, add some functions to it, mod bootscreens, pre-root it and eventually pack and flash the damn thing. While you are skipping the recovery procedure you are way safer than with its crap.
Agree with me?
Click to expand...
Click to collapse
More than one month, 280 view, 1 comment, no solution, no answer. Everyone out there are competing with each other to create their own ROMs/recovery/kernel images with whatever catchy names they can think of. Nice. But what's the point if the basics are not yet nailed down?
BTW, Telegram channel is flooded with non-contributing chit chat.
My casual observation is that lrtwrp seems to be a common theme for those who have had major issues on Joyeuse.
sir_bazz said:
My casual observation is that lrtwrp seems to be a common theme for those who have had major issues on Joyeuse.
Click to expand...
Click to collapse
For what it's worth, TWRP does not currently have any official builds for curtana OR joyeuse as far as I can tell. The flashing of early, unofficial, pre-alpha ports of TWRP directly onto partitions causing bricks is not that surprising. Xiaomi locking down EDL access is a ****ty move, but still.
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 ?
Hi all from Noob member.
I am wanting to update my Redmi Note 4 Snapdragon from stock MIUI Global 11.0.2 as no OTA updates for a long time.
Having searched the forums I see a lot of guides are from 2017 so need up to date help.
I understand first step is to install unlock bootloader and install TWRP.
Q1 I need a recommended guide for 2021. I have found this but the advice is slightly different from that on the TWRP Redmi page e.g. regarding how to deal with DM Verity. These terms are all new to me and somewhat confusing.
Q2 Will I be able to backup the factory ROM in case it all goes wrong and I need to get it back to the current state?
Any other advice gratefully received.
Hi. I have recently installed LineageOS 18.1 on my Redmi Note 4 Global (Snapdragon) and have written a detailed guide for myself, in case I would need to do it again. At first, I had problems with fingerprint not working even though I have installed everything correctly. I have fixed that issue with the help of LOS 18.1 main tester, and I have also written myself a guide for that fix.
If you would like to install LineageOS on your mido, I could share the guide with you.
Regarding your question 2, you can always make a backup of your current ROM before installing customs ROMs, and usually backups work fine, although I do not have any experience with that yet, so your mileage may vary.
Also, if your device is not bricked after tinkering with custom ROMS, you can always use latest fastboot MIUI ROM for your device, and flash it with official Mi Flash tool to get back to MIUI.
First step, as always, is to unlock your bootloader with Mi Unlock tool, which you can find here:
Apply for permissions to unlock Mi devices
en.miui.com
Read this FAQ as well:
https://c.mi.com/thread-2262302-1-0.html
By the way, bootloader on my mido was unlocked instantly with that tool, I did not have to wait at all.
Hi Rigadelt
Many thanks for the reply. I would indeed be interested in seeing your guide if it is not too much trouble.
Everything working correctly including the fingerprint reader would be a must for me. Glad to hear you fixed it.
Good to know you can make backups - I'm assuming this is via TWRP?
Appreciate the tip about fastboot MIUI ROMs - I think I have found them before on the official site when I searched a year or so ago about flashing a new ROM. It seems things are a bit more developed now.
Thanks for getting me pointed in the right direction!
Grump
No worries, just a disclaimer - I am not responsible if you somehow break your phone while following this guide.
I am also a noob on custom ROMs, but I have done the exact same steps, and my phone appears to be working fine, so you should be all right too. After all, these steps are almost identical to all custom ROMs installation instructions, the difference is that this time you will need to use OrangeFox recovery instead, because LOS 18.1 works better with it.
I have written this guide while following OrangeFox recovery guides, and getting help from Redmi Note 4 users on Telegram groups.
First install ADB + Fastboot in your PC (I assume you use Windows 10).
Download these files:
SDK platform tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Google USB Driver: https://dl.google.com/android/repository/usb_driver_r13-windows.zip
I am not sure if Google USB Driver is necessary, but install it anyway because I had it installed too.
For installation instructions, use the attached "ADB Fastboot installation.txt" file.
You can check this video for visual guide as well:
After that, unlock your bootloader with Mi Unlock tool.
Confirm that bootloader is unlocked on your Redmi Note 4 via ADB + Fastboot, following this article (go to PC section, ignore Android phone):
How to check if bootloader is unlocked or locked on Android
How to check if bootloader is unlocked or locked on Android
www.addictivetips.com
At this point, if everything is working fine and your phone is indeed unlocked, I recommend backing up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
Next, download these files and put them in your SD Card or internal phone storage (for example, Download folder). I recommend formatting SD Card and putting the files on it, but you can use internal storage as well.
OrangeFox recovery (R11.0) for mido:
https://dl.orangefox.download/5f14b74f26d98d90b476a532
Latest mido firmware (you will probably not need it, but have it just in case): https://xiaomifirmwareupdater.com/d...4XGlobal_V11.0.2.0.NCFMIXM_83170d3e3a_7.0.zip
LineageOS 17.1 with 4.9 kernel (you will need to install it first):
https://github.com/zeelog/OTA/releases/download/28.0/lineage-17.1-20201215-UNOFFICIAL-4.9-mido.zip
LineageOS 18.1:
https://github.com/zeelog/OTA/releases/download/31.0/lineage-18.1-20210107-UNOFFICIAL-mido.zip
GApps (FlameGApps "basic" is recommended for LOS 18.1):
https://sourceforge.net/projects/flamegapps/files/arm64/android-11/BETA/2020-12-29
I will continue the guide in the next message.
Now, make sure that your phone is charged and has more than 80% battery (just to be safe).
Also note that after the following step, you won't be able to boot to MIUI anymore, so make sure you have made a backup of your files.
Install OrangeFox recovery using this guide:
Installing OrangeFox Recovery
wiki.orangefox.tech
Then, follow the instructions written in the attached "Readme - LOS 17.1 and 18.1 installation" text file.
If you installed LOS 18.1 successfully but your fingerprint does not work anymore (although it worked fine on MIUI and LOS 17.1), then you will need to go back to latest mido MIUI ROM with Mi Flash tool and then follow the instructions in "Fingerprint fix and MIUI errors" text file.
Good luck. If you have any questions, I recommend creating a Telegram account and joining discussions on Redmi Note 4/4x groups.
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
the_real_grumpazoid said:
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
Click to expand...
Click to collapse
You're welcome.
Just wanted to let you know that the main tester of LineageOS 18.1 as of recently recommends using FlameGApps "basic" instead of NikGapps. Apparently some users experienced failed OTA updates (bootloops) due to problems associated with NikGapps.
Download it here:
FlameGApps - Browse /arm64/android-11/BETA/2020-12-29 at SourceForge.net
A Google Apps installer package for devices running on arm64 platform
sourceforge.net
Also, I have updated the installation instructions a bit, so I recommend re-downloading both attached text files above.
Some new info regarding LOS 18.1 updating:
Dirty flash method
1) Download the latest ROM udpate zip file and save it in phone's internal storage or SD Card.
2) Turn off your phone and reboot to recovery.
3) Go to Wipe and wipe:
Dalvik / ART Cache, Cache, System, Vendor
-- DO NOT WIPE "DATA" or "INTERNAL STORAGE" --
4) Ignore "Reboot System" option.
5) Go back to OrangeFox recovery, select latest ROM Update zip and flash it.
6) Ignore "Wipe Caches" and "Reboot System" options.
7) Go back to OrangeFox recovery, select GApps zip and flash it.
8) After flashing, tap "Wipe Caches". Wait for it to wipe and then ignore "Reboot System" option.
9) Go back to OrangeFox recovery, go to Menu, tap on Reboot, then Reboot to Recovery.
10) When the phone successfully reboots to OrangeFox recovery, go to recovery Menu, then Reboot, and Reboot to System.
OTA Update
1) Do not change anything in OrangeFox recovery OTA update options, leave all settings default (OTA disabled). To check if OTA is disabled in the recovery, do this:
1a) Turn off your phone and boot to OrangeFox recovery.
1b) Go to OrangeFox recovery Menu, tap on the Gear symbol in the upper right corner and select OTA & ROM.
1c) Make sure that OTA is disabled (enable OTA is greyed out)
1d) Go back to OrangeFox recovery Menu, then Reboot, and select Reboot to System.
2) Go to Settings, System, Advanced, Updater.
3) Tap on three dots in the upper right corner and select Preferences.
Preferences must be set like this:
* Auto updates check: Once a week
* Delete updates when installed: OFF
* Mobile data warning: ON
* Update recovery: OFF
If you can't disable "Update recovery" option in Updater preferences, then do not worry and leave it enabled. The stock recovery won't be updated (replaced) with LineageOS recovery even if this setting is enabled.
***--- OTA PROBLEMS ---***
In some (rare) cases OTA update might fail (usually due to GApps issues) causing your phone to bootloop, i.e. the phone gets stuck at LineageOS logo loading screen for a couple of minutes, and then reboots to recovery.
To solve this problem you need to install the update manually using Dirty flash method.
The downloaded OTA update file is in this location (in recovery):
root/data/LineageOS Update folder
You will have updated ROM without loosing any data.
Also, you can change GApps from NikGApps to FlameGApps or other GApps every time when you are using Dirty flash method to update your ROM.
Disclaimer:
The use and installation of this software product is at the exclusive responsibility of the user.I am not responsible for any damage that may occur to your device resulting from the use of this software.This software product is "as is". Its first goal is to allow the xiaomi.eu Rom be installed via recovery.If you have any doubts regarding the above lines, you should not use or install it.
Recovery:
Unofficial release 3.7.0 for Xiaomi Mi 10T Lite and Redmi Note 9 Pro 5G devices. Status : StableVersion : 3.7.0.4GRelease Date : 2022.12.26Features:
Android 12 decryptionAndroid 13 decryption (Not tested by myself)FlashingAdbOtg (Not tested by myself)MtpBackup / Restore to / from microSDBackup / Restore through adbSideloadDevice boot Logo changerMagisk tools and theme from @ Brigudav (Not tested by myself)
Notes:
I concluded that custom roms (without Miui) are unable to decrypt /data with this recovery.Checking LineageOS and ArrowOS, it seems that they use a different encryption mode than Miui.I haven't found how to check on Twrp booting what encryption mode /data uses and adjust to it.Therefore, I have uploaded another release for non Miui devices.Can't tested by myself, I don't know if it decrypts fine.However, it is likely the Miui variant will work correctly on the rest.
About official TWRP: The current official release https://twrp.me/xiaomi/xiaomimi10i.html does not work anymore since Miui 13. Use instead this TWRP.
Twrp not decryping on miui 14: Please, read this post
Downloads:
Last release from Xda (Post #2)
Older releases from androidfilehost
Release 3.7.0.3F for CUSTOM NOT Miui rom from Xda (Post #2)
Installation:
Updating this Twrp release:Downloaded to phone:Click on Install and locate the .zip file.Downloaded to PC (no need to copy it to the phone): On phone: start install via ADB (sideload). On PC execute: adb sideload file_name.zip
Try without installing: (does not alter the phone unless you want to do)Extract recovery.img from .zip file downloadedEnter fastboot mode.Execute: fastboot boot recovery.img
Installing this for the first time:
Your bootloader must be open. Extract recovery.img from downloaded .zip file. Enter fastboot mode Execute: fastboot flash recovery recovery.imgCredits:
Team Win RecoveryMinimal Manifest PlatformAlexander Brigudav
Latest release 3.7.0.4G for MIUI rom
Release 3.7.0.3F for CUSTOM Non Miui rom
Nice work
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
kacskrz said:
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
Click to expand...
Click to collapse
Hello. I'm Spanish xiaomi.eu translator and user.
I don't understand how is possible your issue...
When I boot TWRP it asks me for the PIN to decrypt.
I would not have uploaded the image without testing it first.
Also the reboot buttons do what they say..
I have so far tested it without installing, because I have not yet dumped the Stock Recovery partition.
In theory, it is supposed to work exactly the same in boot mode as in flash mode.
Can you try it without installing?
As stated in the third disclaimer lines:
"Its intention is to allow the Rom xiaomi.eu be installed via recovery."
I retired here due to lack of free time and have only become involved now for this reason.
Best regards
tuxafgmur said:
Can you try it without installing?
Click to expand...
Click to collapse
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
kacskrz said:
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Click to expand...
Click to collapse
Your logs do not seem to give relevant information about the issue.
It is clear that booting are completely ignoring the security lockout..
During the night I dumped and unpacked the stock recovery.
After studying it, I found nothing significant except that the kernel is not exactly the same as in boot.img.
I'm now downloading the latest weekly release to unpack it and compare vs stable release.
kacskrz said:
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
Click to expand...
Click to collapse
I'm not sure I understand what this paragraph means..
Regards.
Pixel Experience 12 data decrypted successfully.
Thanks
Lineage os data decrypted successfully.
Unfortunately, the weekly xiaomi.eu does not decipher the date.
For @kacskrz , @nolan2112 and anyone else using weekly xiaomi.eu:
I would appreciate the test of the new Release 3 I just uploaded.
Thanks in advance.
@tuxafgmur Unfortunately, nothing changed. I've posted logs on the xiaomi.eu thread.
The latest version also cannot decode the date. firmware weekly 22.7.21
New release 3.6.2.1B uploaded
In addition to some other minor changes,
fixed decryption on xiaomi.eu weekly.
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Tested to flash xiaomi.eu from storage and sideload.
tuxafgmur said:
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Click to expand...
Click to collapse
Everything is fine, the recovery is fully working. Thanks Amigo!
New release 3.6.2.1B-R3 uploaded
Revision
New release 3.6.2.1C uploaded
Format: Zip file to install from TWRP.
Some reviews.
Since xiaomi.eu rom replaces boot Logo on global devices, showing "Redmi"
this release includes options to switch logo between "MI" and "Redmi".
Each has two versions to choose from:
1 - Factory stock.2 - Like stock but hiding the padlock shown when bootloader is open.
The only recovery that works (and decrypts) on the newest MIUI 13 Android 12. Thank you!
Fantastic work, congratulations!