MIUI V10.2.2.0 PDGMIXM stable - Global - Xiaomi Mi Mix 2S Guides, News, & Discussion

available OTA
MIUI V10.2.2.0 PDGMIXM stable - Global
504 MB
update:
- SYSTEM
Fix: Updated Android Security Patch

dxdy said:
available OTA
MIUI V10.2.2.0 PDGMIXM stable - Global
504 MB
update:
- SYSTEM
Fix: Updated Android Security Patch
Click to expand...
Click to collapse
Security patch 2019-02-01

https://bigota.d.miui.com/V10.2.2.0.PDGMIXM/miui_MIMIX2SGlobal_V10.2.2.0.PDGMIXM_7bb6553bad_9.0.zip

very strange. I just got a new Mix 2S, it's still on MIUI 9, then I unlocked it with official tool, after unlocking (waited 72 hours), the stock rom also updated to MIUI 10. but it's the stock chinese version not global version. And I downloaded this Global version onto the root of phone's memory, follow twrp's official guide, and in the recovery I can't see the zip file. and can't flash it. everything under /sdcard are random folder with long name of string of letters. It's nothing like other phones I've flashed with TWRP.

zhourj said:
very strange. I just got a new Mix 2S, it's still on MIUI 9, then I unlocked it with official tool, after unlocking (waited 72 hours), the stock rom also updated to MIUI 10. but it's the stock chinese version not global version. And I downloaded this Global version onto the root of phone's memory, follow twrp's official guide, and in the recovery I can't see the zip file. and can't flash it. everything under /sdcard are random folder with long name of string of letters. It's nothing like other phones I've flashed with TWRP.
Click to expand...
Click to collapse
The random folder and file names indicate that TWRP did not manage to decrypt your phone. It is supposed to ask for your password when you enter recovery. A workaround is using adb from a pc and sideload the zip.

zhourj said:
very strange. I just got a new Mix 2S, it's still on MIUI 9, then I unlocked it with official tool, after unlocking (waited 72 hours), the stock rom also updated to MIUI 10. but it's the stock chinese version not global version. And I downloaded this Global version onto the root of phone's memory, follow twrp's official guide, and in the recovery I can't see the zip file. and can't flash it. everything under /sdcard are random folder with long name of string of letters. It's nothing like other phones I've flashed with TWRP.
Click to expand...
Click to collapse
It happen also to me just retry to download and you see you don't download the ota 540mb but the full 1.7gb then you can upgrade..

hocuspocus69 said:
It happen also to me just retry to download and you see you don't download the ota 540mb but the full 1.7gb then you can upgrade..
Click to expand...
Click to collapse
yes it is the 1.7GB zip
---------- Post added at 09:46 PM ---------- Previous post was at 09:44 PM ----------
M1chiel said:
The random folder and file names indicate that TWRP did not manage to decrypt your phone. It is supposed to ask for your password when you enter recovery. A workaround is using adb from a pc and sideload the zip.
Click to expand...
Click to collapse
Oh, I see. so how should I do that? I'm not familiar with the command line commands in fastboot.
I think I saw one post around here but didn't memorize it.
---------- Post added at 09:47 PM ---------- Previous post was at 09:46 PM ----------
M1chiel said:
The random folder and file names indicate that TWRP did not manage to decrypt your phone. It is supposed to ask for your password when you enter recovery. A workaround is using adb from a pc and sideload the zip.
Click to expand...
Click to collapse
Thank you very much. And is it possible that I can let TWRP decrypt the phone somehow? when should it ask for password? it's still a fresh system, I didn't set any password yet. Or is there a universal one?

zhourj said:
yes it is the 1.7GB zip
---------- Post added at 09:46 PM ---------- Previous post was at 09:44 PM ----------
Oh, I see. so how should I do that? I'm not familiar with the command line commands in fastboot.
I think I saw one post around here but didn't memorize it.
---------- Post added at 09:47 PM ---------- Previous post was at 09:46 PM ----------
Thank you very much. And is it possible that I can let TWRP decrypt the phone somehow? when should it ask for password? it's still a fresh system, I didn't set any password yet. Or is there a universal one?
Click to expand...
Click to collapse
If you haven't set a PIN or password your data are not supposed to be encrypted, but maybe MIUI has a different approach. I suppose you use the latest twrp from the twrp.me site? Older unofficial versions cannot decrypt. Maybe you can set PIN and see what happens if you reboot in twrp?
A good instruction on how to use sideload is on the LineageOS site: https://wiki.lineageos.org/devices/polaris/install

