Related
Note:- Credits To this guide goes to {Diablosss}
GUIDE FOR UNLOCKING BOOTLOADER OF MEIZU PRO 7
(Sorry for the inconvenience, but there are some issues in posting pictures. Therefore requesting you to please check the attached files for images)
This guide can also work with many other Meizu devices. Checked on 15, 16 all options (s, t, x) and on Pro7I post the archive and instructions in pictures.
Step 1: Download. Unpack. Run meizublunlocker.exe
meizublunlocker:-https://drive.google.com/open?id=1yEm_vZo4rsqEtii279AU6l1mBajiSPQ2
See Image 1 in Attachments.
Step 2:-We connect the phone to the computer in fastboot mode (hold down the Vol. Down and power buttons), click refresh. The program must identify the device.
See Image 2 in Attachments.
Step 3ress CheckBL to check bootloader status.
See Image 3 in Attachments.
Step 4:-Click the Create Request button. This will create a file with the end of req.dat in the folder with this program
We send it to the e-mail [email protected] and wait for the response file to unlock the bootloader.
(This takes usually 1 week to receive the unlocked file, but you can donate to get the file within 3 hours)
See Image 4 in Attachments.
Step 5:- After we received the unlock file with the end of res.dat, click UnlockBL and select the resulting file.
See Image 5 in Attachments.
If the file is correct then get this answer
See Image 6 in Attachments.
That's It. We successfully Unlocked the Bootloader.
Now the next thing is to install the TWRP in our Device. ( Further credits goes to{ sergpolov} )
Step 1: Download and install "adb_run"
adb run:-https://drive.google.com/open?id=1y4wdL53-P7mybKsj5XeimHRoMSpokMkQ
Step 2:- Download the required Files.
Stock Recovery Pro 7:-https://drive.google.com/open?id=1e2tRdqLi5jsT8J854RMcIA-jvZyR7xhT
Twrp Pro 7:-https://drive.google.com/open?id=1uYOT9HGractYuoJvRidgAgh8IBLhzFtu
Step 3:-We load the phone into fastboot mode, flash through the fastboot the recovery you need.
Launch the application shortcut
Step 4:-Click "3" - go to fastboot mode
See Image 7 in Attachments.
Step 5:-Click "3" - recovery
See Image 8 in Attachments.
Step 6:-Here we select the recovery file: - in the window that opens, we throw the file itself and close the window with the file and press any button.
See Image 9 in Attachments.
The process has begun.
See Image 10 in Attachments.
Step 7:- Choose "Y" and "Enter"
See Image 11 in Attachments.
The recovery firmware process is over!
Next Few Steps are Extremely Important , so follow with caution!Step 8:-Reboot into Recovery Mode(hold down "Power" and hold, as soon as the screen goes blank, hold down the second button "Volume +" - hold it until vibration and release "Power", and after it release the button "Volume +")
Step 9:-To disable encryption of the "Data" section (who installs TWRP), we immediately flash the zip archive - tool-root_unlock-Testing-Pro7.zip
(disables encryption of the "Data" section, disables Boot and Recovery checks, installs Magisk and disables system root) and reboot into the system.)
tool-root_unlock-Testing-Pro7.zip:-https://drive.google.com/open?id=1a3Gyyuoo2Jv3EN7EWPwj389tXorSwkxT
Attention ! When installing custom recovery (TWRP) on your device, for the full TWRP functionality, you should format the internal memory (Data section) of the device using TWRP itself, since the "Data" section on Meizu smartphones is encrypted, I highly recommend it before installing custom recovery , on creating backups using the internal Flyme firmware (after creating the backup, it is located in the "backup" folder of the internal drive), as well as copying all the necessary data from the phone’s internal memory to the computer!
NOTE:-No One shall be responsible to any damage ocurring to your device
Doubts and queries are welcomed .
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
XRed_CubeX said:
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
Click to expand...
Click to collapse
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
adityadhage said:
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
Click to expand...
Click to collapse
But then for other MTKs like M5C it will never work?
XRed_CubeX said:
But then for other MTKs like M5C it will never work?
Click to expand...
Click to collapse
i know you have already tried this method with your device and it didnt worked. I am not sure that m5c will get another method in future or not. Bcoz we also got lucky with pro 7 that it got successful by the help of guide ported from Meizu 16TH a Qualcomm device.
its now per donation only.
spiramedia said:
its now per donation only.
Click to expand...
Click to collapse
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
cris2d2 said:
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
Click to expand...
Click to collapse
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
adityadhage said:
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
Click to expand...
Click to collapse
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
cris2d2 said:
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
Click to expand...
Click to collapse
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
adityadhage said:
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
Click to expand...
Click to collapse
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
cris2d2 said:
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
Click to expand...
Click to collapse
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
adityadhage said:
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
Click to expand...
Click to collapse
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
cris2d2 said:
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
Click to expand...
Click to collapse
basically you are right
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
deathbreath2010 said:
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
Click to expand...
Click to collapse
this guide is now updated and guranteed to work with x30 also
follow this
https://www.youtube.com/watch?v=Rnuf-uNBnYA&t=319s
adityadhage said:
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
Click to expand...
Click to collapse
its not 5$ its now 15$ its too mutch
sajib_ngage said:
its not 5$ its now 15$ its too mutch
Click to expand...
Click to collapse
try asking them for lower price, they will help u i think. Tell them its for pro 7 bcoz pro 7 requires less work. try ur luck
Currently I am on Evolution X latest build and today my camera was opened but it won't close.
Now since my phone is under warranty I want to claim it.
How do I revert back to MIUI, unroot the device and remove TWRP. Please help me.
Regards
flash fastboot rom and u will revert back to stock miui unrooted.
^^ Do I need to download MIUI package or simply that command alone will work?
If yes please guide to resources I have Indian variant of K20 Pro.
shashpant said:
^^ Do I need to download MIUI package or simply that command alone will work?
If yes please guide to resources I have Indian variant of K20 Pro.
Click to expand...
Click to collapse
"Flash fastboot rom" was a sentence/direction/hint what you have to do, not a (fastboot) command
I think there is a detailed guide in the Guides section. Otherwise, you need to google about MiFlash, install to the PC, read how to use, find on xiaomifirmwareupdater an appropriate tgz/fastboot rom for your device.
I'm not on Pro, not on Indian, cannot guide you more than as above, where to start googling/reading/learning
^^ Thanks for the clarification.
I downloaded latest rom from https://xiaomifirmwareupdater.com/miui/raphaelin/ I tried both recovery and fastboot version.
I flashed the rom using twrp (is that right?) but nothing happens and devices reboots itsefl into recovery. What am I doing wrong?
I am also unable to locate the guide to revert back. Plus I am on Linux so that windows too might now work.
Edit - The guides mention flashing magisk. But I don't want to root as I have to claim warranty. What do I do now?
Edit 2 - I flashed magisk root but still not able to boot. It reverts back to recovery.
shashpant said:
^^ Thanks for the clarification.
I downloaded latest rom from https://xiaomifirmwareupdater.com/miui/raphaelin/ I tried both recovery and fastboot version.
I flashed the rom using twrp (is that right?) but nothing happens and devices reboots itsefl into recovery. What am I doing wrong?
I am also unable to locate the guide to revert back. Plus I am on Linux so that windows too might now work.
Edit - The guides mention flashing magisk. But I don't want to root as I have to claim warranty. What do I do now?
Click to expand...
Click to collapse
I wrote you to google about and to use Mi Flash, not TWRP.
Besides, I don't know if they have Linux version.
How to Flash Xiaomi Firmware using MIUI Fastboot and Recovery ROM
Ever since the dawn of affordable smartphones in countries like India and China, the demand for more has increased. The consumers now, more than ever, are
www.getdroidtips.com
How to Install MIUI Fastboot ROM - android file box
For some reasons you may want to completely re-install Android OS running on your Xiaomi phone either Mi series or Redmi series. While updating the ROM is simply a one-tap action through...
androidfilebox.com
How-to use Xiaomi Flash Tool to flash or install Firmware
Step-by-Step guidelines to use Xiaomi Flash Tool to Flash Stock Firmware on Xiaomi Smartphone and Tablets.
xiaomiflashtool.com
etc - google for more
shashpant said:
I am also unable to locate the guide to revert back. Plus I am on Linux so that windows too might now work.
Click to expand...
Click to collapse
Actually, consult these guides for Linux:
How to flash MIUI Fastboot ROM from Linux
How to flash MIUI Fastboot ROM from Linux. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
[GUIDE][Linux] Flashing Xiaomi .tgz
Hello everyone, I recently had to flash a stock firmware file from Xiaomi (.tgz) and being primarily a Linux user I was quite disappointed by the fact that the company only provides a flashing tool for Windows. Either way, I booted into Windows...
forum.xda-developers.com
[OTA][FASTBOOT][ROM] Official Stock Fastboot image (V10.0.10.0.PDHMIXM, Android P)
Attention: To be able to flash, the bootloader needs to be unlocked (https://en.miui.com/unlock/). Please be warned though: Xiaomi changed something in the method of unlocking the device from May 2018 security update onwards. Now all data will be...
forum.xda-developers.com
Can someone link me to a full rooting guide for the sweetin variant? It'll be a big help!
Thanks!
a safe haven said:
Can someone link me to a full rooting guide for the sweetin variant? It'll be a big help!
Thanks!
Click to expand...
Click to collapse
Hi
Rooting the sweetin is pretty straight forward like most Mi phones. I am sure you can google it and iron it out.
But just FYI, below are the steps -
Link Mi Account for unlocking in Developer options.
Unlock Bootloader using Mi Unlock Tool (lengthy, considering 15 days waiting period)
Flash latest TWRP
Install Magisk via TWRP.
Please let me know if you need further details
nkrishna said:
Hi
Rooting the sweetin is pretty straight forward like most Mi phones. I am sure you can google it and iron it out.
But just FYI, below are the steps -
Link Mi Account for unlocking in Developer options.
Unlock Bootloader using Mi Unlock Tool (lengthy, considering 15 days waiting period)
Flash latest TWRP
Install Magisk via TWRP.
Please let me know if you need further details
Click to expand...
Click to collapse
I thought TWRP wasnt available/fully functional yet.
Do you have a link to that?
a safe haven said:
I thought TWRP wasnt available/fully functional yet.
Do you have a link to that?
Click to expand...
Click to collapse
It is in a very good shape now that decryption is enabled, although there are a few bugs like sideload. I expect this will be cleared very soon though. You can find more info on that here -
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
And download the TWRP here-
Downloads for : Xiaomi Redmi Note 10 Pro | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
a safe haven said:
Can someone link me to a full rooting guide for the sweetin variant? It'll be a big help!
Thanks!
Click to expand...
Click to collapse
-Enable developer options
-Apply Mi for unlock
insert the active sim
register mi account using that sim
bind the number, account and phone in developer options for unlock
(you can take away sim, if you are using on another phone)
-Check using mi unlock tool and apply for it
you will get a time to wait of 168 hours(7 days)
-Unlock after the wait period
(device will be erased)
go enable developer options again
enable USB debugging
-TWRP
get the TWRP in this forum, which is very good with decryption and USB OTG/SD card access
use adb, fastboot commands on terminal and flash TWRP as your recovery and boot
(If you only want to boot without flash, you can do that too)
-Root with Magisk
with TWRP, you can flash magisk
(latest magisk will be available as apk, so change to zip and flash)
boot to ROM after flash success
-Update magisk
get magisk canary from magisk github(availabl as debug apk) and install that to update already flashed magisk(can use regular apk also which the magisk by itself will do)
canary magisk has the codes to read safety net pass correctly
-safety net check
enable magisk hide, and hide google play services, gpay or any other app you want to
flash magiskhide props config within magisk
check safety net from magisk(if canary) or by safet net test app or using gpay or any banking app
I assume, finer steps and details you already know.
nkrishna said:
It is in a very good shape now that decryption is enabled, although there are a few bugs like sideload. I expect this will be cleared very soon though. You can find more info on that here -
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
And download the TWRP here-
Downloads for : Xiaomi Redmi Note 10 Pro | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Click to expand...
Click to collapse
Thank you, appreciate it.
rathisarov said:
-Enable developer options
-Apply Mi for unlock
insert the active sim
register mi account using that sim
bind the number, account and phone in developer options for unlock
(you can take away sim, if you are using on another phone)
-Check using mi unlock tool and apply for it
you will get a time to wait of 168 hours(7 days)
-Unlock after the wait period
(device will be erased)
go enable developer options again
enable USB debugging
-TWRP
get the TWRP in this forum, which is very good with decryption and USB OTG/SD card access
use adb, fastboot commands on terminal and flash TWRP as your recovery and boot
(If you only want to boot without flash, you can do that too)
-Root with Magisk
with TWRP, you can flash magisk
(latest magisk will be available as apk, so change to zip and flash)
boot to ROM after flash success
-Update magisk
get magisk canary from magisk github(availabl as debug apk) and install that to update already flashed magisk(can use regular apk also which the magisk by itself will do)
canary magisk has the codes to read safety net pass correctly
-safety net check
enable magisk hide, and hide google play services, gpay or any other app you want to
flash magiskhide props config within magisk
check safety net from magisk(if canary) or by safet net test app or using gpay or any banking app
I assume, finer steps and details you already know.
Click to expand...
Click to collapse
Thanks for the full guide, this really helps a lot.
Also, how do you guys install OTA with twrp?
Will I be able to install OTA's using twrp?
a safe haven said:
Thank you, appreciate it.
Thanks for the full guide, this really helps a lot.
Also, how do you guys install OTA with twrp?
Will I be able to install OTA's using twrp?
Click to expand...
Click to collapse
depends on the rom, i believe
can be as simple as download update and flash(it goes through TWRP) or, you might have to download full ROM package, flash that, and then again flash magisk or even TWRP(esp if it gets replaced) sometimes
it varies
rathisarov said:
depends on the rom, i believe
can be as simple as download update and flash(it goes through TWRP) or, you might have to download full ROM package, flash that, and then again flash magisk or even TWRP(esp if it gets replaced) sometimes
it varies
Click to expand...
Click to collapse
Did you install the latest 12.0.10 update then?
I assume you have a rooted note 10 pro max, what was your procedure?
a safe haven said:
Did you install the latest 12.0.10 update then?
I assume you have a rooted note 10 pro max, what was your procedure?
Click to expand...
Click to collapse
note 10 pro indian version
updated to the latest stable and then rooted.
(but I don't think firmware matters; I mean it is the same procedure)
rathisarov said:
note 10 pro indian version
updated to the latest stable and then rooted.
(but I don't think firmware matters; I mean it is the same procedure)
Click to expand...
Click to collapse
Sorry for not clearing it up, I meant by Xiaomi OTA's.
Do tell me what your procedure is gonna be when the next OTA comes out since you're on TWRP.
It'll be a big help since I don't want to use custom ROMs at the moment.
a safe haven said:
Sorry for not clearing it up, I meant by Xiaomi OTA's.
Do tell me what your procedure is gonna be when the next OTA comes out since you're on TWRP.
It'll be a big help since I don't want to use custom ROMs at the moment.
Click to expand...
Click to collapse
unfortunately, always, I move out of MIUI to AOSP based minimalistic ROMs(I like that way)
I might not be of help to you.
But, earlier, it was like this-
once bootloader unlocked, we won't get incremental MIUI updates
so, got to download full ROM, update
and after update, every time recovery will be replaced
so need to re flash TWRP, re flash Magisk
(i don't think anything much changed, still not very sure)
rathisarov said:
unfortunately, always, I move out of MIUI to AOSP based minimalistic ROMs(I like that way)
I might not be of help to you.
But, earlier, it was like this-
once bootloader unlocked, we won't get incremental MIUI updates
so, got to download full ROM, update
and after update, every time recovery will be replaced
so need to re flash TWRP, re flash Magisk
(i don't think anything much changed, still not very sure)
Click to expand...
Click to collapse
I see, I appreciate your input regardless.
Is it usually a dirty flash? or does it wipe out everything as in factory reset after installing the update?
Also, what custom rom have you been using?
Is it stable? Are all the cameras fully functional while using the aosp based rom?
I haven't unfortunately found a stable gcam that fully works with the note 10 pro yet, therefore I am being hesitant to switch to custom ROMs for now, otherwise, I would've flashed an AOSP rom in a heartbeat, I hate MIUI.
rathisarov said:
unfortunately, always, I move out of MIUI to AOSP based minimalistic ROMs(I like that way)
I might not be of help to you.
But, earlier, it was like this-
once bootloader unlocked, we won't get incremental MIUI updates
so, got to download full ROM, update
and after update, every time recovery will be replaced
so need to re flash TWRP, re flash Magisk
(i don't think anything much changed, still not very sure)
Click to expand...
Click to collapse
Hi guys ! I have my k20 pro from 2019 and I never had access to any apps like netflix or mcdonals cause of some insecure software idrk to be honest. Anyways I want to use nfc and I actually can't . Did some research and just found out about eu rom might work but I'm new to this type of things and I need some help to flash the new rom and where to get it from .
These are some phone specs :
I have raphaelin ( aida64 )
K20pro 64 gb rom and 6gb ram
MIUI 12.0.5 Stable - Global rom
Model : M1903F11A
Kernel vers : 4. 14.117-perf-g97c1088
If someone can help I will be more than thankful !
My bootloader is unlocked btw but I don't have TWRP
where did u purchase your k20 pro from.
In India only 6-128 and 8-256 variants are there not 6-64 and also indian variant or model has no nfc.
As per phone codename raphaelin is indian device codename but how come u have 6-64gb model.
It doesn't matter whichever rom u install if ur device doesn't have nfc hardware it won't work and indian model has no nfc support...
I already found out it's 100% percent a Chinese device flashed with India rom. Now I need help to change it
OK, so just to clarify things to avoid future confusion.
Xiaomi label any MIUI version that is not Chinese as 'Global'. This is when you look in the about phone section and see MIUI x.y.z Global ROM. However this description covers 4 separate versions - India, EU/EEA, Russia and everywhere else (true Global).
In order to change region you need to flash the appropriate fastboot ROM. This is the official guide to flashing fastboot ROMs.
https://c.mi.com/oc/miuidownload/detail?guide=2
You will need to view the page in desktop mode on a mobile device, otherwise you'll just see a blank page.
The guide has download links for the latest versions for all devices, however it's probably easiest to find the ROM you want from here
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Select the EEA fastboot ROM.
WARNING
You can not lock the bootloader of a Chinese phone when flashing a non-Chinese ROM. Trying to do this will hard brick the phone. See this from the official forums.
https://c.mi.com/thread-2584760-1-0.html
WARNING
The Mi Flash Tool default flashing option is to flash the ROM and lock the bootloader. If you do not pay attention when flashing you could easily hard brick the phone.
The Mi Flash Tool runs batch scripts contained in the ROM to flash the ROM. The easiest way to avoid bricking the phone is to manually delete the batch script from the ROM before running the tool.
In order to flash the fastboot ROM, it needs to be fully extracted. After extracting it browse the contents of the extracted folder. You'll see a bunch of .bat and .sh files.
Delete the flash-all-lock.bat and flash-all-lock.sh files before doing anything else. (Names of the files might not be exact but you'll know which ones I mean when you see them).
When running the Mi Flash Tool, before hitting the flash button, change the option at the bottom of the app to 'clean all'. If you leave it on the default option and you've deleted the batch scripts above then you'll only get an error that it can't find the batch file.
So now after updating to the EU ROM, you'll have NFC working, but you are still going to have a bunch of issues with financial and tap to pay apps. The security problems you've seen so far have not been around insecure software, but because the bootloader is unlocked, and this is still going to cause you problems. There is something called the SafetyNet test, within android, which fails when run on phones with an unlocked bootloader. Apps that care about security will call the test and fail to run if it fails. To get around these issues you will need to install Magisk. Currently Magisk can spoof the test to give a positive result.
You'll also need to setup Magisk to hide itself from apps that perform security checks before launching, such as financial apps.
Only download Magisk from the official source.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
You should find all the info needed to set up Magisk within the documentation links.
Hello.
I have been trying to get a custom rom flashed on my Redmi 9T the past two days.
The problem I am facing is that the touch screen is not responsive with the flashed ROMs that I have tried.
ROMs I have tried:
PixelPlusUI_3.9_juice-11.0-20210912-1736-OFFICIAL
LegionOS-v3.13-juice-20210922-OFFICIAL-GAPPS
Arrow-v11.0-juice-COMMUNITY-20210809-GAPPS
crDroidAndroid-11.0-20210927-juice-v7.10
What did make the touch screen work was to flash "boot.img" from one of the android 11 builds of MIUI such as "xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11" or "xiaomi.eu_multi_HMNote94G_HM9T_POCO_M3_21.5.27_v12-11" after flashing the custom ROM, but this resulted in "Sytem UI" crashing and wifi not working. There were probably other things that didn't work but I can't have a phone without WiFi so this was not a solution for me.
After looking into what "boot.img" contains, it seems like it contains the kernel and other important system related components.I then tried to flash the following kernels over a new install of the custom ROMs "crDroid" and "PixelPlusUI 3.9":
StormBreaker-lime-r3-0909-0545
CartelProject-lime-BETA-20210915-07
Optimus_Drunk_Citrus_v11.1
But they did not help with getting the touch screen to work.
I also tried a combination of a "boot.img" from an offical android 11 EU MIUI ROM and these three kernels in the hope that I would keep the touch screen fix from "boot.img" and get wifi from the kernels, however every time the kernel was flashed the touch screen stopped working.
This leads me to believe the kernel itself makes the touch screen not work, and other things from the "boot.img" make the WiFi stop working.
So I have a few questions I hope someone can answer:
When do you think Xiaomi will release the source-code for the android 11 kernels that they use in their new MIUI ROMs? As I don't know their release cycles.
When will the firmware for the NVT-ts touchscreen version of Redmi 9T be added to custom kernels?
Is there a way for me to extract the Android 11 MIUI kernel from "boot.img" and flash ONLY that, if that fixes my touchscreen and does not break my WiFi? (If this is legal/allowed/possible)
I don't know anything about android development so if I am wrong please correct me.
Thank you in advance.
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):Download
Fastboot Firmware tgz:Download
Atanassoww said:
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):Download
Fastboot Firmware tgz:Download
Click to expand...
Click to collapse
Thank you for the reply.
However I believe that this is what I did do when I set up the phone with the ROMs.
I still tried to do it exactly as you explained, however this did not work.
I got into a bootloop after flashing firmware through fastboot, even if I cleaned the data using recovery. I tried the Recovery version of the firmware and this worked fine so after that I followed your tutorial just as you described.
This still didn't work, when booted into the Custom ROM the touch screen was still not working at all.
In the meanwhile I found this blog-post:
lemon – Encik Kunci
Posts about lemon written by Encik Kunci
encikkunci.wordpress.com
Where he states and I quote: "Phones with nt36672d display isn’t supported yet." this was posted August 11, 2021.
I don't know who he is or how he knows that.
I am pretty sure it's a kernel problem or firmware or something, regarding the screen being NVT-ts and probably the "nt36672d" variant.
This makes me very sad.
Its indeed an kernel issue, there's ( at least) two screen revisions from two different vendors
coffeemakerexpress said:
Thank you for the reply.
However I believe that this is what I did do when I set up the phone with the ROMs.
I still tried to do it exactly as you explained, however this did not work.
I got into a bootloop after flashing firmware through fastboot, even if I cleaned the data using recovery. I tried the Recovery version of the firmware and this worked fine so after that I followed your tutorial just as you described.
This still didn't work, when booted into the Custom ROM the touch screen was still not working at all.
In the meanwhile I found this blog-post:
lemon – Encik Kunci
Posts about lemon written by Encik Kunci
encikkunci.wordpress.com
Where he states and I quote: "Phones with nt36672d display isn’t supported yet." this was posted August 11, 2021.
I don't know who he is or how he knows that.
I am pretty sure it's a kernel problem or firmware or something, regarding the screen being NVT-ts and probably the "nt36672d" variant.
This makes me very sad.
Click to expand...
Click to collapse
I found this in 4pda:
Quote a reply: Yes, I had the same thing. By the way, if we are talking about OrangeFox recovery, which did not start at all, then it was necessary to use a newer version, I found a link to a google drive on the xda forum, it did not start there.
And on the touch, I also tried 2 custom firmware on them, everything started, but the touch did not work in principle. Only on off or lightweight everyone and on xiaomi.eu worked. I suppose the same case, but I can refine it when the phone is sent back.
ps: Due to freezes and rebots - in the service they changed the motherboard in the end, I'm waiting for the parcel now.
superdragonpt said:
Its indeed an kernel issue, there's ( at least) two screen revisions from two different vendors
Click to expand...
Click to collapse
I see, so my assumption was correct. Thank you for clarifying.
Do you know how often Xiaomi (or if they will at all) release firmware/kernel source codes, and do you know if custom kernel makers/Custom ROM makers, will actually update their kernels/ROMs to use this in the future?
And is there a way/place for me to keep updated on if Xiaomi releases the needed firmware/sourcecode for this display, so that I can ask ROM makers/Kernel makers nicely to add the firmware, assuming they don't know about this issue?
Atanassoww said:
I found this in 4pda:
Quote a reply: Yes, I had the same thing. By the way, if we are talking about OrangeFox recovery, which did not start at all, then it was necessary to use a newer version, I found a link to a google drive on the xda forum, it did not start there.
And on the touch, I also tried 2 custom firmware on them, everything started, but the touch did not work in principle. Only on off or lightweight everyone and on xiaomi.eu worked. I suppose the same case, but I can refine it when the phone is sent back.
ps: Due to freezes and rebots - in the service they changed the motherboard in the end, I'm waiting for the parcel now.
Click to expand...
Click to collapse
So you have the same problem? I'm not sure I understand what you mean here, aside from the touchscreen not working for you either due to this weird display model.
coffeemakerexpress said:
I see, so my assumption was correct. Thank you for clarifying.
Do you know how often Xiaomi (or if they will at all) release firmware/kernel source codes, and do you know if custom kernel makers/Custom ROM makers, will actually update their kernels/ROMs to use this in the future?
And is there a way/place for me to keep updated on if Xiaomi releases the needed firmware/sourcecode for this display, so that I can ask ROM makers/Kernel makers nicely to add the firmware, assuming they don't know about this issue?
So you have the same problem? I'm not sure I understand what you mean here, aside from the touchscreen not working for you either due to this weird display model.
Click to expand...
Click to collapse
Yes or is not Supported right now..
This is just a small update with a possible fix that I haven't tried yet because I'm tired of flashing ROMs all day, I will try it later if I get the motivation to do so. I post this because someone else might have the energy to test this themselves. If I test this I will update this post with an edit or bump this thread.
I Found on a forum called 4PDA where a user by the name "Void_dp" talks about a Xiaomi Redmi 9T with a nt36672d display. The forum is in Russian, but use a translator if you are interested. It is the post this url links to:
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки - 4PDA
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки
4pda.to
I do not know if the website itself or this user is trustworthy or correct, so try this with caution and I am not responsible for anything you decide to do or happens to you or your computer, or phone.
In short he explains that crDroid 7.9 (7.10 is the current version, and is the one I tried) use a different kernel than the Stormbreaker kernel than crDroid 7.10 uses.
He says if you have crDroid 7.10 installed you have to format data before trying this.
1. Download crDroid 7.9 and crDroid 7.10
2. Get the "boot.img" from the crDroid 7.9 rom and extract it
3. Open the zip file for crDroid 7.10 (do not extract anything) and replace the "boot.img" (7.10 version) with the one you just extracted (7.9 version)
4. Do a clean flash with this modified ROM you just made.
That is all he said, but if it doesn't work my first thought is to try the original crDroid 7.9 rom, if you don't care about running the latest update. This is probably not smart in relation to security patches and stuff like that. I take no responsibility for whatever happens.
Additional information:
I checked the Changelog for the crDroid roms, and they changed the kernel from "Optimus Drunk kernel 11.0" to "Stormbreaker" when they upgraded their ROMs version from 7.9 to 7.10.
I tried using the "Optimus Drunk kernel 11.1" kernel in my trial and error with the ROMs without luck, so I will try to flash some roms together with the "Optimus Drunk kernel 11.0" if I can find it.
Link to crDroid ROM for Redmi 9t:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net
coffeemakerexpress said:
This is just a small update with a possible fix that I haven't tried yet because I'm tired of flashing ROMs all day, I will try it later if I get the motivation to do so. I post this because someone else might have the energy to test this themselves. If I test this I will update this post with an edit or bump this thread.
I Found on a forum called 4PDA where a user by the name "Void_dp" talks about a Xiaomi Redmi 9T with a nt36672d display. The forum is in Russian, but use a translator if you are interested. It is the post this url links to:
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки - 4PDA
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки
4pda.to
I do not know if the website itself or this user is trustworthy or correct, so try this with caution and I am not responsible for anything you decide to do or happens to you or your computer, or phone.
In short he explains that crDroid 7.9 (7.10 is the current version, and is the one I tried) use a different kernel than the Stormbreaker kernel than crDroid 7.10 uses.
He says if you have crDroid 7.10 installed you have to format data before trying this.
1. Download crDroid 7.9 and crDroid 7.10
2. Get the "boot.img" from the crDroid 7.9 rom and extract it
3. Open the zip file for crDroid 7.10 (do not extract anything) and replace the "boot.img" (7.10 version) with the one you just extracted (7.9 version)
4. Do a clean flash with this modified ROM you just made.
That is all he said, but if it doesn't work my first thought is to try the original crDroid 7.9 rom, if you don't care about running the latest update. This is probably not smart in relation to security patches and stuff like that. I take no responsibility for whatever happens.
Additional information:
I checked the Changelog for the crDroid roms, and they changed the kernel from "Optimus Drunk kernel 11.0" to "Stormbreaker" when they upgraded their ROMs version from 7.9 to 7.10.
I tried using the "Optimus Drunk kernel 11.1" kernel in my trial and error with the ROMs without luck, so I will try to flash some roms together with the "Optimus Drunk kernel 11.0" if I can find it.
Link to crDroid ROM for Redmi 9t:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net
Click to expand...
Click to collapse
I DIDN't work for me, I got a bootloop, maybe it will work for u
hamid_dabouz said:
I DIDN't work for me, I got a bootloop, maybe it will work for u
Click to expand...
Click to collapse
Thats sad to hear, this phone is a nightmare. I haven't tried this yet, maybe I will try this weekend.
I'm wondering though, did you FORMAT data after flashing?
By bootloop, which of these do you mean:
That it never enters the "loading phase" of the OS (Android/rom splash screen)
That it gets stuck and restarts in the "loading phase" of the OS (Android/rom splash screen)
That it just kicks you to recovery/fastboot over and over again, without showing the OS loading screen
Or something else?
coffeemakerexpress said:
Thats sad to hear, this phone is a nightmare. I haven't tried this yet, maybe I will try this weekend.
I'm wondering though, did you FORMAT data after flashing?
By bootloop, which of these do you mean:
That it never enters the "loading phase" of the OS (Android/rom splash screen)
That it gets stuck and restarts in the "loading phase" of the OS (Android/rom splash screen)
That it just kicks you to recovery/fastboot over and over again, without showing the OS loading screen
Or something else?
Click to expand...
Click to collapse
Ohh Jeesus...
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
superdragonpt said:
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
Click to expand...
Click to collapse
Thank you for respond, But i already flashed Two versions of " stormbreaker"kernel one of them worked but the touch is going insane, if you clicked on somewhere on the screen it will respond in other place of the screen ( i hope you understand what i'm saying)
hamid_dabouz said:
Thank you for respond, But i already flashed Two versions of " stormbreaker"kernel one of them worked but the touch is going insane, if you clicked on somewhere on the screen it will respond in other place of the screen ( i hope you understand what i'm saying)
Click to expand...
Click to collapse
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Atanassoww said:
Ohh Jeesus...
Click to expand...
Click to collapse
Why that reaction? I am here to learn and try to solve my problem, if you have any advice please elaborate on why what I said was wrong or dumb so I won't make the same mistake again.
superdragonpt said:
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
Click to expand...
Click to collapse
I will maybe try the Stormbreaker kernel for Poco M3 this weekend as well then to check it out.
superdragonpt said:
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Click to expand...
Click to collapse
Thank you for this informative answer, do I take it as this is something you will look into? If I can help by using adb or something, to get information from my phone just tell me what to do.
superdragonpt said:
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Click to expand...
Click to collapse
Is this the extract you were talking about? It has the firmware for the touchscreens and everything for android 11. but it is for the Chinese version, so I don't know if that matters.
redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
qssi-user 11 RKQ1.201004.002 V12.0.3.0.RJQCNXM release-keys - redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
github.com
I don't know if this is relevant but I thought I would share it since I found it. Someone smarter than me can maybe use it to make the touchscreen work.
I fix dt2w on Xtended custom rom. Replace kernel and flash Magisk extension. I don.t try others roms....
coffeemakerexpress said:
Is this the extract you were talking about? It has the firmware for the touchscreens and everything for android 11. but it is for the Chinese version, so I don't know if that matters.
redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
qssi-user 11 RKQ1.201004.002 V12.0.3.0.RJQCNXM release-keys - redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
github.com
I don't know if this is relevant but I thought I would share it since I found it. Someone smarter than me can maybe use it to make the touchscreen work.
Click to expand...
Click to collapse
coffeemakerexpress said:
Hello.
I have been trying to get a custom rom flashed on my Redmi 9T the past two days.
The problem I am facing is that the touch screen is not responsive with the flashed ROMs that I have tried.
ROMs I have tried:
PixelPlusUI_3.9_juice-11.0-20210912-1736-OFFICIAL
LegionOS-v3.13-juice-20210922-OFFICIAL-GAPPS
Arrow-v11.0-juice-COMMUNITY-20210809-GAPPS
crDroidAndroid-11.0-20210927-juice-v7.10
What did make the touch screen work was to flash "boot.img" from one of the android 11 builds of MIUI such as "xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11" or "xiaomi.eu_multi_HMNote94G_HM9T_POCO_M3_21.5.27_v12-11" after flashing the custom ROM, but this resulted in "Sytem UI" crashing and wifi not working. There were probably other things that didn't work but I can't have a phone without WiFi so this was not a solution for me.
After looking into what "boot.img" contains, it seems like it contains the kernel and other important system related components.I then tried to flash the following kernels over a new install of the custom ROMs "crDroid" and "PixelPlusUI 3.9":
StormBreaker-lime-r3-0909-0545
CartelProject-lime-BETA-20210915-07
Optimus_Drunk_Citrus_v11.1
But they did not help with getting the touch screen to work.
I also tried a combination of a "boot.img" from an offical android 11 EU MIUI ROM and these three kernels in the hope that I would keep the touch screen fix from "boot.img" and get wifi from the kernels, however every time the kernel was flashed the touch screen stopped working.
This leads me to believe the kernel itself makes the touch screen not work, and other things from the "boot.img" make the WiFi stop working.
So I have a few questions I hope someone can answer:
When do you think Xiaomi will release the source-code for the android 11 kernels that they use in their new MIUI ROMs? As I don't know their release cycles.
When will the firmware for the NVT-ts touchscreen version of Redmi 9T be added to custom kernels?
Is there a way for me to extract the Android 11 MIUI kernel from "boot.img" and flash ONLY that, if that fixes my touchscreen and does not break my WiFi? (If this is legal/allowed/possible)
I don't know anything about android development so if I am wrong please correct me.
Thank you in advance.
Click to expand...
Click to collapse
Atanassoww said:
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):Download
Fastboot Firmware tgz:Downl
Click to expand...
Click to collapse
bogteo said:
I fix dt2w on Xtended custom rom. Replace kernel and flash Magisk extension. I don.t try others roms....
Click to expand...
Click to collapse
Please can you explain more ?
I tried with crdroid 7.9 without success. still cannot use the touchscreen
m210j19sy I began with global miui rom