[HOW TO] remove device encryption and get superSU - Xiaomi Mi 5 Guides, News, & Discussion

[HOW TO] remove device encryption and get superSU - Xiaomi Mi 5 Guides, News, & Discussion

The below steps are only part of the solution since there are a couple of prerequisites (with solutions for those already on these forums and MIUI sites). I'm afraid since it's getting late here, I cannot provide detailed steps for everything, I'm assuming you are like me and only got so far, so already know what you're doing
I'm not responsible for hard bricks, however if any steps I've entered are entirely wrong, please do let me know. I'm only trying to help the community out.
What you need:
Unlocked bootloader, sadly you will have to wait for the permission from them (I don't like this process either)
Decent knowledge of TWRP menu system
no care for completely wiping the SD Card contents - please make a backup of pictures or anything else you want
adb and fastboot both working and recognising the phone properly
Gemini (Xiaomi Mi 5) TWRP - https://drive.google.com/file/d/0B95J_je8rRN0V1Y2T2o0Mlh2R1E/view?usp=docslist_api **Thanks to Nesquix for posting the link to this** it is in Chinese and the theme changing solution did not work for me - but this doesn't really matter if you know your way around TWRP
Latest SuperSU - https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
Latest DEV Fastboot ROM - I cannot post the link however it can be found by searching for "mi 5 fastboot developer rom" on Google and selecting the link going to en.miui.com
STEPS to take:
Extract the contents of the fastboot ROM to a location of your choice. The only file you need is this one: \...\...\images\system.img (if someone can upload separately, I'll link in OP)
Place both the system.img from the fastboot ROM and twrp img file in the location of your fastboot folder
Enter fastboot mode (bootloader) on the Mi 5 via Power off --> volume down + power on --> let go once you see the MI logo
Check your device can be seen via the command, fastboot devices --> ENTER
Now input the following command, fastboot flash recovery twrp-mi5.img --> ENTER
Now enter in to recovery via volume up + power on - There appears to be a bug with TWRP whereby on some boots, touch isn't responsive, just keep booting back till it works (it will eventually)
Swipe on the first screen to enter the menu, tap the top right icon for wiping data, then the bottom right icon, you will see a text box with a warning - enter yes, then tick to fully wipe the SD card
Power off again, and reboot back to fastboot mode (bootloader)
Once there, input this command, fastboot flash system system.img --> ENTER
Once the system is flashed, input this command, fastboot reboot
Skip past initial steps for speed place the superSU zip on the root of the SD Card and then reboot back to recovery again
Flash SuperSU in recovery (top left option, find your zip, flash it
Reboot system
PROFIT - you now have an unencrypted system with working superSU and apps like Adaway work flawlessly - HAVE FUN and don't forget to say thanks if I did actually help you
Interesting notes.....
I'm not sure about anyone else, but I found web browsing to be alarmingly slow with no good explanation, the above steps completely resolved this
Google is now a search option in the default browser (it wasn't before!!)
Call it placebo all you want, but the phone really does seem a lot faster now.
Last but not least, I'm fairly certain to update to newer versions, you only have to extract same system.img from future fastboot ROM zips, and flash this on it's own to update the system.

To get the multilingual functionality of TWRP working, copy this file in TWRP\theme
You can also change the theme color in the advanced settings .
https://drive.google.com/file/d/0B95J_je8rRN0N19DLXdFYXV4NW8/view?usp=docslist_api

nesquix said:
To get the multilingual functionality of TWRP working, copy this file in TWRP\theme
You can also change the theme color in the advanced settings .
https://drive.google.com/file/d/0B95J_je8rRN0N19DLXdFYXV4NW8/view?usp=docslist_api
Click to expand...
Click to collapse
I think we dont need to copy TWRP theme. You can set language in first welcome screen or in Settings menu, and tap "world icon".
Here is the attachment of TWRP Screenshot :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 03:38 PM ---------- Previous post was at 03:26 PM ----------
kickassdave said:
The below steps are only part of the solution since there are a couple of prerequisites (with solutions for those already on these forums and MIUI sites). I'm afraid since it's getting late here, I cannot provide detailed steps for everything, I'm assuming you are like me and only got so far, so already know what you're doing
.
Click to expand...
Click to collapse
I think we dont need to flash system.img. check out my post here. After flashing TWRP via fastboot, format data and type yes in TWRP, all you need to do is reboot to system and swipe disable stock recovery flash. Setup your Mi5 and then copy SuperSU 2.65 or 2.68 beta to your Mi5. Next is reboot back to recovery, swipe allow modification, and then flash the SuperSU. Done. I tested out on Dev ROM and Stable ROM too, that there is no need to flash system.img again.

tomhtg90 said:
I think we dont need to copy TWRP theme. You can set language in first welcome screen or in Settings menu, and tap "world icon".
Here is the attachment of TWRP Screenshot :
---------- Post added at 03:38 PM ---------- Previous post was at 03:26 PM ----------
I think we dont need to flash system.img. check out my post here. After flashing TWRP via fastboot, format data and type yes in TWRP, all you need to do is reboot to system and swipe disable stock recovery flash. Setup your Mi5 and then copy SuperSU 2.65 or 2.68 beta to your Mi5. Next is reboot back to recovery, swipe allow modification, and then flash the SuperSU. Done. I tested out on Dev ROM and Stable ROM too, that there is no need to flash system.img again.
Click to expand...
Click to collapse
When I set to English in TWRP without the theme mod, it instantly reverts to Chinese.
With regards to flashing the system.img, I have a slight nagging issue with regards to the amount of files inside the fastboot image which WEREN'T required for full functionality.
I'm also concerned about where my data was going when browsing, as my browsing was slow no matter which browser I used - almost as if it was proxying via China.
Having only flashed system.img I no longer have this issue.

kickassdave said:
When I set to English in TWRP without the theme mod, it instantly reverts to Chinese.
With regards to flashing the system.img, I have a slight nagging issue with regards to the amount of files inside the fastboot image which WEREN'T required for full functionality.
I'm also concerned about where my data was going when browsing, as my browsing was slow no matter which browser I used - almost as if it was proxying via China.
Having only flashed system.img I no longer have this issue.
Click to expand...
Click to collapse
English languages in TWRP will not go back to chinese if you tap on "Never show this screen during boot again", "swipe to allow modification" and "Swipe disable recovery flash". But, if that's the only method that work for you, good then. Cheers

No need to flash again system here too

What exactly do the rest of the contents of the ROM contain then since I literally flashed on a single img from the entire zip!

I have mine Mi5 unlocked, with TWRP, root (SU) open encryption.
I'm on china dev rom 6.3.17 and would like to upgrade to 6.3.24, as I have some issues (camera force close after trying to get picture during video recording and some apps crashes).
Anyway, my question is: HOW should I update system and not lose all my setting, apps, data, etc and of course I can't lose root, open encryption and unlocked bootloader.
Please advise.

1myxomatosis1 said:
I have mine Mi5 unlocked, with TWRP, root (SU) open encryption.
I'm on china dev rom 6.3.17 and would like to upgrade to 6.3.24, as I have some issues (camera force close after trying to get picture during video recording and some apps crashes).
Anyway, my question is: HOW should I update system and not lose all my setting, apps, data, etc and of course I can't lose root, open encryption and unlocked bootloader.
Please advise.
Click to expand...
Click to collapse
this is what i'm trying to do now. but i'm on another base... not the 6.3.17 but the 7.2.7.0, anyway this is the same procedure.
when you have unlocked your bootloader, there is no way to encrypt all data again if you don't select "flash_all_lock.bat" with MiFlash windows app...
so you can play all TWRP partitions...except the SDCARD (called "data/media", don't mingle/mix up/confound with the "data" partition.... )
So since fastboot is still open with your unlocked bootloader are always able to reflash a recovery and do whatever you want again, don't panic !
i tried updating my rom 7.2.7.0 to 6.3.24 by flashing the system.img BUT there are some force close.... security center FC... wifi not working... i think they forgot to say that we need to manually flash the boot.img too (kernel.... who contain a lot of drivers and system links...)
so i just flashed the system.img and boot.img of the 6.3.24 on my 7.2.7.0 rom, i will report my feedback in some hours max. EDIT : WORKING !
but don't wory, since you don't wipe your SDCARD in the recovery (or use the flash_all_lock.bat with MiFlash), you will not loose your decrypted data partition
if my method of "simple updating" is not working by just flashing system.img and boot.img over the rom........ i suggest to reflash all partition with adb (system.img and boot.img), after that you can reboot to the twrp recovery, flash supersu 2.68 (or the last one) to be root, and setup your phone again... (you can do a MiBackup in the settings, and restore it later, this is working fine for your app, settings and so on)
:silly:
---------- Post added at 08:21 PM ---------- Previous post was at 08:13 PM ----------
UPDATE : WORKING.
Procedure to UPDATE since your phone have UNLOCKED BL, data decrypted and TWRP already flashed (or you can flash it before the procedure by adb) :
PROCEDURE
just flash the system.img AND the boot.img with adb in the CMD
(be sure your files are in the same folder of adb.exe and fastboot.exe)
"fastboot flash system system.img"
"fastboot flash boot boot.img"
then reboot to twrp recovery... flash supersu 2.68..
you don't need to wipe something.
just reboot and wait.
your phone is now updated, with root, twrp, decrypted data, and you don't loose your apps, settings and files. :good:

nesquix said:
[...]
PROCEDURE
[...]
Click to expand...
Click to collapse
Sound so easy and so fantastic that I can't just believe I'll try tomorrow as today I don't have power if something went wrong and I would have to start from a zero point:]

1myxomatosis1 said:
Sound so easy and so fantastic that I can't just believe I'll try tomorrow as today I don't have power if something went wrong and I would have to start from a zero point:]
Click to expand...
Click to collapse

I can't flash anything on TWRP, I can't mount the data... and so there's no file in sdcard

so at which point is the phone unencrypted? With installing SuperSU ?!
I also have the provlem, that TWRP changes the language instantly after changing it. And it also prompts me for password of encrypted partitions

Ivyn87 said:
I can't flash anything on TWRP, I can't mount the data... and so there's no file in sdcard
Click to expand...
Click to collapse
Because your phone is still encrypted.
So read all 3stpage and you will understand what you need to do.
http://forum.xda-developers.com/mi-5/help/rooting-mi-4-unlocking-bootloader-t3334677/page3
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
p1nky said:
so at which point is the phone unencrypted? With installing SuperSU ?!
I also have the provlem, that TWRP changes the language instantly after changing it. And it also prompts me for password of encrypted partitions
Click to expand...
Click to collapse
After wiping all the phone 2 times in the twrp recovery.

nesquix said:
Because your phone is still encrypted.
So read all 3stpage and you will understand what you need to do.
http://forum.xda-developers.com/mi-5/help/rooting-mi-4-unlocking-bootloader-t3334677/page3
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
After wiping all the phone 2 times in the twrp recovery.
Click to expand...
Click to collapse
Very thanks... now it work

Why can't TWRP write to encrypted partitions? I thought this is possible with TWRP 3.0. At least I have not heard from new Nexus owners that disabling encryption is necessary.

Hello,
I have Twrp already and a custom rom, i only want to decrypt . Am i right that i only< had to do this:
Swipe on the first screen to enter the menu, tap the top right icon for wiping data, then the bottom right icon, you will see a text box with a warning - enter yes, then tick to fully wipe the SD card.
And later to get root:
Skip past initial steps for speed place the superSU zip on the root of the SD Card and then reboot back to recovery again
Flash SuperSU in recovery (top left option, find your zip, flash it
Reboot system.
Kind regards gandalf

Thank you very much. !!!!:laugh::laugh:
I saved this tutorial, I had left the phone in the login screen.

Hello guys , I need some advice. I have a Mi5s already unlocked with TWRP and custom rom, but would like to get rid of encryption. My doubt is, if I format data and wipe everything, will I be able to move the rom zip in TWRP? And also, will I still have a system installed ? Thanks for your reply

christ-al said:
Hello guys , I need some advice. I have a Mi5s already unlocked with TWRP and custom rom, but would like to get rid of encryption. My doubt is, if I format data and wipe everything, will I be able to move the rom zip in TWRP? And also, will I still have a system installed ? Thanks for your reply
Click to expand...
Click to collapse
Yes ... U keep system...get blank data... Restart the phone... copy the zip/ROM again...or use USB otg

Related

[Tutorial][Resource][Root]Unlock-Recovery-SuperSU for HTC One M9-Sprint-M9_hima

Hi Everyone! I'm not a Dev (yet), so this is one of my contributions to the Sprint community
This is a DIY root method. By doing it yourself, you will learn some basic knowledge about using cmd windows, using ADB, and using fastboot. All files are in the
Unlock your bootloader - www.htcdev.com Follow the instructions at HTC-Dev to unlock your bootloader.
Flash TWRP Recovery - (refer to the Read Me First Text on how to fastboot flash TWRP Recovery)
Flash SuperSU - (copy to sdcard and flash from TWRP; v2.48 is the first working version)
Using this method will NOT give you S-OFF, but it will help you unlock your bootloader (HTC-DEV method), flash a custom recovery (TWRP for now), and install the Superuser app of your choice.
What's included:
Read Me Text (Instructions, ADB commands, and all the things)
ADB Tool
Latest HTC Drivers v4.2.0.001 and HTC BMP USB Drivers v1.0.5375(32 and 64 bit versions)
TWRP openrecovery v2.8.6.0
SuperSU.apk v2.48
I would like to thank:
TeamWin (for TWRP)
Captain_Throwback for his version of TWRP
Chainfire (for SuperSU)
The Incredible XDA Community
Root Files Below
AFH
DropBox Mirror
Frequently Asked Questions - HTC One-M9-Sprint(M9_Hima)
Disclaimer:
Code:
* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use these files.
* I am not responsible for any damage or problems you may have!
I suggest extracting it to a folder on your desktop so you can find it and start by reading the Read Me Text.
I will update this thread as updates become available.

Driver problems- get HTC Sync Manager HERE
Latest version of SuperSU can be found here: http://download.chainfire.eu/735/SuperSU/BETA-SuperSU-v2.48.zip
If you are having issues with the "Official" TWRP in the folder I recommend this one HERE
Please see the next post (post #3) on how to take an OTA

The first thing EVERYONE should do prior to rooting or anything else that modifies system is DO A NANDROID BACKUP!!! You must also use the latest TWRP, preferably @Captain_Throwback beta version.
On the M9, any changes to system will cause OTAs to fail, even using an older version of TWRP (which mounts the system RW), will cause OTAs to fail. The latest version of TWRP is RO. Captain_Throwback has taken this to the next level by implementing auto detection, if it detects your system is untouched, it is RO allowing you to do a clean backup. If it detects system has been modified, it will allow you to mount system as RW just like in the past.
for reference...
Captain_Throwback said:
Well, the bad news is that rooting will break the ability to take an OTA. In fact, ANY change to the system block (even just mounting it as read/write in recovery) will cause an OTA to fail. This is confirmed by the updater-script:
Code:
(range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "261d26028677f988c9e174a26438698d3049a1f3") || (range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "80a8e88fcc1c59e572557c09d58b46a060ce9313") || [B]abort("/dev/block/bootdevice/by-name/system has been remounted R/W; reflash device to reenable OTA updates")[/B];
if range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1146880") == "1396016f0a12721094d8b414b2f9d2b075409b3d" then
ui_print("Patching system image...");
show_progress(0.900000, 0);
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
else
(range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1146880") == "2a40a25d6999821224a246129bd31fe2e6945272") ||
[B] abort("system partition has unexpected contents")[/B];
endif;
Notice that it's confirming the checksum of the entire system block device. The first thing everyone will need to do before flashing ANYTHING is make a backup of system.
TWRP for the M9 is set up to mount system as read-only to prevent any checksum changes. Any backup taken of system is done via dd, which means the backup is done in image format and should exactly match the original checksum if/when restored.
Click to expand...
Click to collapse
To restore your clean system backup to accept OTAs, you must use fastboot. If you are S-ON, you must be in download mode.
-copy your clean system.emmc.win to your adb/fastboot folder on your pc
-boot into download mode
-use cmd fastboot flash system system.emmc.win
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if using Captain_Throwbacks beta TWRP, now when you boot into TWRP, it should detect an untouched system, you can verify this by making sure TWRP does not show "system" in the Mount menu.
If you have installed a pre-2.8.6.0 TWRP or forgot to do a backup or it's corrupted or whatever, @solver404 has provided a clean M9_stock_twrp_boot_system.zip
for reference on required fastboot...
Captain_Throwback said:
No. You can't just restore the backup. You have to fastboot flash the system image.
Click to expand...
Click to collapse
Captain_Throwback said:
The reason you can't just restore the stock system while in TWRP is because the system in TWRP is mounted read-write. As soon as you restore it, it'll be compromised again. So, you have to flash the system image while in fastboot to ensure it keeps its integrity. Then if you reboot into TWRP, system will be mounted read-only again. That'll allow you to take a full system image backup again after taking the OTA.
Click to expand...
Click to collapse

I think this needs a little more detail you can refer to my thread if you would like

Alright, post #1 has been updated with the links to a zip containing everything necessary (TWRP, superSU, etc) to get your device rooted, and get a custom recovery. I'm still working on the OPs, but it should be (mostly) right, and please look at post #3 by @OMJ on how to restore a backup, and what to do if you'd like to take an OTA

OMJ said:
The first thing EVERYONE should do prior to rooting or anything else that modifies system is DO A NANDROID BACKUP!!! You must also use the latest TWRP, preferably @Captain_Throwback beta version.
On the M9, any changes to system will cause OTAs to fail, even using an older version of TWRP (which mounts the system RW), will cause OTAs to fail. The latest version of TWRP is RO. Captain_Throwback has taken this to the next level by implementing auto detection, if it detects your system is untouched, it is RO allowing you to do a clean backup. If it detects system has been modified, it will allow you to mount system as RW just like in the past.
for reference...
To restore your clean system backup to accept OTAs, you must use fastboot. If you are S-ON, you must be in download mode.
-copy your clean system.emmc.win to your adb/fastboot folder on your pc
-boot into download mode
-use cmd fastboot flash system system.emmc.win
if using Captain_Throwbacks beta TWRP, now when you boot into TWRP, it should detect an untouched system, you can verify this by making sure TWRP does not show "system" in the Mount menu.
If you have installed a pre-2.8.6.0 TWRP or forgot to do a backup or it's corrupted or whatever, @solver404 has provided a clean M9_stock_twrp_boot_system.zip
for reference on required fastboot...
Click to expand...
Click to collapse
If one would rather just keep stock recovery, but have root for apps like Wifi Tether Router, would the below steps work?
1) Unlock with HTCDev
2) Only boot into TWRP (not flash it as permanent recovery): Fastboot boot twrp.img
3) Once booted into TWRP, install supersu
Then should OTA updates work, after which you only have to repeat steps 2 & 3?
My intent is to just get root access for apps like WiFi Tether Router.

ReproOne said:
If one would rather just keep stock recovery, but have root for apps like Wifi Tether Router, would the below steps work?
1) Unlock with HTCDev
2) Only boot into TWRP (not flash it as permanent recovery): Fastboot boot twrp.img
3) Once booted into TWRP, install supersu
Then should OTA updates work, after which you only have to repeat steps 2 & 3?
My intent is to just get root access for apps like WiFi Tether Router.
Click to expand...
Click to collapse
only way to know is to try...I've used fastboot boot in the past, not sure if it still works.
if it doesn't just do this:
-unlock
-flash twrp
-BACKUP!!!
-flash SuperSu
-flash stock recovery
this is actually better, as you want a good backup b4 modifying /system

OMJ said:
only way to know is to try...I've used fastboot boot in the past, not sure if it still works.
if it doesn't just do this:
-unlock
-flash twrp
-BACKUP!!!
-flash SuperSu
-flash stock recovery
this is actually better, as you want a good backup b4 modifying /system
Click to expand...
Click to collapse
Do you have a link for the stock recovery. The one in the post above does not appear to be available yet? I'm getting my M9 over the weekend, and I have used the option to just boot to TWRP on the M8. I was hoping someone may have tried that on the M9.

ReproOne said:
Do you have a link for the stock recovery. The one in the post above does not appear to be available yet? I'm getting my M9 over the weekend, and I have used the option to just boot to TWRP on the M8. I was hoping someone may have tried that on the M9.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3066720 ?

ReproOne said:
Do you have a link for the stock recovery. The one in the post above does not appear to be available yet? I'm getting my M9 over the weekend, and I have used the option to just boot to TWRP on the M8. I was hoping someone may have tried that on the M9.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934552130
pull the recovery from that zip

nickmilla15 said:
http://forum.xda-developers.com/showthread.php?t=3066720
Click to expand...
Click to collapse
That has TWRP. I was asking for the actual stock recovery.img if one wanted to put that back as recovery. Did I miss something?

ReproOne said:
That has TWRP. I was asking for the actual stock recovery.img if one wanted to put that back as recovery. Did I miss something?
Click to expand...
Click to collapse
Yeah, you missed the fact that I'm an idiot today haha. I'm really sorry. I guess I forgot what stock recovery meant ?

nickmilla15 said:
Yeah, you missed the fact that I'm an idiot today haha. I'm really sorry. I guess I forgot what stock recovery meant
Click to expand...
Click to collapse
I believe you are far from an idiot!
I've been reading through all posts before getting my M9 tomorrow.
I intend to unlock the bootloader and then first try to just boot into the newest beta of twrp to install supersu. If that does not work, I am trying to plan ahead and either learn how to backup recovery.img or find the stock of it. Can you assist with that, please?
I basically want root with the ability to accept OTA updates as normal.

ReproOne said:
I believe you are far from an idiot!
I've been reading through all posts before getting my M9 tomorrow.
I intend to unlock the bootloader and then first try to just boot into the newest beta of twrp to install supersu. If that does not work, I am trying to plan ahead and either learn how to backup recovery.img or find the stock of it. Can you assist with that, please?
I basically want root with the ability to accept OTA updates as normal.
Click to expand...
Click to collapse
Sending ya a PM ?

nickmilla15 said:
Sending ya a PM
Click to expand...
Click to collapse
I have replied. Thank you!

OMJ said:
The first thing EVERYONE should do prior to rooting or anything else that modifies system is DO A NANDROID BACKUP!!! You must also use the latest TWRP, preferably @Captain_Throwback beta version.
On the M9, any changes to system will cause OTAs to fail, even using an older version of TWRP (which mounts the system RW), will cause OTAs to fail. The latest version of TWRP is RO. Captain_Throwback has taken this to the next level by implementing auto detection, if it detects your system is untouched, it is RO allowing you to do a clean backup. If it detects system has been modified, it will allow you to mount system as RW just like in the past.
for reference...
To restore your clean system backup to accept OTAs, you must use fastboot. If you are S-ON, you must be in download mode.
-copy your clean system.emmc.win to your adb/fastboot folder on your pc
-boot into download mode
-use cmd fastboot flash system system.emmc.win
if using Captain_Throwbacks beta TWRP, now when you boot into TWRP, it should detect an untouched system, you can verify this by making sure TWRP does not show "system" in the Mount menu.
If you have installed a pre-2.8.6.0 TWRP or forgot to do a backup or it's corrupted or whatever, @solver404 has provided a clean M9_stock_twrp_boot_system.zip
for reference on required fastboot...
Click to expand...
Click to collapse
When i use this flash system method via fastboot in download mode using the instructions provided command prompt looks like its going to start the process but then it just sits there. See screenshot

deakelem said:
When i use this flash system method via fastboot in download mode using the instructions provided command prompt looks like its going to start the process but then it just sits there. See screenshot
Click to expand...
Click to collapse
mine did exactly as you're describing. i had to let it sit for something like 5-10min (i didnt time it), and then it finally progressed. if it doesnt go anywhere for you, make sure you've updated to the newest sdk-tools

deakelem said:
When i use this flash system method via fastboot in download mode using the instructions provided command prompt looks like its going to start the process but then it just sits there. See screenshot
Click to expand...
Click to collapse
So i followed the instructions and flashed the untouched system to my phone but when i attempt to take todays ota it fails and says something like reenabled OTA system has been r/w...
I factory reset and everything too and it still does that
Im using the stock recovery but do i need to relock my bl?
Ill try to get a pic of the error once it happens again.. cause it will

deakelem said:
So i followed the instructions and flashed the untouched system to my phone but when i attempt to take todays ota it fails and says something like reenabled OTA system has been r/w...
I factory reset and everything too and it still does that
Im using the stock recovery but do i need to relock my bl?
Ill try to get a pic of the error once it happens again.. cause it will
Click to expand...
Click to collapse
you shouldn't have to relock. i didn't relock mine, and i just finished updating the new OTA about 10 minutes ago. all i did was fastboot flash the original system image, fastboot flash the stock recovery, and then do the OTA.

hsmith1514 said:
you shouldn't have to relock. i didn't relock mine, and i just finished updating the new OTA about 10 minutes ago. all i did was fastboot flash the original system image, fastboot flash the stock recovery, and then do the OTA.
Click to expand...
Click to collapse
its working now thanks! i was just in a rush and didnt wait for the system to flash all the way like you said it took nearly 10 mins. OTA looks like its good so far
---------- Post added at 04:18 PM ---------- Previous post was at 04:10 PM ----------
hsmith1514 said:
you shouldn't have to relock. i didn't relock mine, and i just finished updating the new OTA about 10 minutes ago. all i did was fastboot flash the original system image, fastboot flash the stock recovery, and then do the OTA.
Click to expand...
Click to collapse
well i spoke too soon.. the ota progressed much further but then eventually said system has unexpected contexts.. I flashed untouch system and rebooted and took OTA thats it. So idk why it would say that

Step-by-step Rooting Guide with SuperSU for MI 8

I wanted to make sure everyone read this part first so that you know it's critical to backup because it happened to me figuring things out. If for any reason you are stuck in a boot loop, just reload twrp recovery and restore boot.img that you backed up for an easy quick fix.
Install drivers and adb on your PC.
Open command prompt or search 'cmd'.
Navigate to the directory with adb.exe
Download and store TWRP 2.2.2 (preferred) in the same directory where adb is located. Recommend renaming recovery file to recovery.img
Enable usb debugging on device by going to settings > about > and click on MIUI version repeatedly until developer settings are enabled. Go back and select additional settings to enable usb debugging.
Run the command: adb devices - to verify if able to connect to device (the serial number of your device will populate if so.
Run the command: adb reboot bootloader and phone device should say "Fastboot" in blue font
Run the command: fastboot boot recovery.img
Recovery will show in Chinese, click on the bottom right button to select English
May require to enter your default password you use to unlock your phone normally.
Click backup and be sure to backup system, boot, and recovery most of all so it's easy to recover your device moving forward.
Download and save SuperSU (I have been unsuccessful in getting Magisk to work at this time) onto storage device from PC to MI 8 that should appear with your Internal storage
Click on "Mount" in TWRP and unselect read-only
Click "Install" and flash SuperSU then reboot (my device rebooted one time and fully boot up the 2nd time so you're not alarmed)
Links:
SuperSU: https://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip?retrieve_file=1
TWRP: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-2-0703-t38126005
Appreciate any feedback, ideas, thoughts, or suggestions where all can collaborate and expand where we help each other further. Look forward to the future development of the MI 8 folks! Please note, I wanted to share the method that seemed to work best for me, but please be aware each and every single MI 8 device is not always exactly the same and the end result may vary and I'm not held accountable or responsible should you choose to follow the directions listed above. However, I wanted to share this information to help avoid any frustration going forward and save you time.
p.s. - If someone could help me figure out how to get twrp recovery to hold and not end up being replaced by mi recovery I would be most grateful as this has been an issue for me (I tried flashing, booting, and installing the img through twrp with no success). Thank you.

Hello thanks for your guide but i think we first need to unlock bl And for the twrp recovery to stick and not to be replaced by xiaomi recovery we need to flash something called "dm-verity " it basically removes that check, which replaces any other recovery by xiaomi recovery
Have a nice day and thanks for your work

I thought so as well, unfortunately I just haven't had much luck with dm verity which led to a soft brick on my device. I'll have to look over the code as it may vary in comparison to other xiaomi devices.
Sent from my MI 8 using Tapatalk

Fastboot flash recovery Command should do it ..
mekaziah said:
I wanted to make sure everyone read this part first so that you know it's critical to backup because it happened to me figuring things out. If for any reason you are stuck in a boot loop, just reload twrp recovery and restore boot.img that you backed up for an easy quick fix.
Install drivers and adb on your PC.
Open command prompt or search 'cmd'.
Navigate to the directory with adb.exe
Download and store TWRP 2.2.2 (preferred) in the same directory where adb is located. Recommend renaming recovery file to recovery.img
Enable usb debugging on device by going to settings > about > and click on MIUI version repeatedly until developer settings are enabled. Go back and select additional settings to enable usb debugging.
Run the command: adb devices - to verify if able to connect to device (the serial number of your device will populate if so.
Run the command: adb reboot bootloader and phone device should say "Fastboot" in blue font
Run the command: fastboot boot recovery.img
Recovery will show in Chinese, click on the bottom right button to select English
May require to enter your default password you use to unlock your phone normally.
Click backup and be sure to backup system, boot, and recovery most of all so it's easy to recover your device moving forward.
Download and save SuperSU (I have been unsuccessful in getting Magisk to work at this time) onto storage device from PC to MI 8 that should appear with your Internal storage
Click on "Mount" in TWRP and unselect read-only
Click "Install" and flash SuperSU then reboot (my device rebooted one time and fully boot up the 2nd time so you're not alarmed)
Links:
SuperSU: https://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip?retrieve_file=1
TWRP: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-2-0703-t38126005
Appreciate any feedback, ideas, thoughts, or suggestions where all can collaborate and expand where we help each other further. Look forward to the future development of the MI 8 folks! Please note, I wanted to share the method that seemed to work best for me, but please be aware each and every single MI 8 device is not always exactly the same and the end result may vary and I'm not held accountable or responsible should you choose to follow the directions listed above. However, I wanted to share this information to help avoid any frustration going forward and save you time.
p.s. - If someone could help me figure out how to get twrp recovery to hold and not end up being replaced by mi recovery I would be most grateful as this has been an issue for me (I tried flashing, booting, and installing the img through twrp with no success). Thank you.
Click to expand...
Click to collapse
Skickat från min MI 8 via Tapatalk

what issues do you get with magisk? I was able to flash it without any issues.

superior8888 said:
Fastboot flash recovery Command should do it ..
Skickat från min MI 8 via Tapatalk
Click to expand...
Click to collapse
Yes it does. Don't know why anyone would run SuperSU though.

mekaziah said:
I thought so as well, unfortunately I just haven't had much luck with dm verity which led to a soft brick on my device. I'll have to look over the code as it may vary in comparison to other xiaomi devices.
Click to expand...
Click to collapse
MAKE SURE U HAVE UNLOCKED BOOTLOADER
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on

-fluffy- said:
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
Click to expand...
Click to collapse
Would you mind stating the version of Magisk?

Strange Guide no Attention for Unlok Bl.

barrielui said:
Would you mind stating the version of Magisk?
Click to expand...
Click to collapse
16.4

magisk has been working fine for me for a while

samwise110712 said:
what issues do you get with magisk? I was able to flash it without any issues.
Click to expand...
Click to collapse
What's your ROM version? I flash twrp then magisk, bootloop...

-fluffy- said:
MAKE SURE U HAVE UNLOCKED BOOTLOADER
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
Click to expand...
Click to collapse
Hello how did you flash the TWRP through the TWRP ???
What version of MiUi you have ???

omek07 said:
Hello how did you flash the TWRP through the TWRP ???
What version of MiUi you have ???
Click to expand...
Click to collapse
simple put twrp.img on ur storage
then flash img from twrp

-fluffy- said:
simple put twrp.img on ur storage
then flash img from twrp
Click to expand...
Click to collapse
Yes but its asking after in which partition.
What partition you chose ?
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
-fluffy- said:
simple put twrp.img on ur storage
then flash img from twrp
Click to expand...
Click to collapse
Could you please tell me what rom you have ???
Thank you

omek07 said:
Yes but its asking after in which partition.
What partition you chose ?
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
Could you please tell me what rom you have ???
Thank you
Click to expand...
Click to collapse
u choose recovery
im using miui eu

magisk is running without any issue.
i am on the newest xiaomi eu beta rom and flashed magisk 16.7 without any issue right now
(after waiting horrible 15 days for unlocking the bootloader)

Ok so both of you have the xiaomi eu. I have global stable 9.5.11. so maybe that's the problem
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
So both of you have xiaomi eu rom. I have global stable 9.5.11. maybe that's the problem.

omek07 said:
Ok so both of you have the xiaomi eu. I have global stable 9.5.11. so maybe that's the problem
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
So both of you have xiaomi eu rom. I have global stable 9.5.11. maybe that's the problem.
Click to expand...
Click to collapse
I have the lastest global version, I cannot get the root access...
Someone tell me flash the Chinese verision then flash xiaomi.eu and magisk.

felixrao said:
I have the lastest global version, I cannot get the root access...
Someone tell me flash the Chinese verision then flash xiaomi.eu and magisk.
Click to expand...
Click to collapse
My friend i changed to the Xiaomi eu and everything worked. You dont have to flash the Chinese Version first you can go from Global to Xiaomi.eu. Just dont forget to do FORMAT data and not only Wipe Data.

[TWRP + Root] Galaxy J7 Refine (8.0) (Boost/Sprint)

TWRP has been successfully ported to the Galaxy J7 Refine (SM-J737P) (Oreo 8.0)ROOT METHOD POSTED BELOW IN POST #2Giving credit where credit is due:
@Dark98 for compiling the TWRP.img
@☆KØŁØЯΛĐØ☆ providing device files + testing/porting
@topjohnwu for Magisk
DISCLAIMER: This is NOT in Odin flashable .tar format. Due to sporadic updates in security & Oreo, Odin won't be much help here.
This has been tested & confirmed working on device build R16NW.J737PVPU1ARG3. It should work on other versions.
UPDATE: This will work on any Oreo version as well, including the new April 1, 2019 R16NW.J737PVPS3ASC2 update.
The patched_boot.img.tar I've attached will not work if you are on a different version of Oreo. You must provide your own patched_boot.img.tar that coincides with your respective version.
Proof of port is in the screenshot below (I've underlined the device build)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is a downside & an upside:
- The downside is that after you flash TWRP & reboot, you will lose root.
- The upside is that TWRP will remain so all you need to do to regain root is flash the Magisk-v18.1.zip in Recovery.
Procedure:
- In order to flash, you need an app that will do so without booting into recovery. View attachment Flashify.apk is the ideal choice for this procedure.
- Flash TWRP in Flashify but do not reboot from the app itself. Power off your device & boot into [TWRP] Recovery manually.
PAY ATTENTION TO THESE NEXT FEW STEPS!!!
- Extract the twrp.img from View attachment J737P_TWRP.zip
- Flash through Flashify, then boot into TWRP for the first time
- Now that you have booted into TWRP the first time, Swipe to allow modifications
- Navigate to Wipe > Format Data > type yes when prompted (this will not delete any files you have in your Internal Storage)
- Once the format is completed, go to TWRP home screen & Reboot > Power Off
DO NOT REBOOT TO SYSTEM
- Once device powers off, reboot back into TWRP (yes you will boot into recovery twice)
If you fail to immediately boot back into TWRP, you will brick & have to start over. The fiirst reboot is to clear out (wipe) the /Data partition to make room for your new recovery. Wiping will not delete any internal storage items. However, it will return a value of 0 for /Data. The second boot is to secure TWRP as your new Recovery, as well as fix the /Data return value.
- Now that you have secured TWRP, go ahead & make a TWRP backup as a safety precaution before you reboot. The backup could be considered "stock" with TWRP as the Recovery. The reason being is that you will lose root after formatting /Data. No worries, you will get it back.
After creating the backup, follow these next steps very carefully!!
You will now flash Magisk-v18.1 to regain root. With the new security measures Samsung put in late 2017, you will need to flash 2 .zip files after to ensure that root sticks.
YOU NEED TO FLASH THESE FILES IN ORDER. DO NOT WIPE CACHE AFTER EACH FLASH. DO NOT REBOOT AFTER EACH FLASH. FLASH EACH PACKAGE ONE AT A TIME. WAIT UNTIL THE 3RD FLASH IS COMPLETE & THEN REBOOT DEVICE. IT WILL TAKE SEVERAL MINUTES SO BE PATIENT.
(Still in TWRP)
- Go to Home & select Instal
- In this order, flash one at a time:
View attachment Magisk-v18.1(18100).zip
View attachment no-verity-opt-encrypt-6.0.zip
View attachment RMM-State_Bypass_Mesa_v2.zip
DO NOT WIPE THE CACHE
Screenshots of proper installation (in order):
- Reboot device normally. If you do not flash the dm-verity & RMM .zip files in order, you will bootloop & have to start over.
- When you get to your home screen, you will receive a notification to update Magisk. Update by either selecting the notification or manually through Magisk Manager.
- Allow Magisk to install the update; do not update through TWRP.
ĐØΠΞ

[ROOT] Galaxy J7 Refine (SM-J737P) (Oreo 8.0)
FOLLOW THESE DIRECTIONS. I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE.
View attachment 4733553 View attachment 4733552
I have given you a freebie by providing the patched_boot.img.tar, thus saving you a few steps
All files needed are uploaded to my Drive: https://drive.google.com/folderview?id=1-8CGkYef58I-DrkyOshRFniecO_0dBDc
NOTICE: Patched_boot.img.tar is solely for the J737PVPU1ARG3 software version. Any attempt to flash to a different version will result in a bootloop. You must patch + flash your own stock boot.img if you are on a different software version.
YOU MUST PAY ATTENTION TO THE FOLLOWING
- In the Bli5zkrieg.zip you extracted, load up Odin_v13.1 (non-patched)
- Load only the BL/AP/CP files from your stock firmware into Odin
- As soon as the flashing process ends, you must reboot quickly back into Download Mode. You have to be quick. If you allow the device to begin booting up, it makes the rooting process more difficult.
Assuming you followed directions...
- Close Odin_v13.1 & unplug your device while still remaining in Download Mode
- Launch Odin_v13.1 [Patched] & load up the patched_boot.img.tar in the AP slot
- Reconnect device & proceed to flash
- Device will reboot with "Verification Failure" so you must reset (this is part of root) (it does not activate FRP lock)
- When device reboots to Setup Wizard, skip through it. Do not add any accounts (Google or Samsung). Do not consent to giving any device data for whatever purposes (they will ask twice; look carefully)
- On the home screen, unlock Dev Options &allow USB Debugging. OEM should already have been unlocked
- Connect device to your pc & in the ZeeToolz folder you extracted, run CMD.exe
- Input adb devices to ensure proper connection
- Input adb install -r MagiskManager-v7.0.0.apk to install MM to your device
- Open MagiskManager & make sure everything is good to go (see attached screenshot)
- If everything is done properly then you will see a superuser tab in the left side-bar, indicating root access
ĐØΠΞ

Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)
note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.
I used the files below.
Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view
Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025
Cheers!

kinehumane said:
Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)
note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.
I used the files below.
Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view
Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025
Cheers!
Click to expand...
Click to collapse
No problem man. I didnt think to test sideload or mtp as I always use an SDcard (comes in handy lol). It was a tad bit tedious to get the whole process down due to Oreo. That being said, ensure that you have a backup. Editing any part of the system (ie. Build.prop) will result in failure. I installed the Time Zones update & it failed. As far as MagiskSU goes, I like the Modules but prefer SuperSU root. Will see about incorporating it in the near future

This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....
So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me. Can't seem to find one that doesn't do a root-check first, refusing to do the deed if root isn't there yet?
Trying from square 1, to the point that I did a total backup, factory reset, and am starting with a reset phone.

pauljulian said:
This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....
So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me.
Click to expand...
Click to collapse
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism
Root Essentials won't work as a secondary flasher bc it requires a custom recovery to be installed beforehand. Flashify will be your best bet so try all possibilities to get it to work

☆KØŁØЯΛĐØ☆ said:
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism
Click to expand...
Click to collapse
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...

pauljulian said:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
Click to expand...
Click to collapse
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP

pauljulian said:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
Click to expand...
Click to collapse
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
☆KØŁØЯΛĐØ☆ said:
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP
Click to expand...
Click to collapse
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.

pauljulian said:
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
When you go to get root, you will need your stock firmware (BL/AP/CP files). My directions are pretty straight forward. Unzip the tools, load up Odin (non-patched), flash BL + AP + CP in their respective slots. Make sure that after you flash the stock, you instantly reboot back into Download Mode. Close the current Odin & open the patched Odin. Load the patched_boot.img.tar I provided to the AP slot & flash. It will reboot with a Verification Failure, thus forcing you to format your device. When your device reboots, skip through Setup Wizard, dont link any Google or Samsung accts. On the home screen, use cmd terminal on your pc to install the MagiskManager.apk. Once sideload, you will see root access & more than likely a toast notification asking you to update Magisk.
Rashr (View attachment de.mkrtchyan.recoverytools.apk) works as a good substitute for Flashify. You just need to move the TWRP.img to the root of your sdcard (/emulated/0/sdcard) & flash it through the Recovery from Storage option. Reboot into TWRP &continue following the instructions I've posted

pauljulian said:
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
Click to expand...
Click to collapse
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...

pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
Click to expand...
Click to collapse
Lol The directions are on point. They're solid. You just have to pay attention ?

Here's the old fart with another question....
After flashing the stock files as instructed, I immediately hit the download mode as soon as the screen went black. Flashed the patched boot as instructed, and, as you stated, it would go immediately into recovery due to verification error.
I wiped the cache and hit factory reset, then reboot.
It's now sitting at the boot logo screen, and has been there for more than 1/2 hour.
Honest! I followed your instructions to the letter, and I recall first boot after rooting taking a while to come up into the system on other devices I've had, but I don't recall first boot taking anywhere this long.
I'm stumped.

pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
Click to expand...
Click to collapse
pauljulian said:
Here's the old fart with another question....
After following the instructions, yes, the phone went immediately into recovery mode, after flashing the error message you described.
I went ahead and did the factory reset, and told it to reboot... It's been sitting at the boot logo for about 25 minutes.
Should it take this long for first boot, after flashing the patched.boot.img.tar? I loaded the tar into the AP slot, as instructed. After flashing it, and the screen going to black, hit the download mode immediately... I flashed it, as said, at reboot, it went into recovery after a quick error message... I did factory reset, then rebooted normally.
I really have no idea... I'll let it keep sitting, to see if it finally boots, but this seems like a terribly long time that it's' at the bootscreen.
Click to expand...
Click to collapse
You seem to be rebooting into Recovery an awful lot. You shouldn't be booting into recovery mode at all when attempting to root. Recovery mode only needs entered during either process whenever you attempt to flash TWRP. Luckily for you, I dont have sh¡t to do tonight so I can help you until you get it right lol Shoot me an email at [email protected] & we can get started. I dont want to clutter up this feed with a revised how-to guide lol

Other Variants
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.

fsceo said:
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
Click to expand...
Click to collapse
I have since revised my instructions for root, starting that my guide is very device specific & you will have to tweak instructions in order to accommodate your version.
As far as TWRP goes, did you boot into TWRP twice? Once for the initial install to format the /data partition & the second to secure TWRP along with flashing the files? You need to do it simultaneously & in order otherwise it won't work

It's a happenin' thang!!!!
Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!
(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)

pauljulian said:
It's a happenin' thang!!!!
Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!
(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)
Click to expand...
Click to collapse
Not a problem buddy. Was fun & if you have any more questions, you have my contact info

fsceo said:
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
Click to expand...
Click to collapse
Sent you a pm, but having trouble rooting the same variant

[Howto][China] Flash TWRP, custom ROM and fix Google Pay

I realize that there's no howto guide yet on this forum. To a new Xiaomi device user, this can be daunting.
This is my guide on how I flashed my China Redmi K20 Pro and fixed Google Pay.
I am NOT responsible for whatever happens to your device as a result of following the below instructions.
At all times remember to download only the ones applicable for the China version i.e. recovery, ROM.
EXTRA:: New phone out of the box and waiting for bootloader unlock?
Install Google Play. Some of the download links in the thread are outdated so it is best to go to apkmirror.com to search, download and install them.
1) In order to flash any custom ROM, the bootloader must be unlocked
Xiaomi locks this by default on all devices. You must unlock it before proceeding to next steps, or you will brick your device. If it's bricked, try this or read the last section of this post.
i. Check Mi lock status from Developer Options. To enable Developer Options, go to Settings -> My Device -> All Specs -> tap on MIUI version. The Developer Options will appear in Settings -> Additional Settings eventually after about 7 taps.
The unlock time can take anywhere from 2 days to 30 days. You can check the timer in step 1vi. You no longer need to apply to Xiaomi to unlock the bootloader.
ii. Download the miflash_unlock_en_3.3.827.31. Extract the zip and run miflash_unlock.exe
iii. On the computer, sign in to the same mi account that's being bound to your phone.
iv. Send the phone to fastboot mode (power down, then power button + volume down button at the same time until the android picture appears).
v. Connect the phone to the computer by USB.
vi. On the computer, attempt to proceed to unlock. It will show you the number of hours left that you need to wait before the phone can be unlocked. Try again after that.
2) Bootloader unlocked
When you try to unlock the phone now (step 1iii - vi), the phone's screen will suddenly change while your mi unlock tool is "verifying" the phone. The tool will say error unlocking. This is normal. On the phone's screen, after progressing about 10% it will appear to reset. Your phone is now unlocked. You can verify the lock status by repeating step 1.
3) Install TWRP custom recovery
You need an Intel (AMD Ryzen seems to be an issue) Windows PC and ADB/fastboot installed. If you don't already, download from here.
There are several recoveries out there, but this one works for me. Download your choice into your PC. When you are done:
i. Open PowerShell (in File Explorer, shift + left click on an empty space) in that folder you downloaded into. If it's a zip, extract to get the .img file.
ii. Send phone into fastboot mode (power down, then vol down button + power button together).
iii. Connect phone to computer.
iv. Type
Code:
fastboot devices
into the PowerShell window. On your computer, you will be able to see that the phone is now in fastboot mode.
v. Type
Code:
fastboot flash recovery TWRP-3.3.1-0529-REDMI_K20PRO-CN-wzsx150.img
vi. When done, send your phone into TWRP recovery (vol up button + power button together).
Note: You must complete step vi or you will lose TWRP recovery because official ROMs restore to official recovery. If you missed this step, you must repeat from steps 3ii to go into TWRP.
4) Send ROM to your phone. If you have the ROM downloaded into your phone already, you may skip this step
Choose a ROM from the ROM section. For me, I use xiaomi.eu 9.8.22. Direct download link for the lazy.
Continuing in the same PowerShell window, type:
Code:
adb devices
adb push "D:\xiaomi.eu_multi_HMK20ProMI9TPro_9.8.22_v10-10.zip" /sdcard/
Replace D:\...... with the full path to the downloaded ROM. The file transfer may take some time. Wait for the PowerShell window to finish the executing command. It took 320 seconds for me.
5) Flash the ROM
For a clean ROM install, be sure to wipe the data, Dalvik and cache partitions. It is called a dirty flash if you wipe only Dalvik and cache.
i. On your phone while still in TWRP, go to Wipe -> Advanced Wipe -> select Dalvik / ART Cache and Data partitions. DON'T choose the FORMAT DATA or wipe any other partition.
ii. Select Install, then choose the ROM and swipe to start the flash. Alternatively, you can also run the same by continuing in the PowerShell window:
Code:
adb shell twrp install /sdcard/xiaomi.eu_multi_MI9_9.8.22_v10-10.zip
iii. When done, select "Reboot System". The first startup will take some time (maybe 3 minutes). You may disconnect the cable from the computer now.
6) Congrats! You are now using a custom ROM!
7) Set up Google Pay
Last tested and still working on 29 August 2019.
There's still one last obstacle. It seems that even though we can pass SafetyNet, Google Pay still doesn't want to work.
a) Make sure Google Pay app has already been installed and run once.
b) Install Magisk Manager
i. Open the App and then download the Magisk zip file.
ii. Send the phone into recovery. Power down the phone, then power button + vol up button at the same time.
iii. Select the Install menu, then select the Magisk zip file and slide to confirm flash. When done, select "Reboot to system".
c) Open Magisk App, then under Downloads, find and install Busybox for Android NDK and SQLite3 for ARM aarch64. Reboot phone.
d) Download the GPay SQLite Fix (more reading here)
Which version to use? It depends on how you want the fix:
Fix stays even if Magisk is uninstalled - use v1.5
To uninstall later, use Termux, type in the following:
Code:
su
chattr -i /data/data/com.google.android.gms/databases/dg.db
Grant superuser to the App when prompted.
Fix is uninstalled together when Magisk is uninstalled - use v1.7
e) Open Magisk app, go to Modules, press on the + button to custom select a module. Select file manager, then browse to the downloaded zip file. When done flashing, reboot phone. You can begin to setup contactless payment next.
If you used v1.5, you may uninstall Magisk now.
TIP: You need to change the NFC method if you want to use Google Pay.
Under Settings, go to Wireless & Networks -> More -> Secure element position -> Use HCE Wallet.
Help! It keeps rebooting into TWRP and never into my ROM!
I hope you never end up needing this. But if it did happen:
a) Download and install MIUI ROM Flashing Tool from MIUI.com. Guide is also available in the page.
b) Download a fastboot ROM from here example: China V10.3.8.0PFKCNXM Fastboot.
c) Unzip into a directory with no space in between:
Code:
D:\Redmi K20 Pro\fastboot - NOT OK
D:\Redmi_K20_Pro\fastboot - OK
d) Send phone to fastboot mode (power down, then vol down button + power button together).
e) Connect phone to computer
f) Open the MIUI ROM Flashing Tool. Browse to the directory where you had extracted the file e.g. D:\Redmi_K20_Pro\fastboot\raphael_images_V10.3.8.0.PFKCNXM_20190601.0000.00_9.0_cn
The program always defaults to "clean all and lock". This option will install the official ROM and lock the bootloader.
Make sure to change to "clean all" to keep the bootloader unlocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
g) Press "refresh" to confirm your phone is listed and then press "flash" when you are ready.
The flashing process will take several minutes. Do not disconnect the cable.
The program will show "success" under result.
Your phone will automatically boot into the official ROM.
You may then repeat step 3 Install TWRP custom recovery.

