Database Develop

hello all.

So I purchased a K20 Pro from eBay, never-msrp specifically. A few days after receiving the phone I was promoted to do a OTA to Android 10. The phone never booted again. I contacted the seller. They sent me a link to reset the phone; didn't work...still stuck on MI recovery 3.0. They said contact Xiaomi when the reset didn't work. Xiaomi says there's nothing they can do because they don't officially support this model in the U.S.. Square Trade during all this finally said they determined they can help me. BUT, they need the IMEI number which I can't get to without booting up the phone.
Any ideas how to recover the IMEI. The box is long gone. All I want is the phone
HELP! ?

afrokorean said:
So I purchased a K20 Pro from eBay, never-msrp specifically. A few days after receiving the phone I was promoted to do a OTA to Android 10. The phone never booted again. I contacted the seller. They sent me a link to reset the phone; didn't work...still stuck on MI recovery 3.0. They said contact Xiaomi when the reset didn't work. Xiaomi says there's nothing they can do because they don't officially support this model in the U.S.. Square Trade during all this finally said they determined they can help me. BUT, they need the IMEI number which I can't get to without booting up the phone.
Any ideas how to recover the IMEI. The box is long gone. All I want is the phone
HELP! ?
Click to expand...
Click to collapse
Sounds like you had a CN model that was probably sideloaded with a different region's ROM perhaps. I'd suggest trying XiaomiADBFastbootTools if you can get the phone in to fastboot (the recovery screen you mentioned). It might list an IMEI in that software once it's hooked up via USB.
https://github.com/Szaki/XiaomiADBFastbootTools
Xiaomi do support the K20 Pro in America; it's the "Mi9T Pro" - if you mention K20 you get a swift "sorrynotsorry can't help you" as they assume it's import given its branded Mi9T for Westerners. But if you've got a boxed CN version the domestic warranty service may turn up their noses at it anyway.
It's in fastboot so you may as well try your luck at MiFlash and try the fastboot files for whatever region the phone is for; but if it's locked it might not go ahead. Can't hurt to try. The fastboot files are 2-3GB a pop so if you don't know what region it is you might need to try all of them;
https://mirom.ezbox.idv.tw/en/phone/raphael/
https://www.7-zip.org/ - to extract the *.tgz fastboot file
https://www.xiaomiflash.com/ - to flash the extracted folder.
Just be sure to use "clean all" and not "clean all and lock". Best of luck.

V40 is it possible to change NT Code without Root?

I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.

suain81 said:
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
Click to expand...
Click to collapse
I'm not sure, but worth a try,I warn the site is Russian, here's how to edit NT code https://4pda.ru/forum/index.php?showtopic=951883&view=findpost&p=100635159 here is a list of NT codes:View attachment NT_code.txtunfortunately needed root!working with QFIL do backup ftm.bin!

lexih said:
I'm not sure, but worth a try,I warn the site is Russian, here's how to edit NT code here is a list of NT codes:View attachment 5134107unfortunately needed root!
Click to expand...
Click to collapse
Thank you for your reply. Yes, I have read many instructions even on this page how to edit, cust_path_mapping.cfg, and that it's surely easy once the phone is rooted. But that's why I first wanted to see the possibilities to do this without that I have to root the phone.

suain81 said:
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
Click to expand...
Click to collapse
So, u have 2 problems right? u want to upgrade to v405ebw30c, but can't, and you also have the nt-code error right?
First, no, they aren't related. I think that's highly unlikely. That's not something lgup checks for. I'd bet you're using the 1.14 version dll and should be using the 1.16 dll and should be doing a refurbish.
As far as the nt-code error. It's a pain, lots and lots of info about fixing it, most of them need root. But here's what worked for me, no root needed: I switched from att pie to Korean open Q (first time had the nt-error and no editing anything would fix it), so went back to att and then did the korean 409N again, first with partition DL. Let that finish, it has to reboot the phone completely to finish. Then, don't change the phone in anyway, just shut it off. Back to LGUP and do a Refurbish with the same kdz.
No more nt-error code. It *seems* that nt-error code info gets propagated to various partitions as a part of refurbish. I verified that the ftm partition, where that information lives, was completely spaces (blank) after the refurbish... it's odd, I know. But for whatever reason, I no longer have the nt-error code problem.
cheers

