hello guys,
my phone is xiaomi mi 8, and has a wifi issue ( mac address 02 00 00 00 00 )
when the phone was on china version the wifi and bluetooth work only when i sign in to mi account and if i sign out the wifi ...ect stop working
when i flash my phone with global version the bluetooth back to work only when i sign in to mi account and the wifi stop working even if i signed in or out to mi account
please help
Chouiyekh said:
hello guys,
my phone is xiaomi mi 8, and has a wifi issue ( mac address 02 00 00 00 00 )
when the phone was on china version the wifi and bluetooth work only when i sign in to mi account and if i sign out the wifi ...ect stop working
when i flash my phone with global version the bluetooth back to work only when i sign in to mi account and the wifi stop working even if i signed in or out to mi account
please help
Click to expand...
Click to collapse
You need to use the correct firmware for your device.
Here is a website that has firmware for the Global and the Chinese version of the Mi8
Here is the chinese Firmware link
https://xiaomifirmwareupdater.com/#stable#dipper
If you continue having an issue after upgrading the firmware, you will need to use QPST to repair your IMEI
tsongming said:
You need to use the correct firmware for your device.
Here is a website that has firmware for the Global and the Chinese version of the Mi8
Here is the chinese Firmware link
https://xiaomifirmwareupdater.com/#stable#dipper
If you continue having an issue after upgrading the firmware, you will need to use QPST to repair your IMEI
Click to expand...
Click to collapse
that what do now, download a lot of chinese and global roms and try them and hoping to find one working
but you wrote if problem continue i have to use QPST to repair IMEI but i don't have problem on IMEI !!
Chouiyekh said:
that what do now, download a lot of chinese and global roms and try them and hoping to find one working
but you wrote if problem continue i have to use QPST to repair IMEI but i don't have problem on IMEI !!
Click to expand...
Click to collapse
Yes I misread and was thought that you were also having cellular connection issue, in addition to WIFI, BT etc. You did not provide very much information
Did you try the most basic steps with resolving your issue.
Such as, fully resetting/or forgetting your Network and then resigning back into your WIFI?
Did you rule out the issue being with your router, or duplicate IP address, did you power cycle the router?
Did you fully wipe your device before switching to a completely different rom?
Your issue is probably an encryption issue, did you first fully wipe your device, including formatting user data? If not that very likely the issue and formatting resolves will absolutely resolve encryption based issues.
In fact, the more that I think about this issue and how the issue improves when able to sign into Mi-Cloud, I am certain that encryption is the problem. So back up your memes, and fully wipe and FORMAT ( not wipe) user storage ( type yes) reboot to recovery, then reinstall your rom and you should be back to using the phone without issues.
tsongming said:
Yes I misread and was thought that you were also having cellular connection issue, in addition to WIFI, BT etc. You did not provide very much information
Did you try the most basic steps with resolving your issue.
Such as, fully resetting/or forgetting your Network and then resigning back into your WIFI?
Did you rule out the issue being with your router, or duplicate IP address, did you power cycle the router?
Did you fully wipe your device before switching to a completely different rom?
Your issue is probably an encryption issue, did you first fully wipe your device, including formatting user data? If not that very likely the issue and formatting resolves will absolutely resolve encryption based issues.
In fact, the more that I think about this issue and how the issue improves when able to sign into Mi-Cloud, I am certain that encryption is the problem. So back up your memes, and fully wipe and FORMAT ( not wipe) user storage ( type yes) reboot to recovery, then reinstall your rom and you should be back to using the phone without issues.
Click to expand...
Click to collapse
i tried every single thing you wrote above, nothing helpful
I also have the same problem someone could already solve it?
Chouiyekh said:
i tried every single thing you wrote above, nothing helpful
Click to expand...
Click to collapse
I am not sure if possibly English is your second language so I will give you the benefit of the doubt, a friendly tip, and another thing to try.
If a stranger on XDA is spending their personal time attempting to HELP YOU, with YOUR issue and providing you with a plethora of things to try, you may want to use your good manners and thank them for spending their time trying to help you, instead of briefly stating, I tried everything and it did not work. You would be amazed with how many doors simple appreciation can open for you. Next, It's called troubleshooting, If I had a definitive answer, with a definite solution I would have told you.
With that in mind here is another idea of something you can try,
It's pretty much all that is left to resolve, at least AFAIK.. So either this works or it's probably a hardware issue. Or an issue that requires using QPST as I stated originally, regardless of your IMEI. There are a million sites that describe step by step QPST steps if needed, I recommended.
Any of the steps below, you do at your own risk.
My last guess is that you probably wiped your persist partition by accident
You will need to restore your persist image and then you should be back in working order.
Important: you need to locate the correct persist image from the correct fastboot rom for your device. You can manually extract the file from the stock fastboot rom for your specific model and then push it to your device via ADB
As mentioned, you can find the rest of the additional steps with Google
@sear01
If you tried everything else, this post is probably the solution that will work for you as well.
Again at your own risk
thanks, I speak spanish and try to install the persist for a while the detail is that in a week I turned the wifi out of nowhere and now that the rom Pixel Experience was updated, the wifi again failed. Excuse me you could detail the steps I already made the flash of several rom both of China and global by Miflash but until now I do not expect anything to understand my desperation.
sear01 said:
thanks, I speak spanish and try to install the persist for a while the detail is that in a week I turned the wifi out of nowhere and now that the rom Pixel Experience was updated, the wifi again failed. Excuse me you could detail the steps I already made the flash of several rom both of China and global by Miflash but until now I do not expect anything to understand my desperation.
Click to expand...
Click to collapse
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
tsongming said:
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
Click to expand...
Click to collapse
thank you very much it is global version Vipper use rom pixel.
thanks for your time
sear01 said:
thank you very much it is global version Vipper use rom pixel.
thanks for your time
Click to expand...
Click to collapse
Click
Okay then, here's the cliff notes.
I have good and not so good news, Keep in mind that repairing Mac address issues, Imei, QCn issues is the same for all Qualcomm processors, it doesn't matter if a post said this is for the Redmi 10, in fact I can't find the link at the moment but Qualcomm themselves published a guide with similar steps across the spectrum of chips. ( Just make sure that you only flash driver ( firmware images ) for your Global Mi8 and not the proprietary files from the links. Otherwise the instructions are the same, various versions of QPST will work, PC drivers, android drivers will also work. If will only benefit you to use the latest version of any of those files. If language is a issue, use chrome with the translator plugin .
I made copies of my personal persist files and spent the time to create the main files that you need and posted them Get the files here : https://mega.nz/#F!0NAXEK7S!Bj_hTKSz2_hMKDjOEocNrg
Install the version of TWRP that is on the link above, Create a folder called restore or whatever you want and place the downloaded files from my Megalink inside of that folder, make sure that they are not compressed. Next, place the folder inside the Twrp/Backup/ <<<< Place your folder there.
Boot to Twrp, click restore, and you should be able to restore the persist image.
If it doesn't work then use ADb to push to your phone. Google it, the steps are listed a billion times on countless sites, and I do not have enough server space to upload a complete recoveries, and plus I will not share my EFS or QCN
If that doesn't work read this post : https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551 ( Note the persist image, present. But also much older. However, it's still worth trying.
Worst case QPST, should absolutely resolve the issue
If what I listed above fails go here: https://forum.xda-developers.com/redmi-note-4/how-to/guide-how-to-change-mac-address-mido-t3773026
(Again, be sure to only use Mi8 files) DO NOT use a QCN from another device.
Here is another guide that has illustrations, again use your own files for your device, Otherwise the steps are identical, I have completed these steps myself on other devices : http://en.miui.com/thread-348525-1-1.html
One last final option that I would suggest trying before using QPST
Did you happen to make a recovery of your phone, after initially installing TWRP for the first time?
If no, search the web for a full stock recovery
tsongming said:
I am not sure if possibly English is your second language so I will give you the benefit of the doubt, a friendly tip, and another thing to try.
If a stranger on XDA is spending their personal time attempting to HELP YOU, with YOUR issue and providing you with a plethora of things to try, you may want to use your good manners and thank them for spending their time trying to help you, instead of briefly stating, I tried everything and it did not work. You would be amazed with how many doors simple appreciation can open for you. Next, It's called troubleshooting, If I had a definitive answer, with a definite solution I would have told you.
With that in mind here is another idea of something you can try,
It's pretty much all that is left to resolve, at least AFAIK.. So either this works or it's probably a hardware issue. Or an issue that requires using QPST as I stated originally, regardless of your IMEI. There are a million sites that describe step by step QPST steps if needed, I recommended.
Any of the steps below, you do at your own risk.
My last guess is that you probably wiped your persist partition by accident
You will need to restore your persist image and then you should be back in working order.
Important: you need to locate the correct persist image from the correct fastboot rom for your device. You can manually extract the file from the stock fastboot rom for your specific model and then push it to your device via ADB
As mentioned, you can find the rest of the additional steps with Google
@sear01
If you tried everything else, this post is probably the solution that will work for you as well.
Again at your own risk
Click to expand...
Click to collapse
I'm very sorry my friend ?, I'm just angry of that problem that's why i forgot to thank you, and I appreciate everything you did and you will. Yes English is not my first or second language, it's my third.
I've tried to flash persist.img through TWRP that what i got (image attached) and when i try to flash it through adb i got write failed
tsongming said:
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
Click to expand...
Click to collapse
Please don't be upset of me, and please accept my apologies
Chouiyekh said:
Please don't be upset of me, and please accept my apologies
Click to expand...
Click to collapse
No worries, it's all good Thanks.
You may not have seen the post I made earlier here: https://forum.xda-developers.com/showpost.php?p=79802367&postcount=11
If these things do not work come back here and report what happened and I will stay with you until we resolve the issue, there is always something else to try.
I have successfully solved similar issues on other devices, the issue here is possibly a permissions issue due to encryption, Read the post above and make sure that you use the version of Twrp that is linked on my Mega drive. That version has no problems with encryption, while many versions of Twrp have issues with decrypting. Plus, that version allows the option to select and restore each partition ( There is a lot!)
Check this post later, I am going to edit this post, and add a link to the Persist Image from the latest Global stable Rom. This will be an alternative and maybe better solution than using the persist images that I uploaded to my Mega drive.
UPDATE EDIT
Okay, I created a folder on the Mega Link called Method with a TWRP flashable persist image >>> Install the Official Xiaomi EU TWRP English version ( The one on my Mega Drive) Boot to TWRP, Mount the persist partition > Choose Restore and install to persist> Forget you WIFI and rejoin, it may and will probably work for you.
Three Options if it does not
One
First Option requires fully wiping your device, so back everything up
Assuming that your Device is a Global Device
Download this Fastboot Rom : http://en.miui.com/download-346.html Download the Full Stable fastboot version and not the Recovery version.
Unpack the Rom, place your phone into EDL Mode - This Rom comes with the Fastboot flashall script, it will fully restore your phone to the a Stable Rom and Overwrite every partition., this is as good as using Qfil to unbrick. In fact I recommend this over Qfil. This should definitely work, as long as your issue is software, and I am certain that it is.
Two
You are too afraid to wipe the phone and would rather try something else first, since you would need WIFI to restore your Google Services and Mi-Cloud.
No worries, here is a QPST alternative that has worked for many people, you basically create a new Mac address by following the steps in this thread, read the comments, it has worked for many people and it may save you time, and its not as difficult as it may seem.
This method has worked for people with WIFI Authentication issues.
https://forum.xda-developers.com/showpost.php?p=70408778&postcount=9
Use this tool to generate a Mac address to use for the above linked steps.
Three
IMEI Repair
http://en.miui.com/thread-260943-1-1.html
Note although, you may not have issues with data or with calling, this solution ay still be relative. But definitely try everything else first, and leave this as a last resort.
Let me know, if it works, and if it does work , change the name of the OP "Solved" at the end. this way others can benefit from the thread
Update,
I just found another, much easier method of restoring the persist partition
Use Google translator and follow instructions here Then go thank the_virus_ua
Note you do not need to download the files on the link the file that I shared on the earlier post will suffice
@Chouiyekh @sear01
I never heard back to hear if your issue was resolved. if you are still having issues, this solution just fixed the issue for someone with a similar issue
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
@tsongming thank you so much for keeping in touch, i've read your solutions, but i still didn't apply them yet, because i was sick these days and now it's time to sleep i will try tomorrow then tell you the result, ( when i was trying to flash persist.img through twrp, i find the persist partition, so the partition not missing? )
Chouiyekh said:
@tsongming thank you so much for keeping in touch, i've read your solutions, but i still didn't apply them yet, because i was sick these days and now it's time to sleep i will try tomorrow then tell you the result, ( when i was trying to flash persist.img through twrp, i find the persist partition, so the partition not missing? )
Click to expand...
Click to collapse
Okay, no worries. Just use that last step first.
That one is the easiest and absolutely worked for another person that I was helping. He had exactly the same issue.
Sent from my Xiaomi MI 8 using XDA Labs
tsongming said:
I never heard back to hear if your issue was resolved. if you are still having issues, this solution just fixed the issue for someone with a similar issue
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Click to expand...
Click to collapse
hello dear, i'm sorry for the delay, i had some urgent work out of my country that why i late to answer, now i'm in my country and i started to apply what you wrote, but when i tried to flash twrp the on your reply i got black screen can't boot to twrp ( i think i made something wrong because i extracted the zip file and flash only twrp img through cmd fastboot ) please correct me or give another twrp img .
i read some comments on google that there is a risk to lose imei or something else, if that right how can we making a back up just in case
i hope to get your answer soon, and thank you sooooo much
anyway, i tried at my own risk, that's what i got in twrp ( see image ) then reboot to system but still have the problem ! no wifi no bluetooth !
** i tried factory reset too, not helping.
Related
Hi guys, I got a big big problem with my K3 Note, I think I went too far with wiping partitions before installing a new rom, here are the folders I wiped:
data, cache, system, protect_f, protect_s, dalvik cache.
After reboot my phone worked just fine but it didn't see the simcard, I thought it's the OS issue and wiped and flashed several times more.
Now when I got into the issue I noticed *#06# returns "invalid imei", after a little bit research I found out it's a common issue with MTK phones and found multiple possibilities for solving the problem, none of which worked for me though, for no known reason ;( What I've tried so far is: chamelephon app, MTK Engineer mode commands, flashable ZIP with the IMEIs, writing it with SN write tool and another program named something like Mauri? if I remember correctly, all done on the stock rom flashed with flashtool, now I'm retrying all of above on a custom rom.
I read somewhere that missing basebands can be an issue for MTK engineer mode, but I couldn't find any more info on the topic
I don't know if it is connected but the stock rom worked much worse than I remember when I first got the phone, it freezes completely(doesn't react to power button, keeps the led light after unconnected from charger, completely no response, I have to take out the battery each time) about once every 3-5minutes.
Another thing is, does anybody have any idea what the protect_f and _s folders are? I think I shouldn't have wiped them...
Any help would be much appriciated, I don't need another bricked phone... ;(
can you access bootloader mode and reflash with flashtools? i assume you dont have a backup? as far as i know the first partitition is responsible for the connection through USB so as far as i know if im not wrong you could reflash these partitions. dont know much however over these mtk devices
---------- Post added at 11:46 PM ---------- Previous post was at 11:41 PM ----------
freezes and shutdowns, even in lenovo stock recovery are a common problem i have found out. this has nothing to do with partitions in this case however dont know if this can be valid in your case. however in my example it is a fault within some lenovo stock roms. hope anyone can help you with more information
I do can flash with flashtool, at least thats how I flashed the stock rom, but I dont have a backup. Is it possible to use my IMEI with a different backup?
with my limited knowledge over the subject. preloader is the recovery since you can get a connection, what is safe to try without tinkering to much is flashing the latest vibe 3.0 45 dev rom over at needrom.com, since this rom also affects other partitions. once you have done this completely wipe every partition manually sometimes in TWRP i have seen some partitions dont function fully until you change partition format from ext4 to f2fs and back to ext4 and then wipe and repair in my case it has been for example.
as for the IMEI i havent been handson with these subjects so it is better for someone else to inform. This tip can be tried without risk as hopefully the dev rom will restore partitioning, at least it is worth a try.
---------- Post added at 02:56 PM ---------- Previous post was at 02:50 PM ----------
i cant answer your question on the IMEIs since lack of experience on the subject. however what i can say is that freezing and shutdown in stock k3 notes is a common problem and it is not hardware related. Does this problem also occur with a custom rom such as AOSP
Just to give you my total view on fixing the issue hopefully what i would try is:
1. flashing twrp
2.through twrp flashing the latest dev rom
3.reformatting every partition (meaning cache,dalvik cache,system,data,internal storage)
4.flashing a rom such as androim through twrp
5.trying the lost IMEI patch, input your info
6.to be sure use xposed framework uninstaller cause of performance gains
7.eventually using some tweaks such as l speed to get your device optimal
If the issue of freezing and random shutdown was of the same nature it should be solved 100%
http://forum.xda-developers.com/and...ed-thread-lenovo-k3-note-k50-t3158522/page117 latest dev rom
Damn, the official roms are unusable, they keep crashing after like 2-3mins.
Thanks for the link to the rom! I was looking for it for some time. Well, it installed without further complications, now I just need to find out how to restore my IMEIs... Hope at least one of all the methods will work this time.
I've found the answer to all my problems. I need a backup from another K3 Note, manually overwrite the IMEIs with mine and voila, it's supposed to work, at least works on other MTK phones.
If anybody here is willing to help me out please contact me, if you're afraid of sharing your IMEI numbers I can send you mine with an instruction on how to overwrite them, you could save me my phone and some money.
https://www.reddit.com/r/lenovok3no...ei_is_gone_after_installation_of_phoenix_rom/
http://forum.xda-developers.com/k3-note/general/organized-thread-lenovo-k3-note-k50-t3158522
refer this
Hi all,
My lenovo also having same problem..
anyone have a working solution..
pls help..
TQ
invalid imei number problem solved
1. flash new stock rom in ur device.
2. now you have two options
a. you can update your device. ( do all the updates of lollipop but don't upgrade it to marshmallow )
b. you can use the current rom that you have got after flashing.
3. root your device using kingroot app that you can easily find on net.
4. after rooting install chamelephon app on your device from play store.
5. remove the battery and note down the imei numbers written on back of the device.
6. plugin the battery and switch on your device.
7. open chamelephon app.
8. enter the imei numbers.
9. Hit apply new imei option.
10. wait for 1 min.
11. switch off your phone and then switch it on.
12. your sims are ready to work.....
Note ( do not update the device to marshmallow as kingroot app is not able to root lenovo vib marshmallow updated devices.)
Nechoya said:
Hi guys, I got a big big problem with my K3 Note, I think I went too far with wiping partitions before installing a new rom, here are the folders I wiped:
data, cache, system, protect_f, protect_s, dalvik cache.
After reboot my phone worked just fine but it didn't see the simcard, I thought it's the OS issue and wiped and flashed several times more.
Now when I got into the issue I noticed *#06# returns "invalid imei", after a little bit research I found out it's a common issue with MTK phones and found multiple possibilities for solving the problem, none of which worked for me though, for no known reason ;( What I've tried so far is: chamelephon app, MTK Engineer mode commands, flashable ZIP with the IMEIs, writing it with SN write tool and another program named something like Mauri? if I remember correctly, all done on the stock rom flashed with flashtool, now I'm retrying all of above on a custom rom.
I read somewhere that missing basebands can be an issue for MTK engineer mode, but I couldn't find any more info on the topic
I don't know if it is connected but the stock rom worked much worse than I remember when I first got the phone, it freezes completely(doesn't react to power button, keeps the led light after unconnected from charger, completely no response, I have to take out the battery each time) about once every 3-5minutes.
Another thing is, does anybody have any idea what the protect_f and _s folders are? I think I shouldn't have wiped them...
Any help would be much appriciated, I don't need another bricked phone... ;(
Click to expand...
Click to collapse
Himanshu Gusai said:
1. flash new stock rom in ur device.
2. now you have two options
a. you can update your device. ( do all the updates of lollipop but don't upgrade it to marshmallow )
b. you can use the current rom that you have got after flashing.
3. root your device using kingroot app that you can easily find on net.
4. after rooting install chamelephon app on your device from play store.
5. remove the battery and note down the imei numbers written on back of the device.
6. plugin the battery and switch on your device.
7. open chamelephon app.
8. enter the imei numbers.
9. Hit apply new imei option.
10. wait for 1 min.
11. switch off your phone and then switch it on.
12. your sims are ready to work.....
Note ( do not update the device to marshmallow as kingroot app is not able to root lenovo vib marshmallow updated devices.)
Click to expand...
Click to collapse
hi himansu,
can you tell me which stock rom you use.
i try already your solution, but still not working for my phone.
Please help
Dear Nechoya,
I got the exact same problem as I followed your footsteps of wiping too much.
Now my K3 note has NO IMEI and sim says NO SIM CARD INSERTED. I have tried all the usual methods mentioned on various threads but nothing is working for me. Can you please clarify what worked for you with some details. I am not a pro and anything from your side or any of the members reading it will be of immense help.
Thank you.
PS I Dont have any kind of backup
Try lord Arcadius' method.
somyaverma1891 said:
Dear Nechoya,
I got the exact same problem as I followed your footsteps of wiping too much.
Now my K3 note has NO IMEI and sim says NO SIM CARD INSERTED. I have tried all the usual methods mentioned on various threads but nothing is working for me. Can you please clarify what worked for you with some details. I am not a pro and anything from your side or any of the members reading it will be of immense help.
Thank you.
PS I Dont have any kind of backup
Click to expand...
Click to collapse
Never mind... I eventually found LordArcadius method here- https://forum.xda-developers.com/android/help/guide-how-to-fix-unknown-baseband-t3096927
And it is so simple working method that solved this IMEI problem.
Thanks.
Hi ALL
I have problem with my Mi 8.
No imei, baseband.
So I can't use my SIM and can't use wi-fi
I tried QPST , IMEI writer but failed
Someone help me please ((
Huynd1094 said:
Hi ALL
I have problem with my Mi 8.
No imei, baseband.
So I can't use my SIM and can't use wi-fi
I tried QPST , IMEI writer but failed
Someone help me please ((
Click to expand...
Click to collapse
Have you simply formatted ( Note that I said format and not wipe) the phone and reinstalled stock?
If yes, then QPST is the only option, and if you used it correctly it will usually work, unless you have a hardware issue. Do you have any recovery backups that you can restore?
These QPST instructions are all over the web, but the steps are always the same. I have repaired IMEI twice but on a different device.
If not you will need to find a donor QCN and retry QPST. ( QCN's can be found here on XDA and on Xiaomi forums) Make sure that you get all of the correct files for your Mi8 ( Your version of the Mi8)
and you can follow the instructions here: https://medium.com/@shekhawatkoki/f...-snapdragon-devices-xiaomi-mi-a1-2ed533548d32
Although these steps are for a A1 the steps are standard across Qualcomm devices. Just be sure to use the correct files.
I included the IMEI rebuilder tool and a QCN attached below. I keep these in case I ever needed it for myself and I have no idea where I got them. Use Google and research the issue heavily before starting. Be sure to try formatting and restoring the full stock Rom via ADB first before doing anything else.
Good Luck.
tsongming said:
Have you simply formatted ( Note that I said format and not wipe) the phone and reinstalled stock?
If yes, then QPST is the only option, and if you used it correctly it will usually work, unless you have a hardware issue. Do you have any recovery backups that you can restore?
These QPST instructions are all over the web, but the steps are always the same. I have repaired IMEI twice but on a different device.
If not you will need to find a donor QCN and retry QPST. ( QCN's can be found here on XDA and on Xiaomi forums) Make sure that you get all of the correct files for your Mi8 ( Your version of the Mi8)
and you can follow the instructions here: https://medium.com/@shekhawatkoki/f...-snapdragon-devices-xiaomi-mi-a1-2ed533548d32
Although these steps are for a A1 the steps are standard across Qualcomm devices. Just be sure to use the correct files.
I included the IMEI rebuilder tool and a QCN attached below. I keep these in case I ever needed it for myself and I have no idea where I got them. Use Google and research the issue heavily before starting. Be sure to try formatting and restoring the full stock Rom via ADB first before doing anything else.
Good Luck.
Click to expand...
Click to collapse
@tsongming Hi Sir! Hey im back with my mi8 problem and i decided to try editing the imei as a final attempt and i got stuck midway. May i request some advice from u?. Im stuck at QPST somehow not transmiting data into my phone. attached picture below. Thanks for your service sir!! will hit thanks
And as a side note. are website that provide downloadable stuff such as https://androidmtk.com/ safe from your years of use? cause they share the same format as https://qpsttool.com/ and just look fishy...
Theevanz said:
@tsongming Hi Sir! Hey im back with my mi8 problem and i decided to try editing the imei as a final attempt and i got stuck midway. May i request some advice from u?. Im stuck at QPST somehow not transmiting data into my phone. attached picture below. Thanks for your service sir!! will hit thanks
And as a side note. are website that provide downloadable stuff such as https://androidmtk.com/ safe from your years of use? cause they share the same format as https://qpsttool.com/ and just look fishy...
Click to expand...
Click to collapse
Sorry for the delay, I have downloaded and used files from this site a few times the past and had no issues whatsoever. However, that was a long time ago and it now looks like a completely different site. But they have an up to date security certificate. However, I would suggest that if you decide that you must use QPST, that you create a developer account with qualcomm and download the qpst tool from them directly. This way you are getting the most up to date tools, and you can get support from their forums.
FYI: you need to enter Diag mode before you can use the QPST tool for IMEI manipulation. Also, the tool will only affect Sim card 1... well that is what I have heard in regard to Xiaomi phones. Beyond those suggestions, as I have mentioned numerous times, on various threads, I do not support QPST with the Mi8. Because I have no experience using it with this device so I can not provide help based on experience.
The last time I used it years ago, and it was for the sake of experimentation. and once you change the IMEI it is difficult if not nearly impossible to restore the phone back to it's originally IMEI unless you have your original QCN backed up.
To go on, I made the post above almost a year ago, and frankly forgot about it. My perspective has changed, I would strongly suggest not using QPST or the QCN file to fix your phone. and to instead attempt to manually repair your phone using the steps suggested on my persist thread. if you have already tried everything on that that thread there is not much more I can offer, it's too risky and I don't want to be involved with permanently damaging your device. Online IMEI Repair services exist, and that may be your best option if the phone restoration route doesn't work.
Another option is using a UMT Box, and following an online tutorial. They cost about $50.
Hey!
Ive been noticing an issue with my device, since I think the update to MIUI 11 (but not sure).
Description:
- The compass (and other apps using compass like Google maps) gives incorrect readings, when put horizontally. When put horizontally and kept still, the compass will spin regularly ca 2 degrees per second completely independent from the actual pointing direction. When the phone is kept vertically the compass works normally. I have made a video displaying the correct reading when vertically, and the spinning when kept horizontally: https://youtu.be/xgC4fHqH4Ys
- When checking the underlying gyroscope functionality with "Sensor Multitool", I have come across what I think is an erratic z axis reading. When I spin the phone randomly, the gyroscope in the x and y axis registers adequate readings, but the z axis stays completely flat. I have produced a video showing this behavior: https://youtu.be/1dY_xdF5Nz8
I have found this thread from Aliosa007 ( https://forum.xda-developers.com/showthread.php?t=3972249 ) that describes a very similar issue, but this user had recently flashed a new rom and the problem is attributed with the flashing. The users there assume the issue being a corrupt persist.img and most problem solving techniques involve flashing etc. But my phone is locked and not rooted. Could I also have received a corrupt persist.img during the normal update process recently to MIUI 11.
Currently trying to figure out, what the best way forward is. Wait and hope that this will be fixed with the next update or go the warranty route?
Thanks for helping me out with this one!
Hi.
I'm sorry I won't be very useful since I'm just having the exact same problem as you and don't know how to solve it... My phone isn't flashed either and my compass spins continuously.
I just wanted to know if you found a solution since your original post.
I also wanted to know if you tried factory resetting your phone ? I was thinking about trying that but if you already did and it didn't solve the issue, maybe I won't bother...
Thanks in advance.
Tistou52 said:
Hi.
I'm sorry I won't be very useful since I'm just having the exact same problem as you and don't know how to solve it... My phone isn't flashed either and my compass spins continuously.
I just wanted to know if you found a solution since your original post.
I also wanted to know if you tried factory resetting your phone ? I was thinking about trying that but if you already did and it didn't solve the issue, maybe I won't bother...
Thanks in advance.
Click to expand...
Click to collapse
Hey Tistou, thanks for your message. I haven't found a solution to the issue yet, unfortunately.
I tried factory resetting the phone but that didn't solve it. Did this problem just occur one day - or was it after you updated the phone? In my case Im not 100% sure it began after the updated and if it didn't, it could be an indication for a hardware issue.
I will keep this thread up to date in case I find a solution to the issue. But at the moment, I am out of ideas. I thought about flashing the phone with an alternative ROM and replace the persist.img. But currently the assumed risk/benefit keep me up from doing that. I'd assume sending Xiaomi feedback on that issue
Best,
schnodda
schnodda123 said:
Hey Tistou, thanks for your message. I haven't found a solution to the issue yet, unfortunately.
I tried factory resetting the phone but that didn't solve it. Did this problem just occur one day - or was it after you updated the phone? In my case Im not 100% sure it began after the updated and if it didn't, it could be an indication for a hardware issue.
I will keep this thread up to date in case I find a solution to the issue. But at the moment, I am out of ideas. I thought about flashing the phone with an alternative ROM and replace the persist.img. But currently the assumed risk/benefit keep me up from doing that. I'd assume sending Xiaomi feedback on that issue
Best,
schnodda
Click to expand...
Click to collapse
Hey,
well I couldn't really tell if it's related to an update : I got my mi 9T pro like two or three weeks ago and updated to 11.0.3 the day I got it...
The weird thing is that I noticed the problem one first time, and then two or three days later the issue solved itself without me doing anything particular and my compass started working normally again... And then two or three days ago it started spinning continuously again... I just hope it's software related and not an hardware issue...
I think I'm just going to wait for the next system update and if doesn't solve the problem I may send the phone back (but I don't wanna ... The phone otherwise is so great...).
I'll update the thread if I find something.
Good luck
Hi there, I had a similar problem a while ago when going from custom rom Android 10 back to miui 10 Android 9. Pop up camera and gyro sensors wouldn't work so no auto rotate either. Simple fix was to flash the persist img in custom recovery, then go into stock camera app and it'll ask to calibrate, after than everything worked fine. This should work for you and everyone else with this problem hopefully.
Flashing persist won't wipe any of your data so don't worries there. I'll see if I can find the file I have it somewhere and I'll send the link.
So really the only way to fix this is to have compatible custom recovery with persist partition, flash the persist.img, but since you have a locked bootloader and stock recovery I don't think you have any options to fix this unfortunately, maybe fastboot rom through miflash? That didn't work for me but it might work for you.
hoopsnake said:
Hi there, I had a similar problem a while ago when going from custom rom Android 10 back to miui 10 Android 9. Pop up camera and gyro sensors wouldn't work so no auto rotate either. Simple fix was to flash the persist img in custom recovery, then go into stock camera app and it'll ask to calibrate, after than everything worked fine. This should work for you and everyone else with this problem hopefully.
Flashing persist won't wipe any of your data so don't worries there. I'll see if I can find the file I have it somewhere and I'll send the link.
So really the only way to fix this is to have compatible custom recovery with persist partition, flash the persist.img, but since you have a locked bootloader and stock recovery I don't think you have any options to fix this unfortunately, maybe fastboot rom through miflash? That didn't work for me but it might work for you.
Click to expand...
Click to collapse
Thank you so much for your response! That keeps my hopes up that I get it solved eventually.
I am currently not planning to unlock my bootloader, I am currently exploring to go the warranty route because that's the easiest way forward. But in case that won't work, I will definitely try to flash the persist.img. I will have to try to get my hands on the persist.img file!
Thanks again!
schnodda123 said:
Thank you so much for your response! That keeps my hopes up that I get it solved eventually.
I am currently not planning to unlock my bootloader, I am currently exploring to go the warranty route because that's the easiest way forward. But in case that won't work, I will definitely try to flash the persist.img. I will have to try to get my hands on the persist.img file!
Thanks again!
Click to expand...
Click to collapse
persist.img is in the fastboot rom, so if you download that and extract you can get the img. You should be able to flash it thru fastboot using adb on PC with the command 'fastboot flash persist persist.img'. no need to unlock bootloader
I'm not gonna be near my PC for a while so won't be able to upload it for you
hoopsnake said:
persist.img is in the fastboot rom, so if you download that and extract you can get the img. You should be able to flash it thru fastboot using adb on PC with the command 'fastboot flash persist persist.img'. no need to unlock bootloader
I'm not gonna be near my PC for a while so won't be able to upload it for you
Click to expand...
Click to collapse
Sorry sir, but i think you cannot flash persist.img thru fastboot, because it read-only partition ,
I read several times that it must be flashed with twrp (dunno what that means)... But I also read that it makes you lose L1 widevine (dunno what that means either). Could someone enlighten me ?
And do you think the next MIUI update could fix that ?
Tistou52 said:
I read several times that it must be flashed with twrp (dunno what that means)... But I also read that it makes you lose L1 widevine (dunno what that means either). Could someone enlighten me ?
And do you think the next MIUI update could fix that ?
Click to expand...
Click to collapse
Not an expert on the matter. But a peripheral knowledge of the matter.
It appears to me that you are new to the matter. So I will use easy language.
TWRP is a so called "custom recovery" for Android that allows users to basically change the underlying firmware/system software (a process often referred to as "flashing") of the device. It is basically the entry point towards conveniently changing system files, that Android normally forbids you to change. To install a costum recovery, the bootloader of the phone has to be unlocked, so that the device can boot into the custom recovery instead of the OS directly. https://www.quora.com/What-is-TWRP-Why-is-it-used?share=1
Widevine L1 is a software part within Android that basically authenticates, that the device at hand is allowed to handle media files that are DRM protected (eg. within Netflix). When Android has been changed from the default configuration (by flashing a custom rom), the software part should revoke the authorization or restrict it. This behavior depends I think on the capability of the custom rom to trick widevine into believing that its genuine.(not so sure about that)
https://www.androidauthority.com/widevine-explained-821935/
Heres hoping that the next update will solve the issue! The issue isnt so dramatic to go the persist.img route. So I will patiently wait for the update. I will keep the thread updated.
schnodda123 said:
Not an expert on the matter. But a peripheral knowledge of the matter.
It appears to me that you are new to the matter. So I will use easy language.
TWRP is a so called "custom recovery" for Android that allows users to basically change the underlying firmware/system software (a process often referred to as "flashing") of the device. It is basically the entry point towards conveniently changing system files, that Android normally forbids you to change. To install a costum recovery, the bootloader of the phone has to be unlocked, so that the device can boot into the custom recovery instead of the OS directly. https://www.quora.com/What-is-TWRP-Why-is-it-used?share=1
Widevine L1 is a software part within Android that basically authenticates, that the device at hand is allowed to handle media files that are DRM protected (eg. within Netflix). When Android has been changed from the default configuration (by flashing a custom rom), the software part should revoke the authorization or restrict it. This behavior depends I think on the capability of the custom rom to trick widevine into believing that its genuine.(not so sure about that)
https://www.androidauthority.com/widevine-explained-821935/
Heres hoping that the next update will solve the issue! The issue isnt so dramatic to go the persist.img route. So I will patiently wait for the update. I will keep the thread updated.
Click to expand...
Click to collapse
Hola @schnodda123, ¿Logaste darle solución? No he podido arreglar mi eje z en mi caso en un Redmi Note 8, estoy algo incomodo, si bien el celular funciona bien el tener el sensor mal es fastidioso
Hi @ schnodda123, Did you manage to give it a solution? I have not been able to fix my z axis in my case on a Redmi Note 8, I am somewhat uncomfortable, although the cell phone works well, having the wrong sensor is annoying
Hi,
After trying to flash I was like you can see in the image "nv data corrupted", does anyone know how to solve it?
sk3lt said:
Hi,
After trying to flash I was like you can see in the image "nv data corrupted", does anyone know how to solve it?
Click to expand...
Click to collapse
"Trying to flash" , what exactly did you flash ?
How do you flash it ?
Why dont you flash TWRP followed by ROM of any choice ?
NV normally contained in EFS partition, which can be backed up and flash from TWRP and QPST.
But again, your description is far from clear for us to help you.
otonieru said:
"Trying to flash" , what exactly did you flash ?
How do you flash it ?
Why dont you flash TWRP followed by ROM of any choice ?
NV normally contained in EFS partition, which can be backed up and flash from TWRP and QPST.
But again, your description is far from clear for us to help you.
Click to expand...
Click to collapse
I already flashed with twrp and miflash with stock rom and xiaomi.eu the flash is finished successfully but the nv data corrupted always comes back. Any idea how can I solve this?
sk3lt said:
I already flashed with twrp and miflash with stock rom and xiaomi.eu the flash is finished successfully but the nv data corrupted always comes back. Any idea how can I solve this?
Click to expand...
Click to collapse
When you flash using TWRP, did you actually managed to boot into system ? Or it stuck in recovery ?
Where did the nv corrupted notification appear when u were using TWRP ?
Prior to facing this issue, what you actually did ? I mean, did this phone work before ? Before you start getting this error, what you did, what you install, what you flash, what you delete ? Or did it just suddenly happen with nothing modified ?
otonieru said:
When you flash using TWRP, did you actually managed to boot into system ? Or it stuck in recovery ?
Where did the nv corrupted notification appear when u were using TWRP ?
Prior to facing this issue, what you actually did ? I mean, did this phone work before ? Before you start getting this error, what you did, what you install, what you flash, what you delete ? Or did it just suddenly happen with nothing modified ?
Click to expand...
Click to collapse
Boot up to the Android logo and then return to recovery.
I flashed a room and lost the imei, I tried to recover with a qcn I found but I must have done something wrong.
sk3lt said:
Boot up to the Android logo and then return to recovery.
I flashed a room and lost the imei, I tried to recover with a qcn I found but I must have done something wrong.
Click to expand...
Click to collapse
You gonna need to ask someone to backup their QCN, take out the imei info, give it to you, and flash it using QPST.
otonieru said:
You gonna need to ask someone to backup their QCN, take out the imei info, give it to you, and flash it using QPST.
Click to expand...
Click to collapse
I can't use qpst, because I can't activate usbdebug and the diag port.
Is it possible to give me a hand?
sk3lt said:
I can't use qpst, because I can't activate usbdebug and the diag port.
Is it possible to give me a hand?
Click to expand...
Click to collapse
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
tsongming said:
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
Click to expand...
Click to collapse
I flashed an altered rom, without success I got a brick I'm without recovery and without fastboot I just have a black screen and it's only recognized by the PC in 9008 mode, you have any idea how I can solve it?
sk3lt said:
I flashed an altered rom, without success I got a brick I'm without recovery and without fastboot I just have a black screen and it's only recognized by the PC in 9008 mode, you have any idea how I can solve it?
Click to expand...
Click to collapse
Sorry that you are having these issues, But my comment was based on the photo that was posted on the OP. Typically formatting is the resolution. If you no longer have that screen available, you should contact an authorised repair center to fix it for you.
Otherwise If the phone is bound to your account, you could try what is listed here: https://www.mobilerdx.com/2019/02/xiaomi-mi-8-test-point-boot-xiaomi-mi-8-into-edl-9008-mode.html
Scams or Actual Fixes?
I have recently read about supposed hacks that according to a couple of Chinese BBS sites, has worked for some that require buying a specialised Jtag programming tool which cost about $60, that you use along with altered versions of following files: prog_emmc_firehose_8909.mbn.elf, mi8 persist image, rawprogram0, frp and a patch file. All of which that can all be obtained from here: https://romprovider.com/2019/09/mi-account-remove-xiaomi/ ( UMT Download)
Supposedly Chimera is another option: https://chimeratool.com/en/docs Again I have not used any of these tools with the mi8, I am merely sharing what I read about recently.
By the time you have spent the money acquiring the tools, it seems that you are better off just mailing the phone off to be repaired by an official repair center. Here is a web page that provides a list of official repair centers : https://www.pinoytechnoguide.com/2014/06/xiaomi-service-centers.html
Good Luck and try anything mentioned above at your own risk.
Edit: Have you tried the Flashall.bat method?
That should work since you are seeing the com port.
tsongming said:
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
Click to expand...
Click to collapse
tsongming said:
Sorry that you are having these issues, But my comment was based on the photo that was posted on the OP. Typically formatting is the resolution. If you no longer have that screen available, you should contact an authorised repair center to fix it for you.
Otherwise If the phone is bound to your account, you could try what is listed here: https://www.mobilerdx.com/2019/02/xiaomi-mi-8-test-point-boot-xiaomi-mi-8-into-edl-9008-mode.html
Scams or Actual Fixes?
I have recently read about supposed hacks that according to a couple of Chinese BBS sites, has worked for some that require buying a specialised Jtag programming tool which cost about $60, that you use along with altered versions of following files: prog_emmc_firehose_8909.mbn.elf, mi8 persist image, rawprogram0, frp and a patch file. All of which that can all be obtained from here: https://romprovider.com/2019/09/mi-account-remove-xiaomi/ ( UMT Download)
Supposedly Chimera is another option: https://chimeratool.com/en/docs Again I have not used any of these tools with the mi8, I am merely sharing what I read about recently.
By the time you have spent the money acquiring the tools, it seems that you are better off just mailing the phone off to be repaired by an official repair center. Here is a web page that provides a list of official repair centers : https://www.pinoytechnoguide.com/2014/06/xiaomi-service-centers.html
Good Luck and try anything mentioned above at your own risk.
Edit: Have you tried the Flashall.bat method?
That should work since you are seeing the com port.
Click to expand...
Click to collapse
Hello, thank you for your answer, the mother is not linked to my account I disconnected to do the experiments. in my country i don't have a xiaomi assistance center, i get the error missmatching image and device.
There is no other way to unbrick without buying these tools so expensive that you mentioned
sk3lt said:
Hello, thank you for your answer, the mother is not linked to my account I disconnected to do the experiments. in my country i don't have a xiaomi assistance center, i get the error missmatching image and device.
There is no other way to unbrick without buying these tools so expensive that you mentioned
Click to expand...
Click to collapse
use testpoint method, and flash it using QFIL.
otonieru said:
use testpoint method, and flash it using QFIL.
Click to expand...
Click to collapse
I always get this error.
I already managed to unbrick with a firmware eng eng.
but then when flash with stock rom stays the same again nv data corrupted.
Any solution to solve this nv data corrupted?
sk3lt said:
I always get this error.
I already managed to unbrick with a firmware eng eng.
but then when flash with stock rom stays the same again nv data corrupted.
Any solution to solve this nv data corrupted?
Click to expand...
Click to collapse
root cause of your issue is that you play with wrong qcn and messed up the nv,
wince you cant plugged to qpst, you need someone to make EFS backup for you torestore from twrp
You can restore phones imei if your bootloader is unlocked but only 2nd sim slot will work
How can I do this? Can you help me please?
jokerm90 said:
You can restore phones imei if your bootloader is unlocked but only 2nd sim slot will work
Click to expand...
Click to collapse
How can I do this? Can you help me please?
Dear All,
While trying to install MIUI 12 Beta , I Lost my IMEI
Installed ENG Firmware which allowed my to edit the IMEI using the Maui META ver 10.1816.0.01 but due to corrupted NV Data the phone isn't booting
Anyone can backup and share the NV Data file ?! i found one online but unfortunately it has a password and can't unrar it.
Your support is much appreciated to guide throw fixing this issue.
sk3lt said:
How can I do this? Can you help me please?
Click to expand...
Click to collapse
You need backup EFS and Modem via TWRP first(better with OrangeFox). After you need Magisk first and some manipulation with QCN file via QPST. I will write it later
MohamedYousri said:
Dear All,
While trying to install MIUI 12 Beta , I Lost my IMEI
Installed ENG Firmware which allowed my to edit the IMEI using the Maui META ver 10.1816.0.01 but due to corrupted NV Data the phone isn't booting
Anyone can backup and share the NV Data file ?! i found one online but unfortunately it has a password and can't unrar it.
Your support is much appreciated to guide throw fixing this issue.
Click to expand...
Click to collapse
Maui Meta is for MTK cpu phones. You need QPST
Note 8 Pro is MTK Device
Long story short, my gf Redmi Note 10 Pro somehow got to MIUI Recovery menu and 3rd party service managed to erase recovery and everything from the phone and gave back the fresh looking brick stuck on Fastboot!!!
I have successfully flashed EEU Sweet ROM (Europe (EEA) latest Fastboot ROM MIUI V12.5.6.0.RKFEUXM) on the Global version though and after that it comes to recovery menu but it shows in red "NV data is corrupted" now I am clueless what to do next. Desperate me tried to flash Global latest Fastboot ROM MIUI V12.5.9.0.RKFMIXM but it gives Anti Rollback error so based on info here https://www.xda-developers.com/xiao...78.2028059671.1642858063-854958160.1642858063 I have checked the Anti_version.txt of the current ROM and the one I try to install and both is on 3 so based on the info I should be able to flash to the same number but it wasn't successful so I tried to edit Flash_all.Bat file and remove the ARB check commands but even after that I still get the ABR error. What should I do? Am I taking a wrong path in solving the issue? Would flashing it again solve the "NV data is corrupted" issue?
I dunno if this helps, but I was stuck in Fastboot as well at some time. Nothing helped, not even flashing through fastboot. The only tool that helped me was the Xiaomi Tool V2 https://www.xiaomitool.com/V2/ here. No ad or something but this really helped alot without problems.
Other possible problem by another user: https://forum.xda-developers.com/t/redmi-note-10-pro-sweet-nv-is-corrupted-fixed.4345659/
Maybe you installed the wrong rom?
romuser87 said:
I dunno if this helps, but I was stuck in Fastboot as well at some time. Nothing helped, not even flashing through fastboot. The only tool that helped me was the Xiaomi Tool V2 https://www.xiaomitool.com/V2/ here. No ad or something but this really helped alot without problems.
Other possible problem by another user: https://forum.xda-developers.com/t/redmi-note-10-pro-sweet-nv-is-corrupted-fixed.4345659/
Maybe you installed the wrong rom?
Click to expand...
Click to collapse
Thanks, DLin the tool you mentioned atm but yes I did dl a EU version on global which I read it is no issue as long as it is not on Chinese version. It all started suddenly, out of nowhere the phone rebooted on Fastboot so it was taken to a 3rd party service and their they tried to fix it by wiping the phone to an unrecoverable state and said this is a new model so the files are not yet published you better take it to an authorized service!!!Oh I am mad! I'll report after trying the tool. Btw the other solution you mentioned was the 1st thing I tried but the file in 1st step is removed from the hosting server and someone asked the thread creator to reupload but no reply yet :/
Asgharjoon said:
Thanks, DLin the tool you mentioned atm but yes I did dl a EU version on global which I read it is no issue as long as it is not on Chinese version. It all started suddenly, out of nowhere the phone rebooted on Fastboot so it was taken to a 3rd party service and their they tried to fix it by wiping the phone to an unrecoverable state and said this is a new model so the files are not yet published you better take it to an authorized service!!!Oh I am mad! I'll report after trying the tool. Btw the other solution you mentioned was the 1st thing I tried but the file in 1st step is removed from the hosting server and someone asked the thread creator to reupload but no reply yet :/
Click to expand...
Click to collapse
Ok so now I tried with the tool and interestingly I had to make choices which were not easy and obvious anyhow, it didn't work
It gives the below error and seems to be called "sideload" status issue. But the phone now still reboots on Main Menu with the same old "NV data is corrupted"
romuser87 said:
I dunno if this helps, but I was stuck in Fastboot as well at some time. Nothing helped, not even flashing through fastboot. The only tool that helped me was the Xiaomi Tool V2 https://www.xiaomitool.com/V2/ here. No ad or something but this really helped alot without problems.
Other possible problem by another user: https://forum.xda-developers.com/t/redmi-note-10-pro-sweet-nv-is-corrupted-fixed.4345659/
Maybe you installed the wrong rom?
Click to expand...
Click to collapse
I could finally flash the latest Global version but the error persists. Accidentally I did flash the phone with clean all and lock ticked Now I cannot even flash anything as bootloader is locked! How can I fix it help please
Here is the wrong selection on MI Flash! Is there anyway to get it unlocked?