Database Develop

Bootloop Realme x2 pro RMX1931EX

Hello
I have the RMX1931 with the bootloader unlocked and the twrp recovery [3.3.1-13] installed
I want reset my phone because have random reboots.
Download RMX1931EX_11.A.10 for twrp
First wipe this partition
Cache
Dalvik
Data
Click to expand...
Click to collapse
Then flash
Ozip RMX1931EX_11.A.10 for twrp
Vbmeta
Magisk
Click to expand...
Click to collapse
But dont boot in system
first boot not see realme logo and reboot in twrp
i try restored old backup twrp clear device but same results.
only work backup twrp with data partition full, that I did before starting this experiment.
I believe it is the given partition that makes the device boot. With this clean partition it goes into bootloop
please help me

Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot

perisman said:
Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot
Click to expand...
Click to collapse
Tonight i try.
Thank you

perisman said:
Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot
Click to expand...
Click to collapse
you are a genius.
IT WORKS.
Now I have installed the A10 system and restored the app backup via swiftbackup.
everything seems to work, I hope it will not restart.
if you can give me more advice.
thank you very much.
EDIT :
The phone continues to restart.
I'm thinking it can be Magisk root.
Without applications installed
I went crazy with this problem

You can try with last update C25. I flashed from twrp, and now t'he device works fast and smooth. I have magisk, viper4android installed. T'he only problem us FP, because unlocked BL. You can try with a custom ROM, I have tried phh treble and aosip 10, and works very well, and FP works also. You cqn revert to color os 6.x allways flashing A10 ozip. If with other ROMs hsppens t'he random reboots, then is a hardware problem.

it is a real dilemma because with the clean system, however, the phone has restarted for no obvious reason.
I can't understand what makes the phone restart.
only Magisk could be the cause.
I installed Magic which recommends Jerry. but even with the standard version the problem was always the same
Now I send you a screen so it's better evident.
{
"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"
}

Try Another rom, clean system one day to see what It happens

Yes I try In These Days.
Thank you so much for your support

perisman said:
Try Another rom, clean system one day to see what It happens
Click to expand...
Click to collapse
I am now testing the LINEAGE it happened to me this I removed the SIM card and I installed the costum Rom, I made the various customizations and the phone never locked OR restarted.
I inserted the SIM card in the phone worked perfectly, then having messed up with luckypatcher I had to reinstall the Rom.
So I performed the same procedure with the SIM card inserted in the phone and already at the first start it was unstable with reboots.
Currently I have applied for a change of sim card.
As soon as it arrives I will try to remove the sim card Install from scratch The system is to insert the new SIM card only so I can have the mathematical certainty that it is the SIM card
I hope my experience can help someone

perisman said:
You can try with last update C25. I flashed from twrp, and now t'he device works fast and smooth. I have magisk, viper4android installed. T'he only problem us FP, because unlocked BL. You can try with a custom ROM, I have tried phh treble and aosip 10, and works very well, and FP works also. You cqn revert to color os 6.x allways flashing A10 ozip. If with other ROMs hsppens t'he random reboots, then is a hardware problem.
Click to expand...
Click to collapse
i try lienage os, but now i want return colorOS.
i try flashing A10 colorOS.ozip but color OS Boot Loop (Stuck in Realme Logo)
you have solution? for now flash lineageOS and work well but i want colorOS.
please help me

-First, change twrp. Install orangefox or skyhawk twrp (I am using skyhawk and I can revert from C10 trebled rom to
C26 backup, firsr install C26 ozip, and after first boot, reinstall twrp from fastboot and restore full backup)
-Reboot to twrp
-Flash full Ozip , I recommend C26. Works very well, antutu 501.850, no lags, with viper4android installed. With
lineage 371.056 in antutu
-flash vbmeta
-flash magisk
-format data
-reboot
-Once system boots to system, reboot to fastboot to reinstall twrp (with ozip install, you have stock recovery,
check this booting it, depends of twrp you are using. Orangefox saves twrp, skyhawk no)
I hope it helps

I should follow these steps
1 - flash recovery skyhawk twrp
2 - Reboot to twrp
3 - Flash full Ozip (i prefered pie have Fingerprint work)
4 - flash vbmeta
5 - flash magisk
6 - format data
7 - reboot
I have already done these steps with the (ozip A10 FOR TWRP) but color OS Boot Loop (Stuck in Realme Logo).
do you think that recovery creates this problem?
i now have lineageOS work but want return colorOS
thanks for the support
EDIT:
I have run your advice but unfortunately this device perhaps has a hardware problem.
Whenever it manages to boot, just 30 seconds and restart.
I noticed artifacts when starting the sistama.
I'm really desperate.
what do you advise me to do?
thanks

westenlive said:
I am now testing the LINEAGE it happened to me this I removed the SIM card and I installed the costum Rom, I made the various customizations and the phone never locked OR restarted.
I inserted the SIM card in the phone worked perfectly, then having messed up with luckypatcher I had to reinstall the Rom.
So I performed the same procedure with the SIM card inserted in the phone and already at the first start it was unstable with reboots.
Currently I have applied for a change of sim card.
As soon as it arrives I will try to remove the sim card Install from scratch The system is to insert the new SIM card only so I can have the mathematical certainty that it is the SIM card
I hope my experience can help someone
Click to expand...
Click to collapse
Hi, I also have rebooting issues does your X2 pro still reboots? Did changing sim cards solved your reboot problem Im getting desperate.

