Database Users

Invalid Imei, Locked Bootloader, no EDL. Can anyone help?

Hi Guys.
This is a Mediatek Helio X25 Redmi Pro and it came to me bricked from its owner who tried to root it the wrong way. I managed to flash an official rom and bring it back to life but as apparently is the case with these phones, the nvram has been corrupted/rewritten and there's no Imei numbers on the phone, which means no calls and stuff. WiFi works fine. I've already had permission to unlock the bootloader but obviously I can't do anything about it since the software won't ID the device. I believe I might be able to flash a backup of nvram.bin, but I don't have one from this phone, which is why I am posting this here, hoping that maybe one of you can help me by sending me a copy of his own Redmi Pro nvram.bin file. Of course I only need it to get the thing back in the system, after which I can unlock it and use the original Imei numbers. Or if someone has another suggestion, I would greatly appreciate it.
Thanks in advance.

Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.

Binnylaw said:
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Click to expand...
Click to collapse
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers

nsterjo said:
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
Click to expand...
Click to collapse
Tried this method?
http://en.miui.com/thread-411112-1-1.html
Sent from my Redmi Note 4 using Tapatalk

If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648

Binnylaw said:
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Click to expand...
Click to collapse
I have tried maybe 3 different versions of Sp Flashtool, including this one. I usually get a timeout message. But I will try again. Is there any specifics I should observe regarding the mdb files I need to use? I have tried all the ones that come with the roms I've tried, but without luck.

MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!

Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
No, you understood fine; it was me who typed SP Flashtool instead of SN Writer, which was what I meant. Everything else is as I wrote. I have tried 3 different versions of SN Writer, I connect fine and it starts the procedure following the same instructions you mentioned, but it stops half way, giving me an error message. I have tried different combinations of MDB and APDB files from several different ROMs I've downloaded, but they all fail. I'm not very familiar with these things but I can follow instructions and am quick to learn. Still, I have no idea why SN Writer or Maui Meta are not working. I tried to download an nvram.bin file I got from the internet with SP Flashtool, but it would not accept it as it was for Helio X20 I believe, which is why I was hoping someone would make available a copy of nvram.bin for this particular phone. I will also try to make a deepflash cable, hoping that might get me into EDL after which I can use MiFlash to reflash a new official Rom, but I don't know if it will work.

help please
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
Hi there, please can you tell me where I find the files (mdb and adb)? Are they somewhere on the phone's firmware? Or somewhere in the rom i flashed?
I'm a beginner having a very similar issue having flashed a rom in rescuing a bricked phone and now have invalid IMEI numbers.
Thanks so much

MI A1 without IMEI, HELP please.

After the error in persist partition, my smartphone is now without IMEI, I've tried everything, but I can not fix. Helpe-me. :crying:
SOLVED

What did you try, there are several threads about it.
You should keep an efs partition backup from twrp in the future.

coremania said:
What did you try, there are several threads about it.
You should keep an efs partition backup from twrp in the future.
Click to expand...
Click to collapse
I tried QPST and WriteDualIMEI, but it did not work, can you help me?

Someone was lucky by flashing the nougat image .18, I never killed my mi a1 iMEI, but I always have a efs backup.
---------- Post added at 19:24 ---------- Previous post was at 19:19 ----------
https://androidfilehost.com/?fid=745849072291691346

coremania said:
Someone was lucky by flashing the nougat image .18, I never killed my mi a1 iMEI, but I always have a efs backup.
---------- Post added at 19:24 ---------- Previous post was at 19:19 ----------
https://androidfilehost.com/?fid=745849072291691346
Click to expand...
Click to collapse
Thank you very much, my friend, I will try here.

Help :/

Look at following thread. https://forum.xda-developers.com/mi-a1/help/mi-a1-imei-lost-phone-restart-t3735440
I could repair it once. Right now I need to repair it again. Don't know how I broke it this time. Will put a step-by-step guide if I can repair it again.

