Related
Hi,
I was stupid not to take a complete backup through TWRP, but oh well.
After reflashing EUI 5.8.019S after I flashed the unofficial December update of EUI 5.9.20S, I discovered that my SIM card wasn't detected and that WiFi wasn't operational. I tried flashing EUI 5.8.015S, wiping, reflashing, OTA updates, flashing the modem separately and a host of other things to no avail. Should I get the device repaired as I'm still under warranty, or can I use fastboot or TWRP to fix this? Currently, I am on EUI 5.8.015S, and waiting for the first build @codeworkx's LineageOS so that I can see if this problem persists. Anyway, if anyone has a TWRP backup that they can upload, I'd be really grateful.
Flash volte fix
From kanak sharma
Availabke at rim thread by me rom thread is tittled unofficial eui 29s step by step guide
Even if nai hua pm me personally will solve the issue
Shrivaas73 said:
Hi,
I was stupid not to take a complete backup through TWRP, but oh well.
After reflashing EUI 5.8.019S after I flashed the unofficial December update of EUI 5.9.20S, I discovered that my SIM card wasn't detected and that WiFi wasn't operational. I tried flashing EUI 5.8.015S, wiping, reflashing, OTA updates, flashing the modem separately and a host of other things to no avail. Should I get the device repaired as I'm still under warranty, or can I use fastboot or TWRP to fix this? Currently, I am on EUI 5.8.015S, and waiting for the first build @codeworkx's LineageOS so that I can see if this problem persists. Anyway, if anyone has a TWRP backup that they can upload, I'd be really grateful.
Click to expand...
Click to collapse
jhakjhuk1853 said:
Flash volte fix
From kanak sharma
Availabke at rim thread by me rom thread is tittled unofficial eui 29s step by step guide
Even if nai hua pm me personally will solve the issue
Click to expand...
Click to collapse
I did that too, doesn't work. It's the one by Kanak Sharma, right? Well, no harm trying it again.
I'll PM you after this.
Shrivaas73 said:
Hi,
I was stupid not to take a complete backup through TWRP, but oh well.
After reflashing EUI 5.8.019S after I flashed the unofficial December update of EUI 5.9.20S, I discovered that my SIM card wasn't detected and that WiFi wasn't operational. I tried flashing EUI 5.8.015S, wiping, reflashing, OTA updates, flashing the modem separately and a host of other things to no avail. Should I get the device repaired as I'm still under warranty, or can I use fastboot or TWRP to fix this? Currently, I am on EUI 5.8.015S, and waiting for the first build @codeworkx's LineageOS so that I can see if this problem persists. Anyway, if anyone has a TWRP backup that they can upload, I'd be really grateful.
Click to expand...
Click to collapse
You can do 1 thing. Restore the phone into stock and then root it with twrp provided by @codeworkxx's.
Maybe it can help.
Thanks
Wrt
HB xt
Fixed ?
I'm sorry I didn't respond until now. Yes, I've fixed it. I repeatedly wiped and reflashed with various TWRP recoveries and even fastboot. After I flashed MIUI, wiped it and used stock recovery to flash EUI 5.8.019S, both WiFi and RIL started working. It's working fine now on LineageOS
I got my device yesterday and today i have been trying to flash legion os 2.11 but i always keep getting error 7 even tried by installing global rom through mi flash tool but still got error 7 from twrp and oxfox both.
Can someone just guide me clearly on flashing roms on this k20 pro.
Currently i using global miui 11 11.0.4.0 rom but want to try other custom roms as well..
Ezio553 said:
I got my device yesterday and today i have been trying to flash legion os 2.11 but i always keep getting error 7 even tried by installing global rom through mi flash tool but still got error 7 from twrp and oxfox both.
Can someone just guide me clearly on flashing roms on this k20 pro.
Currently i using global miui 11 11.0.4.0 rom but want to try other custom roms as well..
Click to expand...
Click to collapse
Try the latest TWRP from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you still get the same problem, report back in this thread.
Robbo.5000 said:
Try the latest TWRP from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you still get the same problem, report back in this thread.
Click to expand...
Click to collapse
yeah finally the twrp 3.4 unofficial worked fine from global miui 11 rom i wiped everything and flashed indian vendor-firmware file and then flashed rom with fcrypt zip file nd worked fine...
Thanks for suggesting this file i was using youtube videos as guide and everyone was using oxfox or older twrp..
Ezio553 said:
yeah finally the twrp 3.4 unofficial worked fine from global miui 11 rom i wiped everything and flashed indian vendor-firmware file and then flashed rom with fcrypt zip file nd worked fine...
Thanks for suggesting this file i was using youtube videos as guide and everyone was using oxfox or older twrp..
Click to expand...
Click to collapse
I've got a bit more time to reply now.
OFox is really designed to be used with MIUI. The majority of it's extra features are specific to running MIUI. I would only recommend it if you decide to stick with MIUI in the long run.
The TWRP I pointed to is from the dev who maintains the official TWRP for our device. The unofficial version you've installed is identical to the official version, but with the TWRP app removed. If you intend to stick with custom ROMs, I recommend you stick with TWRP from mauronofrio.
If you prefer to have your phone encrypted, then there was no need to flash fcrypt/DFE. There are a small number of users that continue to insist that we need to disable encryption, but it is not needed.
Having the phone unencrypted does make life a little easier when flashing, but if you prefer the security and want to know about living with an encrypted phone, reply back and I'll give you more details.
Robbo.5000 said:
I've got a bit more time to reply now.
OFox is really designed to be used with MIUI. The majority of it's extra features are specific to running MIUI. I would only recommend it if you decide to stick with MIUI in the long run.
The TWRP I pointed to is from the dev who maintains the official TWRP for our device. The unofficial version you've installed is identical to the official version, but with the TWRP app removed. If you intend to stick with custom ROMs, I recommend you stick with TWRP from mauronofrio.
If you prefer to have your phone encrypted, then there was no need to flash fcrypt/DFE. There are a small number of users that continue to insist that we need to disable encryption, but it is not needed.
Having the phone unencrypted does make life a little easier when flashing, but if you prefer the security and want to know about living with an encrypted phone, reply back and I'll give you more details.
Click to expand...
Click to collapse
I tried Legion Os which is Aosp based and it installed fine but then i tried Masik X 16 which again said this isn't for your device so had to make changes in updater script then it flashed fine.
Also i would like to know about decryption of storage and would it cause any issues in flashing roms again nd again..
Ezio553 said:
I tried Legion Os which is Aosp based and it installed fine but then i tried Masik X 16 which again said this isn't for your device so had to make changes in updater script then it flashed fine.
Also i would like to know about decryption of storage and would it cause any issues in flashing roms again nd again..
Click to expand...
Click to collapse
If you want to be permanently decrypted, then you will not have any problems flashing ROMs. However, whenever you need to update the vendor and firmware, you will also need to flash the DFE script again.
If you want to be encrypted, then the best thing to do, every time you flash, is to temporarily remove encryption by removing all lockscreen security just before flashing, then once you've finished, restore encryption by adding back lockscreen security. However, if you restore MIUI, then choose to go to another custom ROM, you will need to format the data partition when flashing over MIUI, even if you've removed lockscreen security first.
Robbo.5000 said:
If you want to be permanently decrypted, then you will not have any problems flashing ROMs. However, whenever you need to update the vendor and firmware, you will also need to flash the DFE script again.
If you want to be encrypted, then the best thing to do, every time you flash, is to temporarily remove encryption by removing all lockscreen security just before flashing, then once you've finished, restore encryption by adding back lockscreen security. However, if you restore MIUI, then choose to go to another custom ROM, you will need to format the data partition when flashing over MIUI, even if you've removed lockscreen security first.
Click to expand...
Click to collapse
Ok that means going from miui to aosp & vice versa - format data needed.
So this should similarly apply to all Miui based roms like xiaomi.eu or masik x or it is just for stock miui.
Ezio553 said:
Ok that means going from miui to aosp & vice versa - format data needed.
So this should similarly apply to all Miui based roms like xiaomi.eu or masik x or it is just for stock miui.
Click to expand...
Click to collapse
As far as I know, you only need to format data when flashing over official MIUI. I don't know the details, but it is my understanding that encryption on MIUI does not follow standard practice, which is why it it's necessary to format data when flashing over MIUI. I don't believe this issue exists with MIUI based custom ROMs, or when reverting back to MIUI.
Though, there may be occasions, when flashing from one AOSP ROM to another, and the phone is encrypted, when you may get a bootloop. In this case booting to TWRP and formatting data, will fix the problem. This is why I earlier recommended temporarily removing lockscreen security, if you choose to have an encrypted phone, even though this is a rare occurrence.
Robbo.5000 said:
As far as I know, you only need to format data when flashing over official MIUI. I don't know the details, but it is my understanding that encryption on MIUI does not follow standard practice, which is why it it's necessary to format data when flashing over MIUI. I don't believe this issue exists with MIUI based custom ROMs, or when reverting back to MIUI.
Though, there may be occasions, when flashing from one AOSP ROM to another, and the phone is encrypted, when you may get a bootloop. In this case booting to TWRP and formatting data, will fix the problem. This is why I earlier recommended temporarily removing lockscreen security, if you choose to have an encrypted phone, even though this is a rare occurrence.
Click to expand...
Click to collapse
Thanks for the info.
I tried custom miui rom and well flashing dfe worked fine so i think its just for official miui.
Hiya. So, here's the story:
Xiaomi Mi 9T Pro EEA, bought from Amazon, not a shady reseller
I made a Google Backup of my apps, because I decided to try out some Android 11 roms.
After trying them out, I wanted to go back to Android 10, so I clean flashed my rom, GApps and disable force encrypt, the usual stuff. But the Google Backup, that I previously used on all the A11 roms was suddenly gone.
I thought, that wouldn't be a problem, since I still had my Android 10 TWRP Backup that I made, before I started experimenting with A11.
I restored that backup and couldn't unlock my phone. So I deleted /data/system/locksettings.db and finally my phone would unlock.
But: My sensors didn't work anymore. I searched the internet for info and found out, that my persist partition got corrupted.
tl; dr: I restored a TWRP backup and my Persist partition corrupted.
Until yesterday, I didn't even know, what the Persist partition was. I never touched it.
I know how to get my sensors working again. But I guess my Widevine L1 is gone now, isn't it?
Seki_ said:
Hiya. So, here's the story:
Xiaomi Mi 9T Pro EEA, bought from Amazon, not a shady reseller
I made a Google Backup of my apps, because I decided to try out some Android 11 roms.
After trying them out, I wanted to go back to Android 10, so I clean flashed my rom, GApps and disable force encrypt, the usual stuff. But the Google Backup, that I previously used on all the A11 roms was suddenly gone.
I thought, that wouldn't be a problem, since I still had my Android 10 TWRP Backup that I made, before I started experimenting with A11.
I restored that backup and couldn't unlock my phone. So I deleted /data/system/locksettings.db and finally my phone would unlock.
But: My sensors didn't work anymore. I searched the internet for info and found out, that my persist partition got corrupted.
tl; dr: I restored a TWRP backup and my Persist partition corrupted.
Until yesterday, I didn't even know, what the Persist partition was. I never touched it.
I know how to get my sensors working again. But I guess my Widevine L1 is gone now, isn't it?
Click to expand...
Click to collapse
Yes, it's gone. Share what you did to get the sensors working.
mauam said:
Yes, it's gone. Share what you did to get the sensors working.
Click to expand...
Click to collapse
Unfortunate. Oh well.
There's actually multiple ways. You could:
Flash persist from Xiaomi's full fastboot package
Flash persistbak to persist
Flash a working persist image from another Mi 9T Pro
All those things worked for me. In the end, I settled with the persistbak method.
Seki_ said:
Unfortunate. Oh well.
There's actually multiple ways. You could:
Flash persist from Xiaomi's full fastboot package
Flash persistbak to persist
Flash a working persist image from another Mi 9T Pro
All those things worked for me. In the end, I settled with the persistbak method.
Click to expand...
Click to collapse
could you tell me how you flashed and dumped persistbak?
wavychris said:
could you tell me how you flashed and dumped persistbak?
Click to expand...
Click to collapse
It's almost been a year, so I don't fully remember what I did exactly, but there's some tutorials around you can find pretty easily.
The only thing I remember is going into fastboot and dumping and flashing my partitions via command line, I think.
Seki_ said:
It's almost been a year, so I don't fully remember what I did exactly, but there's some tutorials around you can find pretty easily.
The only thing I remember is going into fastboot and dumping and flashing my partitions via command line, I think.
Click to expand...
Click to collapse
ive been searching for a month and im still not sure which tutorial to follow, all i want is to fix my sensors and get widevine l1 back in case it gets void when i flash persist, any help would be phenomenal!
wavychris said:
ive been searching for a month and im still not sure which tutorial to follow, all i want is to fix my sensors and get widevine l1 back in case it gets void when i flash persist, any help would be phenomenal!
Click to expand...
Click to collapse
Well if you didn't make a backup before, L1 is L Gone. I didn't get it back. Following any tutorial should get you your sensors back though.
And remember: The first thing to do when getting a new phone is to backup that persist partition, so you don't need to worry about something like this happening again.
Seki_ said:
Well if you didn't make a backup before, L1 is L Gone. I didn't get it back. Following any tutorial should get you your sensors back though.
And remember: The first thing to do when getting a new phone is to backup that persist partition, so you don't need to worry about something like this happening again.
Click to expand...
Click to collapse
if i remember correctly you can get widevine l1 back via a magisk module or flashing xiaomi.eu rom and you can download the certificate from there, try it out if you dont got nothing to lose, by the way, if i flash persist will the sensors work permanently or do i have to do this again every once in a while?
wavychris said:
if i remember correctly you can get widevine l1 back via a magisk module or flashing xiaomi.eu rom and you can download the certificate from there, try it out if you dont got nothing to lose, by the way, if i flash persist will the sensors work permanently or do i have to do this again every once in a while?
Click to expand...
Click to collapse
Oh, interesting. Definitely gotta try that, thanks. How do you download the certificate in MIUI? Does it happen automatically?
Since I flashed my persistbak, I didn't flash anything else and my sensors are still working, so I guess it sporadically happens... sometimes?
Btw, if you aren't already, you should use OrangeFox recovery instead of TWRP on Xiaomi devices. It usually doesn't kill itself by wiping partitions or flashing roms, especially when coming from MIUI. Also, you can make persist backups with it. For some reason they removed that feature from TWRP.
Seki_ said:
Oh, interesting. Definitely gotta try that, thanks. How do you download the certificate in MIUI? Does it happen automatically?
Since I flashed my persistbak, I didn't flash anything else and my sensors are still working, so I guess it sporadically happens... sometimes?
Btw, if you aren't already, you should use OrangeFox recovery instead of TWRP on Xiaomi devices. It usually doesn't kill itself by wiping partitions or flashing roms, especially when coming from MIUI. Also, you can make persist backups with it. For some reason they removed that feature from TWRP.
Click to expand...
Click to collapse
in case you got it wrong xiaomi.eu is a custom miui based rom, not official, just to clarify that, and to download the certificate you must enroll fingerprint then go to fingerprint payments and youll find widevine l1 there, then click on certificate in widevine l1, pretty easy stuff, also how do i install orangefox?
wavychris said:
in case you got it wrong xiaomi.eu is a custom miui based rom, not official, just to clarify that, and to download the certificate you must enroll fingerprint then go to fingerprint payments and youll find widevine l1 there, then click on certificate in widevine l1, pretty easy stuff, also how do i install orangefox?
Click to expand...
Click to collapse
Oh, I can't read. For some reason, I thought you said xiaomi.eu or stock, that's why I said MIUI. Anyway, thanks for telling me. I never heard of that.
To install OrangeFox, just download the zip, make backups if you want to be extra sure and flash the zip. Here's the thread: https://forum.xda-developers.com/t/recovery-official-orangefox-recovery-project-r11-1.4308019/
The UI is different, so it took me a little while to get used to it, but ultimately, OrangeFox is a smoother experience than TWRP, at least on Xiaomi.
wavychris said:
if i remember correctly you can get widevine l1 back via a magisk module or flashing xiaomi.eu rom and you can download the certificate from there, try it out if you dont got nothing to lose, by the way, if i flash persist will the sensors work permanently or do i have to do this again every once in a while?
Click to expand...
Click to collapse
No, you cannot get L1 through Magisk module - because you need a (paid) certificate for your hardware
To the contrary, there is a Magisk module that disables L1, dropping you to default L3.
Although I never understood who/why needs that
wavychris said:
could you tell me how you flashed and dumped persistbak?
Click to expand...
Click to collapse
See here how to backup and/or dump Persist and restore/flash it back.
Of course, if you didn't backup a working Persist on time, you have nothing to restore:
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
Seki_ said:
Oh, I can't read. For some reason, I thought you said xiaomi.eu or stock, that's why I said MIUI. Anyway, thanks for telling me. I never heard of that.
To install OrangeFox, just download the zip, make backups if you want to be extra sure and flash the zip. Here's the thread: https://forum.xda-developers.com/t/recovery-official-orangefox-recovery-project-r11-1.4308019/
The UI is different, so it took me a little while to get used to it, but ultimately, OrangeFox is a smoother experience than TWRP, at least on Xiaomi.
Click to expand...
Click to collapse
its alright lol, thanks for your help btw have a nice day/night
zgfg said:
No, you cannot get L1 through Magisk module - because you need a (paid) certificate for your hardware
To the contrary, there is a Magisk module that disables L1, dropping you to default L3.
Although I never understood who/why needs that
Click to expand...
Click to collapse
that sucks man, thanks for the news anyway i might use xiaomi.eu rom to get it back that way at least
zgfg said:
See here how to backup and/or dump Persist and restore/flash it back.
Of course, if you didn't backup a working Persist on time, you have nothing to restore:
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
Click to expand...
Click to collapse
alright thanks i might try it out tommorow ill update you on the process if you want
I want to try out the xiaomi.eu rom this one (https://sourceforge.net/projects/xi...i_HMK20ProMI9TPro_21.1.20_v12-11.zip/download)
I am on evolution x 5.4
Anyone please guide me through the methods to flash it and also explain potential risks
Flashing it is simple just wipe everything except internal and flash this rom and magisk if u want.
If u are decrypted then flash fcrypt disabler to keep your storage decypted or u will need to format data.
But on latest eu build people have been facing bootloader locking issue u should go and check on thier telegram channel on how to fix if u get stuck on that.
Ezio553 said:
Flashing it is simple just wipe everything except internal and flash this rom and magisk if u want.
If u are decrypted then flash fcrypt disabler to keep your storage decypted or u will need to format data.
But on latest eu build people have been facing bootloader locking issue u should go and check on thier telegram channel on how to fix if u get stuck on that.
Click to expand...
Click to collapse
Thanks man
Will you please explain how to return back to aosp
Spidey_002 said:
Thanks man
Will you please explain how to return back to aosp
Click to expand...
Click to collapse
just wipe everything and then flash your region vendor and rom with fcrypt disabler and magisk if needed and reboot.
If u go for oss vendor roms u wont need to flash any vendor just rom file with fcrypt disabler and magisk if required..
Spidey_002 said:
I want to try out the xiaomi.eu rom this one (https://sourceforge.net/projects/xi...i_HMK20ProMI9TPro_21.1.20_v12-11.zip/download)
I am on evolution x 5.4
Anyone please guide me through the methods to flash it and also explain potential risks
Click to expand...
Click to collapse
Also i did try out the miui 12.5 a11 rom i don't remember the version but i had the problem where i will boot to fastboot everytime instead of recovery doesn't matter from rom or by using hardware keys. I don't know why i had that trouble but i decided to stay away from miui as lot of aosp roms are available to try out.
Ezio553 said:
Also i did try out the miui 12.5 a11 rom i don't remember the version but i had the problem where i will boot to fastboot everytime instead of recovery doesn't matter from rom or by using hardware keys. I don't know why i had that trouble but i decided to stay away from miui as lot of aosp roms are available to try out.
Click to expand...
Click to collapse
I faced the same issue after flashing so I reflashed orange fox again and everything works fine
is it possible to replace the app vault and package install manager in the eu rom with their global variants ?
I tried the above mentioned EU rom for a week or so. Battery life is attrocius. I expected the battery life to be better then stock since a lot of crap has been removed but to my horror, battery wouldnt last more then 3-4 hours of SOT. Phone was fully loaded like my regular installation...(I used get about 6-7 hours of SOT before unlocking the bootloader and installing eu rom..)
I flashed LineageOS 18.1 with no GApps (I'm using microG), and I haven't been able to use mobile data at all. No additional mods installed, and WiFi/Bluetooth work properly. Anything that I missed when flashing the ROM, or are there any other fixes I could try? Thanks.
KingSpammerNerd said:
I flashed LineageOS 18.1 with no GApps (I'm using microG), and I haven't been able to use mobile data at all. No additional mods installed, and WiFi/Bluetooth work properly. Anything that I missed when flashing the ROM, or are there any other fixes I could try? Thanks.
Click to expand...
Click to collapse
May be try downgrading the updated version to an lower version i.e "lineage-18.1-20210417-nightly-chef " or even lower , since newer versions sometimes come with an unexpected bug. The Android 11 ie LOS 18.1 has been around for around a month , so I expect them to have these smaller bugs, try contacting the Dev may be ?
Also did you flash your device as mentioned in the LOS webpage ? Reddit seems to recommend Mindthegapps (I might be wrong on this one) , and did you clean flash the device ?
I formatted data, cache and system, then clean flashed using TWRP. Strangely, I've also tried LOS 17.1 and had the exact same problem. Maybe I should clean flash again, but I want to try other solutions first.
KingSpammerNerd said:
I formatted data, cache and system, then clean flashed using TWRP. Strangely, I've also tried LOS 17.1 and had the exact same problem. Maybe I should clean flash again, but I want to try other solutions first.
Click to expand...
Click to collapse
Have you tried may be following the exact instructions on the LOS website ? Using LOS recovery and using the right Gapps ? clean install ? Maybe try installing LOS18.1 without Gapps.
If the issue persists try contacting the developer ,he usually responds.
Im on LOS17.1 February patch , no issue so far.
redbuck007 said:
Have you tried may be following the exact instructions on the LOS website ? Using LOS recovery and using the right Gapps ? clean install ? Maybe try installing LOS18.1 without Gapps.
If the issue persists try contacting the developer ,he usually responds.
Im on LOS17.1 February patch , no issue so far.
Click to expand...
Click to collapse
I'm currently using LOS 18.1 without GApps. LOS recovery hangs when I try to flash it, so I had to use TWRP. Followed the exact instructions, and everything besides data (calls, SMS) works without an issue. Dialling *#*#4636#*#* and checking IMS status gives me "IMS registration: Not registered", and my current "preferred network type" is LTE/WCDMA.
Maybe I should contact the devs, do they have an account on XDA?
Did you ever find a solution for this?