JKD23 said:
Hi, I also have rebooting issues does your X2 pro still reboots? Did changing sim cards solved your reboot problem Im getting desperate.
Click to expand...
Click to collapse
sorry to tell you but unfortunately this phone has an underlying problem ie the modem hardware is of poor quality.
I have done 1000 tests I have tried everything and more but unfortunately it keeps restarting the user interface when a call comes in or when you try to make a call.
especially when you keep the modem busy for other chores such as navigation with Google Maps or other and you receive a call the phone suffers a stress and this causes a restart.
I have given myself this explanation because it is truly inconceivable that a top-of-the-range phone has these problems.
if you find a solution Let me know.
Thanks so much

westenlive said:
sorry to tell you but unfortunately this phone has an underlying problem ie the modem hardware is of poor quality.
I have done 1000 tests I have tried everything and more but unfortunately it keeps restarting the user interface when a call comes in or when you try to make a call.
especially when you keep the modem busy for other chores such as navigation with Google Maps or other and you receive a call the phone suffers a stress and this causes a restart.
I have given myself this explanation because it is truly inconceivable that a top-of-the-range phone has these problems.
if you find a solution Let me know.
Thanks so much
Click to expand...
Click to collapse
Sorry to hear that ? I'm also suspecting that I have hardware problem it only reboots when connecting to LTE mobile data. I already tried using flash tool for a clean flash didnt work though.
I'm still hoping it's a software issue because I can still get LTE signal I just can't use mobile data. I kinda regretted buying this phone. I'm so unlucky I got a defective device. ?
If I find a solution I'll let you know.

JKD23 said:
Sorry to hear that [emoji853] I'm also suspecting that I have hardware problem it only reboots when connecting to LTE mobile data. I already tried using flash tool for a clean flash didnt work though.
I'm still hoping it's a software issue because I can still get LTE signal I just can't use mobile data. I kinda regretted buying this phone. I'm so unlucky I got a defective device. [emoji24]
If I find a solution I'll let you know.
Click to expand...
Click to collapse
Basically these have mounted a modem on this phone which in my opinion is not fully compatible with the Snapdragon.
In fact, the price is really very low if you consider that this is a top-of-the-range Smartphone with a 90 Hertz screen and latest generation processor.
They are practically giving it away now on the official website it costs € 350.

westenlive said:
Basically these have mounted a modem on this phone which in my opinion is not fully compatible with the Snapdragon.
In fact, the price is really very low if you consider that this is a top-of-the-range Smartphone with a 90 Hertz screen and latest generation processor.
They are practically giving it away now on the official website it costs € 350.
Click to expand...
Click to collapse
Realme should acknowledge these problems and improve the quality of their units. Let's hope Realme Dev team would release updates that could fix our units. (fingers crossed)

JKD23 said:
Realme should acknowledge these problems and improve the quality of their units. Let's hope Realme Dev team would release updates that could fix our units. (fingers crossed)
Click to expand...
Click to collapse
Dear
since you texted me I have been looking for the problem once again.
I have ILIAD as an operator.
I had self-configuring SMS sent for APNs.
With the new APN the problem seems to have disappeared.
try it too and let me know
hello [emoji1309]

westenlive said:
Dear
since you texted me I have been looking for the problem once again.
I have ILIAD as an operator.
I had self-configuring SMS sent for APNs.
With the new APN the problem seems to have disappeared.
try it too and let me know
hello [emoji1309]
Click to expand...
Click to collapse
That's good to hear, I tried your suggestion using self configuring apns through sms, my other operator doesn't send me any sms while the other one was not self configuring. Doesn't seems to work for me Ill try again rechecking the APNs. I also pulled an ADB bug report and sent it to Realme Devs through email they haven't replied yet. When I opened it I saw a few errors like but I couldn't understand it since im not a dev but a run some hardware and sensor diagnostics app and all sensors seems to be working fine. I hope the devs would reply sooner.

JKD23 said:
That's good to hear, I tried your suggestion using self configuring apns through sms, my other operator doesn't send me any sms while the other one was not self configuring. Doesn't seems to work for me Ill try again rechecking the APNs. I also pulled an ADB bug report and sent it to Realme Devs through email they haven't replied yet. When I opened it I saw a few errors like but I couldn't understand it since im not a dev but a run some hardware and sensor diagnostics app and all sensors seems to be working fine. I hope the devs would reply sooner.
Click to expand...
Click to collapse
Hi dear
have you tried to update to Version: RMX1931EX_11.C.32.
From the log it would seem that they have solved the problems that happen to us.
I have the phone too full and rooted and I would not like to update to android 10 so I am still stuck on android 9.
Have you updated?

Question [CLOSED] Pls help to fix: dm-verify corruption

For my Redmi Note 10 5G bought from Vodafone UK, initially I used Xiaomi Tool V2 (https://www.xiaomitool.com/V2/) to install the ROM, but it failed with error. After that any power on/reboot shows 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"
}
Then I went into Fastboot and used MiFlash tool to install a ROM, that installed successfully. But each time I reboot (or fresh power on) I get the above error and the phone switches off itself. But if I press the power on within the 5 seconds, it will power on and then the phone works fine.
Although the phone works fine, any reboot doesn't work automatically, I need to press power button within 5 seconds for it to work.
Now my question is how to fix the error in the screenshot?

