Related
Hey guys I wanna know about the Pie update I have mi Mi 8 Lite and as soon as i power up and conect to a wifi and update to 10.2.2.0 ODTMIXM was available so i updated and no problem i unlocked the bootloader (15 days wait time, sad) and flash twrp no root because is magisk and i can't hide root (even with magisk default hide root) for a bank app so is not rooted but since five days I was notified about and update to Pie miui 10.2.2.0PDTMIXM stable (persistent notification) but here are some questions:
* the twrp will cause a problem if I download this update and the updater applies or I have to remove twrp (I'll make a twrp backup just in case I don't have the original img file)
* I've read there no version of twrp for Pie and the version for 8.1 is not ideal. (correct me if i'm wrong)
* I might not need root, no problem the miui have some tweaks and I'm getting used to miui. (I had a Moto X Play with root and xposed and some modules)
* Is the first stable version, should I wait for a next Pie version with bugs solved.?
* I'm knew to miui less than a month with my Mi 8 Lite
orozcore said:
Hey guys I wanna know about the Pie update I have mi Mi 8 Lite and as soon as i power up and conect to a wifi and update to 10.2.2.0 ODTMIXM was available so i updated and no problem i unlocked the bootloader (15 days wait time, sad) and flash twrp no root because is magisk and i can't hide root (even with magisk default hide root) for a bank app so is not rooted but since five days I was notified about and update to Pie miui 10.2.2.0PDTMIXM stable (persistent notification) but here are some questions:
* the twrp will cause a problem if I download this update and the updater applies or I have to remove twrp (I'll make a twrp backup just in case I don't have the original img file)
* I've read there no version of twrp for Pie and the version for 8.1 is not ideal. (correct me if i'm wrong)
* I might not need root, no problem the miui have some tweaks and I'm getting used to miui. (I had a Moto X Play with root and xposed and some modules)
* Is the first stable version, should I wait for a next Pie version with bugs solved.?
* I'm knew to miui less than a month with my Mi 8 Lite
Click to expand...
Click to collapse
There's a TWRP for pie
mr_reaper said:
There's a TWRP for pie
Click to expand...
Click to collapse
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
orozcore said:
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
Click to expand...
Click to collapse
Which TWRP version u running?
mr_reaper said:
Which TWRP version u running?
Click to expand...
Click to collapse
sorry for the late reply the version i'm using is recovery-TWRP-3.2.3-1003-XIAOMI8LITE-CN-wzsx150
orozcore said:
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
Click to expand...
Click to collapse
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go. Mind you that version 1003 is older that the one you need. Due to bad naming scheme, the latest you want is 0212. (12 February 2019).
https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46
MetallicGR said:
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go. Mind you that version 1003 is older that the one you need. Due to bad naming scheme, the latest you want is 0212. (12 February 2019).
https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46
Click to expand...
Click to collapse
You might want to go with TWRP 0121 (also Pie compatible) instead, as someone reported in another thread having problems doing a restore with 0212 and nobody has yet verified if 0212 can actually do a successful restore. We are still a fairly small group here.
EDIT: Also, the stock Pie release is good. I am currently on Pixel Experience but may switch back to stock rooted at some point. Until Xiaomi releases the Pie kernel sources, no custom ROM is going to be perfect.
lexridge said:
You might want to go with TWRP 0121 (also Pie compatible) instead, as someone reported in another thread having problems doing a restore with 0212 and nobody has yet verified if 0212 can actually do a successful restore. We are still a fairly small group here.
Click to expand...
Click to collapse
Has anyone reported a successful restore with *any* version of TWRP on the Mi8 Lite? I have only seen the unsuccessful one you mentioned, and another one who couldn't restore with either 0121 or 0212. I have not tried it myself, and believe that most people are using TWRP only to flash magisk or custom roms so far.
---------- Post added at 02:39 AM ---------- Previous post was at 02:22 AM ----------
MetallicGR said:
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go.
Click to expand...
Click to collapse
The default settings in TWRP is to automatically restart the phone after an ota. As the ota overwrites the recovery with the stock version, we would normally need to reflash TWRP.
However the wzsx TWRP allows you to disable this automatic reboot in its settings. This should mean that we can reflash TWRP (and magisk if used) immediately after flashing the ota while still within TWRP, before restarting to the new system, thus avoiding the need for fastboot/PC.
This is just my theory - I haven't tried it myself as I haven't decided to do the pie ota yet.
chan200606 said:
Has anyone reported a successful restore with *any* version of TWRP on the Mi8 Lite? I have only seen the unsuccessful one you mentioned, and another one who couldn't restore with either 0121 or 0212. I have not tried it myself, and believe that most people are using TWRP only to flash magisk or custom roms so far.
---------- Post added at 02:39 AM ---------- Previous post was at 02:22 AM ----------
The default settings in TWRP is to automatically restart the phone after an ota. As the ota overwrites the recovery with the stock version, we would normally need to reflash TWRP.
However the wzsx TWRP allows you to disable this automatic reboot in its settings. This should mean that we can reflash TWRP (and magisk if used) immediately after flashing the ota while still within TWRP, before restarting to the new system, thus avoiding the need for fastboot/PC.
This is just my theory - I haven't tried it myself as I haven't decided to do the pie ota yet.
Click to expand...
Click to collapse
It is disturbing nobody has yet tested a TWRP restore. I would try it myself, but right now I cannot afford any long term downtime, as my mom is having health issues and I cannot take the chance of missing a call in case of emergency. .
Regarding flashing TWRP after update.... I certainly agree with your theory...and this could be done in either of two ways:
Method One, backup the Recovery only within TWRP. You MUST do this before taking the update!!! This lets you simply restore your existing recovery after the update. Not tested, but should work just fine assuming TWRP can indeed successfully restore (unknown).
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
i havent tried cause im still waiting on bootloader to be unlocked when i check earlier i had 124 hrs
lexridge said:
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
Click to expand...
Click to collapse
Why wouldn't you just flash the IMG file to the recovery partition under TWRP?
Not many people will shutdown their phones to test the restore guys. It's difficult, but we have to wait for someone to try this with the latest version of twrp. Nothing dusturbing here in my opinion. We will thank whoever tries this first that's for sure.
chan200606 said:
Why wouldn't you just flash the IMG file to the recovery partition under TWRP?
Click to expand...
Click to collapse
Interesting. I did not know you can flash img files directly with TWRP. Haha. Color me stupid!! How does TWRP know which partition to write the .img to? Does it give you a choice?
Yes it does. Choose recovery.
lexridge said:
It is disturbing nobody has yet tested a TWRP restore. I would try it myself, but right now I cannot afford any long term downtime, as my mom is having health issues and I cannot take the chance of missing a call in case of emergency. .
Regarding flashing TWRP after update.... I certainly agree with your theory...and this could be done in either of two ways:
Method One, backup the Recovery only within TWRP. You MUST do this before taking the update!!! This lets you simply restore your existing recovery after the update. Not tested, but should work just fine assuming TWRP can indeed successfully restore (unknown).
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
Click to expand...
Click to collapse
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
MetallicGR said:
Yes it does. Choose recovery.
Click to expand...
Click to collapse
good to know you can flash a img within twpr so i'll try when I update
mr_reaper said:
i havent tried cause im still waiting on bootloader to be unlocked when i check earlier i had 124 hrs
Click to expand...
Click to collapse
Yes is bad to wait so much time and there's nothing you can do I read about the version of the unlocker but with no luck. So I finally have unlocked bootloader.
Actually v0212 is restoring, I restored data from Arrow to Havoc and no problem with that.
Just all the recoveries and roms are acting weird, I´m not sure if it´s only my device; any AOSP rom is showing bootanimation at first reboot, recovery not responding touch but then press pwr button and after that screen works normally, at time to bootup for first time screen appears totally black then press pwr to screen off and pwr to wake up and now screen is working again, luckily at second reboot all this is normalize.
---------- Post added at 10:11 PM ---------- Previous post was at 09:52 PM ----------
orozcore said:
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
Click to expand...
Click to collapse
If you didn´t read before a member linked to you In the post #6 both TWRP versions.
About your steps:
- No need to backup previous TWRP, just flash the new image and reboot to recovery again.
- If you already have Magisk no need to flash it again so you won´t lose root status nor any data/settings of the rom.
If you want to unroot the 0212 has this option in advanced menu.
orozcore said:
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
Click to expand...
Click to collapse
You should probably update your TWRP first and foremost, otherwise no access to data after you flash the update.. You will also need the Magisk Manager as an apk somewhere on your microSD card. I edited your to-do list:
* Download Magisk Manager and store on your microSD card.
* Flash new TWRP (0212 or 0121).
* Make a full twrp backup and do a recovery only backup as well
* download the update
* let it update and hope no lost of data
* Reflash img or TWRP Recovery backup 0212 or 0121
* Reboot recovery, check that you can decrypt data
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
* After first boot, manually install your saved Magisk Manager app from microSD card. Run it. Check if all is good.
Do you use Titanium Backup? If so, make a full TB before doing any of this.
---------- Post added at 01:04 AM ---------- Previous post was at 12:42 AM ----------
SubwayChamp said:
Actually v0212 is restoring, I restored data from Arrow to Havoc and no problem with that.
Just all the recoveries and roms are acting weird, I´m not sure if it´s only my device; any AOSP rom is showing bootanimation at first reboot, recovery not responding touch but then press pwr button and after that screen works normally, at time to bootup for first time screen appears totally black then press pwr to screen off and pwr to wake up and now screen is working again, luckily at second reboot all this is normalize.
---------- Post added at 10:11 PM ---------- Previous post was at 09:52 PM ----------
Click to expand...
Click to collapse
Good to know that it is working for you. I will try a restore over the weekend myself, as I plan on getting rid of PE ROM. Not very happy with it, and the dev is not responding to anyone at all. I will probably just go back to stock PIE with alternate launcher.
Regarding your odd problems, I am not having any of your mentioned issues at all. My reboot times are very speedy and recovery touch has always worked from the start. I have only flashed one 3rd party ROM so far. Pixel Experience. It is actually a pretty good ROM, but the camera(s) are a bit flaky. I need my camera to work 100%. I did just install the MiX Cam, which so far is working really well. I have more testing to do before I make a decision. It seems camera apps work great for a few days, then suddenly start crashing. Ugh!
lexridge said:
Good to know that it is working for you. I will try a restore over the weekend myself, as I plan on getting rid of PE ROM. Not very happy with it, and the dev is not responding to anyone at all. I will probably just go back to stock PIE with alternate launcher.
Regarding your odd problems, I am not having any of your mentioned issues at all. My reboot times are very speedy and recovery touch has always worked from the start. I have only flashed one 3rd party ROM so far. Pixel Experience. It is actually a pretty good ROM, but the camera(s) are a bit flaky. I need my camera to work 100%. I did just install the MiX Cam, which so far is working really well. I have more testing to do before I make a decision. It seems camera apps work great for a few days, then suddenly start crashing. Ugh!
Click to expand...
Click to collapse
I never saw before this kind of weird behaviour btw is working generally speaking fine.
I´m not a fan of camera but the stock is so far better, I noticed that HavocOs rom has the feature to enable camera2 api and EIS, maybe you might try it. Regarding to use a custom launcher on stock miui rom there´s Poco launcher that keeps the same system icons than theme chosen and is very fast.
If you've flashed a non-stock recovery like TWRP*, you can not use the OTA update feature. You need to flash the full ROM via TWRP.
* TWRP is now officially supported, make sure you flash that version if you're using an older, unofficial TWRP.
1. Obtain the ROM you want to install. Make sure the download is from miui.com if you want stock
Official site -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab. The website does not update links immediately after a ROM update is released, so you may have to do a bit of digging if you want a very recent update.
You can also check ROM links on third party sites like ezbox.idv.tw, again, make sure the actual download links are from miui.com and not somewhere else.
Latest EEA ROM(Android 10) as of 2020-10-24 -
V12.0.3.0.QFJEUXM
Nightly official LineageOS builds
2. Get into TWRP
Either run 'adb reboot recovery'
Or power phone off and boot into TWRP by holding PWR+VOL_UP during boot
3. Upload the ROM to the phone
Code:
adb push ~/Downloads/[B]miui_DAVINCIEEAGlobal_V12.0.3.0.QFJEUXM_12b99693bc_10.0.zip[/B] /sdcard/
4. Flash the ROM via TWRP
5. Flash Magisk if you use it, because flashing the ROM deletes it.
6. Remove the update file:
Code:
adb shell rm /sdcard/[B]miui_DAVINCIEEAGlobal_V12.0.3.0.QFJEUXM_12b99693bc_10.0.zip[/B]
That's it! Reboot your phone into your new ROM!
Also check out my debloat list and my detailed phone settings.
Additional note - formatting /system will brick your phone and you'll have to recover using a fastboot ROM.
Please can I get the 10.3.15 ota zip for the official recovery I cant get the update and my phone is now on 10.3.12 it always say no update available even though I have done the update before and returned to 10.3.12 but it does show it to me again and also my otg doesn't work . please help me
Benfatica said:
Please can I get the 10.3.15 ota zip for the official recovery I cant get the update and my phone is now on 10.3.12 it always say no update available even though I have done the update before and returned to 10.3.12 but it does show it to me again and also my otg doesn't work . please help me
Click to expand...
Click to collapse
OTA zip is here => https://bigota.d.miui.com/V10.3.15....PFJEUXM-V10.3.15.0.PFJEUXM-14bc6a5788-9.0.zip
Micdu70 said:
OTA zip is here => https://bigota.d.miui.com/V10.3.15....PFJEUXM-V10.3.15.0.PFJEUXM-14bc6a5788-9.0.zip
Click to expand...
Click to collapse
Thanks,I was able to get it over ota but it doesn't come now has xiaomi removed it or something
I also get this message if I try to download the latest package. Is something wrong with my phone
It looks like the 10.3.15.0 update was pulled and 10.3.12.0 is now latest.
C0rn3j said:
It looks like the 10.3.15.0 update was pulled and 10.3.12.0 is now latest.
Click to expand...
Click to collapse
Ok thanks, but why though ??
My last update is 10.3.11.0 July security patch
C0rn3j said:
If you've flashed a non-stock recovery like TWRP, you can not use the OTA update feature. You need to flash the full ROM via TWRP.
So how to get around this when the updater is telling you there is an incremental update?
Simple, we tell the updater to download the full image instead, move the update from the original folder so MIUI won't attempt to upgrade from it on next reboot, boot into TWRP and flash the image there.
1. Settings -> About Phone -> System update -> three dots -> Download latest package
2. Get filename of the update:
3. You now have the filename of the update. I got miui_DAVINCIEEAGlobal_V10.3.15.0.PFJEUXM_b6738621e2_9.0.zip and will be using this name throughout the rest of this how-to, replace the examples accordingly based on what name you got.
4. (optional) Backup the latest ROM file to your PC:
5. Prevent MIUI from seeing the update file and trying to update from it on accident by moving the file a folder higher:
6. Power phone off
7. Boot into TWRP by holding PWR+VOL_UP during boot
8. Flash the ROM via TWRP
9. Flash Magisk if you use it, flashing the ROM deletes it.
10. Boot back into Android and remove the update file:
That's it!
You can also download the full ROM directly through miui.com, but keep in mind the website does not instantly update the link there after a ROM update is released.
https://en.miui.com/download-361.html#619 -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab.
Page best viewed in Firefox, clicking on the lock icon -> Arrow icon in the security tab -> Disable protection, since Xiaomi can't even set their website up properly.
In my case the ROM download through phone was corrupted and I had to edit the site URL from the filename I got to get a proper update file:
Click to expand...
Click to collapse
Redmi K20 Open Beta File Link?
Wrong thread.
Don't quote the OP, it clutters the thread.
For people who want the 10.3.15.0 update. I uploaded it to mega. Link is here:
https://mega.nz/#!pddQUaBL!s5En8LWaxWciUyNowU8_rYYMk2D48Dj8J7_PbJwv0kc
C0rn3j said:
...
https://en.miui.com/download-361.html#619 -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab.
Page best viewed in Firefox, clicking on the lock icon -> Arrow icon in the security tab -> Disable protection, since Xiaomi can't even set their website up properly.
...
Click to expand...
Click to collapse
The most accurate, updated and actual site for Mi 9t/K20 (davinci) firmware/rom - https://mirom.ezbox.idv.tw/en/phone/davinci/
10.3.15 ota is back online, just received it
Hey @C0rn3j
I am on stock 10.3.12.0 PFJEUXM and TWRP 4PDA 3.3.1.-2 fix and Magisk.
My questions:
1. Is it worth the upgrade to MIUI 11 as it is still Android 9
2. If I flash it through TWRP, did you loose any dual app settings? (as I lost dual apps while backing up the phone with TWRP and Titanium backup)
3. as you said I have to flash the Magisk again, did you choose the latest or the same as was installed on the phone before the upgrade?
Thanks in advance for reply
rastip said:
Hey @C0rn3j
I am on stock 10.3.12.0 PFJEUXM and TWRP 4PDA 3.3.1.-2 fix and Magisk.
My questions:
1. Is it worth the upgrade to MIUI 11 as it is still Android 9
2. If I flash it through TWRP, did you loose any dual app settings? (as I lost dual apps while backing up the phone with TWRP and Titanium backup)
3. as you said I have to flash the Magisk again, did you choose the latest or the same as was installed on the phone before the upgrade?
Thanks in advance for reply
Click to expand...
Click to collapse
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
C0rn3j said:
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
Click to expand...
Click to collapse
I have Nova Launcher, do you use default or as well external one?
Do you think Nova will stay untouched with this upgrade?
rastip said:
I have Nova Launcher, do you use default or as well external one?
Do you think Nova will stay untouched with this upgrade?
Click to expand...
Click to collapse
Nothing will happen to it
If the Magisk have to be flashed again, does it mean all the hide settings which were there before has to be set again or stay there from the old version? I have few apps in Magisk hide root, so just wondering how this will be affected with rom update
A second question:
I am on 10.3.12.0 not upgraded yet to 10.3.15.0.
Can I upgrade straight to V11.0.2.0 or first to 10.3.15.0 and then to V11?
---------- Post added at 05:27 PM ---------- Previous post was at 05:09 PM ----------
C0rn3j said:
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
Click to expand...
Click to collapse
While flashing did you untick Recovery in the TWRP as I believe the whole 2,2GB ZIP has recovery image and could be flashed and overwrite the TWRP?
Your guide not working, twrp failed to install the update "file corrupted".
I've downloaded the OTA package from "http://c.mi.com//miuidownload/detail?device=1700361" and twrp very happy to install this file, my Mi_9T at the latest update 11.
Unfortunately the archive downloaded through the Updater cannot be flashed as is through TWRP (message: file corrupted)
miui_RAPHAELEEAGlobal_V11.0.3.0.QFKEUXM_153f9511ae_10.0.zip
Just received the new update.
Thanks for notification, also just received it.
How to update with unlocked bootloader, TWRP and rooted with Magisk?
Download the hole update zip, flash it in TWRP and immediately Magisk afterwards?
bmwbasti said:
How to update with unlocked bootloader, TWRP and rooted with Magisk?
Download the hole update zip, flash it in TWRP and immediately Magisk afterwards?
Click to expand...
Click to collapse
Backup everything on your phone.
From what I understand; if you flash an OTA zip you'll end up on MIUI without root or TWRP unless, whilst still in TWRP after the zip has flashed, you immediately flash TWRP's image again along with Magisk without rebooting even once so that both persist.
That's if TWRP let's you flash whatever file ends up in /sdcard/downloaded_rom to begin with. Flashing MIUI zips - typically only supported by OrangeFox if I remember correctly. And if I'm right MIUI updater will download the full rom instead of an OTA if it detects a custom recovery.
I'd advise backing up everything before going ahead. If you want OTA your best bet might be to go on your PC and do "fastboot boot twrp.img" instead of "fastboot flash recovery twrp.img" then use the temporary TWRP to install the OTA zip and Magisk zip - that way it'll patch the stock bootloader.
I'd wait for someone with a little more knowledge though. I could be deathly wrong as I've only read this stuff and not updated MIUI with OTA before.
Hello Mi 9T Pro with Global ROM owners!
For someone who have installed V11.0.2.0QFKMIXM update and have ROOT => Can you please share these following two files "/vendor/lib/liboemcrypto.so" and "/vendor/lib64/liboemcrypto.so", thanks!
Micdu70 said:
Hello Mi 9T Pro with Global ROM owners!
For someone who have installed V11.0.2.0QFKMIXM update and have ROOT => Can you please share these following two files "/vendor/lib/liboemcrypto.so" and "/vendor/lib64/liboemcrypto.so", thanks!
Click to expand...
Click to collapse
https://drive.google.com/folderview?id=10zBJh6Ud8cqMykHSfrupENSc8w8C2tOz
The one named with -1 is lib64 version
And one camera bug.
In Spanish (Spain) language selected camera FC in pro mode.
In Spanish (America) all is ok.
here's the download link
https://bigota.d.miui.com/V11.0.2.0.QFKMIXM/miui_RAPHAELGlobal_V11.0.2.0.QFKMIXM_6050442ee4_10.0.zip
r4yv3n said:
https://drive.google.com/folderview?id=10zBJh6Ud8cqMykHSfrupENSc8w8C2tOz
The one named with -1 is lib64 version
And one camera bug.
In Spanish (Spain) language selected camera FC in pro mode.
In Spanish (America) all is ok.
Click to expand...
Click to collapse
Thanks! Can you post a screen of Widevine informations with "DRM Info" app? Thx again.
Any OTA at this time or just full rom?
Found ota file, downloading now
https://bigota.d.miui.com/V11.0.2.0...QFKMIXM-V11.0.2.0.QFKMIXM-a84af52957-10.0.zip
Micdu70 said:
Thanks! Can you post a screen of Widevine informations with "DRM Info" app? Thx again.
Click to expand...
Click to collapse
https://drive.google.com/file/d/10IJ_zGk77vxgeTpbOuR0GY9lhekbivSz/view?usp=drivesdk
?
This is from 11.0.1
I had to return back , stuck in fastboot ?
how much sot here?
I'm on miui 11.0.1 QFKMIXM and i am waiting for a month when 11.0.2 is available, but still now i dont have any new OTA update?? Why
Giangvo200837 said:
I'm on miui 11.0.1 QFKMIXM and i am waiting for a month when 11.0.2 is available, but still now i dont have any new OTA update?? Why
Click to expand...
Click to collapse
I think it's been withdrawn. It never officially came out of beta. They're still trying to fix a few minor Q bugs like battery drain and camera app issues; on top of that the development for MIXM in particular has been a bit behind - probably due to Chinese new year and/or Coronavirus. Though it's possible the MIXM (or Global) branch is compiled outside China; truth be told I have no idea why the Q update has been handled so badly for this particular device channel. The Mi9T Pro's development has been seemingly 'paused' as of late for Global users.
Reminds me a lot of my Redmi 5 Plus. Development was paused for much of the product's lifespan and they never fixed certain bugs on the device; just merged MIUI branch changes. Hopefully the same doesn't happen to the Mi9T Pro. It is a flagship-esque device and barely six months old (August 2019).
?Miui Global Stable Mi V11.0.2
? Android 10 | Miui 11
? 2/15/2020
?Changelog:
Deodex
Add Call, Contact and SMS MIUI
Center Clock
And You
For the Install Process MANDATORY Using Custom Recovery DX By MiRoom
If you do not use Custom Recovery DX By MiRoom, it will definitely enter Fastboot mode
? For the installation process, please see / download the video below. ?
? Download Video / Streaming: here
? Download Rom: here ?
Download vbmeta.img: here | Mirror
Download Custom Recovery DX By MiRoom Install via Fastboot mode : here
By Redmi K20 Pro Indonesia
Giangvo200837 said:
I'm on miui 11.0.1 QFKMIXM and i am waiting for a month when 11.0.2 is available, but still now i dont have any new OTA update?? Why
Click to expand...
Click to collapse
I had to download the OTA zip someone sent here and ended up manually updating. Tap a few times on the 11 in the updater until a toast message pops up saying that you enabled additional options and then tap on 3 dots and select Choose update package and browse to the zip you downloaded and select it.
Honestly I have like since forever used custom ROMs on my phones and this time I wanted to have the "stock experience", but if they keep delaying updates like this I'll just switch to xiaomi.eu weekly builds.
Since 31st of January Xiaomi suspended temporarily all updates due to the Corona virus outbreak.
How do i flash ota file manually on non rooted phone?
1. Be sure you have the correct OTA file
2. Place the OTA file in a folder of the internal storage named "downloaded_rom".
3. Go to settings/about the phone/systemupdate and tick the 3 dots on the right top
4. Then tick "choose update package" with this text or similar and go to the folder where you copied the Ota file and choose that file
Then let the Ota file update do it's work and after reboot it is done.
Snah001 said:
1. Be sure you have the correct OTA file
2. Place the OTA file in a folder of the internal storage named "downloaded_rom".
3. Go to settings/about the phone/systemupdate and tick the 3 dots on the right top
4. Then tick "choose update package" with this text or similar and go to the folder where you copied the Ota file and choose that file
Then let the Ota file update do it's work and after reboot it is done.
Click to expand...
Click to collapse
The option "Choose update package" doesn't show up unless you tap the 11 in the Updater a few times, because manually installing a .zip is an advanced (duh) option.
Was assuming that people here would know.
Thanks greatly to @ripiad, he shared me the new revision EEA MP6 and I uploaded those(full update & boot image) at here.
Strangely, only global version(OS00MP6) is mentioned at the official forum and no mention for global EEA(OS01MP6). No announcement for new revision neither. I don't know why and just take into account.
wga0 said:
Thanks greatly to @ripiad, he shared me the new revision EEA MP6 and I uploaded those(full update & boot image) at here.
Strangely, only global version(OS00MP6) is mentioned at the official forum and no mention for global EEA(OS01MP6). No announcement for new revision neither. I don't know why and just take into account.
Click to expand...
Click to collapse
Thanks for this important post.
I'm rooted in SMP5, and i'd like to update to SMP6. Just to confirm, The steps to update should be:
1- Flash again stock boot for SMP5
2-Update to SMP6 via OTA
3- Patch stock boot image SMP6 with Magisk Manager
4- Flash patched SMP6 boot image
5- reboot
Is this approach recommended?
Thanks
julipxda said:
Thanks for this important post.
I'm rooted in SMP5, and i'd like to update to SMP6. Just to confirm, The steps to update should be:
1- Flash again stock boot for SMP5
2-Update to SMP6 via OTA
3- Patch stock boot image SMP6 with Magisk Manager
4- Flash patched SMP6 boot image
5- reboot
Is this approach recommended?
Thanks
Click to expand...
Click to collapse
Yes, you can do that without reset. it will ask you to reboot after step 2 to change the slot.
wga0 said:
Yes, you can do that without reset. it will ask you to reboot after step 2 to change the slot.
Click to expand...
Click to collapse
Thanks, I started to do it and after restocking smp5 I realised I have not recieve OTA yet! I have to wait a little bit. Anyway thanks for your confirmation. I'll try again once OTA SMP6 is available in my area
wga0 said:
Thanks greatly to @ripiad, he shared me the new revision EEA MP6 and I uploaded those(full update & boot image) at here.
Strangely, only global version(OS00MP6) is mentioned at the official forum and no mention for global EEA(OS01MP6). No announcement for new revision neither. I don't know why and just take into account.
Click to expand...
Click to collapse
Do you have S00MP6 boot image? My BS2 bootloader is unlocked and I can't update it to Android 10. What must I do? Thanks berore
Sswilim said:
Do you have S00MP6 boot image? My BS2 bootloader is unlocked and I can't update it to Android 10. What must I do? Thanks berore
Click to expand...
Click to collapse
Have you tried downgrading to MP3?
OTA differs from each other, one can have 400 MB and the other 1.5 GB. Which of them can you call a full-fledged recovery ?
Thank you
I can't download any thing
Hi all.
I updated to the latest version last night, but I lost my root in the process.
I tired to re-root my GP6 yet unsuccessful. Anybody manage to do it?
Thanks.
Tried how? Assuming your bootloader is unlocked, the easiest way is probably:
Unhide Magisk on your phone for now (so PixelFlasher can find it to easily automatically patch your boot.img)
Enable USB debugging if you haven't already
Grab the T2B1 beta factory image (as by T2B1 it sounds like you're on the beta), and PixelFlasher
Use PixelFlasher to extract the boot.img from the factory image (red rocket icon right of the browse bar)
With your phone connected, hit Scan in the top right of PixelFlasher, and select your Pixel in the dropdown
With the extracted boot image extracted, hit "Patch" in PixelFlasher and let it do its thing
With the patched (band-aid icon) boot image selected, hit "Flash Boot" on the right, then let it do its thing again
You can hide Magisk again at this point.
You should have root back after doing all of that. Let me know if I missed anything or if it gets stuck anywhere.
Jaitsu said:
Tried how? Assuming your bootloader is unlocked, the easiest way is probably:
Unhide Magisk on your phone for now (so PixelFlasher can find it to easily automatically patch your boot.img)
Enable USB debugging if you haven't already
Grab the T2B1 beta factory image (as by T2B1 it sounds like you're on the beta), and PixelFlasher
Use PixelFlasher to extract the boot.img from the factory image (red rocket icon right of the browse bar)
With your phone connected, hit Scan in the top right of PixelFlasher, and select your Pixel in the dropdown
With the extracted boot image extracted, hit "Patch" in PixelFlasher and let it do its thing
With the patched (band-aid icon) boot image selected, hit "Flash Boot" on the right, then let it do its thing again
You can hide Magisk again at this point.
You should have root back after doing all of that. Let me know if I missed anything or if it gets stuck anywhere.
Click to expand...
Click to collapse
Have the same Problem, no root on latest Beta,
although following the above steps ( used them in the pasta for wach beta)
Anyone with root on newest Beta?
To be fair, I'm not rooting on the latest beta, I'm still on the standard TQ1A December release - the instructions I gave should apply to any version, but it's possible T2B1 has broken something. When you open the Magisk app, does it show that Magisk isn't installed, even after flashing the patched boot image?
Jaitsu said:
To be fair, I'm not rooting on the latest beta, I'm still on the standard TQ1A December release - the instructions I gave should apply to any version, but it's possible T2B1 has broken something. When you open the Magisk app, does it show that Magisk isn't installed, even after flashing the patched boot image?
Click to expand...
Click to collapse
Yes, same thing happened to me this morning after doing the common steps to retain root after applying an OTA. I then proceeded to patch the boot image using adb but stil no root access.
Edit. It appears that no one is able to root on T2B1, as someone said in the official guide rooting pixel 6 here on XDA
Same issue, tried with PixelFlasher, manual commands, diffrent Magisk versions, but still can't get it work
Strange, and interesting. May be worth filing a bug at the official Magisk github page if anyone is willing to go through the steps necessary to help troubleshoot the problem (doing all of the above with the latest debug version of Magisk, for starters; if you report a bug using any other version the bot will automatically close your issue). I would if I were running the beta or if we had working TWRP so I could backup and restore, but I juuust got my Pixel back to the way I like it on the non-beta after a factory reset.
Jaitsu said:
Strange, and interesting. May be worth filing a bug at the official Magisk github page if anyone is willing to go through the steps necessary to help troubleshoot the problem (doing all of the above with the latest debug version of Magisk, for starters; if you report a bug using any other version the bot will automatically close your issue). I would if I were running the beta or if we had working TWRP so I could backup and restore, but I juuust got my Pixel back to the way I like it on the non-beta after a factory reset.
Click to expand...
Click to collapse
I've already posted on Reddit r\Magisk [Help] Flashed magisk pathed pathed boot image T2B1.221118.006 don't works, but maybe submitting bug would be better. Yea, TWRP would be best but still nothing for A13 (and A12 I think). I remember that there was similar issue in older updates, but Canary made it work, but... not this time
Tried all the possible ways to root the phone, either using fastboot or Pixel Flasher, but no avail. Perhaps someone could successfully do it and tell all of us how
Same issue in Pixel 6a
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to patch and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
So, should we download the same latest beta for pixel 7 and extract and patch the boot image inside of it?
BAlex9601 said:
So, should we download the same latest beta for pixel 7 and extract and patch the boot image inside of it?
Click to expand...
Click to collapse
Yea, everything else stays the same. Just after upgrade, instead of patching Pixel 6 boot.img, patch the one from Pixel 7 and flash it.
I've used Pixel Flasher for factory update and then in Magisk app I've patched image and then flashed it with fastboot flash boot <patched_boot.img>.
https://twitter.com/i/web/status/1602774339224367104
Yup broken.. should have read the thread.
m_pastuszek said:
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to patch and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
Click to expand...
Click to collapse
Is this true? I'm downloading it now to test it. Will update later.
UPDATE:
Apparently, flashing Pixel 7 boot.img into Pixel 6 worked like a charm. I get the root back. Thanks guy!
Thanks for the hint regarding boot.img
I'm facing aslo this issue while updating
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.2-9152140'.
Update requires 'slider-1.2-9228550'.
Actually I'm on T1B3.221003.008
Any idea? -> flashed bootloader manually -> solved