Hello Guys!
I'm thinking to install GSI ROM on my Redmi note 12 pro 5G. I have some experience with custom ROM flashing in TWRP. As far as I know there's no TWRP recovery available for my phone!
Can I flash GSI ROM with Fastboot mode in my device?
If you have experience or some guide for me to Flash GSI, please could you tell me?
And I don't familiar with those terms in GSI ROM name so I'm afraid that I would brick my device or some would go wrong.
I'm planning to flash AOSP 12.1 v416 by PHH or Android 13 Project Elixir.
Redmi note 12 pro should be similar close to Note 10, an A/B device with dynamics partitions
Read here, just find the appropriate GSI image and everything else specific for Note 12 pro
[GSI][PHH][13] Guide & Support [Mojito][Sunny]
Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯ Yes. But this thread exists due to the following reasons: You don't wanna fear about devs stop shipping updates. You don't wanna re-flash your custom recovery / kernel after each...
forum.xda-developers.com
x3r0.13urn said:
Redmi note 12 pro should be similar close to Note 10, an A/B device with dynamics partitions
Read here, just find the appropriate GSI image and everything else specific for Note 12 pro
[GSI][PHH][13] Guide & Support [Mojito][Sunny]
Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯ Yes. But this thread exists due to the following reasons: You don't wanna fear about devs stop shipping updates. You don't wanna re-flash your custom recovery / kernel after each...
forum.xda-developers.com
Click to expand...
Click to collapse
i think there is no twrp for this device yet but i think it is fine to just flash gsi.
keithsze001 said:
i think there is no twrp for this device yet but i think it is fine to just flash gsi.
Click to expand...
Click to collapse
True, you won't need twrp or any recovery at all to flash gsi.
Step to flash twrp/recovery is optional if you want to get rooted because fastboot doesn't have sideload function. Unless you go for KernelSU, it's a different topic.
Nowadays twrp function starts to decease, unless you need to dump/backup partition without root. I use included recovery from rom for A/B dynamic device
Thanks for the info, I haven't flashed GSI yet. does anyone know any working well rom or recommend ROM for Ruby except MIUI. I will leave my experience after I flashed GSI.Hope some rom for this device will come out!
Xenolast said:
Thanks for the info, I haven't flashed GSI yet. does anyone know any working well rom or recommend ROM for Ruby except MIUI. I will leave my experience after I flashed GSI.Hope some rom for this device will come out!
Click to expand...
Click to collapse
I am looking forward to hear your experience on gsi !
Please let us know if you find any particular stable rom for this device.
piyush_duggal said:
Please let us know if you find any particular stable rom for this device.
Click to expand...
Click to collapse
I bet if the buyers smart enough, they'll mostly will pass buying this. The price is closer to almost a mint second hand of Poco F4, offering almost better in everything except for maybe the main sensor (ov64b vs. imx766). And here we are Poco F4 has already a headstart in custom rom community.
And if you're willing to let go the OIS, Poco F3 isn't that bad either, price nowadays should be the same, its only disadvantages are slower charging and again, main sensor (imx586 vs imx766).
And the last, not to mention that Poco F5 is just around the corner... That should put some coffin nails to Redmi note 12 Pro.
x3r0.13urn said:
I bet if the buyers smart enough, they'll mostly will pass buying this. The price is closer to almost a mint second hand of Poco F4, offering almost better in everything except for maybe the main sensor (ov64b vs. imx766). And here we are Poco F4 has already a headstart in custom rom community.
And if you're willing to let go the OIS, Poco F3 isn't that bad either, price nowadays should be the same, its only disadvantages are slower charging and again, main sensor (imx586 vs imx766).
And the last, not to mention that Poco F5 is just around the corner... That should put some coffin nails to Redmi note 12 Pro.
Click to expand...
Click to collapse
the phone is just released, how could you put the nail? we haven't seen any development for this phone yet.
try Pixel Experience GSI: https://github.com/ponces/treble_build_pe/releases
groovepeppy said:
the phone is just released, how could you put the nail? we haven't seen any development for this phone yet.
Click to expand...
Click to collapse
What I said was: if you're looking for a particular good phone with a good custom roms support, and if you want it now, or very quickly from now, Poco F4 is already here, and its price is very close to Note 12 Pro with same feature and even more potent SoC. And if custom roms in Poco F4 aren't adequate, there's also Poco F3, its community is more active than F4, new one old stock F3 should be priced similar to Note 12 Pro, only if you're willing to loose the fast 67w charger and OIS in Note 12 Pro.
But if you still want Note 12 Pro with custom rom... Well, that's up to you. I didn't say it wouldn't see any custom rom, it just... looks less interesting than the others two.
Redmi Note 8 Pro is the most active for MTK device as far as I know, and for more two years consecutive after its release, it was ridden by a lot of issues. It was ironed out very lately, just after A12 out, and sadly most people has already moved out. Another one was Redmi Note 9 and Redmi 9, merlin and lancelot, again, most their roms stay on A11 firmware because latest A12 firmware gives a lot of headache. I've seen some development on Note 10s (evoX) and Poco M4 Pro (ported roms?), which those are MTK, but again, they're very slow and they had been released earlier than Note 12 Pro, but to be honest, those devices didn't bring the same attractive to Note 12 Pro.
If those aren't providing enough for arguments... Its closest rival is their own Poco X5 Pro, which again uses more common and widespread soc in custom rom community, the SD 778g, which it has some development on similar device such Mi 11 Lite 5g. Xiaomi 12 Lite also uses SD 778g, still hasn't seen any development yet.
tl;dr: there are many xiaomi devices, even the "flagship" Xiaomi 12 or Xiaomi 12 Pro, has yet seen any custom roms. I'd say: stick to existing community or any "its looks more guaranteed to be supported by community" devices rather than hoping this one would have one in the future.
x3r0.13urn said:
What I said was: if you're looking for a particular good phone with a good custom roms support, and if you want it now, or very quickly from now, Poco F4 is already here, and its price is very close to Note 12 Pro with same feature and even more potent SoC. And if custom roms in Poco F4 aren't adequate, there's also Poco F3, its community is more active than F4, new one old stock F3 should be priced similar to Note 12 Pro, only if you're willing to loose the fast 67w charger and OIS in Note 12 Pro.
But if you still want Note 12 Pro with custom rom... Well, that's up to you. I didn't say it wouldn't see any custom rom, it just... looks less interesting than the others two.
Redmi Note 8 Pro is the most active for MTK device as far as I know, and for more two years consecutive after its release, it was ridden by a lot of issues. It was ironed out very lately, just after A12 out, and sadly most people has already moved out. Another one was Redmi Note 9 and Redmi 9, merlin and lancelot, again, most their roms stay on A11 firmware because latest A12 firmware gives a lot of headache. I've seen some development on Note 10s (evoX) and Poco M4 Pro (ported roms?), which those are MTK, but again, they're very slow and they had been released earlier than Note 12 Pro, but to be honest, those devices didn't bring the same attractive to Note 12 Pro.
If those aren't providing enough for arguments... Its closest rival is their own Poco X5 Pro, which again uses more common and widespread soc in custom rom community, the SD 778g, which it has some development on similar device such Mi 11 Lite 5g. Xiaomi 12 Lite also uses SD 778g, still hasn't seen any development yet.
tl;dr: there are many xiaomi devices, even the "flagship" Xiaomi 12 or Xiaomi 12 Pro, has yet seen any custom roms. I'd say: stick to existing community or any "its looks more guaranteed to be supported by community" devices rather than hoping this one would have one in the future.
Click to expand...
Click to collapse
You got the point, you are right. MTK are very slow in development.
I've flashed 2 GSI ROM (Acient OS, Project Elixir) today.
For somehow, I can't flash vbmeta because it made phone to bootloop when I tried to go fastboot on cmd. Project Elixir is lastest version and it have this strange bug that can't connect to internet via wifi even with VPN and DNS Change. Everything is working fine.
But those two ROM have same issue sharing that's brightness can't be decrease or increase and Screen is flickering in every 5 sec or so.
I didnt test camera with GCam since I've to prepare for my work trip. I may write more later about them.
Xenolast said:
I've flashed 2 GSI ROM (Acient OS, Project Elixir) today.
For somehow, I can't flash vbmeta because it made phone to bootloop when I tried to go fastboot on cmd. Project Elixir is lastest version and it have this strange bug that can't connect to internet via wifi even with VPN and DNS Change. Everything is working fine.
But those two ROM have same issue sharing that's brightness can't be decrease or increase and Screen is flickering in every 5 sec or so.
I didnt test camera with GCam since I've to prepare for my work trip. I may write more later about them.
Click to expand...
Click to collapse
Do you succeed to flash Elixir?? if yes can you share your exact way of flashing...I have bootloop on MI logo..I flashed at least 15 times with different setup without success..thanks
Xenolast said:
I've flashed 2 GSI ROM (Acient OS, Project Elixir) today.
For somehow, I can't flash vbmeta because it made phone to bootloop when I tried to go fastboot on cmd. Project Elixir is lastest version and it have this strange bug that can't connect to internet via wifi even with VPN and DNS Change. Everything is working fine.
But those two ROM have same issue sharing that's brightness can't be decrease or increase and Screen is flickering in every 5 sec or so.
I didnt test camera with GCam since I've to prepare for my work trip. I may write more later about them.
Click to expand...
Click to collapse
Please try this, maybe it's a mediatek related GSI issue https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/post-87620773
it seems that MIUI 14 cause big problems to flash GSI.. A downgrade to MIUI 13 can solve it
rayman95 said:
it seems that MIUI 14 cause big problems to flash GSI.. A downgrade to MIUI 13 can solve it
Click to expand...
Click to collapse
I did flash with MIUI 14 and successfully.
I erase user data,system,cache and A/B partition too.
I would use them if I have time to solve all the problem for myself and I think it's usable as daily rom.
The only problem I face is I can't flash vbmeta and it cause me bootloop to fastboot.
And important things is if you are in fastboot mode, phone screen show as FASTBOOTD
if not you are still in bootloader.
I use
Fastboot getvar is-userspace
Before
Fastboot boot fastboot
Xenolast said:
I did flash with MIUI 14 and successfully.
I erase user data,system,cache and A/B partition too.
I would use them if I have time to solve all the problem for myself and I think it's usable as daily rom.
The only problem I face is I can't flash vbmeta and it cause me bootloop to fastboot.
And important things is if you are in fastboot mode, phone screen show as FASTBOOTD
if not you are still in bootloader.
I use
Fastboot getvar is-userspace
Before
Fastboot boot fastboot
Click to expand...
Click to collapse
Can you share your exact way to flash please. I don't want to erase one more time my device....for nothing and flash again miui...thanks
Xenolast said:
I did flash with MIUI 14 and successfully.
I erase user data,system,cache and A/B partition too.
I would use them if I have time to solve all the problem for myself and I think it's usable as daily rom.
The only problem I face is I can't flash vbmeta and it cause me bootloop to fastboot.
And important things is if you are in fastboot mode, phone screen show as FASTBOOTD
if not you are still in bootloader.
I use
Fastboot getvar is-userspace
Before
Fastboot boot fastboot
Click to expand...
Click to collapse
That doesn't sound as a working solution.
Your are writing .... If I have time to solve all the problem for myself ....
So what does that mean ?
And .....
I erase user data,system,cache and A/B partition too......
is also stupid. In a and b slots are the boot, vbmeta, system_vbmeta. So if you erased a and b slots, it can't boot without boot partition.
rayman95 said:
Can you share your exact way to flash please. I don't want to erase one more time my device....for nothing and flash again miui...thanks
Click to expand...
Click to collapse
I'm back from my trip and I will comment here my process and screenshots. I'm redownloading all tools and rom to my pc.
I'm one of the end user and I'm sorry if I confused you all with unclear method but I will try to describe every step I did.
I'm finding solution for screen flickering, auto brightness issue and no internet connection error.
Related
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.
So guyz since our redmi note 9 has a "Project treble" support,can we just directly flash any GSI custom rom from this link: https://forum.xda-developers.com/project-treble/trebleenabled-device-development ?! Or its still need a developer modification??
great question
In theory yes, but I had the experience of flashing only with the Adb commands and only on devices with "a only" slots it starts up but remember that the Redmi note 9 has two "a / b" slots so I flashed the other device and it asked me twrp and the file "copy partitions.zip" to start I suppose the same thing will happen on this device, we will wait, I can't test GSI on my note 9 because I have important information and I don't have time but I would already be making reports about it.
straikerxd said:
In theory yes, but I had the experience of flashing only with the Adb commands and only on devices with "a only" slots it starts up but remember that the Redmi note 9 has two "a / b" slots so I flashed the other device and it asked me twrp and the file "copy partitions.zip" to start I suppose the same thing will happen on this device, we will wait, I can't test GSI on my note 9 because I have important information and I don't have time but I would already be making reports about it.
Click to expand...
Click to collapse
Ah ok thx bro
Let me know if u managed to boot up a GSI rom on RN9 Merlin
MerlinTop1 said:
Ah ok thx bro
Let me know if u managed to boot up a GSI rom on RN9 Merlin
Click to expand...
Click to collapse
I Managed IT to boot 2 different gsis. Lineare OS 18 and caos Android 11. So i think GSI Roms are No Problem. But my Mobile Data was broken in gsis
I suggest you to keep on stock rom firmware only.
Root it with magisk. Flash it with twrp.
And everything is fine.
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Background: I had a MI A3 earlier and after 1 year of usage and researching a lot on forums I went a step ahead to unlock the bootloader. This incident prompted me to install custom recoveries and ROM's. Everything was good until the Android 11 dropped and it started hard-bricking devices. Now I was on custom rom and hence not in a position to install the official update immediately, this saved me from the hard brick. After all the menace was cleared by Xiaomi and I had installed the official Android 11 update, and I wanted to go back to customization. I had heard a lot of news in the telegram channels and on forums like XDA that the Android 11 firmware was a complete mess for developers to make custom ROM's , even TWRP could not be installed. Even rolling back to Android 10 was not an option as unlocking the bootloader and flashing the fastboot rom would brick the device. Thus I gave up my hope on customization. Now I have got myself a Redmi Note 10 Pro Indian variant, and after a thorough research my hopes are up again for customization.
Now my question is whether an android version update[(maybe android 12)(now I am coming across Redmi Note series phones getting two major Android version update since the Redmi Note 8 Pro)] on my Note 10 Pro would affect my ability to install TWRP(or any custom recovery) after unlocking the bootloader and later installing Custom ROM's ???
I would also like to know whether the Note 10 Pro has ARB enabled?
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
Have never needed to install a GSI before but as we're kind of stuck here without a single custom ROM, I thought I'd have a look.
AFAIK installing one of these would still leave the door open for stock recovery to be used should something go wrong, so as long as you've made a back up it should be fine.
I'm just curious as to the method of installation?
Has anyone had any experience with GSI ROMs before.
How was it? Did it work?
Would DSU image loader be an option?
I've attached what treble version we have and the relevant info required from the treble info app.
Apparently we have VNDK compatibility, not sure what that is but we have it.
Hi @dladz, I ran into a similar question three years ago when I bought a Xiaomi Mi 8 Pro. I was so used to using custom ROMs that I didn't even check before I bought it whether any custom ROMs would be available.
I was honestly shocked to see that that wasn't the case - there was absolutely NOTHING available - and that I had ended up with a device that couldn't even be unlocked right away, you had to wait and open a Mi account to be allowed to unlock it. I couldn't believe it at the time, I had come from a OnePlus X and had helped others root and install custom ROMs on other OnePlus phones without any problems, so I felt like I had just thrown quite some money out the window to run around with a mobile Chinese Spyware gadget I didn't want to use.
That was the first time I ever came across the term GSI ROM and it took me several weeks to figure out how to flash a ROM that I could also use afterwards. I knew I wouldn't want to have a stock ROM by a company that has very loose data privacy standards and even clearly states they collect your data (Lesson learned, I thought, I just had to buy a "proper" phone again and no more phones from budget manufacturers).
Several weeks later, after I had finally managed to get a custom GSI ROM working on my device I posted a lengthy how-to here on XDA.
Again, it took me weeks to get everything to work that I could not go without. And even then, I had to resign to the fact that many features of the phone would not be working (The fingerprint sensor, for example. Also, the Xiaomi Mi stock rom apparently had excellent GPS support (dual GPS support) but GPS positioning is just alright on the GSI ROM I'm using, also there were many cool Xiaomi apps like a compass app that wouldn't work outside MIUI). But I was more than happy I had gotten different GSI ROMs to work in the end and settled on one that I could live with, knowing my phone wouldn't be sending data to some Chinese servers constantly.
Now that the Mi 8 Pro has become a bit slower over time with all the latest apps, I took the plunge and spent a ton of money on the OnePlus 10 Pro 256 GB version only to be disappointed again, but this time by a company that used to be the epitome of openness when it came to custom development.
I got my OnePlus 10 Pro on release in my region in April, together with the 50W wireless charger and both have been sitting here since April, I'm not touching that phone until I can remove all the Spyware it comes installed with. At this stage, I'm not yet willing to go through the weeklong trial-and-error again that it took to get the Mi 8 Pro running a custom GSI ROM (also considering that some of its features never worked...), but if OnePlus doesn't get its **** together soon with the MSM tool and some openness towards developers, I will seriously just consider selling it on eBay again (It is brandnew after all) and will never buy another phone from OnePlus again. This has been an extreme disappointment and I'm still struggling to understand why they wouldn't support custom development any more. I had checked the OnePlus 9 Pro threads on XDA just to see if there's still custom development going on for OnePlus and it seemed everything was still OK, but now... .
On a more positive note: The Mi 8 Pro did eventually get some custom ROM love and there are now several ROMS to choose from, so to answer your original question - If you ask me, don't bother with GSI ROMs until we can be sure there won't be any custom ROMs for our phone. I'm still hoping that will be the case.
Gsi will work but no fingerprint or faceunlock.
Installing is easy just reboot to fastbootd open device with fastboot enchanted and delete all _cow files and reboot too bootloader flash stock vbmeta with
"fastboot --disable-verity --disable-verification vbmeta vbmeta"
Download gsi that you like and flash it in fastbootd using "fastboot flash system gsi.img"
MrScarl3t said:
Gsi will work but no fingerprint or faceunlock. And many more visual glitches.
Installing is easy just reboot to fastbootd open device with fastboot enchanted and delete all _cow files and reboot too bootloader flash stock vbmeta with
"fastboot --disable-verity --disable-verification vbmeta vbmeta"
Download gsi that you like and flash it in fastbootd using "fastboot flash system gsi.img"
Click to expand...
Click to collapse
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
MrScarl3t said:
Gsi will work but no fingerprint or faceunlock.
Click to expand...
Click to collapse
Unless someone posts a step-by-step guide with screenshots of a successful flash, I wouldn't believe anything.
This sounds more like it:
Twiggy000b said:
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
Click to expand...
Click to collapse
It took me weeks going back and forth, going back to stock and retrying again before I had any luck at all with my Mi 8 Pro.
Theoretically, it should work, but you can easily hard-brick your phone if you take one wrong turn and then goodbye to a phone with a premium price tag and no open MSM tool available... .
yo-less said:
It took me weeks going back and forth, going back to stock and retrying again before I had any luck at all with my Mi 8 Pro.
Theoretically, it should work, but you can easily hard-brick your phone if you take one wrong turn and then goodbye to a phone with a premium price tag and no open MSM tool available... .
Click to expand...
Click to collapse
Yeah was not happy said screw it and went back to google at least ive got lineage os now lol but still what a waste of 1k
Twiggy000b said:
Yeah was not happy said screw it and went back to google at least ive got lineage os now lol but still what a waste of 1k
Click to expand...
Click to collapse
Did you try sending it in?
I'll make a guide just like I did with the Xiaomi 11t pro. Post it within a week
Already did it when I got the device but I use the fingerprint alot so not for me.
Only tricky is reflashing system when you want to go for stock again.
nah i reached out and oneplus never got back to me.
sorry to hear that :/
Twiggy000b said:
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
Click to expand...
Click to collapse
What phone was you on mate??
MrScarl3t said:
I'll make a guide just like I did with the Xiaomi 11t pro. Post it within a week
Already did it when I got the device but I use the fingerprint alot so not for me.
Only tricky is reflashing system when you want to go for stock again.
Click to expand...
Click to collapse
That would be great, I'll be your test subject, I can live without fingerprint and face unlock.
Think the camera might be a bit meh but maybe I can live with that.
Another odd thing is I got treble check and it said I cannot use treble ROMs?
No idea if that's true but that's what the app said.
dladz said:
That would be great, I'll be your test subject, I can live without fingerprint and face unlock.
Think the camera might be a bit meh but maybe I can live with that.
Another odd thing is I got treble check and it said I cannot use treble ROMs?
No idea if that's true but that's what the app said.
Click to expand...
Click to collapse
Yeah camera is gcam but the main sensor is fine with it.
Every OnePlus 10 pro works with gsi, and general boot images as well. I will start tomorrow making the guide.
Will test if you can use rollback zip to get back to stock
Here you go https://forum.xda-developers.com/t/how-to-flash-a-gsi-on-oneplus-10-pro-t.4479429/
MrScarl3t said:
Here you go https://forum.xda-developers.com/t/how-to-flash-a-gsi-on-oneplus-10-pro-t.4479429/
Click to expand...
Click to collapse
Legend