ElKidd said:
Look at following thread. https://forum.xda-developers.com/mi-a1/help/mi-a1-imei-lost-phone-restart-t3735440
I could repair it once. Right now I need to repair it again. Don't know how I broke it this time. Will put a step-by-step guide if I can repair it again.
Click to expand...
Click to collapse
Tried the same. I was able to recover IMEI, but after a few hours, my phone rebooted itself and boila.. Lost IMEI again, since then, QPST won't work, so right now i'm only with WiFi.
I think that trying to recover an EFS backup and after that, make an IMEI change with QPST to recover your IMEI instead of the IMEI from the backup EFS should do the work, but i'm not able to find any EFS backup for the Mi A1.

How can someone lose their device's IMEI?

In my case a fastboot image did that. I have the same problem that QPST doesn't work anymore. That makes me crazy. Phone just seems to work fine with Oreo, but can't install the QCN file right now.

Hey friend, can you give me your Facebook or WhatsApp so I can get some doubts? This problem in the cell phone is horrible.

I couldn't fix my phone. I have now ordered a new Mi A1 and hope to fix the broken one with some export of the new one.

Devices status

Byramklc said:
Devices status
Click to expand...
Click to collapse
Could it be that with the backup of another mi a1 we were able to fix?

ElKidd said:
I couldn't fix my phone. I have now ordered a new Mi A1 and hope to fix the broken one with some export of the new one.
Click to expand...
Click to collapse
Could it be that with the backup of another mi a1 we were able to fix?

I hope that.

Bro first flash 7.8.23 rom flash
Phone starting and phone open *#*#717717#*#* input and PC opening USB diag mode open USB driver installing and writedualimei app download and Admin opening program and write IMEI success and phone restart devices is back 8.1.10 rom flash

Byramklc said:
Bro first flash 7.8.23 rom flash
Phone starting and phone open *#*#717717#*#* input and PC opening USB diag mode open USB driver installing and writedualimei app download and Admin opening program and write IMEI success and phone restart devices is back 8.1.10 rom flash
Click to expand...
Click to collapse
I've already done this and it does not work, I'll do it again and install a ROM 8.1.10

@Byramklc
1) ROM version 7.8.23 doesn't work in my case anymore. Don't know if it has something to do that I updated to Oreo.
2) With the tool writedualimei the IMEI didn't change. Maybe it worked for you, but not for me. QPST did work, but only once.

ElKidd said:
@Byramklc
1) ROM version 7.8.23 doesn't work in my case anymore. Don't know if it has something to do that I updated to Oreo.
2) With the tool writedualimei the IMEI didn't change. Maybe it worked for you, but not for me. QPST did work, but only once.
Click to expand...
Click to collapse
Here the QPST does not recognize my cell phone.
I already installed the drivers and did everything, but not work

SOLVED:Stuck at PIN input, then reboots

Well, I f*cked up.
Fastboot works, I can flash stock rom via Xiaomi Flash. Flashing completes without any problems. A notification about encypting phone shows up, at 3% it jumps to 100% and resumes boot. Now after each boot, phone freezes at "input your sim pin" and reboots. Over and over again. What can I try, please help :

edited

twister26 said:
There is an reward for whoever helps me solve this issue
Click to expand...
Click to collapse
u try put your sim on other phone and remove the pin from them , maybe the boot skip that part and dont get freeze

dfranco51207 said:
u try put your sim on other phone and remove the pin from them , maybe the boot skip that part and dont get freeze
Click to expand...
Click to collapse
no luck, removed sim and now it reboots as soon as android one text is displayed
I've also tried wiping cache in default recovery, no luck

twister26 said:
no luck, removed sim and now it reboots as soon as android one text is displayed
I've also tried wiping cache in default recovery, no luck
Click to expand...
Click to collapse
Try to format data in twrp or stock recovery.
If it does not work flash an android 8.0 or Nougat ROM. Do not lock the bootloader.

Let me guess. From Pie to Oreo or Nougat?

Mercoory said:
Let me guess. From Pie to Oreo or Nougat?
Click to expand...
Click to collapse
yes, exactly is there a thread already open somewhere here and i missed? last time TWRP was working, I even got a message "your system has been destroyed" or something like that.
sipollo said:
Try to format data in twrp or stock recovery.
If it does not work flash an android 8.0 or Nougat ROM. Do not lock the bootloader.
Click to expand...
Click to collapse
will try!

https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624