M1chiel said:
If you haven't set a PIN or password your data are not supposed to be encrypted, but maybe MIUI has a different approach. I suppose you use the latest twrp from the twrp.me site? Older unofficial versions cannot decrypt. Maybe you can set PIN and see what happens if you reboot in twrp?
A good instruction on how to use sideload is on the LineageOS site: https://wiki.lineageos.org/devices/polaris/install
Click to expand...
Click to collapse
Thank you very much.
I might try using Lineage actually. My nexus galaxy was on cyangen rom all the time.
this Mi phone is really difficult now. I tried to use MIUI's own flash tool with the global rom, but it didn't recognize the zip file. And after unzipping it, it didn't find any "flash all.bat". Is that really a problem for this rom?

zhourj said:
Thank you very much.
I might try using Lineage actually. My nexus galaxy was on cyangen rom all the time.
this Mi phone is really difficult now. I tried to use MIUI's own flash tool with the global rom, but it didn't recognize the zip file. And after unzipping it, it didn't find any "flash all.bat". Is that really a problem for this rom?
Click to expand...
Click to collapse
You have to look for a flashable version. I downloaded one from here: http://en.miui.com/a-234.html. If I remember correctly you have to unzip it twice. Make sure you do not use the bat file that relocks your bootloader.

M1chiel said:
You have to look for a flashable version. I downloaded one from here: http://en.miui.com/a-234.html. If I remember correctly you have to unzip it twice. Make sure you do not use the bat file that relocks your bootloader.
Click to expand...
Click to collapse
i didn't know there are different version of the bat files there.

I don't know why this unit can't be flashed with it. And also I want to use lineage OS rom, however that zip file can't be seen under TWRP recovery. still the same thing.
Even it's the latest version for this model, and I flashed the recovery onto the phone memory, it still can't work.
Have you encountered such problem before?
M1chiel said:
You have to look for a flashable version. I downloaded one from here: http://en.miui.com/a-234.html. If I remember correctly you have to unzip it twice. Make sure you do not use the bat file that relocks your bootloader.
Click to expand...
Click to collapse

zhourj said:
very strange. I just got a new Mix 2S, it's still on MIUI 9, then I unlocked it with official tool, after unlocking (waited 72 hours), the stock rom also updated to MIUI 10. but it's the stock chinese version not global version. And I downloaded this Global version onto the root of phone's memory, follow twrp's official guide, and in the recovery I can't see the zip file. and can't flash it. everything under /sdcard are random folder with long name of string of letters. It's nothing like other phones I've flashed with TWRP.
Click to expand...
Click to collapse
not needed to unlock device to flash (upgrade with) official global ROM
download http://en.miui.com/download-343.html and just copy zip file to downloaded_rom folder and run update

fps on video settings
subboxcb said:
Security patch 2019-02-01
Click to expand...
Click to collapse
i noticed the fps on video setting is now only in 30fps in previous updates i can still see the 60fps on 4k and 1080p, you guys noticed it too? and also adaptive battery has been added and my battery life have been so good after this update since 10.2.1, i hope they fix the video setting soon if im the only one experiencing this problem.

Hello, I come to ask for help, I have my mi mix 2s that offers me the update v10.2.2.0 PDGMIXM stable 1.7G the problem is once download with the phone it tells me impossible to check the source of the file and does not update I tried to download the rom from here: http://en.miui.com/download-343.html the problem is the same. do you have an idea of the solution?
I am currently with the rom MIUI GLOBAL STABLE 10.0.2.0 ODGMIFH
EDIT : solved

New updated 10.3.3.0 stable

miras65000 said:
New updated 10.3.3.0 stable
Click to expand...
Click to collapse
Where ? Link ?

Related

[OTA] Official Marshmallow build MCG24.251-5

WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.
This is the stock recovery version, correct?
koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.
TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones
koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.
Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )
kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!
It works in LOCKED BOOTLOADER??? .-.
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.
TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.

[ROM] MCG24.251-5 100% Stock

Flash using TWRP. This will flash all files in the MCG24.251-5 update except for recovery.
New features in this update that I've noticed:
-Marshmallow, aged to perfection in Verizon's own servers. Only one major release version obsolete, and with outdated security patches!
-WiFi calling (woooooo! Those custom roms just got another carrier-specific, unportable feature to compete with)
-The command center widget has been replaced with the Droid Turbo 2 version
Get it here: https://mega.nz/#!G1xg1aYa!fm2hUL7hDDVaxTAj_iPbtY61P-8VrQEvoOJiVsDtdho
Here's the stock recovery image if you want it: https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Flashing this rom updates the bootloader to a version that can communicate with the kernel to tell SafetyNet that it is unlocked, causing it to fail. Fret not, however, as there are two options to fix this:
OPTION 1: Flash the SU4TL-49 bootloader using the following TWRP package: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
OPTION 2: Flash this patch made by @bhb27: https://www.androidfilehost.com/?fid=745425885120696423
Wipe cache and dalvik/art cache after either of these options.
NOTE that these options only fix failures due to SafetyNet checking the bootloader status. It will still fail due to root, xposed and the like. There are no known consequences or side effects to either of these options, so just pick whichever one you feel like.
If you notice weird things after you flash this rom (long boots other than the first one which is supposed to be long, random reboots, etc.) try flashing the stock recovery image and factory resetting.
If you want root, flash this version of SuperSU first, then flash whatever newer version you want: https://download.chainfire.eu/751/SuperSU/
If you have trouble flashing this, try TWRP Mod 3 instead of Mod 4.
Ouch, you have almost full flash inside archive, with bootloader too... Who is the most brave, introduce yourself ))
+ mirror
I can confirm that it works on old bootloader.
I had SULT-49 5.1 installed before and I just flashed this via TWRP. I haven't taken the OTA. It works perfectly. Thank you.
PS: My bootloader now is moto-apq8084-70.95 (2016-06-29). Do you have same version after taking OTA?
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Thanks OP
rickyblaze13 said:
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
When in doubt, always wipe.
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
rickyblaze13 said:
have to wipe the system, data and cache first
Click to expand...
Click to collapse
It works w/o, but, IMO, better wipe, than not. You don't need extra bugs, right )
It's completing setup now, I did a wipe after I backed up my phone. It's unlocked and rooted before I flashed the zip
Sent from my QMV7A using Tapatalk
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Crowick said:
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Click to expand...
Click to collapse
My google drive is full and I don't have Dropbox. But if you wanted to mirror it, I will gladly add the link to the OP.
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
thanks for gdrive mirror
Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
I don't. I don't know how I would get it since I need root access to get it, and I can't get root access without TWRP, and I have to overwrite the stock recovery to get TWRP.
TheSt33v said:
I have to overwrite the stock recovery to get TWRP.
Click to expand...
Click to collapse
fastboot boot TWRP.img
s5610 said:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Nice! Good call.
https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Is anyone else having exceptionally long reboot/start times for their phone after flashing this rom?
Just the first boot after flashing
Sent from my XT1254 using Tapatalk
Thanks for that! Did anybody try to install it right over SU4TL-44? Just in case, I'm rooted, using xposed and twrp.
TheSt33v said:
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
Click to expand...
Click to collapse
Perhaps this:
https://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
I just tried using AP a few hours ago and it failed with the screen in the article. OTA with unlocked bootloader.

[GUIDE] How to install EMUI 9 / Android 9 Beta