im having issue with twrp, i flashed it successfully and boot to the system(rom) but when i try to boot to recovery the stock recovery overwrites twrp, flashed 4x same result, how to fix this?

karltabby said:
im having issue with twrp, i flashed it successfully and boot to the system(rom) but when i try to boot to recovery the stock recovery overwrites twrp, flashed 4x same result, how to fix this?
Click to expand...
Click to collapse
Same here and flipping bought my phone from Ebay and its now locked to Mi account

Gooners4life said:
Same here and flipping bought my phone from Ebay and its now locked to Mi account
Click to expand...
Click to collapse
your have mi accnt of the previous owner

ionflux said:
I realize that there's no howto guide yet on this forum. To a new xiaomi device user this can be daunting.
This is my guide on how I flashed my Redmi K20 Pro and fixed gpay.
I am NOT responsible for whatever happens to your device as a result of following the below instructions.
EXTRA:: New phone out of the box and waiting for bootloader unlock?
Install Google Play. Some of the download links in the thread are outdated so it is best to go to apkmirror.com to search, download and install them.
1) In order to flash any custom ROM, the bootloader must be unlocked. Xiaomi locks this by default on all devices. You must unlock it before proceeding to next steps, or you will brick your device.
i. Check Mi lock status from Developer Options
To enable Developer Options, go to Settings -> My Device -> All Specs -> tap on MIUI version. The Developer Options will appear in Settings -> Additional Settings eventually after about 7 taps.
If this is locked, you will need to apply to Xiaomi to unlock. This can take anywhere from 2d to 30d. I think it is a random countdown timer set by Xiaomi. Mine took 7 days.
ii. You will be able to download their unlock tool (miflash_unlock_en_3.3.827.31) after applying. Extract the zip and run this tool (miflash_unlock.exe).
iii. On the computer, sign in to the same mi account that's used on your phone.
iv. Send the phone to fastboot mode (power down. then power button + volume down button at the same time until android picture appears)
v. Connect the phone to the computer by USB
vi. On the computer, attempt to proceed to unlock. It will show you the number of hours left you need to wait before the phone can be unlocked. Try again after that
2) Bootloader unlocked
When you try to unlock the phone now (step 1iii - vi), the phone's screen will suddenly change when your mi software is "verifying" the phone. The software will say error unlocking. This is normal. On the phone's screen, after progressing about 10% it will appear to reset. Your phone is now unlocked. You can verify by trying step 1.
3) Install TWRP custom recovery
There is a thread here that links to the custom TWRP made for Redmi K20 Pro. The last time I tried the download link had expired, so I used the archived one linked by the thread poster.
After extracting the zip, you will find a few important files:
These are essentially all you need to flash the custom recovery.
i. Open PowerShell in that folder you unzipped into. (In File Explorer, shift + left click on an empty space)
ii. Send phone into fastboot mode (power down, then power button + vol down button together)
iii. Connect phone to computer
iv. Type into the PowerShell window. You will be able to see that the phone is now in fastboot on your computer.
v. Type
vi. Type
vii. Your phone should boot into TWRP now.
4) Send ROM to your phone. If you have the ROM downloaded into your phone already, you may skip this step.
I downloaded the stable ROM 10.3.12.0. Direct link for the lazy
Continuing in the same PowerShell window, type
Replace D:\...... with the full path to the downloaded ROM. The file transfer may take some time. It took 454 seconds for me.
5) Flash the ROM.
Before flashing the ROM, clean the data and Dalvik cache partitions.
i. On your phone while it's still in TWRP, go to Wipe -> Advanced Wipe -> select Dalvik Cache and Data partitions. DON'T wipe any other partitions.
ii. Go back to home screen. Now go to Install menu, then select the ROM.zip in your /sdcard/ directory. Slide to confirm flash. When done, select "Reboot to system". The first startup will take some time (maybe 3 minutes).
6) You are using xiaomi.eu ROM (yay!)
Congrats! You are now using xiaomi.eu ROM!
7) Set up Google Pay
There's still one last obstacle. It seems that even though we can pass SafetyNet, Google Pay still doesn't want to work.
As of this post, I have tried this fix and it works.
Make sure Google Pay app has already been installed and run once.
a) Install Magisk Manager
i. Open the App and then download the Magisk zip file.
ii. Send the phone into recovery. Power down the phone, then power button + vol up button at the same time.
iii. Select Install menu, then select the Magisk zip file and slide to confirm flash. When done, select "Reboot to system".
b) Open Magisk app, then under Downloads, find and install busybox. Reboot phone.
c) Download the gpay sqlite fix (more reading here)
d) Open Magisk app, go to Modules, press on the + button to custom select a module. Select file manager, then browse to the downloaded zip file. When done flashing, reboot phone.
OPTIONAL: If you don't want Magisk, you can uninstall it now. After the phone reboots, you can begin to setup contactless payment.
If you want to keep Magisk, then you should hide Magisk Manager and all other apps that check for rooting i.e. Google Pay and other banking apps.
TIP: You need to change the NFC method if you want to use Google Pay
Under Settings, go to Wireless & Networks -> More -> Secure element position -> Use HCE Wallet.
Click to expand...
Click to collapse
You no longer need to apply for unlock permissions. This has been the case for a few months. I've no idea why Xiaomi don't take down the unlock request page.
---------- Post added at 03:04 PM ---------- Previous post was at 03:02 PM ----------
karltabby said:
im having issue with twrp, i flashed it successfully and boot to the system(rom) but when i try to boot to recovery the stock recovery overwrites twrp, flashed 4x same result, how to fix this?
Click to expand...
Click to collapse
MIUI will restore stock recovery on reboot. After flashing TWRP immediately boot into TWRP and install Magisk. This will prevent stock MIUI from restoring stock recovery.

