Related
Hi all,
I just got my Mi MIX today (6gb version). I have been trying to get TWRP and SuperSU working on it, then flash the EU rom. During this process, my TWRP has become unresponsive. At the same time, my Wifi cannot be enabled. (I am installing EU rom because my Google Play Store download speed was throttled, and I could not find the option in Mi App Store to disable)
I am hoping that someone has a stock recovery I can flash, or knows how I can revert to stock. I have ADB and Fastboot installed.
I have tried re-flashing TWRP, and it does not work. I have also tried Fastboot -w to see if it helps. It instead shows me the screen asking to write to system again, instead of the main menu like before.
Any help is very appreciated! :crying:
go read the entire detailing how to install xposed, twrp, etc others have had similar things happen and there are instructions on what to type in fastboot to fix. just read the thread.
http://forum.xda-developers.com/mi-mix/how-to/guide-flash-global-china-rom-root-gapps-t3510592/page1
The OP in this thread has a comprehensive run through of how to install TWRP, EU ROM and root with Su. I suggest using the EU TWRP from the beginning as we found that it works best with the CN Stable ROM (8.0.11.0) .
Don't forget to root
Cheers
J
Sent from my MIX using XDA Labs
Hello,
I encountered the same problem (TWRP not responsible)
Solved with flashing this version of TWRP that work with latest EU ROM .
https://mega.nz/#!A91zFZqQ!AB1AB6HMaAtVS-2GQlUNgVXDtn-ZJej22rjEwJgVQlU
Try and tell me if it's OK ?
Thanks all! This is solved now Happy to be using my new Mi MIX!
4DM said:
Thanks all! This is solved now Happy to be using my new Mi MIX!
Click to expand...
Click to collapse
Glad to hear you have it working
Enjoy your Mix
Best
J
Sent from my MIX using XDA Labs
Hi there. I have the UK varient which is not the same as the us version. I'm looking for info regarding root and custom roms. All info I can find points toward the us (James) varient.
Any info or links greatly appreciated
ok so update, found this thread but not sure if the information is correct, thoughts or experiences please
https://forum.xda-developers.com/moto-e5/how-to/moto-e5-xt1920-15-pettyl-unlock-t3859586
mac_d4di said:
ok so update, found this thread but not sure if the information is correct, thoughts or experiences please
https://forum.xda-developers.com/moto-e5/how-to/moto-e5-xt1920-15-pettyl-unlock-t3859586
Click to expand...
Click to collapse
That's my thread and yes the information is correct.
If you are not sure yourself that the information I have posted is correct, then I suggest you stop thinking about rooting your E5 or flashing custom ROMs.
You have to remember no one has tested the rooting/flashing procedures on PETTYL.
Everything that's listed here on XDA is designed for James/Nora/Hanna devices so no one has tested anything on our devices as it's newer and not many have it.
All the GSIs (custom ROMs) are only listed as working on the James/Nora/Hanna devices, there is currently no support offered for PETTYL, although technically they should work.
The devs of those other devices and the resources for them claim everything should work on our E5 as its treble compatible, but unfortunately that's not quite correct.
If you are really not sure about anything, or don't know if information is correct, you will have problems.
Im not being mean.....I really don't want anyone else to have the problems I have had and really wouldn't advise anyone to go through the process as it's fraught with issues, bad explanations and lacking important information.
Some files are incorrect for our device and some listed procedures for the other devices do not work on our E5.
BTW-my device is an E5 play XT1920-15 PETTYL SIM unlocked purchased from Argos.
Here's a list of the issue I found, it might be different for someone else as two people are saying they successfully rooted their PETTYL, and I couldn't.......
1. I had no issues unlocking the bootloader.
2. There are two versions of TWRP posted on XDA for PETTYL, but neither worked for me.
I used the James version.
3. I could not root my device.
Magisk installed but I could not get v17.3 or v17.2 to flash.
V17.1 did flash but magisk manager showed device not rooted and magisk not installed.
4. Flashing any GSI (Oreo or Pie) causes problems to the system sounds, ringtones, notification tones and music which is totally distorted and very poor quality.
The camera has very poor quality as well.
5. Lineage OS 15.1 is the GO version, you also should flash lineage before flashing other GSIs as you can't flash most GSis over stock.
6. You can use the full Google apps on a couple of android 9 gsis which makes your device a normal android, not an android Go device, but I would recommend not to bother with Android 9.0 GSis for this device as they are very buggy and very slow, and they use three times more battery than android 8.1 Go.
Also, live wallpaper and notification access still don't work on android 9.
Just remember as well the US E5 is much more powerful than our E5, and I assume thats why android 9 runs so crap on our E5.
7. You have a very complicated process to get your Google account working on any GSI, if you do it wrong, you will not be able to use your Google account at all and will get spammed with never ending notification from Google of using an "uncertified device"
8. If you run into problems and decided to return to stock, you cannot download the "retail_GB" stock firmware (SIM unlocked) for PETTYL unless you pay for it....the EE and Tesco SIM locked firmware is free to download, but neither work on the SIM unlocked version if you use non EE or non Tesco SIM cards.
9. Someone has posted a twrp back up of rooted stick for PETTYL.
It did not boot on my device and just kept boot looping.
That could have been a twrp issue and nothing to do with the shared back up - I couldn't get back into a gsi or stock to test it.
My post is warning to other PETTYL users- with my own experience.
What you choose to do is up to you but I really would not bother tampering with it, leave it be.
Stock android Go 8.1 is way better than anything else that's currently available for PETTYL right now, every gsi I tried had an issue of some description that affected performance so badly they were practically unusable.
Even though I'm back on stock now I still have sound issues, and many graphic glitches that makes my screen flash and glitch out randomly.
I'm sorry it's such a long reply, I wanted to give you as much information as possible so you have some idea of what's involved for our device., And let's just hope the situation for our device will get better soon.
Thanks for your detailed reply, I only asked if this was correct as I was aware of the differences between models etc.
I wouldnt say im new to rooting cfw etc, I have been flashing phones since 2002 lol.
But I dont want to brick this device as its currently my only phone, so I will wait and see if the situation improves in the future.
Its not a bad phone as it is you get quite a lot of phone for £65 nowadays.
Oh and im using simlocked tesco model so free to download, I find it stupid that you have to pay for stock firmware its beyond belief
mac_d4di said:
Thanks for your detailed reply, I only asked if this was correct as I was aware of the differences between models etc.
I wouldnt say im new to rooting cfw etc, I have been flashing phones since 2002 lol.
But I dont want to brick this device as its currently my only phone, so I will wait and see if the situation improves in the future.
Its not a bad phone as it is you get quite a lot of phone for £65 nowadays.
Oh and im using simlocked tesco model so free to download, I find it stupid that you have to pay for stock firmware its beyond belief
Click to expand...
Click to collapse
Just like you, I've been rooting and flashing phones since like forever, and this device is the first I've ever had issues with.
It's entirety possible that as I'm a "noob" to flashing system images and fastboot flashing as apposed to flashing "ROMs" I may have messed up the procedures or made mistakes.
But not to be outdone, I have just before typing this reply tried again to root my E5 and flash a GSI, and again the process failed for me.
I could not boot into lineage OS 15.1 due to a "decryption error" and also couldn't get twrp to flash anything.
I've read now my issues are down to the DM Verity kernel which seems to be causing a lot of confusion amongst users and It now seems the process to remove forced encryption is what's causing all my issues.
I don't understand the process if I'm honest (it's an age thing lol) and worse, there is a lot of conflicting information, as a few people are saying the DM Verity process isn't necessary!!!
So unfortunately I've given up completely for now and stand by my original advice.
It's best to leave this particular device well alone until we have a proper procedure and tutorial in place for our own devices rather than trying to follow procedures for the US version.
I'm jealous though you only paid £65, as I paid £79.99, but I still think this Moto E is better than the Nokia 3 it replaced.
If any one can send me any issues they have with pettyl xt1920-15 rooting/twrp/etc I will try to test everything I can and see what works don't expect anything till January cause got college till the 23 and no time now
plscotland said:
If any one can send me any issues they have with pettyl xt1920-15 rooting/twrp/etc I will try to test everything I can and see what works don't expect anything till January cause got college till the 23 and no time now
Click to expand...
Click to collapse
That's very generous of you.
Like you, I don't get much time (due to work) but I have two weeks off from 21/12 and can supply as much information as you want.
I would like root if it's possible.
If some can check this twrp in fast boot by booting it and tell me dose it work on thier phone i be thankfull https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_04-33
plscotland said:
If some can check this twrp in fast boot by booting it and tell me dose it work on thier phone i be thankfull https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_04-33
Click to expand...
Click to collapse
I have a "working" 3.2.3 version for PETTYL but I'm not sure it's the version you linked
The one I have "works" in that it boots to TWRP fine from fastboot but obviously it doesn't flash.
I can't flash GSIs through that version, where they do flash no problems through fastboot......
Finally, I can flash magisk through that as even though magisk flashes successfully, magisk manager shows magisk is not installed and asks to flash it again.
@plscotland
TWRP - won't flash to recovery partition.
Cannot mount vendor to flash Fstab
Magisk flashes but magisk manager shows not installed.
I tried the twrp I sent you and the James version.
Lineage - I can successfully flash and boot lineage over stock (Phhusson version) but I have issues with "device not certified by Google" and get spammed by constant notification from Google
Cannot use for daily driver due to no nav bar orfind any settings to enable nav bar.
Descendants 1.0.5 - I have successfully flashed and booted this "rom" and used it but the sound from system ringtones and notification tones is awful and distorted
Lots of graphical glitches and system UI has stopped errors
Pixel experience - cannot flash - error whilst flashing that system IMG is bigger than target.
If I wipe data, it just bootloops and won't go past splash screen.
Resurrection remix - cannot boot
Bootleggers 3.0 - cannot boot
Hope some of this information helps you.
XT1920 - 15 retail GB firmware (SIM unlocked) stock android 8.1 go currently
bubba1601 said:
@plscotland
TWRP - won't flash to recovery partition.
Cannot mount vendor to flash Fstab
Magisk flashes but magisk manager shows not installed.
I tried the twrp I sent you and the James version.
Lineage - I can successfully flash and boot lineage over stock (Phhusson version) but I have issues with "device not certified by Google" and get spammed by constant notification from Google
Cannot use for daily driver due to no nav bar orfind any settings to enable nav bar.
Descendants 1.0.5 - I have successfully flashed and booted this "rom" and used it but the sound from system ringtones and notification tones is awful and distorted
Lots of graphical glitches and system UI has stopped errors
Pixel experience - cannot flash - error whilst flashing that system IMG is bigger than target.
If I wipe data, it just bootloops and won't go past splash screen.
Resurrection remix - cannot boot
Bootleggers 3.0 - cannot boot
Hope some of this information helps you.
XT1920 - 15 retail GB firmware (SIM unlocked) stock android 8.1 go currently
Click to expand...
Click to collapse
Thanks I check and send u how to boot resurrection remix later cause there are extra steps for it to work and fstab also has to be done in another way once IM off work I do a guide for it /Info helped a lot
plscotland said:
Thanks I check and send u how to boot resurrection remix later cause there are extra steps for it to work and fstab also has to be done in another way once IM off work I do a guide for it /Info helped a lot
Click to expand...
Click to collapse
Great, thanks
Qestion do u just want working magisek root on pettyl ?
There 2 ways
One download magisek manager
Get a twrp buckup of your boot image
Go to magisek manager choose patch boot image and choose your twrp buckup boot image (turn off compression of buckup when taking it ) after it finishes go find the patched boot image it should be in downloads or magisek folder can't remember then go to twrp and flash the patched boot image
/
Second way is to add the fstab or whater its called skip the adb mount part and only do the adb push part (look in tread for exact) https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 then flash the magisek 18.0 tell me did it work after. here the twrp that should work for every ones pettyl [ https://drive.google.com/file/d/1VsZRGkBujHay02a1M14eJM87H_RHFE9J/view?usp=drivesdk ] !Im not responsible if u brick your phone
!!try to boot twrp before u flash do fastboot boot (twrp image just drag the file to cmd to avoid path erors )
plscotland said:
Qestion do u just want working magisek root on pettyl ?
There 2 ways
One download magisek manager
Get a twrp buckup of your boot image
Go to magisek manager choose patch boot image and choose your twrp buckup boot image (turn off compression of buckup when taking it ) after it finishes go find the patched boot image it should be in downloads or magisek folder can't remember then go to twrp and flash the patched boot image
/
Second way is to add the fstab or whater its called skip the adb mount part and only do the adb push part (look in tread for exact) https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 then flash the magisek 18.0 tell me did it work after. here the twrp that should work for every ones pettyl [ https://drive.google.com/file/d/1VsZRGkBujHay02a1M14eJM87H_RHFE9J/view?usp=drivesdk ] !Im not responsible if u brick your phone
!!try to boot twrp before u flash do fastboot boot (twrp image just drag the file to cmd to avoid path erors )
Click to expand...
Click to collapse
Yeah, Ive been skipping the mount vendor and pushing Fstab via ADB whilst in twrp.
I'll give this twrp a whirl later this evening when my kids laptop is available
I've bricked my E5 and cannot get past "decryption unsuccessful."
Stock/los15/any other gsi I tried.
Reflashed stick but getting errors flashing gpt.partition.
Everything else then shows errors after each command.
Twrp- i followed your 1st step with a magisk altered boot image.
Tried second step and that failed.
I had to combine both steps into one and twrp then booted and flashed successfully to the recovery partition.
Adb pushed fstab before flashing twrp to recovery but once rebooted to stock I got "decryption unsuccessful" error and got into a bootloop.
Reflashed stock then los15.1 but same again.
Reflashed stock but gpt partition and system sparsechunk.2, 3 and 4 give errors.
Cannot flash stock or gsi currently or reboot to recovery, just keeps going back to fastboot.
bubba1601 said:
I've bricked my E5 and cannot get past "decryption unsuccessful."
Stock/los15/any other gsi I tried.
Reflashed stick but getting errors flashing gpt.partition.
Everything else then shows errors after each command.
Twrp- i followed your 1st step with a magisk altered boot image.
Tried second step and that failed.
I had to combine both steps into one and twrp then booted and flashed successfully to the recovery partition.
Adb pushed fstab before flashing twrp to recovery but once rebooted to stock I got "decryption unsuccessful" error and got into a bootloop.
Reflashed stock then los15.1 but same again.
Reflashed stock but gpt partition and system sparsechunk.2, 3 and 4 give errors.
Cannot flash stock or gsi currently or reboot to recovery, just keeps going back to fastboot.
Click to expand...
Click to collapse
in fastboot enter (use cmd powershell gives erorrs) fastboot -w
And then try rebooting it can take a while and tell me did it fix the problem
Recuperación TWRP 3.3.1-0-Pettyl
Hola buen día soy de Guadalajara México
A mí sí me funcionó está recuperación para rotear con magisk e instalar un mood de píxel.
La instalación de TWRP3.3.1-0-PETTYL Lo hice gracias a la aplicación Root essentials en el apartado flasher flasheando la imagen de la recuperación y ya dentro de la recuperación hice una copia de seguridad e instale magisk
Mi dispositivo es el Moto e5 play go pettyl XT1920-18
Heeeeeelp
(First Sorry for my bad english I'm a Brazilian boy with 17 years old only lmfao)Guys, I have only this little piece of s**** as my phone
#1 and this is not useable, it stop The apps constantely and freezes The system on simple apps (like play music and YouTube)... So I want to leave this cellphone in The trash can and walk away, but I cant make this because i have only this "bombphone"... Anywere can make an downgrade to Android 6.1 or 7.1 to this phone? Seriously I cant live with this phone in this situation. thanks and good night from Brazil
João klebão (supahjohn64) said:
(First Sorry for my bad english I'm a Brazilian boy with 17 years old only lmfao)Guys, I have only this little piece of s**** as my phone
#1 and this is not useable, it stop The apps constantely and freezes The system on simple apps (like play music and YouTube)... So I want to leave this cellphone in The trash can and walk away, but I cant make this because i have only this "bombphone"... Anywere can make an downgrade to Android 6.1 or 7.1 to this phone? Seriously I cant live with this phone in this situation. thanks and good night from Brazil
Click to expand...
Click to collapse
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
bubba1601 said:
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
Click to expand...
Click to collapse
thanks for the tips friend, i flashed some gases from android 9.0 and noticed that 90% of the performance improved which allowed me to played a little free fire lmfao so that unfortunately out of nowhere i faced some crashes and received the message from the user interface you are not responding, right now I am downloading the rom ressurrection remix oreo to see if it will work ... do you happen to know how to build a modified kernel? I have plans to make one for my cell phone but I don't know where to start. obrigado pelas dicas!!!! boa noite do brasil:good:
---------- Post added at 11:14 PM ---------- Previous post was at 11:09 PM ----------
bubba1601 said:
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
Click to expand...
Click to collapse
thanks for the tips friend,
I already work in some way with custom roms since 2013 when I had my lg l1 2 lmfao... i flashed some gases from android 9.0 and noticed that 90% of the performance improved which allowed me to played a little free fire lmfao so that unfortunately out of nowhere i faced some crashes and received the message from the user interface you are not responding, right now I am downloading the rom ressurrection remix oreo to see if it will work ... do you happen to know how to build a modified kernel? I have plans to make one for my cell phone but I don't know where to start. obrigado pelas dicas!!!! boa noite do brasil
My new MI8 SE is not my daily use, so I got time to check all available MIUI custom rom (eu,Globe,MiRum,Miuipro,Ros,MS and Masik 1.8.)
At this point no problem, they install very well and they answer my needs.
BUT:
AS EVERYBODY should know that it is very easy to delete the central Password and finger print by the mean of our sophisticated tool (I mean TWRP).
In order to be safe '(without turning back to stock rom) I tried to encrypt the phone WITHOUT success...
Process failed every time with different results (full reset, logo loop for hours, partial encrypt for data only). But was always the point that minimum security can't be reached!
Question:
-Can you well sleep If you mind that you are having all your precious data available in the wind as soon your phone is lost or stolen or even worst let in some bad friends hands...? It takes 1 mn to delete the file without any computer.
I see a partial solution by installing afterward a stock recovery that does allow to trick the system file.
(If somebody has it, I am available to test this option, but don't tell me to flash a stock rom as solution!!)
Your comments/solutions are welcome.
You can have encryption with custom ROM, if the corresponding kernel enabled built-in force encryption.
I'm currently running phh treble 9.0 encrypted, with stock kernel patched by this script:
https://forum.xda-developers.com/an...rceencrypt-t3817389/post77572812#post77572812
NexusRunner said:
You can have encryption with custom ROM, if the corresponding kernel enabled built-in force encryption.
I'm currently running phh treble 9.0 encrypted, with stock kernel patched by this script:
https://forum.xda-developers.com/an...rceencrypt-t3817389/post77572812#post77572812
Click to expand...
Click to collapse
Thanks for taking care of my post.
This is old now.
I've investigated a bit more and found ways to get MIUI custom ROM encrypted. (for now I want to stay with MIUI stuff!)
I know that almost all AOSP like rom may well encrypt from first install.
My aim was and is still to warn people that without encrypt their phone are open like a lost book.
Thanks for the very interesting and documented thread (link) you directed me to.
lolo9393 said:
Thanks for taking care of my post.
This is old now.
I've investigated a bit more and found ways to get MIUI custom ROM encrypted. (for now I want to stay with MIUI stuff!)
I know that almost all AOSP like rom may well encrypt from first install.
My aim was and is still to warn people that without encrypt their phone are open like a lost book.
Thanks for the very interesting and documented thread (link) you directed me to.
Click to expand...
Click to collapse
If you don't mind could you post a detailed guide to flash our Mi 8 Se. I tried once and got mine hard bricked and i'm scared to try again.
Our forum lacks detailed instruction and it's all hit and trial. And since you have had your hands dirty, could you do that?
me_death said:
If you don't mind could you post a detailed guide to flash our Mi 8 Se. I tried once and got mine hard bricked and i'm scared to try again.
Our forum lacks detailed instruction and it's all hit and trial. And since you have had your hands dirty, could you do that?
Click to expand...
Click to collapse
The process do not differ from other XIAOMI phone and is available at main forums.
Exemple:
https://xiaomi.eu/community/threads/9-1-24-26.48919/
or here
http://en.miui.com/search.php?mod=f...hsubmit=yes&kw=how+to+flash+custom+rom&month=
If you have specific issue with flashing process you are allowed to post in order to get support.
lolo9393 said:
The process do not differ from other XIAOMI phone and is available at main forums.
Exemple:
https://xiaomi.eu/community/threads/9-1-24-26.48919/
or here
http://en.miui.com/search.php?mod=f...hsubmit=yes&kw=how+to+flash+custom+rom&month=
If you have specific issue with flashing process you are allowed to post in order to get support.
Click to expand...
Click to collapse
Thanks Could you just point me the recovery you're using? that would be great, like exact recovery. I backed up my rom and then while restoring my device, it got hard bricked. :silly:
me_death said:
Thanks Could you just point me the recovery you're using? that would be great, like exact recovery. I backed up my rom and then while restoring my device, it got hard bricked. :silly:
Click to expand...
Click to collapse
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.
lolo9393 said:
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.
Click to expand...
Click to collapse
Thank you so much for all the help.
lolo9393 said:
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.
Click to expand...
Click to collapse
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:
me_death said:
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:
Click to expand...
Click to collapse
What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.24/25
me_death said:
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:
Click to expand...
Click to collapse
9. What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.14
lolo9393 said:
What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.24/25
Click to expand...
Click to collapse
I tried installing
https://xiaomi.eu/community/threads/9-2-14-15.49206/
Version: WEEKLY 9.2.15
me_death said:
I tried installing
https://xiaomi.eu/community/threads/9-2-14-15.49206/
Version: WEEKLY 9.2.15
Click to expand...
Click to collapse
That's OK!
you flash 9.2.15 with TWRP 1102 or 1217.
YOU DON't REBOOT THE ROM.
you flash twrp 1227 and THEN you reboot the rom and wait install finish, take some time be partient.
simple!
lolo9393 said:
That's OK!
you flash 9.2.15 with TWRP 1102 or 1217.
YOU DON't REBOOT THE ROM.
you flash twrp 1227 and THEN you reboot the rom and wait install finish, take some time be partient.
simple!
Click to expand...
Click to collapse
Finally i got it working following your instructions on the MIUI EU forum. Thanks a bunch. :victory: :highfive:
To others for reference. Following are the procedures that i followed to boot up Miui Eu :silly:
- Flash official 8.12.13 (Dev Fastboot Rom) through MiFlash.
- Flash TWRP 1102
- Clean Data
- Push/ Copy and Flash 8.12.20( EU Rom), it booted up finally without redirecting to Fastboot.
- Update 8.12.20 to latest available from system updater.
- Now there won't be any recovery or we aren't able to enter into available recovery even though the system boots.
- Flash TWRP 1227.
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
For some weeks now my Redmi Note 10 Pro has been facing severe lags. The lags appear regularly about each 5 sec. Then the video and audio or the UI freezes completly for about 1 sec, making it impossible to watch videos or making phone calls. I flashed several roms but it's the same issue everywhere. I even put back the phone in factory condition fashing MIUI and relocking the bootloader, but with no success. At the moment I am coming to the conclusion that I must have damaged my hardware somehow.
mi-girl said:
For some weeks now my Redmi Note 10 Pro has been facing severe lags. The lags appear regularly about each 5 sec. Then the video and audio or the UI freezes completly for about 1 sec, making it impossible to watch videos or making phone calls. I flashed several roms but it's the same issue everywhere. I even put back the phone in factory condition fashing MIUI and relocking the bootloader, but with no success. At the moment I am coming to the conclusion that I must have damaged my hardware somehow.
Click to expand...
Click to collapse
Try really clean flash with fw and formating data in TWRP with yes.
For example Los 19.1
mi-girl said:
For some weeks now my Redmi Note 10 Pro has been facing severe lags. The lags appear regularly about each 5 sec. Then the video and audio or the UI freezes completly for about 1 sec, making it impossible to watch videos or making phone calls. I flashed several roms but it's the same issue everywhere. I even put back the phone in factory condition fashing MIUI and relocking the bootloader, but with no success. At the moment I am coming to the conclusion that I must have damaged my hardware somehow.
Click to expand...
Click to collapse
Try stress testing to see where the issue is
Eg: https://github.com/aystshen/AndroidStressTest
Laptapper said:
Try really clean flash with fw and formating data in TWRP with yes.
For example Los 19.1
Click to expand...
Click to collapse
I did already many clean flashes. And as mentioned I even put the phone back to factory condition by flashing MIUI with Xiaomi Flash Tool.
mi-girl said:
I did already many clean flashes. And as mentioned I even put the phone back to factory condition by flashing MIUI with Xiaomi Flash Tool.
Click to expand...
Click to collapse
Factory reset won't help if fw is broken and and and....
Formating by manually typing yes in TWRP and firmware first then ROM and then formating is mandatory
RAMBO29 said:
Try stress testing to see where the issue is
Eg: https://github.com/aystshen/AndroidStressTest
Click to expand...
Click to collapse
Good idea! I have trouble installing the apk. It says "App not installed as package conflicts with an existing package." Not sure what package to delete. I have vanilla MIUI on my device. Unrooted and locked bootloader.
Laptapper said:
Factory reset won't help if fw is broken and and and....
Formating by manually typing yes in TWRP and firmware first then ROM and then formating is mandatory
Click to expand...
Click to collapse
I think you misunderstand me. As stated above I went through several ROMs and when reverting back to MIUI I used MIUI Flash Tool. It formates/wipes everything and installs the latest firmware/rom completely new. Besides that I did a "format data" after every custom rom installation.
mi-girl said:
I think you misunderstand me. As stated above I went through several ROMs and when reverting back to MIUI I used MIUI Flash Tool. It formates/wipes everything and installs the latest firmware/rom completely new. Besides that I did a "format data" after every custom rom installation.
Click to expand...
Click to collapse
Hmmm , did you've flashed manually the firmware in front of a custom ROM and the right one? I've destroyed my sweetin with wrong fw and now I've got a new sweet.
If here also your answer is yes then your phone can be repaired perhaps in a Xiaomi store....
Yes. I even tried several different firmwares. In the meantime I also did a CPU stress test it shows no problems.
mi-girl said:
Yes. I even tried several different firmwares. In the meantime I also did a CPU stress test it shows no problems.
Click to expand...
Click to collapse
Which Phone Modell you've got exactly?
Laptapper said:
Which Phone Modell you've got exactly?
Click to expand...
Click to collapse
sweet
mi-girl said:
sweet
Click to expand...
Click to collapse
Mee too
May you wanna try at last my actually running perfect config and exactly my steps....
Flash ofox 12.1_3
Format data with yes
Reboot twrp
Flash fw
Flash ROM (take screenshots of flashing progress for analysis)
Format data with yes
Reboot system
Fw, ofox attached
ROM
👍 [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 19.02.23/ checked by myself
Update on page 14 Update latest los 20 on page 7 I'm on pulkits android 13 for testing. Quiet good! Soon you'll get a beta! Thanks a lot to @Pulkit Agarwal Please donate him, thanks Update see post Post in thread '👍 [SHARED][ROM] [ANDROID...
forum.xda-developers.com
If this is not working too, your phone has a hardware prob....
Is it lagging when you are in airplane mode(WIFI scan issues) ? Or stressing CPU(IT'S not stuck in low frequency) ? Clear data from Gapps?
If this is clear and above steps are still same, as @Laptapper said suspect hardware.
I flashed back to custom ROM as described by @Laptapper. The problem still persists. Also with a downloaded 1080p video and airplane mode on. CPU Stress Tests shows no abnormalities.
Thanks for all the good ideas and the input. I will give this phone up. I probably screwed the hardware. Anyhow it was a nice time with this phone, the great community and custom rom support.