AsItLies said:
So, u have 2 problems right? u want to upgrade to v405ebw30c, but can't, and you also have the nt-code error right?
First, no, they aren't related. I think that's highly unlikely. That's not something lgup checks for. I'd bet you're using the 1.14 version dll and should be using the 1.16 dll and should be doing a refurbish.
As far as the nt-code error. It's a pain, lots and lots of info about fixing it, most of them need root. But here's what worked for me, no root needed: I switched from att pie to Korean open Q (first time had the nt-error and no editing anything would fix it), so went back to att and then did the korean 409N again, first with partition DL. Let that finish, it has to reboot the phone completely to finish. Then, don't change the phone in anyway, just shut it off. Back to LGUP and do a Refurbish with the same kdz.
No more nt-error code. It *seems* that nt-error code info gets propagated to various partitions as a part of refurbish. I verified that the ftm partition, where that information lives, was completely spaces (blank) after the refurbish... it's odd, I know. But for whatever reason, I no longer have the nt-error code problem.
cheers
Click to expand...
Click to collapse
Thank you for your reply. No I don't know if they're related either, it was just a guess since the problems started at the same time. Well, I always had a kind of "problem" since I never have been able to upgrade from LG Bridge. And that I guess is from the NT-code. But the sign in the start appeared after the Android 10 upgrade. However, I'm using LGUP 1.16.0.3 and I have used it everytime, with DLL version 1.9.39.7.
And actually it wouldn't bother me too much having this sign in the start anyway, I only restart the phone like once per week. But of course it bothers me that I can't make the upgrade like before. And I can also mention that I have never tried to refurbish with LGUP, only upgrades, because I have some bank apps etc. that are a bit complicated to reinstall. Of course it's possible, but I have to be mentally prepared for it. So I'll only do that when I know there's no other option. And the phone work good today, so I'm not in a rush, but in a couple of months I should be doing an upgrade of course.
And thanks for telling me the other option too, I will surely try it one day but since it also requires refurbish I will try after I fail to make the normal refurbish.
I don't have any experience of rooting, if I root my phone, will I keep all the data or is it comparable to refurbish? Are the any other risks rooting the phone? I'll lose the warranty, but I don't really have the warranty anyway since it's not an official product in my country.

suain81 said:
I don't have any experience of rooting, if I root my phone, will I keep all the data or is it comparable to refurbish? Are the any other risks rooting the phone? I'll lose the warranty, but I don't really have the warranty anyway since it's not an official product in my country.
Click to expand...
Click to collapse
No, to root, you loose all data and have to start again. Part of rooting is to flash dm-verity which turns off encryption. But, that allows you to do a backup of the data partition once you've reinstalled everything. The positive side there is that in the future, you could back up that partition (data), make any other changes, then flash data back, and your apps would be back as they were.
Other risks? Well, maybe, if the phone was stolen I guess, it would be easier for someone to steal your data. Your situation, with serious banking apps, it **may be** you don't want that risk...
Maybe for just trying a refurb to lose nt-code, look at LG's 'restore' from previous device ability, use it to save off the apps somewhere, then restore after refurb? no root needed.
cheers

How To Guide x70 Pro Plus Origin OS to FunTouch 36.9.3

Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.

RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.

Many thanks, may I relock the bootloader when i finished change to Global rom?

amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question

Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.

amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?

does any one change the origin os /ocean into funtouch？
version？ how to relock after it can switch to funtouch？
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91​

I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.

i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)

I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!

stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.

Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.

Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.

Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.

Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.

hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3

Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?

amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question

adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash

redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?

Network Unlock After Crossflashing

I Need Help... Few days ago I bought Lg V40 Think At&t locked network phone and it was on Android 8.1 Oreo. I wanted to update it to Android 10 somehow I came to know that we can update through lgup. But I accidently flashed Verizon kdz and now I get to know that we can't flash At&t kdz as its not available anywhere.
Now my phone is not asking for network unlock code as it asked on previous firmware At&t. But Sim is also not Working and also giving nt-code carrier unmatched error message whenever I restart Phone.
I found it on xda that Nt code error can be fixed by flashing v405ebw rom as someone else also faced this error and fixed Nt code error by flashing v405ebw.
Now to Main Question Can I unlock network now after crossflashing the kdz my previous network was At&t