Hi,
you want to flash EMUI 9 Beta, are FRP and bootloader unlocked and rooted? Great, here we go.
Disclaimer: I am not responsible for your bricked devices. I only tested this on my Windows 10 x64 computer with my CLT-L09 C432 - I don't know if this works with your phone or your computer. Other models may or may not work. Please don't use that method if you don't know how to recover your phone from a bricked or semi-bricked state.
It might be a good idea to disable your antivirus if you run into warnings. There is no root.
Steps:
- Download THE TOOLâ„¢ v0.2
- Download the matching firmware bundle for your device. With EMUI 9 the firmware files for L09 and L29 differ.
- Extract THE TOOLâ„¢
- Extract the firmware bundle, you'll get two ZIPs and some XMLs.
- Start FLASH.bat inside of the extracted tool folder - it will guide you through the procedure.
- I did not have to factory reset. Maybe you will still need to.
- I have no idea if you will be able to receive OTAs or upgrade to future builds.
Disclaimer: Its not my fault or my responsibility if you brick your phone. I have almost no spare time at the moment, so I will probably not be able to help you. Also, there is no root.
Download:
CLT-L09 C432 - Build 9.0.0.108
CLT-L29 C432 - Build 9.0.0.108
Upgrade / Downgrade:
Upgrade from Beta to Beta: CLICK HERE (thanks @side_flip15)
Downgrade back to Oreo: CLICK HERE (thanks @Androlark)
Massive thanks to:
- @Atarii
- @Androlark
- @ante0
- @dkionline
- @frantorresm5434
- laststandingdroid
- @mankindtw for the original NoCheck recovery
- @Pretoriano80
- @shimp208 for the bundled minimal ADB + Fastboot
- and of course to all the brave testers!
There is no root. Also, please don't blame if your device dies. And I don't know if VoLTE works.
Click HERE for the P20 (EML) thread.
02.10.2017 - v0.2 - updated download links from 9.0.0.47 to 9.0.0.108; added links to downgrade and upgrade instructions
07.09.2017 - v0.2 - script now should work inside path containing spaces
06.09.2018 - v0.1 - initial release
windows only :-/. Luckily seems easy enough
---------- Post added at 11:48 PM ---------- Previous post was at 11:40 PM ----------
Thanks. Does this update the bootloader? Can you downgrade again?
josdehaes said:
windows only :-/. Luckily seems easy enough
---------- Post added at 11:48 PM ---------- Previous post was at 11:40 PM ----------
Thanks. Does this update the bootloader? Can you downgrade again?
Click to expand...
Click to collapse
Yes, the bootloader (xloader) will be updated, there's no way around it. Yes, downgrading works, but you will have to factory reset after downgrading.
Having a problem after renaming the second update zip. After I press enter with both zip files in the zip folder it says I'm missing zip files.
---------- Post added at 02:18 AM ---------- Previous post was at 02:16 AM ----------
CaseyS said:
Having a problem after renaming the second update zip. After I press enter with both zip files in the zip folder it says I'm missing zip files.
Click to expand...
Click to collapse
Solved
Nice thanks man
Pretoriano80 said:
Yes, the bootloader (xloader) will be updated, there's no way around it. Yes, downgrading works, but you will have to factory reset after downgrading.
Click to expand...
Click to collapse
If ever I want to go back to 8.1 which method should I use? Will HuRu or eRecovery work?
Worked great.
Should add in op that tool folder needs to be in c drive directory else you will get a ton of replies about missing zips.
side_flip15 said:
If ever I want to go back to 8.1 which method should I use? Will HuRu or eRecovery work?
Click to expand...
Click to collapse
NoCheck works. (from BKL/Honor View 10)
side_flip15 said:
If ever I want to go back to 8.1 which method should I use? Will HuRu or eRecovery work?
Click to expand...
Click to collapse
No - as @ante0 said in his comment: You'll need the NoCheck recovery. I'm probably going to make a rollback bundle, too - but since I'm moving this is going to take at least until Sunday.
JamieD81 said:
Worked great.
Should add in op that tool folder needs to be in c drive directory else you will get a ton of replies about missing zips.
Click to expand...
Click to collapse
Thank you. It should be fixed inside the updated link in OP.
Anybody can upload any file server?megaupload have limited..
ekremxx said:
Anybody can upload any file server?megaupload have limited..
Click to expand...
Click to collapse
Use MEGASync desktop app
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
Possible to flash this on region other than 432???
side_flip15 said:
Use MEGASync desktop app
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
Possible to flash this on region other than 432???
Click to expand...
Click to collapse
/cust contain all different cust (like eu, meafnaf, us etc) so it should be possible.
Seeing this post https://forum.xda-developers.com/showpost.php?p=77551305&postcount=6 it has been done partially already (L09 on L29)
And as Oreo TWRP is pretty functional it is easily re-flashed.
ekremxx said:
Anybody can upload any file server?megaupload have limited..
Click to expand...
Click to collapse
I updated the links in OP.
What about magisk anybody know how to root?
without root. Pie is not worth.
david6910 said:
What about magisk anybody know how to root?
Click to expand...
Click to collapse
As it is stated in the OP (three times ) there is currently no known rooting method.
otonieru said:
without root. Pie is not worth.
Click to expand...
Click to collapse
ok
david6910 said:
What about magisk anybody know how to root?
Click to expand...
Click to collapse
otonieru said:
without root. Pie is not worth.
Click to expand...
Click to collapse
There is no way to flash Magisk, yet anyway.
But I'm not certain TopJohnWu will be working on fixing it after he found out Patch01 broke Magisk (Which apparently has been fixed by @Tecalote)
Hi, I created a shell script for usage on Linux/MacOS. Should run if bash is available.
!! Note that you need to have adb/fastboot already in your $PATH and working!!
enjoy.

