Database Develop

Android Pay - MIUI 8.2.3.0 (MAHCNDL) | Chinese Stable ROM

Seems like Android Pay does not recognise the latest system update as an official ROM, after installing Android pay and giving all the permissions:
Android Pay can't be used on this device. This may be because your device is rooted, has an unlocked bootloader, or is running a custom ROM. As a result, Google can't confirm that your device meets Android Pay's security standards.
Click to expand...
Click to collapse
I inadvertently ran this update after purchasing the phone 2 days ago, didn't unlock the bootloader (though applied for it) and of course, haven't rooted.
I factory reset twice and still got the same. Looking forward to unlocking the bootloader so I can downgrade to the older ROM or even go on the global one (since I saw in another thread Android Pay's working on the latest global ROM V8.2.1.0.MAHMIDL, and the latest downloadable Chinese stable Rom V8.2.2.0.MAHCNDL)
Anyone updated and experience the same issue? And as I'm a newb in all of this, must I unlock the bootloader in order to downgrade?

Tried to get it to work, this time through using recovery flash (without need to unlock the bootloader and what not). Here's how I finally got Android Pay to work, and also got myself on Global Rom (lovin' it)
Prerequisite: Download the latest stable ROM file here to PC
1. Download the Chinese version of the Xiaomi Mi PC Suite and run it
2. Plug in your phone to PC and boot into recovery mode (push both volume up button + power button together until your phone reboots)
3. Allow driver to install, if you're in recovery mode, a prompt will come up. If not don't panic, read step 4. Otherwise go to Step 5.
4. If the PC Suite does nothing even if you push the big orange button on the right to connect (apparently they haven't upgraded the software to support Android 6.0 yet -_-"), click this button show below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and select the button with the words "Recovery" in it, it will prompt you to reboot your phone into recovery mode (push both volume up button + power button together until your phone reboots).
5. Select the ROM you pre-downloaded on your PC and let it run.
6. The PC Suite will look like it hits some error and on desktop the progress remains at 0% but somehow things are churning on your phone as you can see "MIUI update" and a progress bar below.
7. Let it run its course and allow the phone to reboot
8. Voilà, your phone is now in Global ROM
And Android Pay now works, hoorah!!!

Great guide, thanks a lot! I've got the sister phone to this one, the Xiaomi Mi Note 2... and my Android pay was not working with 8.3.2 global.. But now it is.. I will post a guide elsewhere as to how I had to fix it...

THIS is a DANGEROUS post, it may work - or like in my case it will start for just a moment then stop [causing a factory reset to occur] without updating. Make sure you have your mi account login and pass ready when it comes back up - or your locked out of the device setup.
Due to frustration caused by trying this post I ended up unlocking / rooting the device. It was easier than I thought it would be, flashed global fine from there and updated to 8.2.4.0 just fine OTA. Have gone on too work on other things I had decided not to due because I hadn't decided to root the device. So I guess there was a silver lining to this.

Question Unresponsive touchscreen

I am on a global firmware, version 12.5.4, and sometimes the touchscreen becomes really unresponsive to the point that the device is almost unusable. I am aware that this is a known issue, has anyone found a permanent fix? Is this still a thing on more recent ROMs?
I feel this is not acceptable on a top-of-the-line phone like the MI 11 Ultra.

You must activate antiflicker in display settings and select "custom" in "prevent accidental edge touches". This is a workaround and improve this issue, still it may occur from time to time. Otherwise you can update to the latest 12.5.6.0, so far in this version I haven't seen this problem (although with those settings enabled)

xNAPx said:
You must activate antiflicker in display settings and select "custom" in "prevent accidental edge touches". This is a workaround and improve this issue, still it may occur from time to time. Otherwise you can update to the latest 12.5.6.0, so far in this version I haven't seen this problem (although with those settings enabled)
Click to expand...
Click to collapse
Thank you. Anti flickering mode is nice. But the problem still persist. No update is available yet but buying best of best by MI and you get this small irritating UI issues is actually very bad.

Unfortunately the workaround only reduce it

Since the 12.5.6.0 touch issues are complete gone for me.
Thx god, the issues were frustratin sometimes

comediiian said:
Since the 12.5.6.0 touch issues are complete gone for me.
Thx god, the issues were frustratin sometimes
Click to expand...
Click to collapse
Hey bro, are you on RKAMIXM? And is your device rooted or unlocked bootloader? Or as original as it is out of box?

hassanaliyeh said:
Hey bro, are you on RKAMIXM? And is your device rooted or unlocked bootloader? Or as original as it is out of box?
Click to expand...
Click to collapse
Yeah, running Global Stable, Bootloader is unlocked but device is unrooted.
No need for root on my side

comediiian said:
Yeah, running Global Stable, Bootloader is unlocked but device is unrooted.
No need for root on my side
Click to expand...
Click to collapse
Thanks,
Just confirmed my theory, I couldn't update to 12.5.6 because of locked bootloader

You can push the update with advanced features. To activate them you need to press on miui button 6/7 times. After that download the latest .ZIP package (recovery update) and when in the updater select on the 3 dots in the up right "choose installation package"

xNAPx said:
You can push the update with advanced features. To activate them you need to press on miui button 6/7 times. After that download the latest .ZIP package (recovery update) and when in the updater select on the 3 dots in the up right "choose installation package"
Click to expand...
Click to collapse
I did that already and it stopped midway with stable recovery update, I had to format factory reset device and reupdate to original 12.5.4 to be able to use device normally.. And with only incremental update, it gave me an error saying cannot update with unofficial release.

May I ask you what did you download please?

Stable update 12.5.6 - local update- went all good, once reached the point to restart phone, then it fails after restart with veeeeeery slow phone and almost unresponsive, took 10mins to unlock screen instead of split of a sec.
Tried to flash a new 12.5.6 and 12.5.4 by fastboot, failed no matter what I do as bootloader is locked. The only way I got away with it was download 12.5.4 and local update it after I factory reset device which didn't help with smoothness but was needed to access local update again

AFAIK there is no fastboot 12.5.6.0 update, only recovery. I would suggest to re download the update as the one you downloaded might have been corrupted

xNAPx said:
AFAIK there is no fastboot 12.5.6.0 update, only recovery. I would suggest to re download the update as the one you downloaded might have been corrupted
Click to expand...
Click to collapse
Hi, about flashing the latest ver, this one is beta no? If i do flash it will i lose ota updates?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Why you should lose OTA updates? It is stable beta

Updated manually to 12.5.6 and the problem seems finally gone.

If your bootloader is locked I'd recommend not to update.
If it is locked and you successfully update please let me know

thyrel said:
Updated manually to 12.5.6 and the problem seems finally gone.
Click to expand...
Click to collapse
I confirm that, problem is gone. System is super smooth and reactive. Close to perfection

xNAPx said:
Why you should lose OTA updates? It is stable beta
Click to expand...
Click to collapse
I don't know, just got the phone 2 days ago. I'm trying not to mess with anything I'm not sure of.
Sorry if that seemed stupid but i do not want to risk it.
So if i update using that file I'm fine? Also is it the correct file or it should be bigger??

Usually recovery ZIP is smaller than fastboot. Onestly I pushed manually the update through OTA from stable 12.5.4.0 and everything went perfectly. Even with root and of course I have bootloader unlocked. Don't know what can go wrong if you have bootloader locked

Pixel 4xl bricked itself

Hey all. My wifes phone decided to brick itself. Hers is/was an unlocked unit not purchased from verizon but on their network. I noticed its now locked. It randomly reset and on boot, the screen started blinking and was unresponsive. Then it rebooted again and the "try again, factory reset" note came up at the top of the screen. Try again yielded the same pattern. So, I tried full wipe, same thing, loop back to the try again screen. Then, I tried to side load the ota. All seemed ok. Installed her sim, all good. Went to settings to change to 3 button nav and boom, fail and try again screen. Was this a delay from maybe a bad sim card? Is 3 button nav an issue? Did evil verizon lock her phone? Can they do that?
So, I ordered another 4xl because she needs a solid phone to function for work. Id still like to know if I can recover the borked unit. Any help is appreciated.

You did all the correct things. Unfortunately it sounds like a hardware issue. Anytime you factory reset you have ruled out a software issue. Further, flashing a "rescue ota" via adb that resets the phone even with a locked bootloader. You've done everything you can do, except leave the red devil.

So now, I have it working, but not trusting it. I dont dare change to 3 button nav though...hahaha Still going to use the one we bought so she has a solid phone for work.
On another note. We're now stuck in the gmail recovery loop. 2 email addresses referencing eachother for recovery of passwords. Its maddening. I thought if I could get her phone to work, there would be some google magic that may kick in.
Its all evil.

sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.

Hey all.
So for carbon coupe:
1. Verizon can't just lock your phone if it is unlocked, this is something that happens during the manufacturer process. So if it randomly restarted there may be another cause.
2. You wrote that when on 3 button navigation it works fine but if you switch the phone starts boot looping. This is clearly a software issue rather than a hardware issue(there is no chip responsible for the type of navigation system), so there may be a problem with the OS. This is a good thing because it means it's fixable without the need of money.
Factory reset usually fixes most problems but not all of them, as some partition aren't changed during the process, like boot or system.
So the problem is in one of those partition, just like when you have a locked phone and after reseting it it still knows it is lock.
The solution is to flash the firmware of the phone to fix it.
For sSjBlueVN197,
if you are on this mode it's called EDL mode. If you are on this mode it means fastboot and adb aren't available. On that mode you can flash firmware to the phone, even if it is locked or bricked.
This propose of this mode is to allow developers to flash firmware if when the system is damage, and some other partitions like boot and others are also damage. It's just like an emergency mode to rescue the phone.
Anyway, for both of you, here is what you need to fix your phone:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode.
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.

#mcl said:
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.
Click to expand...
Click to collapse
hi, i have pixel 4 xl firehose but its asking for 2 more files raw program and patch file...
pixel4-XL_firehose - Google Drive
drive.google.com

#mcl , can you advices me the method that can fix this problem . so xml file can not meet this point .

Question Changing ROM to MIUI Global

Hi everyone. I recently got my Mi 11 Ultra with Chinese ROM (I'm guessing, from settings I can see MiUI 12.5.2.0). I'd like to change to latest version of MIUI global ROM. What would be the safest way to do so? I'd like to backup everything first before doing so (I haven't done this before) just in case something goes wrong. Also is there any up to date guide on how to do so? I did notice few posts related to that but I'm not sure if they are up to date. Best regards.

You must have an unlocked bootloader.
You need to upload the tgz file with the rom. You will do it through Miflash. Just remember to select the clean all option in Miflash. Don't block the bootloader.
As for the backup, you better not do it depending on what you want to restore. The copy from the Chinese version of the rom can not work well in the global version.
Copy your important stuff on PC then back to your Global Rom phone.

Bartos81 said:
You must have an unlocked bootloader.
You need to upload the tgz file with the rom. You will do it through Miflash. Just remember to select the clean all option in Miflash. Don't block the bootloader.
As for the backup, you better not do it depending on what you want to restore. The copy from the Chinese version of the rom can not work well in the global version.
Copy your important stuff on PC then back to your Global Rom phone.
Click to expand...
Click to collapse
Thanks for a quick response, so mi flash is on this location right (https://www.xiaomiflash.com/)? And for the roms is it safe to use them from this link (https://c.mi.com/global/miuidownload/index). Any other advice just so I don't end up with a dead phone? Also do I unlock bootloader also via MiFlash?

I recommend this version of miflash
https://www.xiaomiflash.com/downloads/MiFlash20180528.zip
Also watch carefully the movie
fastboot files for miflash
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
in the rom file you will have to delete the ARB line
as for unlocking the bootloader, the Xiaomi website is for this.
Apply for unlocking Mi devices
en.miui.com
I have uploaded global 10 times, and there were no problems at all.

Bartos81 said:
I recommend this version of miflash
https://www.xiaomiflash.com/downloads/MiFlash20180528.zip
Also watch carefully the movie
fastboot files for miflash
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
in the rom file you will have to delete the ARB line
as for unlocking the bootloader, the Xiaomi website is for this.
Apply for unlocking Mi devices
en.miui.com
I have uploaded global 10 times, and there were no problems at all.
Click to expand...
Click to collapse
I've tried using this miflash link but it was password protected so I get latest version. I did follow the guide and one of other videos from same author for unlocking. I got to this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure should I wait now or what . I did try logging in via same number on my browser and on utility and on phone, and also ID of account is the same and I can see phone number as recovery option and my ultra under device. Got no idea why phone number wouldn't be associated. One thing I can see when I turn on my phone is SMS service can't be activated, and also find my phone seems to be available only in China (seen a post somewhere that it needs to be turned on). MiUnlock seems to show option to add account and device everytime I enter it

First you need to unlock the bootloader. To do this, you must correctly add the Mi account to the phone and wait for 2 - 3 weeks

Bartos81 said:
First you need to unlock the bootloader. To do this, you must correctly add the Mi account to the phone and wait for 2 - 3 weeks
Click to expand...
Click to collapse
Yup that's what I tried but I can't even get to the period of 168h. Probably since SIM seems to not be activated. Even though I can send and receive SMS normally

Ok, managed to get it working, I've deleted my old account and created a new one directly from phone and got to the timer
I can now normally use my phone for that period of time?

jarac2 said:
Ok, managed to get it working, I've deleted my old account and created a new one directly from phone and got to the timer
View attachment 5486783
I can now normally use my phone for that period of time?
Click to expand...
Click to collapse
Yes. You can normally use it. Just not able to unlock the Bootloader and because of that no root / Magisk and stuff. But you can still debloat with ADB if you want.

Question Unable to update Android (NE2213 of unknown origin)

I bought a slightly used 10 Pro (NE2213) from the local ebay. I am based in Bulgaria.
Phone is in great condition and has no sign of wear and tear. HOWEVER....
1. The Camera app keeps crashing.
2. Half of my pictures show as black squares in my Gallery. I don't know if they're not being saved or the previews are glitchy.
That's a big deal to me, because I bought this phone for my wife, so she can take photos of our baby.
So I thought I'd go ahead and update the software of the phone. It has Android 11. No matter what I do, it is impossible to get the update to install. "Extraction failed. Please try again".
I tried resetting the phone to factory settings several times, I tried turning on Developer Mode to install it manually, I tried installing Oxygen Updater from the Playstore, but I was never able to get past this error.
What am I missing here and what can I do? Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did you try to do a local upgrade with the update downloaded from OxygenUpdater?

TheNewHEROBRINE said:
Did you try to do a local upgrade with the update downloaded from OxygenUpdater?
Click to expand...
Click to collapse
Yes, I downloaded the package from OxygenUpdater. Then turned on Developer mode, but the Local Upgrade button from the 3 dots on the top right was always greyed out. OxygenUpdater says I need to install pending updates first, and then use their tool. I was never able to get past the screenshot above. :\

That's a nice tip...on the oxygen updater posts, there is one to restore your phone form Android 13, use that full package to flash OOS 12 again and you're good to go.

zopostyle said:
That's a nice tip...on the oxygen updater posts, there is one to restore your phone form Android 13, use that full package to flash OOS 12 again and you're good to go.
Click to expand...
Click to collapse
Please excuse my ignorance.
How do I "use a package to flash OOS 12 again"? Keep in mind I have Android 11, not 13. and that it's my first time having to do something like this. Does my phone need to be rooted for that?
I appreciate your patience and help, this is my first time having to deal with phone mods.

He said that he has the local update option grayed out so he can't install any package manually. Maybe it's grayed out because there is already another update downloaded. You should try to disable automatic updates and then delete the downloaded update from the internal memory of the phone, it should be in a folder called .Ota. If you can't see that folder you need to enable the option to show hidden files.

My best guess is use the NE2213 Full Downgrade ZIP. It should upgrade you to Android 12 and it's their only released FULL recovery zip so, it's your best bet.
However, seeing as you are on Android 11, some people here might want a dump of some images first, hahaha. It's widely believed this phone does not ship with Android 11

Download this package
https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip
And apply it using this apk https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Source: https://oxygenupdater.com/article/346/
You don't need to do anything more, but I would recommend you to unlock your bootloader just for precaution if something goes wrong.
Remember to have a full battery before starting the process and I strongly recommend to download from your PC or from oxygen updater to make sure that the package didn't corrupted

zopostyle said:
Download this package
https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip
And apply it using this apk https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Source: https://oxygenupdater.com/article/346/
You don't need to do anything more, but I would recommend you to unlock your bootloader just for precaution if something goes wrong.
Remember to have a full battery before starting the process and I strongly recommend to download from your PC or from oxygen updater to make sure that the package didn't corrupted
Click to expand...
Click to collapse
I agree with this. I think it's the best option.

ivan_10pro said:
Please excuse my ignorance.
How do I "use a package to flash OOS 12 again"? Keep in mind I have Android 11, not 13. and that it's my first time having to do something like this. Does my phone need to be rooted for that?
I appreciate your patience and help, this is my first time having to deal with phone mods.
Click to expand...
Click to collapse
The phone released with Android 12 dude, not 11... If I remember correctly there was an Android 11 preview but it was never official so it may be a test device or ambassador device.
My first thoughts would be... Send it back... There's zero reasons why you can't as you're covered for things just like this.... If it's eBay then you should really use PayPal so you're covered.
Beyond that you can use the rollback package to roll back to the earlier versions of android 12, this will flash 2213 onto the device, just Google OnePlus community rollback and you'll find it.
Few other things, are you sure it's a 2213 or a region changed Chinese variant? Did it come in a box? Does that state 2213?
Either way this issue shouldn't be occurring, I'd be sending that back buddy.