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
Related
Hello guys,
I don't see a dedicated section for lenovo Z5s but I managed to download the TWRP 3.3.1 from baidu (only chinese and english but chinese default).
I then looked for rom authors, it seems they all are using chinese custom roms, anyway they are mirrored and MIUI has been tested by me.
I decided to mirror all downloads I found (they were quite hard to get):
TWRP :
TWRP-3.3.1-LENOVO_Z5S-CN-wzsx150-fastboot.7z (with fastboot instructions and files)
TWRP-3.3.1-0529-LENOVO_Z5S-CN-wzsx150.zip (can be flashed with TWRP)
recovery-TWRP-3.3.1-0529-LENOVO_Z5S-CN-wzsx150.img (only .img file)
Chinese Roms :
Z5s_miui_19.5.20(9.5.16)_Pie_Public_by Art_Chen(TWRP_FASBOOT_2in1).zip
Z5S_H2OS_190722
Z5s_Flyme7.3.1.0A_YouLinw_V1.5_19.07.25
GSI Roms : (Seems to be AB, because A-Only are not working)
According to 4PDA, only Pixel Experience have been tested for now, they provide screenshot and video.
Pixel Experience GSI Tested working!
Ressurection Remix Tested working!
Arrow OS Tested Working!
All other public GSI images (tested many, none of them working, no idea why)
Official ROM backup (QPST format):
https://mirrors.lolinet.com/firmware/lenovo/l78071/
I added permissiver v4 I got from Telegram on Android Q GSI channel
Instructions for GSI Images (thanks to 4PDA):
Using TWRP recovery:
0. Download the firmware files to your smartphone.
1. Enter the recovery menu. To do this, turn off the smartphone and simultaneously hold down the power button and volume +.
2. In the recovery menu, select the item Cleaning -> Selective cleaning. Check the boxes on Dalvik / ART Cache , System , Data and Cache . Swipe the slider to the right. Return to the main recovery menu.
3. In the main recovery menu, select Installation -> Install Img. Select firmware file XX.img. For system section firmware, select System Image, and for boot - Boot. Swipe the slider to the right. Go to the main recovery menu. Select Reboot -> System.
This procedure is new for all smartphones, so don't be afraid to ask questions if something went wrong.
Click to expand...
Click to collapse
Using adb:
0. Install the USB, ADB and Qualcomm drivers on the PC. Reboot the computer and connect the smartphone to the PC. Download files for firmware on PC.
1. In the folder where the files (.img) were saved, press SHIFT and the right mouse button from scratch. In the context menu, select PowerShell or CMD (activate command console).
2. Enter the commands one by one
fastboot flash system XX.img
fastboot erase userdata
fastboot -w
fastboot reboot
PS In some cases, it will be necessary to flash vendor and / or boot:
fastboot flash vendor XX.img
fastboot flash boot XX.img
Click to expand...
Click to collapse
Source for TWRP: https://club.lenovo.com.cn/thread-5442053-1-1.html
Source/author for H2OS & Flyme : Weibo
Source/author for MIUI : Weibo
4PDA page : https://4pda.ru/forum/index.php?showtopic=960895
Please move topic to another section if wrong.
First, thanks for the Thread. Very informative.
let me report that H2OS showes black screen after boot logo,
Flyme seems working but with some minor problems (bad english translation, no google apps on built-in chinese app store, upper notification bar not aligned, etc).
TASON42 said:
First, thanks for the Thread. Very informative.
let me report that H2OS showes black screen after boot logo,
Flyme seems working but with some minor problems (bad english translation, no google apps on built-in chinese app store, upper notification bar not aligned, etc).
Click to expand...
Click to collapse
Hi, thanks. H2OS is the only one i have not tested, i will remove the link. If you live outside Cina I would recommend GSI rom since chinese roms might have issues with notifications.
I now recommend AEX (arm64 AB)
vickdu31 said:
Hi, thanks. H2OS is the only one i have not tested, i will remove the link. If you live outside Cina I would recommend GSI rom since chinese roms might have issues with notifications.
I now recommend AEX (arm64 AB)
Click to expand...
Click to collapse
Don't you lost WIFI after flashing just GSI img file? I need to flash MIUI before flashing any GSI to keep WIFI working.
and this maybe is a lil bit off topic but have you ever had problems with fastboot?
my fastboot is not working properly since I bought this smartphone, 'fastboot devices' works but
can't flash anything, saying random error like 'maxium download size not reported', 'too many links', and even 'error: no error'...
tried changing usb port, cable, driver, everything I can think of.
I can still flash boot.img, recovery.img, vbmeta.img via QFIL but I want to use fastboot which is less hassle..
Report:
MSM Xtended is working too.
problems I hav till now.
1. WIFI not working if you flash directly from ZUI, or wipe cache/dalvic.
2. loud speaker sound problems at various ROMs, with or without equalizer app.
3. notch size is not matching with status bar at every ROMs
4. double tap to wake is not working for every ROMs.
I actually did flash miui first.
I contacted art_chen to get international MIUI, he told me he dont have phone anymore but we can download his miui zip and replace system.img with the one official from MI9 (taking the system.img full global fastboot firmware and it should work).
The vendor image and boot.img included in the miui rom have been customised by art_chen so he probably fixed wifi !
Since i also dont have the phone i cannot test so well.
vickdu31 said:
I actually did flash miui first.
I contacted art_chen to get international MIUI, he told me he dont have phone anymore but we can download his miui zip and replace system.img with the one official from MI9 (taking the system.img full global fastboot firmware and it should work).
The vendor image and boot.img included in the miui rom have been customised by art_chen so he probably fixed wifi !
Since i also dont have the phone i cannot test so well.
Click to expand...
Click to collapse
1. did you had loud speaker problem after flashing treble GSI files? Mine distorts heavily with every .img file i tried.
2. I'm testing swapping .img file with other xiaomi devices but none of them is working. Sounds like you don't own the device anymore so this will be lonely fight.
---------- Post added at 03:41 AM ---------- Previous post was at 03:36 AM ----------
I need FM radio which is not included in Art_chen's ROM so I tried swapping system.img with Redmi note 7 (closest spec), and failed.
TWRP log is saying "Failed to mount '/system_root'" so i guess the reason is partition chart problem or pre-installed magisk, I'm not sure I can fix this but I'll keep trying.
since FM radio is not even on the hardware list so i decided to give up FM radio, but updating android security patch with
Mi 9 (since OP mentioned), Mi 9 SE (quite close spec) and Mi CC9 (not international but even closer than redmi note 7) firmware files,
I don't think any of them would work, but I'll keep trying(2).
You could also try with Flyme blobs (boot, vendor etc) they are from different dev
If you messed up partition i recomment flash wjole miui or flyme with adb
Looking for Global Rom
I purchased the Chinese version of this model.
I tried various GSIROMs, but there were a lot of things that didn't work.
I want to use ZUIOS obediently. Does anyone have a Global Rom?
Also, you should be careful about overwriting GSIROM.
The lighting adjustment has gone wrong.
(No problem with genuine ROM)
teketake said:
I purchased the Chinese version of this model.
I tried various GSIROMs, but there were a lot of things that didn't work.
I want to use ZUIOS obediently. Does anyone have a Global Rom?
Also, you should be careful about overwriting GSIROM.
The lighting adjustment has gone wrong.
(No problem with genuine ROM)
Click to expand...
Click to collapse
there is no Official Global Firmware since this phone is only for china mainland. You can enable google service/calendar/GPS by downloading play store .apk from lenovo app store.
there is faulty firmware chimera with chinese rom + google service preinstalled, but trust me, it is unusable. It has every unfamiliar chinese-specific settings + bunch of 'google service force closed' alarms, bad battery drain by google service, crashing app downloading, etc.
Yes, I'm still using this mediocre device, found some useful articles about GSI, will throw links here.
https://www.dospy.wang/forum.php?mod=viewthread&tid=1626&extra=page=1
https://www.htcmania.com/showthread.php?t=1504540
it's not in English but google translate will help you guys.
here's the essence.
Flash MIUI first, its mandatory. Without it you will lost WiFi.
But, you will lost DT2W and FM radio at kernel level if you flash MIUI.
Now you can flash any GSI, but I recommend Pixel Experience from the link I uploaded,
because fixes of common GSI issues like statusbar height (use magisk+rirucore+riruedxposed+gravitybox), sound distortion (use magisk+audio compability), headphone not detecting (random) are integrated to the GSI.
Global ROM was uploaded to 4PDA.
K10 note is almost identical with Z5s and now it's Global released, you can get the QFIL files, I guess just swap system.img and userdata.img might work.
the difference between Z5s chinese ROM and K10 note global ROM must be something like that of Z6 pro chinese and global version...
edit: yes it is working, just swap system_xx.img and userdata_xx.img files will do the work, only camera.apk won't work properly (no optical zoom just digital, ramdom crash sometimes ) but we can stick with Gcam port.
I flash pixel experience then i find out auto brightness isn't work well.i adjust it to the lowest , but it still so bright.how can i fix it?
H2OS 9 : https://mp.weixin.qq.com/s/45L1TZFa0g1MP3-jSYhMDg
Flyme 8 : https://mp.weixin.qq.com/s/P8tL8eq9UhV8Hbq8-7nYBQ
MIUI 11 : https://mp.weixin.qq.com/s/q-8qnFI1VP8upyz6quZZmw
it's all from YouLinw, the dev of Flyme 7 port in OP.
Flyme 8 is still in daily alpha, it boots but stuck in Terms&Conditions screen.
MIUI 11 and H2OS works great, (but don't use pre-installed Magisk, install official v19.3 from via TWRP. idk why but pre-installed one or lastest v20.1 won't work.)
Android Security Patch in MIUI11 is Sep 1st while H2OS is Aug 1st (same with PE I linked before)
so it's your choice to use MIUIsh MIUI with newer ASP, or H2/PE which is more stock android, but with older ASP.
Quack phh Android 10 is not working sadly,
neither vendor by Art_Chen (MIUI10) nor YouLinw booted,
with original vendor it boots but Wi-Fi won't work, like always.
---------- Post added at 04:29 AM ---------- Previous post was at 04:21 AM ----------
s94084sammy said:
I flash pixel experience then i find out auto brightness isn't work well.i adjust it to the lowest , but it still so bright.how can i fix it?
Click to expand...
Click to collapse
I have the same problem, I just bear it since it's not major one. you can use any third party apps from play store that dims your screen if you want to.
Hello, i think about buying this phone or xiaomi note 7 pro . Want to flash lineage or aosp base rom, someone has a point of view about best hardware and best dev support ? For me note 7 pro have better dev support but one week for unlock bootloader and lcd cheaper for repair . Can't find photo versus, z5s have three module but rn7p have 48mp , someone have an advice ?
bretzelpopo said:
Hello, i think about buying this phone or xiaomi note 7 pro . Want to flash lineage or aosp base rom, someone has a point of view about best hardware and best dev support ? For me note 7 pro have better dev support but one week for unlock bootloader and lcd cheaper for repair . Can't find photo versus, z5s have three module but rn7p have 48mp , someone have an advice ?
Click to expand...
Click to collapse
I think Redmi Note 7 pro is the buy.
I chose Z5s because of its cheaper price, lighter weight, and more premium material (alu+glass).
And I also had nice Dev experience with ZUK Z2 so I expected the same with this phone (which was wrong guess )
Cam, I assume stock camera is better in Z5s, but You won't use stock ZUI/MIUI ROM anyway so that won't bother you.
GCam works great on both model, ported stock camera apk won't work as good as it's on stock ROM, both in Z5s/Note 7.
Sound, both mediocre.
Screen, both mediocre (HDR on Z5s is fake color boost only for chinese content apps),
and Z5s has unusual copper plate type connection not like normal ribon cable.
Dev, Z5s is for China mainland only so you won't get proper global/AOSP ROM developments,
but you can get bunch of MIUI/Flyme/H2OS ROMs...
Official Update is also better in MIUI over ZUI.
Hi there. Was there any AOSP or LineageOS working on our Z5S?
Hi @vickdu31 do you have a copy of recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img ? I tried as a guest in 4pda but I get a 404 error. Thanks for your help!
carlshark said:
do you have a copy of recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-JwD0Ie5xY2CQRDv8rvZMK6ICf0vmp4n/view?usp=drivesdk
Android Version : MIUI-11-EU-PIE Easy recovery install.
You should be having proper knowledge of flashing Custom ROM and how to Restore a phone if anything goes wrong.
Take complete backup before taking any action based on this thread. I am not responsible for any action taken by you.
I am just compiling all the information / files available on different websites into this thread, I have patched together with cyber spit, bubblegum, and tape, for a pretty much fully working MIUI-11--EU-PIE running rom. With the help from Mohzuned. I have removed what I believe to be all of the bloat. We worked to modify a working pie vendor. Magisk v20 modified boot for root access, Just install magisk manager.
All Credit goes to respective developer/s. I request XDA moderator and or Developer of Respective files to let me know if I have forgotten to mentioned (give credit) their name in this thread. The Download Links are given directly from respective Developer/s.
You need the following two files to Test MIUI-11-EU-PIE on Mi Max 2 (Oxygen). This ROM recovery is ported from the Xiaomi RedMi with many patches and customized from various sources. This ROM maybe Stable enough for your daily use on Mi Max 2. I have access to two MM2 4/64 Global versions using a 1tb sd card one on At&t the other on Tmobile and MOST features I need are currently working.
1a. Treble Mi Max 2 Recovery 3.2.1 https://androidfilehost.com/?fid=5862345805528056270
1b. OrangeFox Recover 10
https://sourceforge.net/projects/ora...n.zip/download
2. MIUI-11-EU-PIE
https://drive.google.com/file/d/15lRb49s75rqVV0Kg8C16Eao_BuTPvBWr/view?usp=drivesdk
First step:
Start your phone into recovery and Flash a Treble recovery, if already not flashed. Restart into Recovery.
Click Wipe then Advance wipe and clear System, Vendor, Boot, Data, Cache, and Dalvick cache.
Second step:
Now Extract the Downloaded Rom files in Recovery backup folder. You should know where and how to Extract. (Use extract tool for android or pc then copy paste to recovery backup folder.)
Third step:
Click Restore and Select System, Boot, Vendor and Swipe to confirm. Wait for restore to complete. If any errors, Reboot recovery and try again. Or Mount the System, Vendor, Boot and try again. After Restore completes Reboot. Please allow 1-2 Minutes for first boot.
What works:
?
What doesn't work:
?
If I missed anything in the above, kindly let me know to include. If you make any further updates / patches that makes this ROM more stable / perfect or enables new features, please don't hesitate to message me to include in this thread.
I have an old PC running windows with 8gb max HDD at any one given time, So if you would like to make the recovery image into a flashable zip, I'd be happy to update/add it.
If you can afford it, Im trying to save for a computer from this decade, any help is appreciated
https://www.paypal.me/LiamMcGinnisIv
If you would like to use the boot, vendor, system, or any other files, All I ask is pass on the proper credits.
Any Others Who May Have Been Missed
Best of Luck and Happy Flashing )
Camera/Torch.
Camera, fingerprint and fm radio, dont work, congratulations, good rom. Thanks.
Cool....... thanks dude
liammc83 said:
Camera/Torch.
Click to expand...
Click to collapse
Iam ready for the test ride......
I will test today. Thank you for your job!
Beast developer...too fast man thanks
If you will fix Camera and Torch it will be great! We are all waiting! Thank you!
---------- Post added at 06:51 AM ---------- Previous post was at 06:38 AM ----------
May be it is better to do Port from Mi Mix 2S? Camera and Torch worked on that port.
Bro.......
I cannot find the fingerprint option in the rom..?
Firstly I upgraded from the nougat rom.,it made me to suck....it booted but instantly rebooted to recovery on every boot......
Cannot find the fingerprint option ..,Cannot add the face unlock option due to the camera bug...,it's harder always using pattern/pin.,? flashlight ? issue is negligible.....
But mi cloud has no issues and working fine able to login..
Home button isn't working.,full screen guesture option isn't seen in the rom..
May be it's because of the redmi note 4x....it might be good if it's from max3 or mix2s as u done previously.,only hotspot bug majorly
You are too good bro....,you are beastly fast and tough..,???
Please fix the camera!!!
zavorotnii said:
Please fix the camera!!!
Click to expand...
Click to collapse
He is trying continuously and I believe soon it will be resolved.
zavorotnii said:
Please fix the camera!!!
Click to expand...
Click to collapse
I'm not screaming "Donate!!!!!"
I do this for free for a phone I no longer use, please be patient.
Considering all sources from xiaomi are outdated, And this is being done again for FREE with modifications on an ancient netbook.
I also can now verify, I have a working modified vendor/boot image that will run gsi images, But again since problems with vendor no camera, Still working on it.
Sorry, I just asked. I understand your position and ready to test new changes
No need to wait for me to port.
https://forum.xda-developers.com/mi-max-2/development/mi-max-2-oxygen-gsi-bootable-vendor-t3987191
I really liked this rom .. I want to use daily ... only thing that is bothering me is the home button and the camera that is not working? already have a solution? fingerprint to taste .. but you can use with the pin normally
Hi all.
I've just bought this device. When I first launched it, it was on miui9, i updated to miui 10 stable 10.0.3.0 (8.1 Android) via ota. Then, I saw that I could also upgrade to miui 11. However, I've read that battery is worse than Miui 10 so I don't know If I should install it.
I've unlocked the recovery because I want to try some custom roms but I'm a bit scared of the anti-rollback.
Could you please tell me what should I do?
Thanks all.
Before you do anything you need to figure out which device you own. You bought it and you already unlocked the bootloader? That generally takes 360 hours, are you sure it wasn't already unlocked? If it was unlocked you probably have a Chinese device, and in that case be extremely careful about not relocking the bootloader. if the phone is not bound to your account ( linked to you personally) then you could brick it and have no recourse.
if you unlocked it yourself and you have a locked device , then don't worry about anti-rollback. So far it has not been implemented. Next, you heard wrong about Miui 11, its battery is equally as good. Although the best version of Miui and currently the most stable Android 10 overall is Xiaomi.EU which is a custom rom based on the china beta but globalised, with Google services.
Again do your homework, avoid extremely old posts that are no longer relevant. Never attempting upgrading your screen refresh and never flash someone else's persist image and you will be good. This community has tons of infor...read a lot and take your own notes.
tsongming said:
Before you do anything you need to figure out which device you own. You bought it and you already unlocked the bootloader? That generally takes 360 hours, are you sure it wasn't already unlocked? If it was unlocked you probably have a Chinese device, and in that case be extremely careful about not relocking the bootloader. if the phone is not bound to your account ( linked to you personally) then you could brick it and have no recourse.
if you unlocked it yourself and you have a locked device , then don't worry about anti-rollback. So far it has not been implemented. Next, you heard wrong about Miui 11, its battery is equally as good. Although the best version of Miui and currently the most stable Android 10 overall is Xiaomi.EU which is a custom rom based on the china beta but globalised, with Google services.
Again do your homework, avoid extremely old posts that are no longer relevant. Never attempting upgrading your screen refresh and never flash someone else's persist image and you will be good. This community has tons of infor...read a lot and take your own notes.
Click to expand...
Click to collapse
Hi Thanks for your reply.
My device is global version (not just global ROM, I do know the difference)
I am unlocked the bootloader using the Xiaomi official tool, i had to activate the developer tools on the device and check the bootloader status and the button which was there ( U know what I mean). Besides, when I turn on the device it says unlocked.
I've read that miui 11 has kinda bad sot because of miui and/or the bug with WhatsApp. So I don't know if I have to update via ota and If I do that I don't know if I will have any problems while trying to install a custom ROM.
I've had a Xiaomi before so I know that I shouldn't install strange zips.
Thank you
Boiisxu said:
Hi Thanks for your reply.
My device is global version (not just global ROM, I do know the difference)
I am unlocked the bootloader using the Xiaomi official tool, i had to activate the developer tools on the device and check the bootloader status and the button which was there ( U know what I mean). Besides, when I turn on the device it says unlocked.
I've read that miui 11 has kinda bad sot because of miui and/or the bug with WhatsApp. So I don't know if I have to update via ota and If I do that I don't know if I will have any problems while trying to install a custom ROM.
I've had a Xiaomi before so I know that I shouldn't install strange zips.
Thank you
Click to expand...
Click to collapse
Yes, the last build of Xiaomi.EU had worse SOT than usual ( about 5 hours. However, the issue was only with one of the weekly builds) I personally resolved that issue for myself by flashing the kernel from the previous build. Also, Xiaomi.EU is updated every Thursday so later today there will be a new build that will very likely resolve the issue. On the other hand the stable builds do not have an issue with SOT. At least not in my experience. I have averaged around 8 to 9 hours SOT.
I don't use Whatsapp, so I can't help you with that.
Since you were previously on stock you will need to backup your data, if you are still using stock, backup to MiCloud as well. This way if you use a Miui based rom you can quickly restored most of your data and partial settings. You will also need to format use storage (type yes, reboot to recovery)
tsongming said:
Yes, the last build of Xiaomi.EU had worse SOT than usual ( about 5 hours. However, the issue was only with one of the weekly builds) I personally resolved that issue for myself by flashing the kernel from the previous build. Also, Xiaomi.EU is updated every Thursday so later today there will be a new build that will very likely resolve the issue. On the other hand the stable builds do not have an issue with SOT. At least not in my experience. I have averaged around 8 to 9 hours SOT.
I don't use Whatsapp, so I can't help you with that.
Since you were previously on stock you will need to backup your data, if you are still using stock, backup to MiCloud as well. This way if you use a Miui based rom you can quickly restored most of your data and partial settings. You will also need to format use storage (type yes, reboot to recovery)
Click to expand...
Click to collapse
I see.
I've just updated to miui 11 stable via ota.
BTW, Is TWRP the best recovery for this device isn't it? I've read that exist other types of recovery (not CWM but someones).
And my last question, I cannot find which version of gcam fits on miui 11 (Android Pie). Is there any thread, telegram channel?
Thanks for all.
Boiisxu said:
I see.
I've just updated to miui 11 stable via ota.
BTW, Is TWRP the best recovery for this device isn't it? I've read that exist other types of recovery (not CWM but someones).
And my last question, I cannot find which version of gcam fits on miui 11 (Android Pie). Is there any thread, telegram channel?
Thanks for all.
Click to expand...
Click to collapse
Personally I use the TWRP that I posted here : I talked to a few friends / android developers on other devices and several of them believe that this a TWRP issue.
I have not had any more of these issues since using this TWRP https://forum.xda-developers.com/showpost.php?p=80952013&postcount=121
If using AOSP, you should use the official version.
The best Gcam ( I Think is by Sanity )
https://www.celsoazevedo.com/files/android/google-camera/dev-san1ty/
FYI the builds made for the Poco F1 and Razer 2 are also compatible.
tsongming said:
Personally I use the TWRP that I posted here : I talked to a few friends / android developers on other devices and several of them believe that this a TWRP issue.
I have not had any more of these issues since using this TWRP https://forum.xda-developers.com/showpost.php?p=80952013&postcount=121
If using AOSP, you should use the official version.
The best Gcam ( I Think is by Sanity )
https://www.celsoazevedo.com/files/android/google-camera/dev-san1ty/
FYI the builds made for the Poco F1 and Razer 2 are also compatible.
Click to expand...
Click to collapse
Thank for helping me.
As I've posted in the official twrp thread, I was able to install twrp and get to it but after power off the phone and try to get there again miui recovery was there instead.
I've installed the last build of twrp 3.3.1.1.
Maybe If I install magisk via TWRP I will have twrp *forever*.(?)
Thank you man
Boiisxu said:
Thank for helping me.
As I've posted in the official twrp thread, I was able to install twrp and get to it but after power off the phone and try to get there again miui recovery was there instead.
I've installed the last build of twrp 3.3.1.1.
Maybe If I install magisk via TWRP I will have twrp *forever*.(?)
Thank you man
Click to expand...
Click to collapse
No problem.
After installing TWRP, you must initially install Root and then reboot to recovery.
Often you will see a message asking if you want to install the TWRP manager, click those boxes and then proceed to rebooting to recovery.
If you are using the full stock Rom, you must have root, so anytime that you flash the official Global stable rom, or an update, flash root again...unless you see via the Recovery terminal that Root maintained it's persistence.
tsongming said:
No problem.
After installing TWRP, you must initially install Root and then reboot to recovery.
Often you will see a message asking if you want to install the TWRP manager, click those boxes and then proceed to rebooting to recovery.
If you are using the full stock Rom, you must have root, so anytime that you flash the official Global stable rom, or an update, flash root again...unless you see via the Recovery terminal that Root maintained it's persistence.
Click to expand...
Click to collapse
Okey, I'll try tomorrow again.
Thanks.
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
Camera doesn't film horizontally. I thought the problem is with auto rotate so turned it on but camera still films vertically. Watched some videos but then the screen would stay horizontal even after exiting the video. Did some googling and found out that the sensors are not working and need to flash persist.img. Thanks in advance to whoever can help.
desertfoxtim said:
Camera doesn't film horizontally. I thought the problem is with auto rotate so turned it on but camera still films vertically. Watched some videos but then the screen would stay horizontal even after exiting the video. Did some googling and found out that the sensors are not working and need to flash persist.img. Thanks in advance to whoever can help.
Click to expand...
Click to collapse
If you want to do that , get the persist.img file from a fastboot rom or flash it via MIFLASH tool.
https://www.mifirm.net/model/olive.ttt
lolo9393 said:
If you want to do that , get the persist.img file from a fastboot rom or flash it via MIFLASH tool.
https://www.mifirm.net/model/olive.ttt
Click to expand...
Click to collapse
I have a similar problem, but there's no persist.img in the stock ROM zip
I've downloaded only firmware files too. No persist.img . I'm searching for the Willow version.
WinBug2 said:
I have a similar problem, but there's no persist.img in the stock ROM zip
I've downloaded only firmware files too. No persist.img . I'm searching for the Willow version.
Click to expand...
Click to collapse
You must download a FASTBOOT rom and not a ZIP.
Once unpacked Fastboot version let acces to all the rom content.
lolo9393 said:
You must download a FASTBOOT rom and not a ZIP.
Once unpacked Fastboot version let acces to all the rom content.
Click to expand...
Click to collapse
Hmm on Xiaomi's page are only zip files with stock roms. I don't understand what fastboot rom means. It's the third device I'm rooting and using customs roms etc. So I'm not totally newbie but fastboot rom?? I extracted the boot.img files for flashing it via fastboot. But....
Do you have a source for fastboot roms?
//Edit:
Found https://c.mi.com/oc/miuidownload/detail?guide=2
WinBug2 said:
Hmm on Xiaomi's page are only zip files with stock roms. I don't understand what fastboot rom means. It's the third device I'm rooting and using customs roms etc. So I'm not totally newbie but fastboot rom?? I extracted the boot.img files for flashing it via fastboot. But....
Do you have a source for fastboot roms?
//Edit:
Found https://c.mi.com/oc/miuidownload/detail?guide=2
Click to expand...
Click to collapse
you need to flash the zip from here through twrp since the fastboot commands dont support zips
I HAVE BEEN USING REALME 2 FROM PAST 2 YEARS THERE HAS BEEN NO PROBLEM.
Few weeks back I heard about Custom rom.
And Now My mind says install it you will get good battery and performance
On the Other My other part of my mind says you will get bugs l and you will brick it
I am totally terrified. Because there is a war going in my mind whether I should install custom rom or not.
Every morning I wake up I think about installing custom rom. I can't get rid of this thought.
I think I will go mad or something. Please Help me.
ANTROBAROTICS said:
I HAVE BEEN USING REALME 2 FROM PAST 2 YEARS THERE HAS BEEN NO PROBLEM.
Few weeks back I heard about Custom rom.
And Now My mind says install it you will get good battery and performance
On the Other My other part of my mind says you will get bugs l and you will brick it
I am totally terrified. Because there is a war going in my mind whether I should install custom rom or not.
Every morning I wake up I think about installing custom rom. I can't get rid of this thought.
I think I will go mad or something. Please Help me.
Click to expand...
Click to collapse
Well, installing custom roms has its own advantages and disadvantages.
(just like everything in life, so get over it)
Personally, I had to install twrp and a new miui ROM, because the message that miui says while updating "Do not power off your phone" was playing with my mind and i pulled the battery off
Then it blacked out and lit up on a screen saying "The system has been destroyed, hold the power button to shutdown"
Imagine how it could be
Either way a custom ROM is better than the default one.
But i dont recommend you to do it now because there might be an issue with SafetyNet right now if you install a custom ROM
You should do much more research before installing custom roms or rooting
What i recommend is that you wait some time more to get this issue out of the way.
P.S.: If you fail safetynet test you wont have any acces to Netflix and most banking apps
gabtit7 said:
Well, installing custom roms has its own advantages and disadvantages.
(just like everything in life, so get over it)
Personally, I had to install twrp and a new miui ROM, because the message that miui says while updating "Do not power off your phone" was playing with my mind and i pulled the battery off
Then it blacked out and lit up on a screen saying "The system has been destroyed, hold the power button to shutdown"
Imagine how it could be
Either way a custom ROM is better than the default one.
But i dont recommend you to do it now because there might be an issue with SafetyNet right now if you install a custom ROM
You should do much more research before installing custom roms or rooting
What i recommend is that you wait some time more to get this issue out of the way.
P.S.: If you fail safetynet test you wont have any acces to Netflix and most banking apps
Click to expand...
Click to collapse
But custom rom can be installed without rooting. So then also safety net will not work ?
Google realeased a new update that checks if the bootloader is unlocked
and the only way to lock it after flashing ROMs is to do a complete format and reinstall the original ROM, it replaces twrp or anything else with the original ROM (miui in our case)
So dont install roms
Okay. Thank you. I just wanted a reason not to install. Now is the end of custom rom I think majority will now no more root or install custom rom because of safety net. Copyright, Security & Privacy are now priority in today's world.
Some other members just found the solution but it supports only Android 10 & 11
[TUTORIAL] WORKING FIX FOR SAFETYNET / CTS PROFILE FAILED
Alright , here we go again . Steps to follow : 1. Open Magisk and select modules tab 2. Install Module for Android 11 - (https://t.me/XiaomiEUCloud/156) For Android 10 - (https://t.me/XiaomiEUCloud/158) from Storage 3. Reboot your Device Done . [emoji3544] UPDATE : NO NEED TO FLASH THIS ON...
xiaomi.eu