Related
Hello everyone, i installed the leaked soak test with the "apply update from SD card" on stock recovery after locking my bootloader.
One week later, i unlocked it again and flashed TWRP for rooting with magisk.
Even with root tweaks i still face problems with soak 8.1, due to the lack of custom kernels.
So i decided to flash Stock N (1st April) with the TWRP Flashable zip from @Jleeblanch , how i avoid IMEI loss doing that? If i backup Oreo's EFS with TWRP, it will be compatible if i try to restore it after flashing, or it's not even necessary?
The TWRP flashable zip files by @Jleeblanch does not have the commands "fastboot erase modemst1" and "fastboot erase modemst2" so your IMEI will be fine. However Stock Oreo does mess up with IMEI.
Flash TWRP flashable Stock Nougat by Jleeblanch. You will not lose IMEI, but there will still be a problem of persist (i.e you will lost IMEI if you flash Stock ROM via fastboot). So to fix persist, follow this thread: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
Losing IMEI is a persist related problem (Soak Test 8.1, and all 64bit Pie ROMs are causing this). So if you fix persist, then you will never lose IMEI.
I recommend you to take backup of EFS before this process (i.e while having a bad persist and working EFS) and also after fixing persist (i.e while having a good persist and working EFS).
EFS backup by Lyuu's TWRP takes a backup of EFS, fsg and persist.
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Heeth21 said:
The TWRP flashable zip files by @Jleeblanch does not have the commands "fastboot erase modemst1" and "fastboot erase modemst2" so your IMEI will be fine. However Stock Oreo does mess up with IMEI.
Flash TWRP flashable Stock Nougat by Jleeblanch. You will not lose IMEI, but there will still be a problem of persist (i.e you will lost IMEI if you flash Stock ROM via fastboot). So to fix persist, follow this thread: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
Losing IMEI is a persist related problem (Soak Test 8.1, and all 64bit Pie ROMs are causing this). So if you fix persist, then you will never lose IMEI.
I recommend you to take backup of EFS before this process (i.e while having a bad persist and working EFS) and also after fixing persist (i.e while having a good persist and working EFS).
EFS backup by Lyuu's TWRP takes a backup of EFS, fsg and persist.
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat.
Click to expand...
Click to collapse
Rajat's 64bit TWRP doesn't have EFS Backup option here. I will try Lyuu's
Thanks for the help.
xSamukaBRx said:
Rajat's 64bit TWRP doesn't have EFS Backup option here. I will try Lyuu's
Thanks for the help.
Click to expand...
Click to collapse
Read the second post again, I have edited it.
Heeth21 said:
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Click to expand...
Click to collapse
I kinda fear it auto-updating, so i'll make sure to delete the "3c_ota" app from /priv-app
EDIT: Already know the risks of taking OTA with unlocked bootloader or after downgrade...
Heeth21 said:
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Click to expand...
Click to collapse
What about Lineage-based 7.1.2 32 bits ROMs? Can i flash them without issue? Already flashed Stock N
with TWRP, and It worked fine. Just want to know.
Please don't tell me i need the fastboot Stock N, i can't flash that anymore i think. :crying:
xSamukaBRx said:
What about Lineage-based 7.1.2 32 bits ROMs? Can i flash them without issue? Already flashed Stock N
with TWRP, and It worked fine. Just want to know.
Please don't tell me i need the fastboot Stock N, i can't flash that anymore i think. :crying:
Click to expand...
Click to collapse
Yes you can flash Custom ROMs from TWRP, however, I don't think you should right now.
I got my device hard bricked randomly from Custom ROM. idk what caused it, maybe some changes which I did or something else. If a similar thing were to happen with you, there's no guarantee whether the current blankflash would work or not.
Heeth21 said:
Yes you can flash Custom ROMs from TWRP, however, I don't think you should right now.
I got my device hard bricked randomly from Custom ROM. idk what caused it, maybe some changes which I did or something else. If a similar thing were to happen with you, there's no guarantee whether the current blankflash would work or not.
Click to expand...
Click to collapse
Even through i just want a pure lineage OS instead of a custom based on it (too many stuff comes with a risk, right?), i better not try...
hi all, as people are posting tutorial to downgrade from pie to oreo with the help of restoring boot and efs folder uploaded by them,, is it safe to restore from someone's else twrp backup i mean efs folder??
as per my knowledge efs is backup of imei right?
so restoring from someone's else efs won't affect mine imei?
No help here?
??????????????????????????????/
i don't think so people are helpful here or either not expert as nobody is replying lol
No idea. Sorry
taran181 said:
hi all, as people are posting tutorial to downgrade from pie to oreo with the help of restoring boot and efs folder uploaded by them,, is it safe to restore from someone's else twrp backup i mean efs folder??
as per my knowledge efs is backup of imei right?
so restoring from someone's else efs won't affect mine imei?
Click to expand...
Click to collapse
4-6 months back there was thread why we should not restore efs of someone & proper tutorial for people who messed up their mac address with some kernel.
Now this tutorial on downgrading pie to oreo. I have no idea. Someone's efs would mess your IMEI, wifi mac, Bluetooth mac, thats what i think. But there are tutorial how to edit imei using some Qualcomm tool.
Ask @CosmicDan. He's the expert.
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
I was having an issue since using custom rom with december fw btw.
and I was mistaken flashing november fw back to solve some calling issue, so I ended up with no signal which should be came from I didn't restore dev's efs backup.
So I start from flashing full clean stock november and ended with bootloop on it, which is something I still curious what cause it.
At that times, I'm on locked bootloader and can't even enter edl to reflash the rom and can't unlock bootloader since the rom still not booting to enable oem unlocking option.
I don't remember what I have done to it, but at times my phone can boot with no signal, 0 imei on sim1 and null on sim2.
So I start to rewrite the imei then everything is back to normal.
Downgraded using the method of restoring boot and efs... Nothing changed for me, imei is the same as in the box of my mi a1. ? Maybe people did something before doing the downgrade that messed up something.
CosmicDan said:
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
Click to expand...
Click to collapse
@CosmicDan no flashing just oreo doesn't help, phone gets stuck in bootloop, so people has posted tutorial about flashing their efs and boot etc through twrp to get out of bootloop.
Eg: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
fhsd22 said:
Downgraded using the method of restoring boot and efs... Nothing changed for me, imei is the same as in the box of my mi a1. ? Maybe people did something before doing the downgrade that messed up something.
Click to expand...
Click to collapse
but my question why use someone's else efs while downgrading, as efs contains imei and modem backup ..
taran181 said:
@CosmicDan no flashing just oreo doesn't help, phone gets stuck in bootloop, so people has posted tutorial about flashing their efs and boot etc through twrp to get out of bootloop.
Eg: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Click to expand...
Click to collapse
Well you can try it I guess, just backup the EFS partition and other stuff with my backup tool and you can always go back if worse comes to worst.
CosmicDan said:
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
Click to expand...
Click to collapse
Xiaomi put out a message on their forum that after the Pie update, the phone should not be rolled back. Its for all Android one models. When users flash an older roms, bootloops occur.
https://www.fonearena.com/blog/271177/xiaomi-pie-oreo-downgrading-disabled-android-one-devices.html
taran181 said:
but my question why use someone's else efs while downgrading, as efs contains imei and modem backup ..
Click to expand...
Click to collapse
But what he is saying is that he did downgrade EFS, but IMEI didn't change. This suggests that EFS isn't the original source of IMEI after all. Or maybe the bootloader can re-write IMEI and stuff on boot, who knows... Surely others have actually confirmed that EFS cross-flash = IMEI change, right? Not just assumed?
...point is, you can backup your EFS via EDL mode so there should be no risk. If you made a full EDL backup of your own device when you were still on Oreo then you would be golden, as EDL has full access to all partitions.
Just bought a new Xiaomi mi 6T device. My previous phone was a Sony Xperia m6. To unlock the bootloader and get root access was a bit of a pain on the latter. I remember having to backup a ta-partition to secure my DRM-keys.
Wanting to unlock the bootloader on this device I couldn't find any information about backing up and restoring a certain partition to secure the DRM-keys. What I did find was this post on the mi community forum about how unlocking the bootloader results in the widevine beïng downgraded from L1 to L3 (read the post for further details. The only way to reverse that process is to relock the bootloader again according to the the information I found.
So this is my question: Is there a way to keep the widevine L1 version, with better HDR performances, with an unlocked bootloader by backing up and restoring any data or partition on the phone that is responsible for widevine or other DRM content?
Medeon said:
Just bought a new Xiaomi mi 6T device. My previous phone was a Sony Xperia m6. To unlock the bootloader and get root access was a bit of a pain on the latter. I remember having to backup a ta-partition to secure my DRM-keys.
Wanting to unlock the bootloader on this device I couldn't find any information about backing up and restoring a certain partition to secure the DRM-keys. What I did find was this post on the mi community forum about how unlocking the bootloader results in the widevine beïng downgraded from L1 to L3 (read the post for further details. The only way to reverse that process is to relock the bootloader again according to the the information I found.
So this is my question: Is there a way to keep the widevine L1 version, with better HDR performances, with an unlocked bootloader by backing up and restoring any data or partition on the phone that is responsible for widevine or other DRM content?
Click to expand...
Click to collapse
No, you don't loose L1. You don't need to backup anything. You will allways have L1 with the official roms (global/eea) and L3 with all other at the moment including china official, xiaomi.eu and all forks.
e.g:
I have L1 with global rom, unlocked BL and magisk.
fabsen said:
No, you don't loose L1. You don't need to backup anything. You will allways have L1 with the official roms (global/eea) and L3 with all other at the moment including china official, xiaomi.eu and all forks.
e.g:
I have L1 with global rom, unlocked BL and magisk.
Click to expand...
Click to collapse
Thank you very much for confirming this, that's a huge relief! I also just found out about it reading this article.
Medeon said:
Thank you very much for confirming this, that's a huge relief! I also just found out about it reading this article.
Click to expand...
Click to collapse
I'm unlock and rooted, on L1, but u can't install Netflix from play store, so no full HD
I kinda anticipated that, since when you root your device with magisk, Android prevents you from installing Netflix. Which is no problem in my case, since I only watch Netflix on my television or Pc. You can watch Netflix though on an unlocked device if don't root your devices, isn't it?
I just installed magisk and remains L1. Just that the app doesn't appear on play store. Sideloeaded and got hdr working just fine.
i think only SONY has this problem with drm keys and widevine l1..if you unlock the bootloader of any SONY mobile said goodbye to this keys.And the hdr of the camera i think..
I only recommend that you back up the persist partition with TWRP if you are going to change the ROM on the Mi 9T. Some ROMs try to damage this partition and if it does you will Widevine L1 forever as I lost it
LeonardoBordin said:
I only recommend that you back up the persist partition with TWRP if you are going to change the ROM on the Mi 9T. Some ROMs try to damage this partition and if it does you will Widevine L1 forever as I lost it
Click to expand...
Click to collapse
Using OrangeFox and there is no checkmark to include Persist to Backup - screenshot attached.
I think it was the same with the official TWRP.
Which TWRP offers to backup Persist?
Btw, I was able to disk-dump Persist:
https://forum.xda-developers.com/mi-9t/how-to/to-extract-stock-boot-recovery-images-t4058447
But read somewhere (cannot find now and didn't try) that Persist.img cannot be flashed through Fastboot (?)
Medeon said:
Just bought a new Xiaomi mi 6T device. My previous phone was a Sony Xperia m6. To unlock the bootloader and get root access was a bit of a pain on the latter. I remember having to backup a ta-partition to secure my DRM-keys.
Wanting to unlock the bootloader on this device I couldn't find any information about backing up and restoring a certain partition to secure the DRM-keys. What I did find was this post on the mi community forum about how unlocking the bootloader results in the widevine beïng downgraded from L1 to L3 (read the post for further details. The only way to reverse that process is to relock the bootloader again according to the the information I found.
So this is my question: Is there a way to keep the widevine L1 version, with better HDR performances, with an unlocked bootloader by backing up and restoring any data or partition on the phone that is responsible for widevine or other DRM content?
Click to expand...
Click to collapse
No, but you will lose the safeties that could lead in to a persist partition corrupted.
Backup your persist partition and store this backup OUT of the phone, on a cloud or a PC.
Pupet_Master said:
No, but you will lose the safeties that could lead in to a persist partition corrupted.
Backup your persist partition and store this backup OUT of the phone, on a cloud or a PC.
Click to expand...
Click to collapse
The same question that was in the preceeding post:
Using OrangeFox and there is no checkmark to include Persist to Backup .
I think it was the same with the official TWRP
Which TWRP offers to backup Persist?
Btw, I was able to disk-dump Persist:
https://forum.xda-developers.com/mi-9t/how-to/to-extract-stock-boot-recovery-images-t4058447
But read somewhere (cannot find now and didn't try) that Persist.img cannot be flashed through Fastboot (?)
zgfg said:
The same question that was in the preceeding post:
Using OrangeFox and there is no checkmark to include Persist to Backup .
I think it was the same with the official TWRP
Which TWRP offers to backup Persist?
Btw, I was able to disk-dump Persist:
https://forum.xda-developers.com/mi-9t/how-to/to-extract-stock-boot-recovery-images-t4058447
But read somewhere (cannot find now and didn't try) that Persist.img cannot be flashed through Fastboot (?)
Click to expand...
Click to collapse
The chinese team TWRP
Pupet_Master said:
The chinese team TWRP
Click to expand...
Click to collapse
Pls link for that TWRP
Andd a question, official TWRP and OtangeFox properly support encryption - it is not needed to format Data, jus each time on booting to TWRPt to enter the current Android screen unlock pin/pass and they rrad/write to Internal storage
Is it also the case with the Chineer TWRP?
zgfg said:
Pls link for that TWRP
Andd a question, official TWRP and OtangeFox properly support encryption - it is not needed to format Data, jus each time on booting to TWRPt to enter the current Android screen unlock pin/pass and they rrad/write to Internal storage
Is it also the case with the Chineer TWRP?
Click to expand...
Click to collapse
If you will flash ANY different ROM, you NEED to format. since the ROM wont be able to access a encrypted data partition from another ROM/Encryption key.
Also, you can do a forum search for the chinese TWRP, i don't have the link
Good luck.
Pupet_Master said:
If you will flash ANY different ROM, you NEED to format. since the ROM wont be able to access a encrypted data partition from another ROM/Encryption key.
Also, you can do a forum search for the chinese TWRP, i don't have the link
Good luck.
Click to expand...
Click to collapse
Im absolutely not interested in custom ROMs (I only do rooting of the stock, and for that, as well as for official TWRP ahd OrangeFox, no kind of forkatting any partition is needed)
However, I have asked about Persist partitions just in case
Good luck
zgfg said:
Im absolutely not interested in custom ROMs (I only do rooting of the stock, and for that, as well as for official TWRP ahd OrangeFox, no kind of forkatting any partition is needed)
However, I have asked about Persist partitions just in case
Good luck
Click to expand...
Click to collapse
If you install stock MIUI but from a zip, such as xiaomi.eu is is a custom rom..
Stock is just what come with the phone.
Pupet_Master said:
If you install stock MIUI but from a zip, such as xiaomi.eu is is a custom rom..
Stock is just what come with the phone.
Click to expand...
Click to collapse
Tthank for teaching but I know what the stockk means
My Mi 9T came with v10.3.12 PFJEUXM, updated by OTA to v11.0.3 PFJEUXM and then again by OTA to v11.0.4 QFJEUXM.
Alll syock firmwares, no eu weekly ROMs and no AOSP ROMs (only debloating by ADB, twrp.me davincii TWRP, OranfeFox, Canary Magisk root and modules)
Instead of this OT discussion, I still did not get answers for sone originally asked questions but please nwm(for example about flashing from Fastboot the disk-dumped Persist.img)
Good luck and goodbye
zgfg said:
Tthank for teaching but I know what the stockk means
My Mi 9T came with v10.3.12 PFJEUXM, updated by OTA to v11.0.3 PFJEUXM and then again by OTA to v11.0.4 QFJEUXM.
Alll syock firmwares, no eu weekly ROMs and no AOSP ROMs (only debloating by ADB, twrp.me davincii TWRP, OranfeFox, Canary Magisk root and modules)
Instead of this OT discussion, I still did not get answers for sone originally asked questions but please nwm(for example about flashing from Fastboot the disk-dumped Persist.img)
Good luck and goodbye
Click to expand...
Click to collapse
fastboot a disk dump persist.img will cause you to lose DRM, i did it my self and i lost.
Pupet_Master said:
fastboot a disk dump persist.img will cause you to lose DRM, i did it my self and i lost.
Click to expand...
Click to collapse
What about
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
to backup and
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
to restore?
That's how I did it with my Moto G5+. Later the official TWRP recovery for that device had checkmarks for persist and efs too.
Edit: Sorry,I've seen that @zgfg posted that method so follow his steps:
https://forum.xda-developers.com/mi...ck-boot-recovery-images-t4058447/post81871363
Sent from my Moto G5 Plus using XDA Labs
You will lose DRM even with "dd" to restore (tested on Mi Mix 3 5G)
Hi guys,
I have a problem with my device. I recently had a problem with the sensors and I flash the persist.img of fastboot rom with twrp.
I lost WIDEVINE L1 and safetynet checks (only with ROM customs and without ROOT). I would like to know if there is a way to go back and "uncorrupt" the internal storage?
isman77 said:
Hi guys,
I have a problem with my device. I recently had a problem with the sensors and I flash the persist.img of fastboot rom with twrp.
I lost WIDEVINE L1 and safetynet checks (only with ROM customs and without ROOT). I would like to know if there is a way to go back and "uncorrupt" the internal storage?
Click to expand...
Click to collapse
No l1 is gone forever, sorry mate
Doesn't it bring the Global Rom "davinci_global_images_V10.3.11.0.PFJMIXM_20190802.0000.00_9.0_global_ea6683ef55.tgz" 3.3GB with MI PC Suite to flash?
And bring the phone back to its original state?
spedyy said:
Doesn't it bring the Global Rom "davinci_global_images_V10.3.11.0.PFJMIXM_20190802.0000.00_9.0_global_ea6683ef55.tgz" 3.3GB with MI PC Suite to flash?
And bring the phone back to its original state?
Click to expand...
Click to collapse
I have not tried with the MI PC suite, by cons I tried several times with Mi flash, without success ...
In your opinion, should I try with MI PC SUITE?
Benfatica said:
No l1 is gone forever, sorry mate
Click to expand...
Click to collapse
I tell myself that maybe with luck someone has a solution ...
Did you try the FASTBOOT file .tgz or the RECOVERY .zip?
There is no hope for us. Sorry
Wysłane z mojego Mi 9T przy użyciu Tapatalka
I'm sorry, I can't help but as someone who is looking at flashing a rom tomorrow, how do I avoid this from happening?
I would still like to use Netflix
spedyy said:
Doesn't it bring the Global Rom "davinci_global_images_V10.3.11.0.PFJMIXM_20190802.0000.00_9.0_global_ea6683ef55.tgz" 3.3GB with MI PC Suite to flash?
And bring the phone back to its original state?
Click to expand...
Click to collapse
It will flash back to factory settings and reset everything, I would backup and restore after doing so, with widevine though that will stay at level 3 and no chance of getting L1 back ever.
---------- Post added at 12:07 AM ---------- Previous post was at 12:01 AM ----------
BJozi said:
I'm sorry, I can't help but as someone who is looking at flashing a rom tomorrow, how do I avoid this from happening?
I would still like to use Netflix
Click to expand...
Click to collapse
Don't flash persist.img unless it's from your phone, backup with twrp, you could even connect the phone to your PC and copy the persist.img file to your PC and use that if anything happened, the problem is people are extracting the persist.img file from the ROM and it's not the original file for the phone and flashing to correct faulty sensors, this breaks widevine and doesn't restore regardless if a ROM supports it, the phone doesn't anymore because it's now basically corrupt and can't be restored unless using the original persist.img.
I'm not sure I fully understand.
So I've unlocked my bootloader, I'm about to flash Twrp and a custom rom such as Pixel Experience or Havoc.
Am I right in saying this will have broken it already?
Before flashing I should backup everything in Twrp, I can then reviver only the persist part after flashing a room and things will be as normal but with a different rom?
I made a backup of ALL partitions (including the partition persist) 3 months ago that I transferred to my PC and that I later deleted, if I manage to find it with software like Recuva and restoring with TWRP, would it work?
isman77 said:
I made a backup of ALL partitions (including the partition persist) 3 months ago that I transferred to my PC and that I later deleted, if I manage to find it with software like Recuva and restoring with TWRP, would it work?
Click to expand...
Click to collapse
I would say yes if you have the original files, you can try with those, if flashing from stock ROM that didn't belong to your phone then it won't work.
isman77 said:
Hi guys,
I have a problem with my device. I recently had a problem with the sensors and I flash the persist.img of fastboot rom with twrp.
I lost WIDEVINE L1 and safetynet checks (only with ROM customs and without ROOT). I would like to know if there is a way to go back and "uncorrupt" the internal storage?
Click to expand...
Click to collapse
how did you flash persist.img? i dont use netflix anyways and same thing happened to me that happened to you, i just want to get persist.img back, help?
I also lost it for the same sensors fix reason.
Has anyone tried restoring a twrp backup from a working L1 device?
Can someone with untouched persist that still has L1 upload a twrp backup of their persist partition, please?
It probably won't work as the l1 keys are linked to each device individually but we lose nothing for trying.
bihariel said:
I also lost it for the same sensors fix reason.
Has anyone tried restoring a twrp backup from a working L1 device?
Can someone with untouched persist that still has L1 upload a twrp backup of their persist partition, please?
It probably won't work as the l1 keys are linked to each device individually but we lose nothing for trying.
Click to expand...
Click to collapse
Have flash any persist image from the fastboot ROM?
Yep, that's what I did. I didn't know that would break L1 but I wasn't using it anyway.
bihariel said:
Yep, that's what I did. I didn't know that would break L1 but I wasn't using it anyway.
Click to expand...
Click to collapse
Then it's gone, you can't fix it
I know, but has anyone tried what I suggested?
bihariel said:
I know, but has anyone tried what I suggested?
Click to expand...
Click to collapse
Yes.
Hello,
In your opinion does the xiaomi warranty take care of this problem?
Summary of the thread:ANDROID 11 XIAOMI.EU ROMS AS OF CURRENT CORRUPT PERSIST PARTITION.
IF YOU HAVE LOST YOUR PERSIST BACKUP - COPYING PERSISTBAK TO PERSIST IS THE WAY, BUT REQUIRES CALIBRATION AFTERWARDS.
Original post:After spending some time with latest xiaomi.eu weekly I have finally decided to downgrade my phone back to Android 10.
First I've tried fastboot flashing CN 12.0.8.0 with subsequent recovery flash of xiaomi.eu stable 12.0.8.0 which is the latest stable Android 10 firmware.
However, to my surprise DRM Info showed Widevine L3.
Passwords & security -> Fingerprint unlock -> Fignerprint payments -> Widevine (L1) had:
Payment status - Not available
Certificate number - 0
Certificate update -
Pressing Download certificate resulted in Couldn't download certificate. Error code: 1.
Netflix also reported Widevine L3.
At this point I thought that maybe xiaomi.eu didn't have Widevine L1 support for my device back then, so I've tried latest xiaomi.eu weekly which still had Android 10 - 20.7.9.
Unfortunately, same story with that one.
Reading changelogs made me think that maybe support for Widevine L1 appeared only on Android 11 xiaomi.eu lmi releases, so I went for stock firmwares.
I've tried EEA 11.0.6.0 (I think this is the one I've had out of the box), EEA 12.0.3.0 and Global 12.0.4.0 all of which had Widevine L3. The earliest one didn't even have option for downloading Widevine certificate.
As soon as I've updated back to Android 11, I had my Widevine L1 restored, which makes me think that it is impossible to rollback Android version on Poco F2 Pro without loosing Widevine L1.
I've never tampered with persist or persistbak partitions. Maybe flashing persist with persistbak would solve my issues on lower firmwares?
Would be great if someone could confirm that.
So think twice before upgrading to Android 11. Mostly it's about improving DRM (hardware SafetyNet attestation, /data/ encryption, system components wrapped in .apex format files) with lots of features broken on MIUI (3rd party launchers are still kinda broken, though working, they have no support for custom recents menu and default one lags when used with non-default launcher).
It doesn't even have a proper documentation of changes that are required for old applications to work on it (most of them regarding permissions).
Originally my phone was in android 10 with Widevine L1.( V12.0.1.0.QJKMIXM )
I installed EU,Aosp,stock(android 10/11) roms and I always kept Widevine L1.
You may have gone a little too far in downgrade.
Regarding the stock roms, I always used Miflash.(because zip firmware,sometimes doesn't work with twrp).
.
NOSS8 said:
I installed EU,Aosp,stock(android 10/11) roms and I always kept Widevine L1.
Click to expand...
Click to collapse
This is strange, since I never messed with persist partition which is what determines Widevine. Yet my experience is not quite the same as yours.
NOSS8 said:
You may have gone a little too far in downgrade.
Click to expand...
Click to collapse
I've mentioned that, but let me reiterate, I've tried both the earliest (11.0.6.0.QJKEUXM) and latest (V12.0.3.0.QJKEUXM) available EEA official ROM that is still Android 10. Also I've tried latest available Android 10 Global ROM (12.0.4.0.QJKMIXM). No avail.
NOSS8 said:
Regarding the stock roms, I always used Miflash.(because zip firmware,sometimes doesn't work with twrp).
Click to expand...
Click to collapse
Not an issue in my case, since as I said, I've been flashing using fastboot, which mitigates recovery altogether.
Edit:
It appears I am not the only one, but it doesn't look like there is a solution unfortunately.
there have been some post about the loss of the L1 widevine with the first TWRPs also in root cases.
try with miflash ,Just to confirm..
In the rom fastboot (tgz) there is the perstist img
NOSS8 said:
there have been some post about the loss of the L1 widevine with the first TWRPs also in root cases.
try with miflash ,Just to confirm..
Click to expand...
Click to collapse
I don't have TWRP and never used it to flash but whatever, just for the sake of it, I've tried flashing with MiFlash the very same fastboot rom I flashed previously (lmi_eea_global_images_V12.0.3.0.QJKEUXM_20200923.0000.00_10.0_eea). Clean all - flash_all.bat.
Checked DRM Info - Widevine L3.
Fingerprint payments - same as before.
NOSS8 said:
In the rom fastboot (tgz) there is the perstist img
Click to expand...
Click to collapse
Yeah, I did notice that, but as far as I am concerned, it is not used in the flashing process. Upon inspecting flash_all.bat script I didn't find it mentioned at all!
P.S. Ignore red error message, I didn't want to lock the bootloader, so it didn't get to the checkpoint in the .bat file where it actually does that.
AlexJi said:
I don't have TWRP and never used it to flash but whatever, just for the sake of it, I've tried flashing with MiFlash the very same fastboot rom I flashed previously (lmi_eea_global_images_V12.0.3.0.QJKEUXM_20200923.0000.00_10.0_eea). Clean all - flash_all.bat.
Checked DRM Info - Widevine L3.
Fingerprint payments - same as before.
Yeah, I did notice that, but as far as I am concerned, it is not used in the flashing process. Upon inspecting flash_all.bat script I didn't find it mentioned at all!
P.S. Ignore red error message, I didn't want to lock the bootloader, so it didn't get to the checkpoint in the .bat file where it actually does that.
Click to expand...
Click to collapse
https://c.mi.com/thread-3260759-1-0.html
NOSS8 said:
https://c.mi.com/thread-3260759-1-0.html
Click to expand...
Click to collapse
It doesn't work, I've already wrote in the first post that "Pressing Download certificate resulted in Couldn't download certificate. Error code: 1."
Also check out my second screenshot.
Also read the last comment in the link you've provided.
AlexJi said:
It doesn't work, I've already wrote in the first post that "Pressing Download certificate resulted in Couldn't download certificate. Error code: 1."
Also check out my second screenshot.
Also read the last comment in the link you've provided.
Click to expand...
Click to collapse
I know, I saw afterwards.
I used this rom V12.0.3.0 in global and I had the L1 widevine.
maybe your phone that has a problem.
NOSS8 said:
I know, I saw afterwards.
I used this rom V12.0.3.0 in global and I had the L1 widevine.
maybe your phone that has a problem.
Click to expand...
Click to collapse
That's the thing, I also remember having that version prior to updating to Android 11 and having Widevine L1 intact.
AlexJi said:
That's the thing, I also remember having that version prior to updating to Android 11 and having Widevine L1 intact.
Click to expand...
Click to collapse
Is it an EEA or Global version?
NOSS8 said:
Is it an EEA or Global version?
Click to expand...
Click to collapse
It was EEA version. Back then there was no Android 11 for EEA/Global and I was only using OTA updates.
AlexJi said:
It was EEA version. Back then there was no Android 11 for EEA/Global and I was only using OTA updates.
Click to expand...
Click to collapse
Mine is a global one.
Maybe try to flash only global versions.(with miflash ).
Eu roms are better than stock.
NOSS8 said:
Mine is a global one.
Maybe try to flash only global versions.(with miflash ).
Click to expand...
Click to collapse
It's all the same. Apparently miflash doesn't do much apart from starting flash_all.bat script with provided minimal adb.
NOSS8 said:
Eu roms are better than stock.
Click to expand...
Click to collapse
That's true, but it doesn't solve my issue, since I have absolutely the same experience with eu stable and weeklies that are Android 10.
zip file
AlexJi said:
It's all the same. Apparently miflash doesn't do much apart from starting flash_all.bat script with provided minimal adb.
That's true, but it doesn't solve my issue, since I have absolutely the same experience with eu stable and weeklies that are Android 10.
Click to expand...
Click to collapse
Some people had lost the FOD due to bad handling, only miflash was able to get it back.
Tgz files are much bigger than zips and this is not a coincidence.
AlexJi said:
After spending some time with latest xiaomi.eu weekly I have finally decided to downgrade my phone back to Android 10.
First I've tried fastboot flashing CN 12.0.8.0 with subsequent recovery flash of xiaomi.eu stable 12.0.8.0 which is the latest stable Android 10 firmware.
However, to my surprise DRM Info showed Widevine L3.
Passwords & security -> Fingerprint unlock -> Fignerprint payments -> Widevine (L1) had:
Payment status - Not available
Certificate number - 0
Certificate update -
Pressing Download certificate resulted in Couldn't download certificate. Error code: 1.
Netflix also reported Widevine L3.
At this point I thought that maybe xiaomi.eu didn't have Widevine L1 support for my device back then, so I've tried latest xiaomi.eu weekly which still had Android 10 - 20.7.9.
Unfortunately, same story with that one.
Reading changelogs made me think that maybe support for Widevine L1 appeared only on Android 11 xiaomi.eu lmi releases, so I went for stock firmwares.
I've tried EEA 11.0.6.0 (I think this is the one I've had out of the box), EEA 12.0.3.0 and Global 12.0.4.0 all of which had Widevine L3. The earliest one didn't even have option for downloading Widevine certificate.
As soon as I've updated back to Android 11, I had my Widevine L1 restored, which makes me think that it is impossible to rollback Android version on Poco F2 Pro without loosing Widevine L1.
I've never tampered with persist or persistbak partitions. Maybe flashing persist with persistbak would solve my issues on lower firmwares?
Would be great if someone could confirm that.
So think twice before upgrading to Android 11. Mostly it's about improving DRM (hardware SafetyNet attestation, /data/ encryption, system components wrapped in .apex format files) with lots of features broken on MIUI (3rd party launchers are still kinda broken, though working, they have no support for custom recents menu and default one lags when used with non-default launcher).
It doesn't even have a proper documentation of changes that are required for old applications to work on it (most of them regarding permissions).
Click to expand...
Click to collapse
RECAP
MIUI 12 12.0.4.0 indonesian android 10 widewine is L1 ----- OTA update to 12.2.2.0 indonesian android 11 windewine is L1 --- downgrade to 12.0.4.0 indonesian android 10 windewine is still L1.
MIUI 12 12.0.4.0 indonesian android 10 widewine is L1 ----- Flashed Xiaomi.eu latest WEEKLY 21.2.4 android 11 widewine is L1 ---- downgrade to 12.0.4.0 indonesian causing lost widewine and showing L3.
Same as yours ---- Passwords & security -> Fingerprint unlock -> Fignerprint payments -> Widevine (L1) had:
Payment status - Not available
Certificate number - 0
Certificate update -
Pressing Download certificate resulted in Couldn't download certificate. Error code: 1.
It only happen on latest xiaome.eu to me, early version of xiaomi.eu rom was fine and L1 was there in downgrade to android 10.
Anyway i restore my original persist and persistbak and problem solved
Dadovvv said:
It only happen on latest xiaome.eu to me, early version of xiaomi.eu rom was fine and L1 was there in downgrade to android 10.
Anyway i restore my original persist and persistbak and problem solved
Click to expand...
Click to collapse
Oho, so what actually happens is that xiaomi.eu roms corrupt persist partition despite that they are flashed using recovery?
And if I don't have persist.img backup, I am basically screwed in terms of returning to Android 10 with Widevine L1 certification? Or is flashing persistbak.img to persist partition would be sufficient to revert the damage? I've noticed that persistbak has much less files than persist.
AlexJi said:
Oho, so what actually happens is that xiaomi.eu roms corrupt persist partition despite that they are flashed using recovery?
And if I don't have persist.img backup, I am basically screwed in terms of returning to Android 10 with Widevine L1 certification? Or is flashing persistbak.img to persist partition would be sufficient to revert the damage? I've noticed that persistbak has much less files than persist.
Click to expand...
Click to collapse
Persististbak is same as persist on stock ROM u have persist.img and persistbak.img and it's absolutely same file.
And yes latest xiaomi.eu ROM have something new in therms of widewine L1 so it editp persistimg I think
Dadovvv said:
Persististbak is same as persist on stock ROM u have persist.img and persistbak.img and it's absolutely same file.
And yes latest xiaomi.eu ROM have something new in therms of widewine L1 so it editp persistimg I think
Click to expand...
Click to collapse
Il let u know how many kB have original persist img from Indonesian ROM, but if u have different size probably persist.img is from xiaomi.eu and persistbak.img your original
EDIT : original persist.img in Indonesian is 65,536 KB
Dadovvv said:
Persististbak is same as persist
Click to expand...
Click to collapse
Not in my case. My persistbak seems to hold its original files, while persist clearly was modified.
Can you confirm how your original persist partition (the one you've backed up) looks like?
Here is a screenshot of my persist and persistbak contents.