Stock Recovery Image

Does anyone happen to have the stock ColorOS recovery.img for this device?
Thanks!
Jaernyx said:
Does anyone happen to have the stock ColorOS recovery.img for this device?
Thanks!
Click to expand...
Click to collapse
I've been looking for it also. I couldn't find it in the ozip OTA files.
I have the Chinese variant and want to test the Chinese TWRP, but need the stock recovery just in case...
it's all inside the file system.new.dat.br I'm also trying with the global version
Kratong said:
it's all inside the file system.new.dat.br I'm also trying with the global version
Click to expand...
Click to collapse
I extracted that file. There are a lot of folders. Not sure where to look. Any idea?
with which program? I can't do it I need a fastboot rom
I'll take a look in the system file as well when I get off work.
Smart of you to back your stuff up before diving in. I was trying to see if I could create a rom for my device but I believe I borked my partitions up.
The twrp from wzsx150 in the other thread doesn't boot on my device so I'm hoping the stock recovery image will get me on the right path. I was able to make a bootable twrp but the system partition doesn't mount correctly so I can't flash with it.
I'm pretty new to this stuff but learning more every time I work on it, haha. Should have taken correct precautions though.
Jaernyx said:
I'll take a look in the system file as well when I get off work.
Smart of you to back your stuff up before diving in. I was trying to see if I could create a rom for my device but I believe I borked my partitions up.
The twrp from wzsx150 in the other thread doesn't boot on my device so I'm hoping the stock recovery image will get me on the right path. I was able to make a bootable twrp but the system partition doesn't mount correctly so I can't flash with it.
I'm pretty new to this stuff but learning more every time I work on it, haha. Should have taken correct precautions though.
Click to expand...
Click to collapse
I can't fastboot boot that recovery either and I have the Chinese variant.
Did you do the disable verity etc before trying to boot until your TWRP? Or it could be encryption that's preventing you from viewing the system partition? Might need to format data?
None of these things I'm willing to try without a backup stock recovery though
anandlal said:
I can't fastboot boot that recovery either and I have the Chinese variant.
Did you do the disable verity etc before trying to boot until your TWRP? Or it could be encryption that's preventing you from viewing the system partition? Might need to format data?
None of these things I'm willing to try without a backup stock recovery though
Click to expand...
Click to collapse
I poked around all the dat.br files in the OTA update except the numbered version files and wasn't able to find any recovery.
Unfortunately, I've already fully wiped and it still wont' mount. It kind of seems like my system partition got completely nuked, although tbh I'm not entirely sure how I did that
That being said, I tried directly mounting /system, but I get the error that a block device is required. I checked the fstab files on what I have available and it seems to point to a file that isn't on my device. RIP, haha.
I'll continue to see what I can figure out though. Happy to know it doesn't boot for you actually, as I thought it not booting was due to me gunking up something. Oh yeah, I have a Chinese variant too.
Jaernyx said:
I poked around all the dat.br files in the OTA update except the numbered version files and wasn't able to find any recovery.
Unfortunately, I've already fully wiped and it still wont' mount. It kind of seems like my system partition got completely nuked, although tbh I'm not entirely sure how I did that
That being said, I tried directly mounting /system, but I get the error that a block device is required. I checked the fstab files on what I have available and it seems to point to a file that isn't on my device. RIP, haha.
I'll continue to see what I can figure out though. Happy to know it doesn't boot for you actually, as I thought it not booting was due to me gunking up something. Oh yeah, I have a Chinese variant too.
Click to expand...
Click to collapse
Damn... That's insane! So I guess you have to wait for the stock recovery to be available before you can go back to the stock rom.
What I do like about the stock recovery is that your have the option to go online and install the stock rom.
Kratong said:
with which program? I can't do it I need a fastboot rom
Click to expand...
Click to collapse
Convert system.dat.br to system.dat (brotli)
Convert system.dat to RAW system.img (sdat2img)
Extract system.img (imgextractor)
I installed the twrp chinese version on the global version now i am rom china I wanted to go back but I can't go back to global
Kratong said:
I installed the twrp chinese version on the global version now i am rom china I wanted to go back but I can't go back to global
Click to expand...
Click to collapse
You were actually able to install the CN ROM in the Global variant?!
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Kratong said:
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Click to expand...
Click to collapse
What was the steps you took to go from EU to CN?
I was actually considering going from CN to EU but thought I'd was not possible due to the different partition sizes for system etc..
I can't convert system.img to raw system.img for flash with fastboot can someone post it already converted? for rmx2076.thanks
Kratong said:
I can't convert system.img to raw system.img for flash with fastboot can someone post it already converted? for rmx2076.thanks
Click to expand...
Click to collapse
this link system.img for rmx2076
https://bit.ly/2Yse5ue
i flashed system.img with fastboot reports this error invalid sparse file at header magi. what should i do?
Kratong said:
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Click to expand...
Click to collapse
They just released a flash tool. Let me know if this works for you.
https://www.realmebbs.com/post-deta...subForumId=1156882636577189888&language=zh-CN
thanks later I look at it but is it ok for the global version too? my situation is now this I managed to install the Chinese rom on rmx 2076 involuntarily but the modem part doesn't work everything else works
Kratong said:
thanks later I look at it but is it ok for the global version too? my situation is now this I managed to install the Chinese rom on rmx 2076 involuntarily but the modem part doesn't work everything else works
Click to expand...
Click to collapse
From the looks of it. You just need to have your phone in fastboot mode and select the file you want to flash. So you can try selecting the Global ozip and see if that would bring you back to stock.