karltabby said:
your have mi accnt of the previous owner
Click to expand...
Click to collapse
The phone was sealed when I got it and boot loader was unlocked. On a Paypal dispute.

Robbo.5000 said:
You no longer need to apply for unlock permissions. This has been the case for a few months. I've no idea why Xiaomi don't take down the unlock request page.
Click to expand...
Click to collapse
can you share the link to this? i wouldn't dare to try flashing a custom ROM without unlocking

karltabby said:
im having issue with twrp, i flashed it successfully and boot to the system(rom) but when i try to boot to recovery the stock recovery overwrites twrp, flashed 4x same result, how to fix this?
Click to expand...
Click to collapse
you cannot boot into system after flashing twrp. on the official ROM they will restore to the official recovery. you need to flash a custom ROM like xiaomi.eu while in TWRP, then boot into system.

Gooners4life said:
Same here and flipping bought my phone from Ebay and its now locked to Mi account
Click to expand...
Click to collapse
same how? could you get into TWRP? you need to sign out of the mi account

ionflux said:
you cannot boot into system after flashing twrp. on the official ROM they will restore to the official recovery. you need to flash a custom ROM like xiaomi.eu while in TWRP, then boot into system.
Click to expand...
Click to collapse
If i flash eu rom while on twrp after reboot twrp will stay as default recovery? Someone tol me to flash "descript" i have no idea what it is