Haiderkaramatali said:
I Need Help... Few days ago I bought Lg V40 Think At&t locked network phone and it was on Android 8.1 Oreo. I wanted to update it to Android 10 somehow I came to know that we can update through lgup. But I accidently flashed Verizon kdz and now I get to know that we can't flash At&t kdz as its not available anywhere.
Now my phone is not asking for network unlock code as it asked on previous firmware At&t. But Sim is also not Working and also giving nt-code carrier unmatched error message whenever I restart Phone.
I found it on xda that Nt code error can be fixed by flashing v405ebw rom as someone else also faced this error and fixed Nt code error by flashing v405ebw.
Now to Main Question Can I unlock network now after crossflashing the kdz my previous network was At&t
Click to expand...
Click to collapse
Well first, the nt-error code thing, no, you do not have to flash ebw rom to fix that, that's a misunderstanding and the post you read the person may not have made that part clear.
The nt-error code is pretty easily fixed, but, it has zero effect. It does absolutely no harm, and it only happens when you boot the phone. So, if you are thinking that somehow is contributing to your problem, no, it is not.
So your problem though is a pretty big one, as you suspect. You have to have the at&t variant rom for it to ask for the code, but the at&t kdz doesn't exist. I'd suggest join the tele group for v40, they have people there that have been through this problem, and pretty sure there's a backup of at&t there also. You would probably have to use qfil and flash ea partition one by one, but at least you'd get it back, the rom that is.
cheers

AsItLies said:
Well first, the nt-error code thing, no, you do not have to flash ebw rom to fix that, that's a misunderstanding and the post you read the person may not have made that part clear.
The nt-error code is pretty easily fixed, but, it has zero effect. It does absolutely no harm, and it only happens when you boot the phone. So, if you are thinking that somehow is contributing to your problem, no, it is not.
So your problem though is a pretty big one, as you suspect. You have to have the at&t variant rom for it to ask for the code, but the at&t kdz doesn't exist. I'd suggest join the tele group for v40, they have people there that have been through this problem, and pretty sure there's a backup of at&t there also. You would probably have to use qfil and flash ea partition one by one, but at least you'd get it back, the rom that is.
cheer
Click to expand...
Click to collapse

Horrible_AT&T_Android_Q_build.7z
drive.google.com
I found this file on notes on lg v40 group saying attq, when opened link it says Horrible Att Android q Build and it's zip file.
I wants to ask is that the backup for Att Android 10 firmware or is it something else.
AsItLies said:
Well first, the nt-error code thing, no, you do not have to flash ebw rom to fix that, that's a misunderstanding and the post you read the person may not have made that part clear.
The nt-error code is pretty easily fixed, but, it has zero effect. It does absolutely no harm, and it only happens when you boot the phone. So, if you are thinking that somehow is contributing to your problem, no, it is not.
So your problem though is a pretty big one, as you suspect. You have to have the at&t variant rom for it to ask for the code, but the at&t kdz doesn't exist. I'd suggest join the tele group for v40, they have people there that have been through this problem, and pretty sure there's a backup of at&t there also. You would probably have to use qfil and flash ea partition one by one, but at least you'd get it back, the rom that is.
cheers
Click to expand...
Click to collapse
Horrible_AT&T_Android_Q_build.7z
drive.google.com
I found this file on notes on lg v40 group saying attq, when opened link it says Horrible Att Android q Build and it's zip file.
I wants to ask is that the backup for Att Android 10 firmware or is it something else.

Haiderkaramatali said:
Horrible_AT&T_Android_Q_build.7z
drive.google.com
I found this file on notes on lg v40 group saying attq, when opened link it says Horrible Att Android q Build and it's zip file.
I wants to ask is that the backup for Att Android 10 firmware or is it something else.
Horrible_AT&T_Android_Q_build.7z
drive.google.com
I found this file on notes on lg v40 group saying attq, when opened link it says Horrible Att Android q Build and it's zip file.
I wants to ask is that the backup for Att Android 10 firmware or is it something else.
Click to expand...
Click to collapse
Yes that's the backup of Q. The person said 'horrible' just because it's at&t, that's all, not anything to do with the quality of the backup.
Many people have used that backup and it's worked for them.

AsItLies said:
Yes that's the backup of Q. The person said 'horrible' just because it's at&t, that's all, not anything to do with the quality of the backup.
Many people have used that backup and it's worked for them.
Click to expand...
Click to collapse
Can you guide me how to flash it through qfil I'm not an expert. I can't find any forum etc on this topic for flashing at&t rom through qfil with this kind of backup.
.
Thanks