fm663 said:
For my Redmi Note 10 5G bought from Vodafone UK, initially I used Xiaomi Tool V2 (https://www.xiaomitool.com/V2/) to install the ROM, but it failed with error. After that any power on/reboot shows this error:
View attachment 5458547
Then I went into Fastboot and used MiFlash tool to install a ROM, that installed successfully. But each time I reboot (or fresh power on) I get the above error and the phone switches off itself. But if I press the power on within the 5 seconds, it will power on and then the phone works fine.
Although the phone works fine, any reboot doesn't work automatically, I need to press power button within 5 seconds for it to work.
Now my question is how to fix the error in the screenshot?
Click to expand...
Click to collapse
Try with:
adb disable-verity
or flashing blank/null vbmeta:
fastboot --disable-verity flash vbmeta vbmeta.img or:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta vbmeta.img

@SubwayChamp Thank you for help. However I am getting this error:
adb disable-verity
verity cannot be disabled/enabled - USER build​
If I were do do the fastboot commands, will it wipe out the ROM+data in the phone (Note I have already been using it for last 1-2 weeks)? Also where to get the vbmeta.img file?

fm663 said:
@SubwayChamp Thank you for help. However I am getting this error:
adb disable-verity
verity cannot be disabled/enabled - USER build​
If I were do do the fastboot commands, will it wipe out the ROM+data in the phone (Note I have already been using it for last 1-2 weeks)? Also where to get the vbmeta.img file?
Click to expand...
Click to collapse
This vbmeta will work https://forum.xda-developers.com/attachments/vbmeta-tar.5065875/ (unzip it) not sure if this solves it, but it is worth the try. And not, flashing the vbmeta won't wipe your data.
I guess your device is unlocked, or maybe you did try to flash something unofficial on it being locked?, what happened prior to this appear?

SubwayChamp said:
This vbmeta will work https://forum.xda-developers.com/attachments/vbmeta-tar.5065875/ (unzip it) not sure if this solves it, but it is worth the try. And not, flashing the vbmeta won't wipe your data.
I guess your device is unlocked, or maybe you did try to flash something unofficial on it being locked?, what happened prior to this appear?
Click to expand...
Click to collapse
Initially I unlocked the phone, then installed Indonesian ROM from Xiaomi website and locked it back.
Does the phone need to be unlocked again?

fm663 said:
Initially I unlocked the phone, then installed Indonesian ROM from Xiaomi website and locked it back.
Does the phone need to be unlocked again?
Click to expand...
Click to collapse
Yes, of course, this is why the warning message is appearing. In the other hand you were lucky to not brick your device, be careful not all the firmwares are interchangeable, specifically the Chinese, to be locked.
I mean, if you only are interested in this message to disappear, you should install again the same ROM that your device was in, but the Indonesian ROM is more attractive over the Global ROM despite the bloatware that can be uninstalled easily.

SubwayChamp said:
Yes, of course, this is why the warning message is appearing. In the other hand you were lucky to not brick your device, be careful not all the firmwares are interchangeable, specifically the Chinese, to be locked.
I mean, if you only are interested in this message to disappear, you should install again the same ROM that your device was in, but the Indonesian ROM is more attractive over the Global ROM despite the bloatware that can be uninstalled easily.
Click to expand...
Click to collapse
Yes, it is the best ROM for my requirements, except I couldn't get Dual Apps to work in it. Do you know how to?
As I want to use Google Pay + NFC, thus I need it locked.
Problem now is I'll loose all data and its time consuming to install everything all over again.
Maybe I'll leave with this error as is for now, unless I find an easier way

fm663 said:
Yes, it is the best ROM for my requirements, except I couldn't get Dual Apps to work in it. Do you know how to?
As I want to use Google Pay + NFC, thus I need it locked.
Problem now is I'll loose all data and its time consuming to install everything all over again.
Maybe I'll leave with this error as is for now, unless I find an easier way
Click to expand...
Click to collapse
Strange, I used Dual apps in my RN8 exactly in Indonesian ROM (I switched from global because of the absence of Phone and Message native apps) although you are fear to, probably you need to format data in order that can work.
There are some workarounds in the Magisk thread to use GPay and NFC, although rooted.
I don't think there is an easy way because of locked bootloader.

SubwayChamp said:
Strange, I used Dual apps in my RN8 exactly in Indonesian ROM (I switched from global because of the absence of Phone and Message native apps) although you are fear to, probably you need to format data in order that can work.
There are some workarounds in the Magisk thread to use GPay and NFC, although rooted.
I don't think there is an easy way because of locked bootloader.
Click to expand...
Click to collapse
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?

fm663 said:
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?
Click to expand...
Click to collapse
actually all you have been asking has been discussed already, we are all busy but at least spend 10 minutes searching, vbmeta, dm-verity, nfc+Google pay all well discussed already, please spend 10 minutes by searching

simika said:
actually all you have been asking has been discussed already, we are all busy but at least spend 10 minutes searching, vbmeta, dm-verity, nfc+Google pay all well discussed already, please spend 10 minutes by searching
Click to expand...
Click to collapse
Thank you for the tips.
Maybe I am not good at searching. I have many days of searching over the last few months and did not find the answers. I have another phone Mi Mix 2 that is unlocked and few things don't work in it due to CTS Profile issue. I would like to get that fixed too. Can you point to me specific pages please? Thank you

fm663 said:
Thank you for the tips.
Maybe I am not good at searching. I have many days of searching over the last few months and did not find the answers. I have another phone Mi Mix 2 that is unlocked and few things don't work in it due to CTS Profile issue. I would like to get that fixed too. Can you point to me specific pages please? Thank you
Click to expand...
Click to collapse
sure:
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
here you'll find answers about root, dm-verity and much more, always related to poco m3 pro and redmi note

fm663 said:
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?
Click to expand...
Click to collapse
If you want to stay locked no way to disable this warning message but if you decide to unlock your device and root it, it is pretty easy to fix it, one of the methods available is what I indicated, flashing a blank/null vbmeta through specific fastboot commands, there are other methods though, but this is the most universal and easy to use.
In regard to the CTS issue, I don't use GPay, so I can't tell you, but no better place that the Magisk Discussion Thread, it is the appropriate thread where you can find all the info from all the members affected on that, in the meantime you also can take a read on this https://droidholic.com/fix-safetynet-failed-cts-profile-false/

1. Hello friends, there are two ways to fix this problem. First, you need Root, and after using Root, you need to download any file manager and give Root permission. You need to backup your baseband, nvram nvdata nvcfg after backup Save, you also need an MTK Bypass You can search for MTK Auth Bypass Tool through Google. To download, you also need to use SP Flash to flash the machine. You need to download the official firmware package. You can download it through xiaomirom.com, download the corresponding version, and use SP Flash to read your firmware package, after the reading is completed, choose to format all and download, wait for the completion, press the power button after completion, you will find that the error has disappeared, but the baseband is lost, but you have backed up. Boot through fastboot to unlock the BL lock, and proceed fastboot flash nvram ....... fastboot flash nvdata ....... fastboot flash nvcfg ....... Fastboot reboot reboot. congratulations your baseband is back, i am a newbie and my instructions are very Not comprehensive, such as where is the baseband position, but I have too many characters, I will list the baseband position. 2. Replace a new motherboard, all mobile phone problems are solved.
Hope to help you.

THREAD LOCKED
As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
-snip-
-snip-
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
-snip-
Click to expand...
Click to collapse
Please search the forum for existing/similar threads before posting a new thread. For continuing discussion, kindly use the existing thread: https://forum.xda-developers.com/t/how-to-get-rid-of-dm-verity-corruption-on-boot.4290677/
Regards,
shadowstep
Forum Moderator

Question -12 hours before bootloader unlock, what next?

Hi guys,
I hope you are all well.
Finally tomorrow I will be able to unlock the BT of my Mi 11.
I would like to flash the EEA Rom without any other customization. The phone is currently on MIUI 12.5.7 CN Rom, I did not update it on purpose.
Shall I just unlock the bootloader and flash the fastboot venus_eea_global_images_V12.5.9.0.RKBEUXM_20211214.0000.00_11.0_eea_dc91966e19 with Mi Flash?
12.5.9 over 12.5.7 will be alright?
My understanding is that I should keep widevine L1 but safetynet will be a fail?
Thank you all for your help.
P.S.
Checking the unlock status after requesting BT unlock did not reset the counter for me, I kept checking every day

Above all, be careful to NEVER reloack your CN Venus Mi 11 with a another branch rom (EEA / Global), if not you will brick your device.
So be careful to Mi Flash, because by default option "clean & lock" is always selected by default.
{
"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 advise to install Stable Xiaomi.eu from here, more safe, you have less risk to brick your device because a **** OTA (MIUI 13 is knowed for that)

Pho3nX said:
Above all, be careful to NEVER reloack your CN Venus Mi 11 with a another branch rom (EEA / Global), if not you will brick your device.
So be careful to Mi Flash, because by default option "clean & lock" is always selected by default.
View attachment 5550211
I advise to install Stable Xiaomi.eu from here, more safe, you have less risk to brick your device because a **** OTA (MIUI 13 is knowed for that)
Click to expand...
Click to collapse
Thank you.
Yes I ll leave the bootloader unkocked...but I ll flash the eea rom, I m looking for a stock experience as much as possible.
If it bricks the phone I ll fix it and sell it afterwards, I m already stressed AF in this period, cannot be stressed about the phone too! I ll buy a Pixel maybe, not a lot of choices in europe actually...

Dorian. said:
Thank you.
Yes I ll leave the bootloader unkocked...but I ll flash the eea rom, I m looking for a stock experience as much as possible.
If it bricks the phone I ll fix it and sell it afterwards, I m already stressed AF in this period, cannot be stressed about the phone too! I ll buy a Pixel maybe, not a lot of choices in europe actually...
Click to expand...
Click to collapse
I really recommend you to use miui 13 Xiaomi.eu Stable or miui 13 global/EEA. Android 12 update really make this device ui smooth without any noticeable frame drops. Xiaomi.eu is basically a CN ROM with all the global languages. Have both google dialer, messages and Xiaomi dialer and messages. You can find a fastboot version that I made of miui 13 global/EEA here https://forum.xda-developers.com/t/...-global-eea-stable-and-miui-13-china.4381953/. It is very easy to install, just one click on "windows_fastboot_first_install_with_data_format.bat" file and wait for the phone to restart.(will wipe your internal storage) You do not need Mi flash for this, and thus can not lock your bootloader accidentally.

Hi guys,
just to follow up on this.
unlocked the bootloader today, after unlocking the phone got stuck on the Miui logo...
so I ve rebooted in Fastboot mode and flashed the EEA 12.5.9 rom with MiFlash.
All went good apparently but in the end it completed with an error (mentioning a checkpoint)
booted, factory reset, started phone setup.
All good and as expected, widevine 1, Safetynet fail, my banking apps are working..only issue is Netflix from Googleplay not available, I ll try to sideload it later on.
Everything seems good enough,waiting for Miui13 OTA.
Thank you all again for your help

Dorian. said:
Hi guys,
just to follow up on this.
unlocked the bootloader today, after unlocking the phone got stuck on the Miui logo...
so I ve rebooted in Fastboot mode and flashed the EEA 12.5.9 rom with MiFlash.
All went good apparently but in the end it completed with an error (mentioning a checkpoint)
booted, factory reset, started phone setup.
All good and as expected, widevine 1, Safetynet fail, my banking apps are working..only issue is Netflix from Googleplay not available, I ll try to sideload it later on.
Everything seems good enough,waiting for Miui13 OTA.
Thank you all again for your help
Click to expand...
Click to collapse
I am using 12.5.9 EEA. Came from phone with Global ROM, so I did exactly what you did - unlocked bootloader, then used miflash to do the EEA flash.
I can tell you it is normal to see the error at end of flash when you pick the "erase but don't lock" option. If you look at the .bat file for this option, the end of the batch file references something that doesn't exist, causing the error. Xiaomi folks screwed something up there, and actually it has been like that since the Mi 9 days (I used to own a Mi 9). So nothing to worry about.

seemebreakthis said:
I am using 12.5.9 EEA. Came from phone with Global ROM, so I did exactly what you did - unlocked bootloader, then used miflash to do the EEA flash.
I can tell you it is normal to see the error at end of flash when you pick the "erase but don't lock" option. If you look at the .bat file for this option, the end of the batch file references something that doesn't exist, causing the error. Xiaomi folks screwed something up there, and actually it has been like that since the Mi 9 days (I used to own a Mi 9). So nothing to worry about.
Click to expand...
Click to collapse
Hi, just to report I got Miui 13 OTA by changing region from ireland to Italy. I did the update, all good, works well

Question How to remove an encrypted custom os

{
"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 have a pixel 5a that was flashed with a custom os the restricted developer options and locked the bootloader is there any way for me to remove the os and go back to stock android?
This is what they sent me
(I was told that I might be able to flash the snapdragon soc directly by putting the phone in edl mode does anyone know if it’s feasible?)

I am certainly far from the sharpest tool in the shed here, but since no one else is speaking up, I'll try my hand at it.
You shouldn't be concerned with the bootloader being locked - you should be concerned if it can be UNLOCKED. The keys are writable from fastboot- custom ROMs like CalyxOS can be built and flashed with the proper keys to boot with a locked bootloader. The process of signing is described in AOSP documentation, and works on the 5A 5G (I have a customized variant of CalyxOS, signed by myself, with locked bootloader).
Carriers make special deals with the phone companies to OEM lock the bootloaders so that they cannot be unlocked via fastboot, without a key (likely IMEI specific). I don't know of anyone who has figured out how to OEM lock without actually being an OEM, but maybe it is possible.
Are you just finding a phone cheaper than the stock Pixel, hoping to reflash, or is this more complicated? The retail Google phone is most certainly unlockable with /no/ drama...

SomeRandomGuy said:
I am certainly far from the sharpest tool in the shed here, but since no one else is speaking up, I'll try my hand at it.
You shouldn't be concerned with the bootloader being locked - you should be concerned if it can be UNLOCKED. The keys are writable from fastboot- custom ROMs like CalyxOS can be built and flashed with the proper keys to boot with a locked bootloader. The process of signing is described in AOSP documentation, and works on the 5A 5G (I have a customized variant of CalyxOS, signed by myself, with locked bootloader).
Carriers make special deals with the phone companies to OEM lock the bootloaders so that they cannot be unlocked via fastboot, without a key (likely IMEI specific). I don't know of anyone who has figured out how to OEM lock without actually being an OEM, but maybe it is possible.
Are you just finding a phone cheaper than the stock Pixel, hoping to reflash, or is this more complicated? The retail Google phone is most certainly unlockable with /no
SomeRandomGuy said:
I am certainly far from the sharpest tool in the shed here, but since no one else is speaking up, I'll try my hand at it.
You shouldn't be concerned with the bootloader being locked - you should be concerned if it can be UNLOCKED. The keys are writable from fastboot- custom ROMs like CalyxOS can be built and flashed with the proper keys to boot with a locked bootloader. The process of signing is described in AOSP documentation, and works on the 5A 5G (I have a customized variant of CalyxOS, signed by myself, with locked bootloader).
Carriers make special deals with the phone companies to OEM lock the bootloaders so that they cannot be unlocked via fastboot, without a key (likely IMEI specific). I don't know of anyone who has figured out how to OEM lock without actually being an OEM, but maybe it is possible.
Are you just finding a phone cheaper than the stock Pixel, hoping to reflash, or is this more complicated? The retail Google phone is most certainly unlockable with /no/ drama...
Click to expand...
Click to collapse
im not even sure that I can access it from fastboot because as I said developer options is restricted on the phone so I can’t enable usb debugging and oem unlocking
Click to expand...
Click to collapse

I need to find someway to flash stock android back onto it

Google's support website for the Pixels lets you do it... directly from any browser that supports WebUSB (e.g. Chrome and its variants, newer FF's, etc).

SomeRandomGuy said:
Google's support website for the Pixels lets you do it... directly from any browser that supports WebUSB (e.g. Chrome and its variants, newer FF's, etc).
Click to expand...
Click to collapse
I dont think it’ll work without enabling usb debugging

CustomOShacks said:
I dont think it’ll work without enabling usb debugging
Click to expand...
Click to collapse
you can flash the stock factory image from here in bootloader mode (power + vol down)
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
i use to this site remove non stock keys. at the very bottom of the webpage if i want to return to stock and flashed calyxos or graphenos to my phone.
GrapheneOS web installer
Web-based installer for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org

rchris494 said:
you can flash the stock factory image from here in bootloader mode (power + vol down)
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
i use to this site remove non stock keys. at the very bottom of the webpage if i want to return to stock and flashed calyxos or graphenos to my phone.
GrapheneOS web installer
Web-based installer for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
Click to expand...
Click to collapse
The bootloader is locked

CustomOShacks said:
The bootloader is locked
Click to expand...
Click to collapse
i did run across this. i am not sure how trust worthy the tools this person has are
https://www.youtube.com/c/5MinuteSolutions-DZ
i also did not see anything pixel 5a related.
also maybe there is something on 4pda that can help with the problem

rchris494 said:
i did run across this. i am not sure how trust worthy the tools this person has are
https://www.youtube.com/c/5MinuteSolutions-DZ
i also did not see anything pixel 5a related.
also maybe there is something on https://4pda.to/ that can help with the problem
Click to expand...
Click to collapse
Can you please post something more specific

Do you know if these tools will work without usb debugging enabled because the custom rom that my 5a is running restricts developer options so I don’t know how to enable usb debugging

So, by chance (and my stupidity) I am now in the same boat. This is a very frustrating situation that is close to making me swear off the entire Pixel line, forever.
TL;DR: Is there ANYTHING that works in fastboot mode with a locked bootloader?
Long version:
- I have a properly signed custom OS, and all the images AOSP would build (the factory image, the OTA image, etc).
- When the phone was last booted, "Enable OEM Unlocking" was ON, with the bootloader locked. Everything worked nicely.
- I stupidly let Magisk update itself, which of course borked the boot
- I can no longer get into recovery from fastboot (whines about broken OS) (e.g. to sideload OTA update)
- Despite OEM unlocking being on (or having been on and cursed with somehow it getting turned off), I can't unlock bootloader from fastboot
- I can't flash ANY partition (at least that I tried); all whine about locked bootloader
- I can't flash original Google image either (from Google web installer), whines about unlocking
- I can't use the GrapheneOS web installer to unlock bootloader (just fails)
- I can't fastboot boot <signed_boot_image> (e.g. to get to sideload from recovery), whines about unlocking
Especially with a device that doesn't allow SDCards, I'm far more concerned with something bad happening (like whoops, clicked the wrong button and autoupdated => brick) and me not being able to pull my data (SMS/MMS stuff, pictures, etc) than I am about all the (mostly valid) reasons for verified boot.
I would assume that I could still flash partitions that were properly signed by whatever keys were installed. Guess not. What a stupid restriction.
I'd also assume I could flash partitions signed by Google (if secure boot can tell me I'm running something other than stock, that means it has keys to verify stock, right?). Guess not. What a stupid restriction.
On a OnePlus, a quick EDL flash would unbrick this (would destroy data, of course, but at least I am not out $~500). I understand there are no EDL images published anyway (and I certainly can't find any).
I've read the above posts about overwriting the FBI's version of Android, and didn't find any functional means of unlocking and/or returning to stock (e.g the web installers for GrapheneOS or Google).
Is there maybe something I've missed? A lower level fastboot command I can use to restore the boot partition (again, I've got a properly signed one).