ionflux said:
can you share the link to this? i wouldn't dare to try flashing a custom ROM without unlocking
Click to expand...
Click to collapse
You still need to unlock the bootloader and you will most likely need to wait to unlock it, probably 7 days. But you no longer need to apply for unlock permissions for your Mi account.
There are still a lot of Xiaomi bootloader unlock How-to articles being written that tell you to go to the Xiaomi bootloader unlock permission webpage and apply for unlock permissions for your Mi account. This is not necessary anymore.
---------- Post added at 06:06 PM ---------- Previous post was at 06:01 PM ----------
ionflux said:
you cannot boot into system after flashing twrp. on the official ROM they will restore to the official recovery. you need to flash a custom ROM like xiaomi.eu while in TWRP, then boot into system.
Click to expand...
Click to collapse
If you want to keep an official ROM, then you need to install Magisk.
Though if you are not installing a custom ROM or you're not installing Magisk, then I'm not sure why you'd be installing TWRP.

I am having this slight issue of restarting my device of freezing at the redmi logo for awhile and the phone just shuts down, if i try to power the phone for a couple of times then it will bbot up, can you help me out how to solve this? Im still on stock rom/recovery
---------- Post added at 11:53 PM ---------- Previous post was at 11:28 PM ----------
am having this slight issue of restarting my device of freezing at the redmi logo for awhile and the phone just shuts down, if i try to power the phone for a couple of times then it will bbot up, can you help me out how to solve this? Im still on stock rom/recovery, this problem started after i flashe twrp a couple of times i am unlocked btw