ccalixtro said:
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Click to expand...
Click to collapse
will give it a read, it it works, I'll PM you and you'll give me your paypal address. Fair is fair.
can't unlock OEM, because I can't boot up to developer tools. great, just great. will try to fix that first.

if you can boot to fastboot try to flash stock pie 10.0.4.0 with miflash, after that your device should be able to boot, than unlock OEM and bootloader and downgrade to what version you want

fdc77 said:
if you can boot to fastboot try to flash stock pie 10.0.4.0 with miflash, after that your device should be able to boot, than unlock OEM and bootloader and downgrade to what version you want
Click to expand...
Click to collapse
I can get to fastboot yeah, but MiFlash tool says that remote oem unlock is not allowed. So I'll probably have to open it up for EDL. Reboot to edl isn't working. Thanks for the advice tho.

twister26 said:
I can get to fastboot yeah, but MiFlash tool says that remote oem unlock is not allowed. So I'll probably have to open it up for EDL. Reboot to edl isn't working. Thanks for the advice tho.
Click to expand...
Click to collapse
i had a problem like yours, but i have flashed stock rom in non EDL mode and everything had start to work apart LTE band missing that i restored with qualcomm's tools
which stock rom have you try to flash? are you downgrading from oreo? bootloop on android one logo after downgrading is a common issue due to ARB (anti rollback protection)

twister26 said:
Whoever saves my precious Mi A1 gets 10$ on his paypal.
Click to expand...
Click to collapse
This is ****
This is not XDA spirit
You can get help without to pay
Please cancel the reward, do it. For all the people on this community.

tropbel said:
This is ****
This is not XDA spirit
You can get help without to pay
Please cancel the reward, do it. For all the people on this community.
Click to expand...
Click to collapse
reward is cancelled from this point on i will reward the one who helped me so far tho. still working on solving the problem so winner has not been decided yet.

you don't understand.
There are no winners and no loosers.
You are free to donate to anyone you want, but your post boost and encourages a bad attitude.
If people start to solve only paid problems, the spirit of the community will be destroyed.