Android 11 beta

Beta version is out for umi (and cmi) and appears to be completely stock Android, although very buggy, such as no fingerprint sensor amongst others.
As it's early Chinese beta there's no Google play installed.
fastboot version
http://106.7.64.1/bigota.d.miui.com...ive.user_20200614.0000.00_11.0_6c6b84e950.tgz
Not recommended just yet...
[Edit] removed first link as posted weekly a10 beta by mistake.
We should waiting for Beta 2...
fards said:
Beta version is out for umi (and cmi) and appears to be completely stock Android, although very buggy, such as no fingerprint sensor amongst others.
As it's early Chinese beta there's no Google play installed.
https://bigota.d.miui.com/20.6.15/miui_UMI_20.6.15_826e1ce00a_10.0.zip
And fastboot version
http://106.7.64.1/bigota.d.miui.com...ive.user_20200614.0000.00_11.0_6c6b84e950.tgz
Not recommended just yet...
Click to expand...
Click to collapse
I tried this rom and it turns out to be android 10 with miui 12 beta security update 6/1
tknguyencsu said:
I tried this rom and it turns out to be android 10 with miui 12 beta security update 6/1
Click to expand...
Click to collapse
Ah. Just noticed the first link was for the weekly beta.
The second link is for the Android 11 beta.
I'll remove the first link.
That's what you get for posting links while in the supermarket ?
There is no adaptation in the status bar, expecting the third-party ROM to arrive as
There is no adaptation in the status bar, expecting the third-party ROM to arrive as soon as possible
try to update gsi by DSU
http://bigota.d.miui.com/0.06.14.na....gl.user_20200615.0000.00_11.0_30884eb908.tgz
updated beta build, looks like a daily builds are on.
fards said:
http://bigota.d.miui.com/0.06.14.na....gl.user_20200615.0000.00_11.0_30884eb908.tgz
updated beta build, looks like a daily builds are on.
Click to expand...
Click to collapse
OTA support?
k1n9n0th1n9 said:
OTA support?
Click to expand...
Click to collapse
Unlikely
Version with miui12 is now out.
https://bigota.d.miui.com/20.6.28/miui_UMI_20.6.28_a5e0d69c19_11.0.zip
Lots of bugs though. (Google translate from Chinese)
1. The status bar shows some problems
2. The camera night view function cannot be used
3. Xiaomi classmates do not support voice wake-up
?? Assistant??
4. Temporarily does not support the long screenshot function
5. Temporarily does not support the Xiaomi mutual transmission function
6. Temporarily does not support one-key switch
7. The sun screen of some machines does not take effect ?? Daylight??
8. Probably failed to upgrade the application in the application store ?? some apps wont update??
It also might need stock recovery to flash it
There's another build dated 06.30.20 out as well.
https://hugeota.d.miui.com/20.6.30/miui_UMI_20.6.30_0d99b1b562_11.0.zip
I am in 20.06.17, how to install 20.06.30 via stock recovery?
https://hugeota.d.miui.com/20.7.2/miui_UMI_20.7.2_bb17565fc5_11.0.zip
letfly said:
I am in 20.06.17, how to install 20.06.30 via stock recovery?
Click to expand...
Click to collapse
Have you tried fastboot a normal build?
I've but used stock recovery so I don't know.
What is the error?
fards said:
Have you tried fastboot a normal build?
I've but used stock recovery so I don't know.
What is the error?
Click to expand...
Click to collapse
Fastboot a normal build? I dont understand so much. 2020.06.30 is zip file, so I think must use recovery, but twrp is not compatible. Can you tell me how can we fastboot this build? Just because I dont know that way.
letfly said:
Fastboot a normal build? I dont understand so much. 2020.06.30 is zip file, so I think must use recovery, but twrp is not compatible. Can you tell me how can we fastboot this build? Just because I dont know that way.
Click to expand...
Click to collapse
no.
Fastboot flash a standard non-beta build.. (don't let it relock the bootloader) using miflash with one of the fastboot roms.
https://c.mi.com/oc/miuidownload/detail?guide=2
That way you should hopefully get back to a stock working android 10 rom and stock recovery, from there if you want to flash another beta you can go through the process again.
Android 11 has changed something with the FBE and twrp doesn't decrypt properly.
fards said:
no.
Fastboot flash a standard non-beta build.. (don't let it relock the bootloader) using miflash with one of the fastboot roms.
https://c.mi.com/oc/miuidownload/detail?guide=2
That way you should hopefully get back to a stock working android 10 rom and stock recovery, from there if you want to flash another beta you can go through the process again.
Android 11 has changed something with the FBE and twrp doesn't decrypt properly.
Click to expand...
Click to collapse
No. I already did it. But when in Stock MIUI, stock recovery dont allow to update 20.06.30, it say need fastboot. But 20.06.30 dont have fastboot rom, only zip rom. so I dont know how to flash it.
letfly said:
No. I already did it. But when in Stock MIUI, stock recovery dont allow to update 20.06.30, it say need fastboot. But 20.06.30 dont have fastboot rom, only zip rom. so I dont know how to flash it.
Click to expand...
Click to collapse
Have you tried putting an older update-binary in the zip file?
That it supposed to work for twrp if you're on a normal stock rom.
fards said:
Have you tried putting an older update-binary in the zip file?
That it supposed to work for twrp if you're on a normal stock rom.
Click to expand...
Click to collapse
I will try it. Put older update-binary. Do we need to put older update-scripts?
letfly said:
I will try it. Put older update-binary. Do we need to put older update-scripts?
Click to expand...
Click to collapse
In the android 10 zip file there is a compatibility.zip which does not exist in the android 11 zip file. I think it might cause a problem if you put the older update-binary zip in the android 11 zip file.

Categories

Resources