Robbo.5000 said:
You still need to unlock the bootloader and you will most likely need to wait to unlock it, probably 7 days. But you no longer need to apply for unlock permissions for your Mi account.
There are still a lot of Xiaomi bootloader unlock How-to articles being written that tell you to go to the Xiaomi bootloader unlock permission webpage and apply for unlock permissions for your Mi account. This is not necessary anymore.
Click to expand...
Click to collapse
How do you find the official link to download the unlock tool or trigger the countdown if you don't do the apply?
Robbo.5000 said:
If you want to keep an official ROM, then you need to install Magisk.
Though if you are not installing a custom ROM or you're not installing Magisk, then I'm not sure why you'd be installing TWRP.
Click to expand...
Click to collapse
I'm quite certain this thread is about how to flash a custom ROM and I was explaining why the user was having trouble entering TWRP and kept returning to the official recovery. Perhaps you want to clarify why you're talking about magisk on an official ROM?

karltabby said:
If i flash eu rom while on twrp after reboot twrp will stay as default recovery? Someone tol me to flash "descript" i have no idea what it is
Click to expand...
Click to collapse
Yes, that's how it worked for me. I am not aware of a "descript".
karltabby said:
I am having this slight issue of restarting my device of freezing at the redmi logo for awhile and the phone just shuts down, if i try to power the phone for a couple of times then it will bbot up, can you help me out how to solve this? Im still on stock rom/recovery
---------- Post added at 11:53 PM ---------- Previous post was at 11:28 PM ----------
am having this slight issue of restarting my device of freezing at the redmi logo for awhile and the phone just shuts down, if i try to power the phone for a couple of times then it will bbot up, can you help me out how to solve this? Im still on stock rom/recovery, this problem started after i flashe twrp a couple of times i am unlocked btw
Click to expand...
Click to collapse
After you flash TWRP and the phone enters into TWRP, can you install a custom ROM?