Question [SOLVED] cant get past thru Mi account verification

hi everyone,
i was wiping data off my redmi note 10 5g, i was completely aware about the mi account lock (this):
{
"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 tried to log in then it let me in into setup wizard and immediately reappeared the same screen of the mi account lock. So, I basically put the right verification code and credentials of my MI Account and it wouldnt let me in to setup my phone.
I tried logging in more 3 times and the same thing over and over again, I even tried flashing a GSI just to realize the mi account lock is either connected to the phone's IMEI - as i have read somewhere in xda - or whatever Xiaomi decided to make up in their heads.
This has happened to me when I did the same thing - and the most weird thing is that, few months ago, I was testing a GSI coming from miui with my MI account, and then reflashed MIUI back again and no MI account lock popped up, being the same account since I ever got the phone, even though I tried to flash a GSI to see if it would solve it.
I even locked it by trying out the Find My Device and it let me in perfectly fine.
And yes, this has unlocked bootloader, but the 2 phrases above also was when I had it unlocked, and even with root.
I dont know what to do anymore, recovery flashing just doesnt work too, it doesnt detect my device, and I please ask for some help to be fast too, I appreciate it.

1lopes said:
hi everyone,
i was wiping data off my redmi note 10 5g, i was completely aware about the mi account lock (this):
View attachment 5721901
I tried to log in then it let me in into setup wizard and immediately reappeared the same screen of the mi account lock. So, I basically put the right verification code and credentials of my MI Account and it wouldnt let me in to setup my phone.
I tried logging in more 3 times and the same thing over and over again, I even tried flashing a GSI just to realize the mi account lock is either connected to the phone's IMEI - as i have read somewhere in xda - or whatever Xiaomi decided to make up in their heads.
This has happened to me when I did the same thing - and the most weird thing is that, few months ago, I was testing a GSI coming from miui with my MI account, and then reflashed MIUI back again and no MI account lock popped up, being the same account since I ever got the phone, even though I tried to flash a GSI to see if it would solve it.
I even locked it by trying out the Find My Device and it let me in perfectly fine.
And yes, this has unlocked bootloader, but the 2 phrases above also was when I had it unlocked, and even with root.
I dont know what to do anymore, recovery flashing just doesnt work too, it doesnt detect my device, and I please ask for some help to be fast too, I appreciate it.
Click to expand...
Click to collapse
Just in case, you should connect to the Wi-Fi. and then activate your Mi account, the Mobile data doesn´t work.
Open Mi account in a PC, and check if you are not missing something.

Connect tu eifi, and after insert mi password. Is simply

its not about that. i cant verify it, I put the right code, my mi account credentials, and it doesnt work. it just re-appears the same screen after I do everything right, even changed my mi account password 3 times, verified both with phone and email
check the gif for example below
https://imgur.com/a/VVZ7zaH
(its imgur and only the gif just for you guys to understand)

1lopes said:
its not about that. i cant verify it, I put the right code, my mi account credentials, and it doesnt work. it just re-appears the same screen after I do everything right, even changed my mi account password 3 times, verified both with phone and email
check the gif for example below
https://imgur.com/a/VVZ7zaH
(its imgur and only the gif just for you guys to understand)
Click to expand...
Click to collapse
Sign in Xiaomi/Mi account, go to /Signing in and Security/Manage Devices/Your device, then click on it, and Delete device, you will sign in out from your Xiaomi account, and you have to restart your device.
Just keep in mind, that the same that it could be, actually happening, if your device was linked to another Mi account, in the past, being for a previous user, or the seller did need to unlock it by any means, it won't work, otherwise, definitely, it has to work.

SubwayChamp said:
Sign in Xiaomi/Mi account, go to /Signing in and Security/Manage Devices/Your device, then click on it, and Delete device, you will sign in out from your Xiaomi account, and you have to restart your device.
Just keep in mind, that the same that it could be, actually happening, if your device was linked to another Mi account, in the past, being for a previous user, or the seller did need to unlock it by any means, it won't work, otherwise, definitely, it has to work.
Click to expand...
Click to collapse
nope, sadly no work, it had the device on my mi account but even after removing it, it did the same thing where I verified and it would reapper the same screen.
this is the only account of xiaomi i have, that ive ever used since i first got this phone, and it wasnt bought from anyone nor even used (i dont know where it was bought tho since it was a gift, but it came with the box and everything in it normally and was never mi locked)

1lopes said:
nope, sadly no work, it had the device on my mi account but even after removing it, it did the same thing where I verified and it would reapper the same screen.
this is the only account of xiaomi i have, that ive ever used since i first got this phone, and it wasnt bought from anyone nor even used (i dont know where it was bought tho since it was a gift, but it came with the box and everything in it normally and was never mi locked)
Click to expand...
Click to collapse
Check the IMEI from the box, and compare with https://www.mi.com/global/verify/#/en/tab/imei, if the model is the same as it is supposed to.
Try to go to recovery mode, for that, power off device, then press volume up + PWR buttons, and wipe data, see if it helps.

SubwayChamp said:
Check the IMEI from the box, and compare with https://www.mi.com/global/verify/#/en/tab/imei, if the model is the same as it is supposed to.
Try to go to recovery mode, for that, power off device, then press volume up + PWR buttons, and wipe data, see if it helps.
Click to expand...
Click to collapse
it is the same model and i know about it, also wiping data does absolutely nothing, did it over 3 times, this is probably connected to the phone's imei or whatever. its probably unrecoverable without going to a service center anyways or using a GSI rather than miui.
wonder why your solution to remove the device from my mi account didnt work, even after verifying its the same.
anyways, ill see what i can do with it, unless you or someone else can get it to work, would be alot thankful, but dont go out there looking for it as probably most of what you can find probably I have used to do it, so yea leaves us with little to no options in the end afterall and solution is either go to the service center.
thanks alot for the help tho, appreciate it

1lopes said:
it is the same model and i know about it, also wiping data does absolutely nothing, did it over 3 times, this is probably connected to the phone's imei or whatever. its probably unrecoverable without going to a service center anyways or using a GSI rather than miui.
wonder why your solution to remove the device from my mi account didnt work, even after verifying its the same.
anyways, ill see what i can do with it, unless you or someone else can get it to work, would be alot thankful, but dont go out there looking for it as probably most of what you can find probably I have used to do it, so yea leaves us with little to no options in the end afterall and solution is either go to the service center.
thanks alot for the help tho, appreciate it
Click to expand...
Click to collapse
The only thing I can think of, is that, some kind of protection was triggered, after a non-authorized action to the user side. Also, the vendor partition could get corrupt, after flash other image.
With this tool, https://github.com/bkerler/mtkclient you should back up every partition, it doesn't matter super image, and data also occupy a lot of space.
After backup every partition, try erasing the FRP partition, and try to boot.

SubwayChamp said:
The only thing I can think of, is that, some kind of protection was triggered, after a non-authorized action to the user side. Also, the vendor partition could get corrupt, after flash other image.
With this tool, https://github.com/bkerler/mtkclient you should back up every partition, it doesn't matter super image, and data also occupy a lot of space.
After backup every partition, try erasing the FRP partition, and try to boot.
Click to expand...
Click to collapse
Thanks for that one, seems risky, right?
Ill see if i can, since ive sent it to someone i know of, idk if i have it since im not home rn.

SubwayChamp said:
The only thing I can think of, is that, some kind of protection was triggered, after a non-authorized action to the user side. Also, the vendor partition could get corrupt, after flash other image.
With this tool, https://github.com/bkerler/mtkclient you should back up every partition, it doesn't matter super image, and data also occupy a lot of space.
After backup every partition, try erasing the FRP partition, and try to boot.
Click to expand...
Click to collapse
ok, could you do a quick explanation to use mtkclient? just to backup etc, i know the erase partitions, in general, ive never used or touched this phone partitions.

1lopes said:
ok, could you do a quick explanation to use mtkclient? just to backup etc, i know the erase partitions, in general, ive never used or touched this phone partitions.
Click to expand...
Click to collapse
You have to set it up the usual mtk drivers, the UsbDk installer, the Lib USB drivers, then, inside the mtkclient-main.zip, you'll find a README.md, open it with some text reader of your preference, it contains the main commands that you can use.
python mtk r boot boot.img will back up your boot partition, this is using the CLI tool, you also have the GUI tool with an interface, to interact more easily, I prefer the command line, but it's up to you.
The GUI tool lists the partitions, your device has, if you prefer to use the command line, to know them, you can run a bad command like python mtk r bot (instead of boot) boot.img, and the tool will tell you the partitions available.

SubwayChamp said:
You have to set it up the usual mtk drivers, the UsbDk installer, the Lib USB drivers, then, inside the mtkclient-main.zip, you'll find a README.md, open it with some text reader of your preference, it contains the main commands that you can use.
python mtk r boot boot.img will back up your boot partition, this is using the CLI tool, you also have the GUI tool with an interface, to interact more easily, I prefer the command line, but it's up to you.
The GUI tool lists the partitions, your device has, if you prefer to use the command line, to know them, you can run a bad command like python mtk r bot (instead of boot) boot.img, and the tool will tell you the partitions available.
Click to expand...
Click to collapse
so if im correct, i found out a way, but comes out as 3 files each one. i tried dumping (as gpt) and writing vbmeta_a and i got it, i used mtkgui too. so now i do everything you said then erase the frp partition and it should work?

1lopes said:
so if im correct, i found out a way, but comes out as 3 files each one. i tried dumping (as gpt) and writing vbmeta_a and i got it, i used mtkgui too. so now i do everything you said then erase the frp partition and it should work?
Click to expand...
Click to collapse
Now that you have a backup from this partition, you can try it.

SubwayChamp said:
Now that you have a backup from this partition, you can try it.
Click to expand...
Click to collapse
alright thank you so much for your help, ill see soon if i can

1lopes said:
alright thank you so much for your help, ill see soon if i can
Click to expand...
Click to collapse
SubwayChamp said:
Now that you have a backup from this partition, you can try it.
Click to expand...
Click to collapse
sadly its still locked even after erasing the frp partition

1lopes said:
sadly its still locked even after erasing the frp partition
Click to expand...
Click to collapse
Well, the other two partitions that can store credentials are persist and vendor, you can try with them, if you have a backup.
And, flashing a GSI, I wouldn't recommend an official image from a Pixel device in Google site, but some of the custom GSI available in the net.
And, probably, flashing a different fastboot ROM, may make a difference.
Also, finally, flashing a Miui based custom ROM like miui.eu ROM, may get you out of this. It's probable that some flashing process just corrupted a specific partition, and re-flashing it, may restore it, as it seems not an issue from the servers but from your device.

SubwayChamp said:
Well, the other two partitions that can store credentials are persist and vendor, you can try with them, if you have a backup.
And, flashing a GSI, I wouldn't recommend an official image from a Pixel device in Google site, but some of the custom GSI available in the net.
And, probably, flashing a different fastboot ROM, may make a difference.
Also, finally, flashing a Miui based custom ROM like miui.eu ROM, may get you out of this. It's probable that some flashing process just corrupted a specific partition, and re-flashing it, may restore it, as it seems not an issue from the servers but from your device.
Click to expand...
Click to collapse
ok, that works, it disables the lock till i connect to an wifi. what can i do now?

1lopes said:
ok, that works, it disables the lock till i connect to an wifi. what can i do now?
Click to expand...
Click to collapse
Mm, what do you mean with "till I connect to a Wi-Fi?" Could you boot to system?

SubwayChamp said:
Mm, what do you mean with "till I connect to a Wi-Fi?" Could you boot to system?
Click to expand...
Click to collapse
Yes, i could, even set it up and go to the home screen, but if i connect to any wifi it will relock itself till I delete the persist partition once again and I dont connect to a wifi