The problem is with the Pie specific partition table
I write the whole guide from memory, so it can differ a bit.... I skipped some steps ( erasing, reboot, fastboot mode, TWRP loading via fastboot, OEM unlock )
From previous writings I think you can know the skipped steps.
Keep in mind: It is dangerous, you can loose your IMEI ( it will only work again with Pie - or there are some writings at forum how can you manually change it. ).
Steps:
1 - Backup with TWRP (fastboot) efs,persist,modem & make copy to your computer and or to your cloud provider.
2 - Create a new folder in Internal Storage -> TWRP -> BACKUP -> With a new date directory ( the backup already made one, make a new folder, with different date )
3 - Download someone's older TWRP backup from xda (I cheated, I copied the following links ) :
(I'm still a new user, so can't directly write url's )
Mediafire : https COLON SLASH SLASH bit.ly SLASH 2QU5NtC
Mirror: Google Drive : https COLON SLASH SLASH bit.ly SLASH 2UN1DTo
4 - Unpack, and copy EFS to the folder created 2 point
5 - Fastboot TWRP -> Restore EFS
6 - Flash the Official latest firmware from en.miui.com ( If you want to make sure go with EDL mode )
7 - Now, the IMEI & Mac addresses are missing. Don't panic! Download update with System Updates.
8 - When you are on Pie again, restore your first TWRP (fastboot) persist partition
9 - One more System restore
At this time, you will have IMEI & Mac addressees, and hopefully a working phone.
Hope this helps. The same thing happened with me 2 weeks ago. This is how I solves it.

Thank you, I solved it yesterday. Hopefully this post will come in handy for other people!

[Help plz] Mobile radio / WIFI / diag mode broken after modifying NV Item QPST/QXDM

Hey guys,
Here is a story of stupid myself and now i need help with my phone Please enjoy and help if you can. Thanks.
I was trying to unlock LTE bands on EEA mi 9t (BAD DECISION, DON'T DO IT!) following any of those tutorials online, and i broke:
1, mobile network
2, wifi
3, diag mode/port
What i did:
- I have root with Magisk, used "adb shell / su / setprop sys.usb.config diag,adb" to enable diag port.
- Connected QPST and QXDM
- In QXDM's NV browers, i put "17592185995263" in both lines in NV item 06828 LTE_BC_CONFIG without backing up the original value (BAD DECISION, DON'T DO IT!)
- Rebooted the phone, and now mobile network and wifi disconnectes every 5 seconds.
What i have tried to fix this:
1, Reconnect QPST and QXDM, now QPST doesn't read phone's ESN number, and QXDM is saying that i can read/write to any NV items. Basically the diag mode is not communicating correctly anymore.
2, factory reset, no good.
3, recovery flashing, no good
4, fastboot flashing, no good
5, EDL/MiFlash tool flashing, (YES, with an authorized account), including persist partition (modified crclist.txt and etc), NO GOOD
I am here right now. I have done so much research on this topic and nobody has seem to run into this.
I am an embedded engineer and have a little bit android dev experience, and here is what i think based on what i have done and what i have read:
1, the NV items are stored in some location in flash memory, and they are loaded in the boot sequence when the phone boots up. But these NV items are not in persist, modem1 nor modem2 partitions as i have tried. And this block is not flashed by any flashing method, even EDL mode.
2, once the modified NV item (LTE_BC_CONFIG) has been loaded, it cause the firmware/hardware of qualcomm to not function correctly, thus the diag mode/port is not communicating properly to QPST/QXDM.
So I am (still) looking to fix this problem in 2 ways according to my theory above:
1, find the location that stores the NV items and try to revert the LTE_BC_CONFIG part back (but i don't know the original, yet possible to calculate it based on phones spec sheet).
2, find a way to reset the diag mode/port so that it talks to QPST/QXDM again.
Please help if you know anything about this.
Otherwise my phone is just a tablet that does not have internet lol
Thank you in advance!
tag: redmi k20 pro mi 9t global eea lte band unlock

Does a full reflash not fix it? You probably tried already.

SnowFuhrer said:
Does a full reflash not fix it? You probably tried already.
Click to expand...
Click to collapse
yea lol Qualcomm's EDL mode flash has no effect

Take it to service center after installing miui .
State that network is fluctuating by itself. I have done something similar on other device without taking backup . Only way is to change the whole motherboard .

Gaurav0007 said:
Take it to service center after installing miui .
State that network is fluctuating by itself. I have done something similar on other device without taking backup . Only way is to change the whole motherboard .
Click to expand...
Click to collapse
That method totally makes sense...expect that xiaomi has no service center in Canada and i bought this potentially European version phone ftom Gearbest (which ships from China) lol its a whole lot of locations that dont match up lol..

anyone?
worst case, i may need to sell the phone as a internet-less digital famera for scrap money lol

Tmobile brand 12
Is there a way to enable all the tmobile bands?

russellglen72 said:
Is there a way to enable all the tmobile bands?
Click to expand...
Click to collapse
if i can fix my phone i'd volunteer to try lol

If you need QCN backup for 9T, I got one working. This might restore your original settings after you wipe modemst1&2 and fsg.

SEXCAVATOR said:
If you need QCN backup for 9T, I got one working. This might restore your original settings after you wipe modemst1&2 and fsg.
Click to expand...
Click to collapse
Thanks! I could give it a try, as the problem is mainly that the phone does not talk to any of these tools any more.
Let me know where i can get it plz.
And what tool did uou create the backup with?

kezzuki said:
Thanks! I could give it a try, as the problem is mainly that the phone does not talk to any of these tools any more.
Let me know where i can get it plz.
And what tool did uou create the backup with?
Click to expand...
Click to collapse
This backup I found from a local forum is taken using QPST tool (2.7.477 I remember). It belongs to Xiaomi Mi 9T device. Only one IMEI is working though (the other one is nulled). Why your phone doesn't talk to tools anymore, can't get DIAG mode on?
https://gofile.io/?c=gxTHSm (IMEI of the backup is written in the name. You can search and change using HEX edit method).

SEXCAVATOR said:
This backup I found from a local forum is taken using QPST tool (2.7.477 I remember). It belongs to Xiaomi Mi 9T device. Only one IMEI is working though (the other one is nulled). Why your phone doesn't talk to tools anymore, can't get DIAG mode on?
https://gofile.io/?c=gxTHSm (IMEI of the backup is written in the name. You can search and change using HEX edit method).
Click to expand...
Click to collapse
Diag mode can be enabled, but qpst says says its in a wrong state and cannot read or write NV items lol

kezzuki said:
Diag mode can be enabled, but qpst says says its in a wrong state and cannot read or write NV items lol
Click to expand...
Click to collapse
I would have backup modemst1&2 and fsg then wipe those partitions. That might jump start.

SEXCAVATOR said:
I would have backup modemst1&2 and fsg then wipe those partitions. That might jump start.
Click to expand...
Click to collapse
May I ask what those partitions do?

kezzuki said:
May I ask what those partitions do?
Click to expand...
Click to collapse
They are where the NV items and modem config are located and their backup. Once you purge those partitions, android system will renew it from an inner source. If anything goes wrong, you can always restore those partitions from an image you took previously. I did it numerous times. My bootloader was unlocked and I had TWRP. Those are necessary.

SEXCAVATOR said:
They are where the NV items and modem config are located and their backup. Once you purge those partitions, android system will renew it from an inner source. If anything goes wrong, you can always restore those partitions from an image you took previously. I did it numerous times. My bootloader was unlocked and I had TWRP. Those are necessary.
Click to expand...
Click to collapse
Wow, that seems like it will work. I will try it when i get a chance.
Where did you find this information?...i tried searching the entire internet but didn't see anything like that...
Thanks!

kezzuki said:
Thanks! I could give it a try, as the problem is mainly that the phone does not talk to any of these tools any more.
Let me know where i can get it plz.
And what tool did uou create the backup with?
Click to expand...
Click to collapse
I learned in a hard way. Bricked my device while playing with the bands, lost my IMEI...
This info I gave you is served in XDA forums under different topics. If you gonna give it a try, I can give you exact steps.

SEXCAVATOR said:
I learned in a hard way. Bricked my device while playing with the bands, lost my IMEI...
This info I gave you is served in XDA forums under different topics. If you gonna give it a try, I can give you exact steps.
Click to expand...
Click to collapse
wow guess you saved your phone lol
I can wipe blocks and will try that method later. Thanks!

kezzuki said:
wow guess you saved your phone lol
I can wipe blocks and will try that method later. Thanks!
Click to expand...
Click to collapse
I know its an old thread, but did you manage to solve that problem? I got a phone here with exactly the same issue

find device storage corrupted your device is unsafe now

hey guys i recently flashed pixel experience on my redmi k20 but i decided to revert back to stock so i flashed latest stable version through mi flash but now i am getting "find device storage corrupted your device is unsafe now" notifications did i messed something up? and i had an unlocked bootloader but now i cant unlock it. the error i get is "you should wait until 30 days before you can unlock another device"

once you've unlocked the bootloader, you can unlock it anytime again and as often as you want. have tested this several times, just once again with the same mi account unblock - without waiting.
how did you leave MIUI installed with MIflash and lock down on the bottom right?

You somehow corrupted your persist partition. When you are able to unlock again, you can fix that by flashing persist.img from fastboot image to persist partition via TWRP. You can't flash that via fastboot, that will not work. Be aware that you will loose Widevine L1 forever on MIUI (should still work on custom roms) unless you have a backup of your persist partition you can restore.

lucifer said:
hey guys i recently flashed pixel experience on my redmi k20 but i decided to revert back to stock so i flashed latest stable version through mi flash but now i am getting "find device storage corrupted your device is unsafe now" notifications did i messed something up? and i had an unlocked bootloader but now i cant unlock it. the error i get is "you should wait until 30 days before you can unlock another device"
Click to expand...
Click to collapse
Why did you leave the pixel experience ROM , wasn't it good . Just wanted to know because I want to flash it too

nill3bor said:
once you've unlocked the bootloader, you can unlock it anytime again and as often as you want. have tested this several times, just once again with the same mi account unblock - without waiting.
how did you leave MIUI installed with MIflash and lock down on the bottom right?
Click to expand...
Click to collapse
yup locked with mi flash with the lock option on bottom but can't unlock it again with the same id somehow now the phone is seen as new device

nckmml said:
You somehow corrupted your persist partition. When you are able to unlock again, you can fix that by flashing persist.img from fastboot image to persist partition via TWRP. You can't flash that via fastboot, that will not work. Be aware that you will loose Widevine L1 forever on MIUI (should still work on custom roms) unless you have a backup of your persist partition you can restore.
Click to expand...
Click to collapse
can service center fix that for me.?

Benfatica said:
Why did you leave the pixel experience ROM , wasn't it good . Just wanted to know because I want to flash it too
Click to expand...
Click to collapse
no its works great my poco f1 screen broke thats why i reverted back to miui on k20

lucifer said:
yup locked with mi flash with the lock option on bottom but can't unlock it again with the same id somehow now the phone is seen as new device
Click to expand...
Click to collapse
its not good?
but you have not created a backup of twrp?
but you can create a new account, because it's 7 days to unlock. but you can only unlock a phone every 30 days!
what did you do, why is the partition corrupt? that should not happen with the image!

nill3bor said:
its not good?
but you have not created a backup of twrp?
but you can create a new account, because it's 7 days to unlock. but you can only unlock a phone every 30 days!
Click to expand...
Click to collapse
no its not good
yes i created a backup but to flash twrp again i need unlocked bootloader
will try with new account
and can servce center fix this for me.?
And i just flashed with mi flash tool nothing else it works fine on my poco done several times already but somehow something went wrong

lucifer said:
no its not good
yes i created a backup but to flash twrp again i need unlocked bootloader
will try with new account
and can servce center fix this for me.?
Click to expand...
Click to collapse
create a new account, wait and after unlock flash the backup and report
MIUI works good or do you have problem? IMEI and MAC its ok?

nill3bor said:
create a new account, wait and after unlock flash the backup and report
MIUI works good or do you have problem? IMEI and MAC its ok?
Click to expand...
Click to collapse
Miui works fine except it can't sync with mi cloud
Imei and mac is fine
update : mi cloud sync works on new id

lucifer said:
Miui works fine except it can't sync with mi cloud
Imei and mac is fine
update : mi cloud sync works on new id
Click to expand...
Click to collapse
wait for unlock, flash partion here or flash a backup (partition)

Flash twrp persist.img

nill3bor said:
wait for unlock, flash partion here or flash a backup (partition)
Click to expand...
Click to collapse
Ok will wait for unlock and will update
Thanks for the help

Those that haven't flashed their persist partition and are rooted, are you able to look in there and see if there's any files or folders related to the widevine certification?

nill3bor said:
wait for unlock, flash partion here or flash a backup (partition)
Click to expand...
Click to collapse
If i flash partion that is not my backup will i lose widewine L1 on miui.?

lucifer said:
If i flash partion that is not my backup will i lose widewine L1 on miui.?
Click to expand...
Click to collapse
That's why I asked about IMEI, Bluetooth and sensors. But before you flash, try this one again and report.
Of course, twrp must be installed.
did you create a new account?
do you have less than 30 days wait now?
did you have a foreign backup fash before?
is the IMEI the same number as on the packaging?

nill3bor said:
That's why I asked about IMEI, Bluetooth and sensors. But before you flash, try this one again and report.
Of course, twrp must be installed.
did you create a new account?
do you have less than 30 days wait now?
did you have a foreign backup fash before?
is the IMEI the same number as on the packaging?
Click to expand...
Click to collapse
yes every sensor is working fine
yes i did create a new account
7 days wait now
what is foreign backup?
yes imei is same as on packaging
and can service center fix this for me.?

lucifer said:
yes every sensor is working fine
yes i did create a new account
7 days wait now
what is foreign backup?
yes imei is same as on packaging
and can service center fix this for me.?
Click to expand...
Click to collapse
thats ok, try this
if you do not have your own backup, I would not import it, because in the persist.img sensedata IMEI bluetooth etc stored in the partition
you just have to wait, then you try what was advised and report

nill3bor said:
thats ok, try this
if you do not have your own backup, I would not import it, because in the persist.img sensedata IMEI bluetooth etc stored in the partition
you just have to wait, then you try what was advised and report
Click to expand...
Click to collapse
ok i will wait try and report but will service center be able to solve this problem.?