I thinki can i just did not flash any custom rom atm, im scared that i might brick my device since im experiencing this freezing at the redmi logo

ionflux said:
How do you find the official link to download the unlock tool or trigger the countdown if you don't do the apply?
I'm quite certain this thread is about how to flash a custom ROM and I was explaining why the user was having trouble entering TWRP and kept returning to the official recovery. Perhaps you want to explain clearer why you're talking about magisk on an official ROM?
Click to expand...
Click to collapse
If you want to be safe and download the unlock tool from the Xiaomi site, then yes you are forced to fill the request for unlock permissions before you can access the download. But there are plenty of reliable sources where you can download the unlock tool.
When you create a Mi account it now has unlock permissions automatically.
The countdown will start when you 'Add Device' in the Mi Unlock Status screen within the Developer Options settings. In the last 3 months I've unlocked 2 Xiaomi phones and I've never applied for unlock permissions.
The user with the problem of losing TWRP did not mention whether they want to install a custom ROM or stay on stock. They may have been using your guide only for the TWRP installation. I was giving the information, should they wish to stay on stock.

Hi @ionflux. I tried this and still got an error from gpay saying device has been rooted or altered in some way. I am on stable china rom with magisk and unlocked bootloader. When installing the sqlite fix I get a message in magisk saying sqlite3 binary is not found