Haiderkaramatali said:
Can you guide me how to flash it through qfil I'm not an expert. I can't find any forum etc on this topic for flashing at&t rom through qfil with this kind of backup.
.
Thanks
Click to expand...
Click to collapse
There's really no guide specifically for this, just look in the guides section and get qfil set up and working. Then, simply unzip the att rom file and begin flashing ea individual partition to the appropriate partition in qfil.

Question Need help Mi11 "your System has been Destroyed" Messeage

Hello everyone, im new to this Forum.
I need to ask if someone can help me. I remember using the cleaning Tool on my Mi11 on the Bus and seconds after closing the App the Phone suddenly Turned off & after Turning it back on it just displayed the Message
"your System has been destroyed" and constantly bootlooping.
Recovery Mode was not working, i can only get into fastboot Mode.
I tried flashing new Firmware with the tools provided by Xiaomi but they always tell me to unlock the bootloader wich i havent done and now i cant cause i cant get into the Phone.
I also tried unlocking the Bootloader with MiFlash Unlock but it tells me to add my account in the MIUI Developer Options..
I then contacted some Xiaomi unlocking Service and pay him 30€ to unlock my Phone in a teamviewer Session via AvatarAuthTool and some other stuff but even he was not able to do it.
I removed the backplate from the Phone and shortened the testpoint pins and he tried again with no luck..
i have no Idea how to get this Phone usable again and im desperatly looking for any help or advice bcuz im currently rocking my old Sony Erricson Walkman Phone..
thanks in advance for anyone who is taking the time to read all this and trying to help

You didn't mention if it's still on warranty and whether you can get it repaired from there?
You don't need to unlock the bootloader if you're using the right firmware for your variant.
Do you happen to remember whether it was EEA, MI, IN or etc version for your device?

Unknown.Guy said:
You didn't mention if it's still on warranty and whether you can get it repaired from there?
You don't need to unlock the bootloader if you're using the right firmware for your variant.
Do you happen to remember whether it was EEA, MI, IN or etc version for your device?
Click to expand...
Click to collapse
I dont think i still have warranty cause i bought it as used from a friend, How do i find the correct Firmware as you say i dont need to unlock anything i might have tried with the wrong version. Also i believe its a global version.

Coolpenisbro said:
I dont think i still have warranty cause i bought it as used from a friend, How do i find the correct Firmware as you say i dont need to unlock anything i might have tried with the wrong version. Also i believe its a global version.
Click to expand...
Click to collapse
No worries. You will have to try a couple of fastboot firmwares.
For each of them, you need to use the latest MiFlash Tool and make sure that CLEAN ALL only option is selected.
One thing to note here is that once you select the firmware folder in MiFlash, it automatically switches to Clean All and Lock
So you better make sure to look well and switch to CLEAN ALL only again before you hit the Flash button.
Latest Global:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Latest Global EEA:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Not so latest China Stable:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I couldn't find the latest fastboot version for China. Make sure you download fastboot versions for all of these and try one by one. At least one of these have to work for your bootloader.
If these don't work then we could try Indonesia, Turkey, Taiwan and Russia firmwares. No way none of them works.
Edit: Idk how it selected Bold but nvm. Also, these steps will wipe all data on phone. Will be like a factory reset.

Give this a try first, who knows it might work lol.
How to Fix “The System Has Been Destroyed” Issue on Xiaomi Phones - Techtrickz
Xiaomi smartphones usually work flawlessly, but sometimes it may act weirdly. An OTA update can cause the issue and sometimes it happened without any intervention by users. OTA updates sometimes will brick the phone leaving the message ‘the system has been destroyed’ on the boot screen. For...
techtrickz.com

Unknown.Guy said:
Give this a try first, who knows it might work lol.
How to Fix “The System Has Been Destroyed” Issue on Xiaomi Phones - Techtrickz
Xiaomi smartphones usually work flawlessly, but sometimes it may act weirdly. An OTA update can cause the issue and sometimes it happened without any intervention by users. OTA updates sometimes will brick the phone leaving the message ‘the system has been destroyed’ on the boot screen. For...
techtrickz.com
Click to expand...
Click to collapse
Dude thanks for your efforts in trying to Help. In the end i refunded my Money wich i paid to the first unlocking guy and looked on Telegram, where i found a 100% legit dude. he flashed it on first try. also he was ok with an afterwards payment + he was only 25€. I can link his page if someone is interested.