Related
I have a Xiaomi Mi Max 2 phone (version MIUI Global 9.2 Stable 9.2.1.0 NDDMIEK), I got the permission to unlock it from Xiaomi, I dowloaded Mi Unlock but it stops the procedure because "Current account is no bound to this device".
I went to developer options - Mi Unlock status but all I get is an error 86006 and something in Chinese.
From other threads it is suggested that I should flash some 8.3.1 Developer ROM, meaning that I have to double back my OS in order to unlock it.
Do I really have to do something like that? Is there another option?
And let us suppose that I do double back and it works. What next?
If I root my phone and flash 9.2 again I'll lose the root.
If I flash 9.2 first, will my phone continue to be unlocked in order to root it?
Why are they making things so complex? I know the risks about rooting a phone, just let me do it!
[S8+] Purchased a stock AT&T S8+ in a lot. It has latest bootloader and bad IMEI....
First off, I'm an engineering scientist with years of development experience developing both hardware and software for all sorts of phones and companies. So I feel I'm pretty familiar with Android and every conceivable (and off-the-wall) way to get this phone unlocked, rooted, and/or just flat out usable. And I have failed which is why I am finally giving this to the multiverse in hopes there is someone with some solution I have yet to attempt.
I have been searching and trying every possible option for a week and counting. I'm also aware of how close to impossible it is to work with locked Snapdragon CPUs. But not entirely impossible. There has to be a way of reviving this phone!
So I recently purchased a lot full of untested and "for parts" electronics. In there was an AT&T S8+ with a cracked screen. It was also stuck in a boot loop, so I can safely hazard a guess that someone tried to update the ROM, bricked it, and didn't realize they could reflash stock firmware and fix it. Well, upon further examination, I discovered they had attempted flashing a V7 bootloader. Yes, version 7. So that basically robbed me of any options I may have had, as well as all the bugs I could have used to root the device. All I could do was install Pie with a V7 bootloader. Voila! The phone boots up. But it gets better....
Now that the phone was working, I did some examining, one part of which was the IMEI as I wanted to unlock it if possible. I check the IMEI, and it is frakking blacklisted! So that blew ever being able to use this phone on a network. I even sat on hold for 46 minutes to speak with someone at AT&T to see if they could remove it off the blacklist. They promptly said "sure!", then transferred me to someone else to fix it and the guy said "no".. So it's stuck locked to AT&T, which sucks because I checked with several other networks who all said the phone could be used on their networks. But that's not an option if it is carrier locked and impossible to unlock. :silly:
Furthermore, OEM Unlock is 110% unavailable, and no bugs work or exist to force it to appear on Android 9 Pie like you can with 8 Oreo and 7 Nougat; and I tried for days. So the bootloader is permanently locked. If it wasn't, I could root the phone, fix the IMEI, unlock it, and get the phone functional again. Alas, I cannot, at least any time soon, if ever.
I've tried every possible thing out there to root this, unlock the bootloader, and/or try to roll back Pie to Oreo, Nougat, or some stock ROM with bugs that are still active. At the very least just to change the IMEI and get the phone working again. But there is no version of Oreo/Nougat that can be installed with a V7 bootloader.
Also, there is absolutely no Engineering Mode (NOT Developer Mode) available under this stock Android 9 Pie, either by code or by app/settings. Does anybody know of an exact Android 9 Pie stock ROM with an accessible no-root Engineering Mode?
And I've tried every way out there to force OEM Unlock to appear, but the bugs that work in Oreo and Nougat have all been patched and none of them work on Android 9 Pie. So I'm stuck with this ROM and bootloader
So I'm here today with these issues in hopes someone may have solutions for:
A way to force OEM Unlock to appear under Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to bypass KG state under stock Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to install Android 8 Oreo or Android 7 Nougat with a V7 bootloader
A stock ROM with Engineering Mode available
A way to change the IMEI without root
A way to modify the V7 stock ROM so it installs a Nougat/Oreo ROM instead of Pie
Another option to keep this phone from just being a fancy, pretty paperweight
Any solution we or I may discover, I will clean it up and make a guide to help others with these same issues as there is not much info yet V7 on bootloaders. So this is a group activity that could help many, many people; help me help us all!
Thank you all in advance for anything you can offer to help!
-DL
EDIT 1: I forgot to mention that the KG State is stuck on "Checking...." so I couldn't get "OEM Unlock" even by waiting
I used this video to figure out how to get the OEM Unlock option.
(input this after youtube url) watch?v=zhNhyT4F3e8&t=133s
Hopefully this helps.
domiluci said:
First off, I'm an engineering scientist with years of development experience developing both hardware and software for all sorts of phones and companies. So I feel I'm pretty familiar with Android and every conceivable (and off-the-wall) way to get this phone unlocked, rooted, and/or just flat out usable. And I have failed which is why I am finally giving this to the multiverse in hopes there is someone with some solution I have yet to attempt.
I have been searching and trying every possible option for a week and counting. I'm also aware of how close to impossible it is to work with locked Snapdragon CPUs. But not entirely impossible. There has to be a way of reviving this phone!
So I recently purchased a lot full of untested and "for parts" electronics. In there was an AT&T S8+ with a cracked screen. It was also stuck in a boot loop, so I can safely hazard a guess that someone tried to update the ROM, bricked it, and didn't realize they could reflash stock firmware and fix it. Well, upon further examination, I discovered they had attempted flashing a V7 bootloader. Yes, version 7. So that basically robbed me of any options I may have had, as well as all the bugs I could have used to root the device. All I could do was install Pie with a V7 bootloader. Voila! The phone boots up. But it gets better....
Now that the phone was working, I did some examining, one part of which was the IMEI as I wanted to unlock it if possible. I check the IMEI, and it is frakking blacklisted! So that blew ever being able to use this phone on a network. I even sat on hold for 46 minutes to speak with someone at AT&T to see if they could remove it off the blacklist. They promptly said "sure!", then transferred me to someone else to fix it and the guy said "no".. So it's stuck locked to AT&T, which sucks because I checked with several other networks who all said the phone could be used on their networks. But that's not an option if it is carrier locked and impossible to unlock. :silly:
Furthermore, OEM Unlock is 110% unavailable, and no bugs work or exist to force it to appear on Android 9 Pie like you can with 8 Oreo and 7 Nougat; and I tried for days. So the bootloader is permanently locked. If it wasn't, I could root the phone, fix the IMEI, unlock it, and get the phone functional again. Alas, I cannot, at least any time soon, if ever.
I've tried every possible thing out there to root this, unlock the bootloader, and/or try to roll back Pie to Oreo, Nougat, or some stock ROM with bugs that are still active. At the very least just to change the IMEI and get the phone working again. But there is no version of Oreo/Nougat that can be installed with a V7 bootloader.
Also, there is absolutely no Engineering Mode (NOT Developer Mode) available under this stock Android 9 Pie, either by code or by app/settings. Does anybody know of an exact Android 9 Pie stock ROM with an accessible no-root Engineering Mode?
And I've tried every way out there to force OEM Unlock to appear, but the bugs that work in Oreo and Nougat have all been patched and none of them work on Android 9 Pie. So I'm stuck with this ROM and bootloader
So I'm here today with these issues in hopes someone may have solutions for:
A way to force OEM Unlock to appear under Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to bypass KG state under stock Android 9 Pie (as no Oreo/Nougat hacks work under Pie)
A way to install Android 8 Oreo or Android 7 Nougat with a V7 bootloader
A stock ROM with Engineering Mode available
A way to change the IMEI without root
A way to modify the V7 stock ROM so it installs a Nougat/Oreo ROM instead of Pie
Another option to keep this phone from just being a fancy, pretty paperweight
Any solution we or I may discover, I will clean it up and make a guide to help others with these same issues as there is not much info yet V7 on bootloaders. So this is a group activity that could help many, many people; help me help us all!
Thank you all in advance for anything you can offer to help!
-DL
EDIT 1: I forgot to mention that the KG State is stuck on "Checking...." so I couldn't get "OEM Unlock" even by waiting
Click to expand...
Click to collapse
There is no OEM unlock on us snap dragon devices. Locked boot loader. Closest you will get is the combination firmware. But the OEM unlock in that does not work trust me on this. The imei is cert coded to the hardware. And can't be discussed on xda how to change. It's possible. But not by just anyone. The combination files are nougat. But their not going to help you out in this situation
So, I have the MIUI 12 EEA on a Mi 10 Lite, and it's not the stock ROM but the Vodafone build (QJIEUVF).
As there's the new Android 11 update coming, I'd like to have that and not wait for Vodafone to release its build, as that's notoriously slow.
I tried the official Updater app, to install the XM build, but it says the network carrier is different. Seems like the only way is to unlock the bootloader. However, it seems that means losing Netflix and Google Pay support?
Now, can I unlock the bootloader, flash the QJIEUXM with XiaoMiToolV2, and then relock the bootloader with Clean and Lock? Would that lead to a softbrick? Any other downside to doing that, such as losing OTA updates?
I tried to find info, but it's really hard to find any reliable information anywhere
Hi, I am on the same situation as you, did you successfully relocked your phone?
Hi ,I have one plus 7 Pro T-Mobile locked, before updating it was showing unlocking options in network ,in settings options .But as I updated the software,i was wondering not able to find neither any T-Mobile device unlock app nor in settings .
please help me to find the option for unlocking it.
Anybody also facing the same issue?
You're trying to sim unlock it or bootloader unlock it?
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
smartasiankid said:
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
Click to expand...
Click to collapse
Why is OEM Unlocking greyed out?
In theory, because you are already unlocked.
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
notmyrealhandle said:
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
Click to expand...
Click to collapse
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
smartasiankid said:
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
Click to expand...
Click to collapse
I'm not sure then.
If I was in your situation and I didn't mind wiping my data, I'd probably try booting into the bootloader and trying `fastboot flashing unlock` just to see what happens. If this command works, it will wipe your data so be sure about your backups. If it does unlock, you could try rebooting, check the OEM lock (I expect it will still be greyed out with an unlocked bootloader), and then relock and check again. Regardless if you can unlock inspite of the OEM toggle you shouldn't have much to worry about (at least until the next update).
If this doesn't work then I'd just wait a week or so. Alternatively, you could try the moto site, request your unlock key (again) and then wait a few days. It would be silly if this works, but maybe moto just needs to send a reminder to your device to enable the OEM unlocking toggle.
If none of this works, then I'd try posting to the moto official forums.
HTH
Never mind guys!! Just wait three maybe four days and it will automatically be toggle able again!! Thanks to all of those who tried to help me out!
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
smartasiankid said:
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
Click to expand...
Click to collapse
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
MrCamby said:
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
Click to expand...
Click to collapse
it is greyed out for me. i am on at&t network. it has been greyed out ever since android 11. not sure why that is happening.