karltabby said:
I thinki can i just did not flash any custom rom atm, im scared that i might brick my device since im experiencing this freezing at the redmi logo
Click to expand...
Click to collapse
If you get in to trouble with your phone, then you can restore your phone by installing an official fastboot ROM. If you have bricked your phone, but can boot to the fastboot screen and have a unlocked bootloader, then you can restore the phone this way.
Download the latest official fastboot ROM from here.
https://forum.xda-developers.com/k2...irmware-10-3-8-0-9-6-13-t3939647/post79726515
Then follow this guide to flash the ROM via fastboot.
http://en.miui.com/a-234.html
In step 5 you need to make sure the option at the bottom is 'Clean All', otherwise you will lock the bootloader again.

Is there a situation that flashing twrp acouple times will mess up the device? Ive just experience this freezing after i flash twrp like 7x,do you think i can just dive in and flash eu rom? My bl is unlocked so that makes my devices restorable?

karltabby said:
Is there a situation that flashing twrp acouple times will mess up the device? Ive just experience this freezing after i flash twrp like 7x,do you think i can just dive in and flash eu rom? My bl is unlocked so that makes my devices restorable?
Click to expand...
Click to collapse
Normally, installing TWRP shouldn't cause issues, it's irrelevant how many times you try and install TWRP. I would say go ahead and flash an eu ROM. If you still have freezing issues when booting, then restore the phone and see if that fixes it. If so then start again with the TWRP and eu ROM install.

[ROM][9.0][UN-OFFICIAL][ravel][16.01.2020] crDroid v5.11

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk for Treble for root (after first boot) - (Download from here)
First time installation:
Instructions :
* First of all you need to flash this twrp (I recommend) if not this you can also use other available twrp's.
* Boot into twrp and Format data and wipe system/data/cache/dalvik.
* Flash the rom zip
* After installing the rom , flash the gapps i am going to add into the downloads section.
* If you want to root, flash Magisk
* Reboot to System.
What working?
* camera
* Bluetooth
* wifi
* hotspot
* fingerprint
* livedisplay
* ambient display
* most everything work!
Sources:
ROM: https://github.com/crdroidandroid
Kernel: -foe.kernel
Device-Tree: -kirin970
Download:
ROM AFH
Known issues:
*none
Visit official website @ crDroid.net
crDroid ravel Telegram
crDroid Community Telegram
Donate to help our team pay server costs

Changelog...
*09-01-2020
Initial release
*10-01-2020
Fix major bug
Fix camera / flashlight
Fix ambient display
Fix deep.sleep
Fix wakelock
Fix battery 5000mah
Fix superquick charge ratio
*16-01-2020
Fix deep sleep
Fix aod brightness scale =3
Fix aptouch-deamon

Downloading....

i have tons of apps on my honor note 10 but i would like to try this if anybody can tell how's the sound quality compared to stock rom.
also does the stereo works correctly when the phone is in landscape to the right? tried some open kirin roms and it was awful. stereo channels were inverted if you rotate phone to the right, and you couldn't hear footsteps in pubg.

Do you need to have EMUI 9 to flash? Really looking forward to testing this...

ForgottenSolstace said:
Do you need to have EMUI 9 to flash? Really looking forward to testing this...
Click to expand...
Click to collapse
it needs emui 8

Error installing zip file. This package is for device: ravel; this device is kirin970
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
Probably should edit
Code:
META-INF\com\google\android\updater-script
---------- Post added at 07:02 PM ---------- Previous post was at 06:53 PM ----------
Got this now that I fixed the updater-script:
assert failed: run_program("/sbin/sh", "/system/bin/releasetools.kirin970.sh") == 0
Updater process ended with ERROR: 7
Error installing zip file "/external_sd/...
Click to expand...
Click to collapse
---------- Post added at 07:14 PM ---------- Previous post was at 07:02 PM ----------
Update: it doesn't install correctly, even when I change the device names in updater-script. The device doesn't boot, and skips straight to e-recovery. I also think recovery (TWRP) got overwritten with the flash via the boot img rewrite, so I have to revert to stock to try again.

are you on emui 8 or 9?

dvijetrecine said:
are you on emui 8 or 9?
Click to expand...
Click to collapse
EMUI 8

which twrp you used?

dvijetrecine said:
which twrp you used?
Click to expand...
Click to collapse
This one: https://androidfilehost.com/?fid=11410932744536987360
---------- Post added at 03:38 AM ---------- Previous post was at 03:27 AM ----------
Currently, my phone hangs on the TWRP logo (your TWRP, even when I install your version . I had gotten the old version of TWRP to run upon reverting to stock (stock still wouldn't boot, though, even after reverting via EMUI recovery), but /system would only get mounted read-only. So kind of stuck here. I also tried fastboot flash system on a number of images with no success in booting. I recall I had to flash a zip to disable encryption of /system. Is that still the case, and if so where do I find that zip?

ForgottenSolstace said:
This one: https://androidfilehost.com/?fid=11410932744536987360
---------- Post added at 03:38 AM ---------- Previous post was at 03:27 AM ----------
Currently, my phone hangs on the TWRP logo (your TWRP, even when I install your version . I had gotten the old version of TWRP to run upon reverting to stock (stock still wouldn't boot, though, even after reverting via EMUI recovery), but /system would only get mounted read-only. So kind of stuck here. I also tried fastboot flash system on a number of images with no success in booting. I recall I had to flash a zip to disable encryption of /system. Is that still the case, and if so where do I find that zip?
Click to expand...
Click to collapse
it's not mine. i just have some experience with flashing roms on this phone

okay, so i managed to install the rom successfully.
it was a bit of a trial and error but i made it.
so, you need to be on emui 8. if you're on emui 9, here is the link on how to downgrade: https://huaweiadvices.com/downgrade-huawei-android-pie-emui-9-0-to-oreo-emui-8/
after you downgraded your phone successfully, you can proceed to the next step.
next step is installing the right recovery. first, you install this one: https://androidfilehost.com/?fid=11410932744536987360
then you flash rom and gapps. boot into OS. if you did everything right, it should boot.
now, with the recovery we installed, there will be error with read only system and you won't be able to use your phone right.
so, next step is to install this recovery: https://androidfilehost.com/?fid=4349826312261697516
now the order of installing stuff is very important. don't install second recovery before doing all the steps above.
after successfull installation of second recovery, you will need to wipe data. not just factory reset but full wipe.
when the wiping is done, you can now install rom again, gapps and magisk. then you install this zip: https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip
by the name of the zip you could figure out that it is about disabling force encryption and all that good stuff.
and you are done. now everything should work properly.
problems so far: when you rotate phone to the right, stereo doesn't follow orientation so it's reversed and you can't play fps games. also, overall sound quality is bad

dvijetrecine said:
okay, so i managed to install the rom successfully.
it was a bit of a trial and error but i made it.
so, you need to be on emui 8. if you're on emui 9, here is the link on how to downgrade: https://huaweiadvices.com/downgrade-huawei-android-pie-emui-9-0-to-oreo-emui-8/
after you downgraded your phone successfully, you can proceed to the next step.
next step is installing the right recovery. first, you install this one: https://androidfilehost.com/?fid=11410932744536987360
then you flash rom and gapps. boot into OS. if you did everything right, it should boot.
now, with the recovery we installed, there will be error with read only system and you won't be able to use your phone right.
so, next step is to install this recovery: https://androidfilehost.com/?fid=4349826312261697516
now the order of installing stuff is very important. don't install second recovery before doing all the steps above.
after successfull installation of second recovery, you will need to wipe data. not just factory reset but full wipe.
when the wiping is done, you can now install rom again, gapps and magisk. then you install this zip: https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip
by the name of the zip you could figure out that it is about disabling force encryption and all that good stuff.
and you are done. now everything should work properly.
problems so far: when you rotate phone to the right, stereo doesn't follow orientation so it's reversed and you can't play fps games. also, overall sound quality is bad
Click to expand...
Click to collapse
Thanks for posting this. So in my situation, with a read-only /system on EMUI 8, and a TWRP that hangs on the logo, do I need to revert to stock via Hi-suite? I'm in the process of trying dload method to get to EMUI 9 and try some other ROMs at the moment

you just need to flash stock recovery and do a factory reset or full wipe. that should do it

dvijetrecine said:
you just need to flash stock recovery and do a factory reset or full wipe. that should do it
Click to expand...
Click to collapse
I tried exactly this, but TWRP still hangs on the TWRP logo (both versions). I had locked, stock EMUI 9 running from the dload method, so I did fastboot oem unlock with my bootloader code, which worked. Then a forced factory reset, and without first booting, I flashed twrp. No luck.
Any suggestions? I may also need stock recovery for EMUI 9 if you know where to find that...

you should let it boot. install emui with dload, let it boot and then try flashing twrp. it might hang a bit, but it will work. sometimes a reboot is needed

I got this ROM to install manually via fastboot flash system once I upgraded to EMUI 9. The problem is, now I can't even get to TWRP when I fastboot flash recovery_ramdisk and then press the volume keys (it just goes to EMUI now). I'll continue experimenting
---------- Post added at 05:33 PM ---------- Previous post was at 05:17 PM ----------
Update: the phone was in a transitory state, where running the dload method had failed, hence /system was unencrypted and booting to recovery_ramdisk would fail. I did volume+up on boot to load EMUI recovery, tried a factory reset, and now hanging again at TWRP. Will try a factory reset with legacy EMUI recovery and repeat...

when on emui 9, it's pretty hard to get into twrp. you have to hold on vol up and power when booting to get into twrp. and also, those open kirin roms are no better than this one. this one even feels like the best
---------- Post added at 01:41 AM ---------- Previous post was at 01:36 AM ----------
ForgottenSolstace said:
I got this ROM to install manually via fastboot flash system once I upgraded to EMUI 9. The problem is, now I can't even get to TWRP when I fastboot flash recovery_ramdisk and then press the volume keys (it just goes to EMUI now). I'll continue experimenting
---------- Post added at 05:33 PM ---------- Previous post was at 05:17 PM ----------
Update: the phone was in a transitory state, where running the dload method had failed, hence /system was unencrypted and booting to recovery_ramdisk would fail. I did volume+up on boot to load EMUI recovery, tried a factory reset, and now hanging again at TWRP. Will try a factory reset with legacy EMUI recovery and repeat...
Click to expand...
Click to collapse
just be careful. huawei phones are pretty finicky and love to brick when you interrupt them in upgrading, downgrading or installing anything. it's all good when you go to custom roms, but those often lack features. i had high hopes for this rom but i just can't get over the fact how bad the sound quality is compared to the stock rom. i'm returnig back to emui 8 and probably will sell this phone in some time. thinking about buying rog phone 2, but i love the big screen of the honor note 10

dvijetrecine said:
when on emui 9, it's pretty hard to get into twrp. you have to hold on vol up and power when booting to get into twrp. and also, those open kirin roms are no better than this one. this one even feels like the best
---------- Post added at 01:41 AM ---------- Previous post was at 01:36 AM ----------
just be careful. huawei phones are pretty finicky and love to brick when you interrupt them in upgrading, downgrading or installing anything. it's all good when you go to custom roms, but those often lack features. i had high hopes for this rom but i just can't get over the fact how bad the sound quality is compared to the stock rom. i'm returnig back to emui 8 and probably will sell this phone in some time. thinking about buying rog phone 2, but i love the big screen of the honor note 10
Click to expand...
Click to collapse
Yes, indeed: you need to press and HOLD the volume up rocker AND hold the power button for a real delay. You might expect the phone to turn off again, but it doesn't. You boot to TWRP.
Now, I have the first TWRP installed, but it still hangs on the TWRP logo (EMUI 9). Not sure if I missed a step, but here's what I did:
dload method to EMUI 9 latest
boot to download mode; fastboot oem unlock
wait for factory reset
let the phone reboot. Turn it off to download mode again
flast twrp to recovery_ramdisk
boot to recovery with aforementioned method
Hopefully, I missed something down the line, because I really need root at the very least. Unless someone can point me to the stock boot.img file, I don't see how I'll get root on this device if TWRP won't boot.

Better Mobile App

welcome