Related
I must be very lucky to have unlocked my phone after only one week after I got permission. I tried so many methods but always stuck on 50%. Before giving up and trying unofficial way, I give it last try and Woilaa I succeed. I did lot of research and I believe all information located in phone should be perfectly match to your MIUI ID/Forum settings in order to unlock your phone. So you will need below prerequisite.
PREREQUISITE (Exact what I have done to unlock my phone)
1) Go to your phone setting>My Account>Personal Info> and fill personal Information and Phone/Email. Now go to MIUI forum settings and fill exact data that you have fill up in your phone. (Including your forum username should be same as the name under personal info into phone setting).
2) Also check “Your device and MIUI version” under basic information tab. That should match with your Phone/MIUI version (when it perfectly matches stop upgrading your phone and try to hold MIUI version shows on forum setting, I unlocked my phone on Global MIUI8 stable V8.0.2.0.LHOMIDG).
2) Go to password tab (MIUI forum) and setup security check-up bar to 100% (by setting up 3 secret questions).
3) Add recovery email and recovery phone here (should same as Phone setting).
Now wait at least week after you got permission (I got it one 28-Sep and succeed on 6-Oct, exact after a week)
After week try this method to unlock:-
1) Disable Driver signature enforcement.
2) Remove all locks/patterns fingerprint. Also remove app lock and disable it.
3) Go to developer option and check USB-debug and OEM unlock (if already check then uncheck and re-check it).
4) Go to i.mi.com login with your id (same procedure mentioned all over internet) and check device shows online or not.
5) Check your device is online (should be "Online located just now") IMPORTANT WHEN YOU REFRESH FIND DEVICE BUTTON, YOU SHOULD NOTICE YOUR PHONE SCREEN FLASH or BLUE ICON OF "LOCATION SET BY GPS/SEARCHING FOR GPS" ON NOTIFICATION BAR. (I believe if this happen means your phone is successfully connected to MIUI servers, I failed before many times when I was online but never notice flash/blue icon until last time I succeed)
6) Run unlocks app with “run as administrator” and login with YOUR MI ACCOUNT ID not with your phone number or email.
7) Unlock the phone.
Hope this help anyone
Every time I brick my phone by messing up partitions and I will fire up miflash and flash through edl. I will reboot the phone and will go to fastboot mode directly after flashing. I will launch miunlock tool and clock unlock, even though I didn't even boot up the phone, it will unlock the bootloader. I did this more than 10 times and worked fine. No need to remove app lock, fingerprint, etc. The OEM unlock option in developer options should be enabled to unlock. I think the mi credentials are stored permanently in some place. I am trying to figure out that place where it stored the credentials.
superboy123 said:
Every time I brick my phone by messing up partitions and I will fire up miflash and flash through edl. I will reboot the phone and will go to fastboot mode directly after flashing. I will launch miunlock tool and clock unlock, even though I didn't even boot up the phone, it will unlock the bootloader. I did this more than 10 times and worked fine. No need to remove app lock, fingerprint, etc. The OEM unlock option in developer options should be enabled to unlock. I think the mi credentials are stored permanently in some place. I am trying to figure out that place where it stored the credentials.
Click to expand...
Click to collapse
You are right, MI must have stored the credentials somewhere. I think most of people stuck for the first time. Once you unlocked bootloader, it's easy to unlock again. So may be you were lucky to not faced problem at first try and now you are able to unlock it 10 times.
I think, Mi utilises a digital key similar to those used by Microsoft to activate Windows 10 licences. Once you sign in on a device with a certain Mi account, the server on Mi end ties the IMEI and Device serial number to that account. And, this is the information the MiFlashUnlock searches for when you log on to it. Of course, once you have unlocked your phone, that information too is stored on the server-end, enabling you to unlock your phone multiple times, if it ever gets relocked.
This is my hypothesis anyway. I may very well be wrong.
And, I think the key to unlocking is to remain on the same MIUI version for more than 7 days on a stretch. I did just that and voila, the unlock worked.
Yes, but mine finally unlocked immediately after installing the global dev ROM. It would never get past 50% on 8.0.1, 8.0.2, or 8.0.5. I think there are several factors ( bugs) that cause it to fail, and that those factors interact in various ways that no one here fully understands. So we get all of these elaborate processes that work for a couple of people, but then fail for many others. Oh well.
induna said:
Yes, but mine finally unlocked immediately after installing the global dev ROM. It would never get past 50% on 8.0.1, 8.0.2, or 8.0.5. I think there are several factors ( bugs) that cause it to fail, and that those factors interact in various ways that no one here fully understands. So we get all of these elaborate processes that work for a couple of people, but then fail for many others. Oh well.
Click to expand...
Click to collapse
Stuck at 50 even in dev rom Am fed up now
Sent from my Redmi Note 3 using Tapatalk
dastan4eva said:
Stuck at 50 even in dev rom Am fed up now
Click to expand...
Click to collapse
Yeah, I understand your frustration. I gave up waiting and used the procedure to flash ZXC TWRP with a locked bootloader. It worked perfectly and I was able to install SuperSU and Xposed on MIUI. I tried officially unlocking one last time after that, and it worked. Go figure.
Good luck.
Current account is different from the account on device.
It's been a month after getting official permission.
T3h said:
Current account is different from the account on device.
It's been a month after getting official permission.
Click to expand...
Click to collapse
Yes, it happens. I got unlock permission on 13-August-2016 but was able to unlock only on 07-October-2016. So, I don't really know how long it will take for you to be able to unlock your device.
One thing you can try is to not update MIUI for about 15 or so days and then try to unlock it.
Will wait and keep checking every few days.
T3h said:
Will wait and keep checking every few days.
Click to expand...
Click to collapse
Have you check MIUI version mentioned on your forum setting is same as your device or not. I believe verification of device fails because information stored on Mi servers not matches to your device. So better option is maintain MIUI version shows on forum with your device at least 5 days and stop upgrading your phone once it matches (keep phone connected with Internet during these days so server can interchange data with your device). Good luck.
Apcoolboy said:
Have you check MIUI version mentioned on your forum setting is same as your device or not. I believe verification of device fails because information stored on Mi servers not matches to your device. So better option is maintain MIUI version shows on forum with your device at least 5 days and stop upgrading your phone once it matches (keep phone connected with Internet during these days so server can interchange data with your device). Good luck.
Click to expand...
Click to collapse
Yes the MIUI version matches in the forum too.
I've been checking this from few weeks.
T3h said:
Yes the MIUI version matches in the forum too.
I've been checking this from few weeks.
Click to expand...
Click to collapse
Well, we build many hypothesis how Xiaomi unlock phones. But it is fact that Xiaomi software sucks at unlocking, rather they should have mail us unlock code like motorola does.
Apcoolboy said:
Well, we build many hypothesis how Xiaomi unlock phones. But it is fact that Xiaomi software sucks at unlocking, rather they should have mail us unlock code like motorola does.
Click to expand...
Click to collapse
Indeed or they should unlock it prior buying like they did earlier.
T3h said:
Yes the MIUI version matches in the forum too.
I've been checking this from few weeks.
Click to expand...
Click to collapse
Please try this which I have tried and got success
rajumack07 said:
Please try this which I have tried and got success
Click to expand...
Click to collapse
He mentioned he had to add phone number in forum same as in phone setting. Also match device model on forum settings. That is true, what I try to point out in this post is you need all information perfectly matches between miui server and your device (some unmatched information like miui version, phone no etc works for some people and some not work). In a nutshell, try to match all information saved on device to miui forum settings. It should works.
Apcoolboy said:
He mentioned he had to add phone number in forum same as in phone setting. Also match device model on forum settings. That is true, what I try to point out in this post is you need all information perfectly matches between miui server and your device (some unmatched information like miui version, phone no etc works for some people and some not work). In a nutshell, try to match all information saved on device to miui forum settings. It should works.
Click to expand...
Click to collapse
I think we should try at max. those steps which we have control like flashing global dev, having only one sim also in the 1st slot for which we've got permission etc. just to maximize your chances of identifying yourself in the server.
superboy123 said:
Every time I brick my phone by messing up partitions and I will fire up miflash and flash through edl. I will reboot the phone and will go to fastboot mode directly after flashing. I will launch miunlock tool and clock unlock, even though I didn't even boot up the phone, it will unlock the bootloader. I did this more than 10 times and worked fine. No need to remove app lock, fingerprint, etc. The OEM unlock option in developer options should be enabled to unlock. I think the mi credentials are stored permanently in some place. I am trying to figure out that place where it stored the credentials.
Click to expand...
Click to collapse
anyone with a kate tried this?
What happens after getting stuck at 50% ?
Does the phone dont boot anymore ? Or can i reboot it to system just like it was before ?
Sent from my Redmi Note 3 using XDA-Developers mobile app
a.broken.star said:
What happens after getting stuck at 50% ?
Does the phone dont boot anymore ? Or can i reboot it to system just like it was before ?
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
No, nothing happens. The bootloader just remains locked, that's it. The phone continues to function as before.
I recently received my black Xiaomi Mi Max 2 Global Version and wished to unlock the bootloader in order to create a Custom firmware (which will be based around Stock, but have a lower DPI and use the Google Now launcher to have 7 icons in the dock & a 6x6 icon grid elsewhere).
During the unlock process I got stuck within the 'Add account and device' in Developer Options, with the error code 86006 being displayed. The solution to this issue is to change from the Stable MIUI 8 to the latest Developer ROM - once this is flashed, the device will register with no error messages.
An overview of the process is therefore:
1. Flash the latest Development ROM on the phone, via the Updater app
2. Register for a Mi account, if you do not have one, and log into the phone with this account.
3. Request the Unlock privilege for your Mi account
4. Enroll the device for an Unlock in Developer Options
5. Wait 72 hours
6. Unlock the bootloader with the Windows Mi Flash Unlock tool.
Mi Account
The Unlock tool will require that the phone is logged into the same Xiaomi account in order for the unlock process to be successful, so ensure you have set yourself up with a Mi account and signed into the phone using this account.
I tend to ensure I have posted a few items on the MIUI forum before I make a request as, during the request process, it states that they will take the activity of your account into consideration when they are making the decision to grant you the unlock privilege.
If the request is denied, you have to wait 30 days to re-apply, so better to be safe than sorry!
Request the Unlock privilege
The first thing you will need to do is to make sure you have applied for Unlock rights for your Mi account. This can be done here:
Mi Unlock
Try to make the given reason for unlocking something specific, rather than generic, as your request is more likely to be granted this way.
The time between application and hearing back from the MIUI team seems to vary. The last time I applied the request was granted after just a few minutes, but previous applications have taken days!
Setting up the phone
Before you can successfully unlock the phone using the unlocking tool you will need to enrol the phone into the scheme, which is performed in Developer Options.
1. Go to Settings / About Phone
2. Press MIUI version 7 times to enable Developer options
3. Go to Settings / Additional Settings / Developer options
4. Click on Mi Unlock status
5. Click on Add account and device
Note that if you get an error code of 86006 then download and flash the latest Developer ROM through the built-in Updater app:
Xiaomi ROM Download
Three Day Wait
After enrolling the phone, Xiaomi require that 72 hours (3 days) must elapse before the bootloader can be unlocked with Xiaomi's MiFlash Unlock Tool.
If you attempt to unlock during this period, the process will get to 99% before displaying an error message requesting you wait 72 hours.
Unlocking the bootloader
Once the phone is enrolled and 72 hours have passed, you can use the Unlock tool.
This can be downloaded from the MIUI Unlock site once your unlock request has been granted:
Mi Unlock
On a Windows PC, extract the zip file to a temporary folder and run the miflash_unlock.exe tool.
Log on using the same Mi account that you have signed into the device with and follow the on screen prompts, which involve booting the phone into Fastboot with Power and Volume Down.
Not working for me
Tried everything as mentioned above still not able to unlock the bootloader. It gets stuck at 99% and I am not able to bind my account in phone in developer options.
I get error 86012 and something in Chinese.
On latest developer ROM
Did you unlock it yourself?I got this error from tool. Couldn't find a way to make request and looped back to unlocker page always.View attachment 4237380
mwarner said:
I recently received my black Xiaomi Mi Max 2 Global Version and wished to unlock the bootloader in order to create a Custom firmware (which will be based around Stock, but have a lower DPI and use the Google Now launcher to have 7 icons in the dock & a 6x6 icon grid elsewhere).
During the unlock process I got stuck within the 'Add account and device' in Developer Options, with the error code 86006 being displayed. The solution to this issue is to change from the Stable MIUI 8 to the latest Developer ROM - once this is flashed, the device will register with no error messages.
An overview of the process is therefore:
1. Flash the latest Development ROM on the phone, via the Updater app
2. Register for a Mi account, if you do not have one, and log into the phone with this account.
3. Request the Unlock privilege for your Mi account
4. Enroll the device for an Unlock in Developer Options
5. Wait 72 hours
6. Unlock the bootloader with the Windows Mi Flash Unlock tool.
Mi Account
The Unlock tool will require that the phone is logged into the same Xiaomi account in order for the unlock process to be successful, so ensure you have set yourself up with a Mi account and signed into the phone using this account.
I tend to ensure I have posted a few items on the MIUI forum before I make a request as, during the request process, it states that they will take the activity of your account into consideration when they are making the decision to grant you the unlock privilege.
If the request is denied, you have to wait 30 days to re-apply, so better to be safe than sorry!
Request the Unlock privilege
The first thing you will need to do is to make sure you have applied for Unlock rights for your Mi account. This can be done here:
Mi Unlock
Try to make the given reason for unlocking something specific, rather than generic, as your request is more likely to be granted this way.
The time between application and hearing back from the MIUI team seems to vary. The last time I applied the request was granted after just a few minutes, but previous applications have taken days!
Setting up the phone
Before you can successfully unlock the phone using the unlocking tool you will need to enrol the phone into the scheme, which is performed in Developer Options.
1. Go to Settings / About Phone
2. Press MIUI version 7 times to enable Developer options
3. Go to Settings / Additional Settings / Developer options
4. Click on Mi Unlock status
5. Click on Add account and device
Note that if you get an error code of 86006 then download and flash the latest Developer ROM through the built-in Updater app:
Xiaomi ROM Download
Three Day Wait
After enrolling the phone, Xiaomi require that 72 hours (3 days) must elapse before the bootloader can be unlocked with Xiaomi's MiFlash Unlock Tool.
If you attempt to unlock during this period, the process will get to 99% before displaying an error message requesting you wait 72 hours.
Unlocking the bootloader
Once the phone is enrolled and 72 hours have passed, you can use the Unlock tool.
This can be downloaded from the MIUI Unlock site once your unlock request has been granted:
Mi Unlock
On a Windows PC, extract the zip file to a temporary folder and run the miflash_unlock.exe tool.
Log on using the same Mi account that you have signed into the device with and follow the on screen prompts, which involve booting the phone into Fastboot with Power and Volume Down.
Click to expand...
Click to collapse
Some advices about same issue (Error 86006) say that after successful unlock request sending to Xiaomi (and before unlock process itself) the previous stable (not developpers!) Global ROM can be re-flashed in Mi Max 2.
So, that way phone BL can be unlocked with stable Global ROM and with unlock rights received from Xiaomi using developpers ROM. Is that true?
Another question: there is an advice (in MIUI flashing guide) to use fastboot (not recovery) flashings when flashing developpers ROM on stable ROM and vice versa, as recovery flashings may cause flashing failures . Any comment?
mwarner said:
Unlocking the bootloader
Once the phone is enrolled and 72 hours have passed, you can use the Unlock tool.
This can be downloaded from the MIUI Unlock site once your unlock request has been granted:
Mi Unlock
On a Windows PC, extract the zip file to a temporary folder and run the miflash_unlock.exe tool.
Log on using the same Mi account that you have signed into the device with and follow the on screen prompts, which involve booting the phone into Fastboot with Power and Volume Down.
Click to expand...
Click to collapse
Hey! I've followed your guide, and at this part where I try unlocking the device using the Mi Flash tool, I'm stuck at 99% & and error comes up saying that "Current Account is not Bound to this device"
But I've signed into the same account on both the PC & the device. Also I've added the account to the device from the "Mi Unlock Status" option.
Kindly help us out..
Thanks in advvance Mate
@V_v3k Same issue here. Any luck?
V_v3k said:
Hey! I've followed your guide, and at this part where I try unlocking the device using the Mi Flash tool, I'm stuck at 99% & and error comes up saying that "Current Account is not Bound to this device"
But I've signed into the same account on both the PC & the device. Also I've added the account to the device from the "Mi Unlock Status" option.
Kindly help us out..
Thanks in advvance Mate
Click to expand...
Click to collapse
unlocked my max 2 without hitches whatsoever. the device has global stable rom 8.5.6.0.
RAMBO29 said:
@V_v3k Same issue here. Any luck?
Click to expand...
Click to collapse
No luck mate... :crying:
It's really annoying... They could have made a more simple procedure like sending the device's serial/IMEI & attaching it to account immediately, so that unlocking could be done immediately. But this is like, insane...
V_v3k said:
Hey! I've followed your guide, and at this part where I try unlocking the device using the Mi Flash tool, I'm stuck at 99% & and error comes up saying that "Current Account is not Bound to this device"
But I've signed into the same account on both the PC & the device. Also I've added the account to the device from the "Mi Unlock Status" option.
Kindly help us out..
Thanks in advvance Mate
Click to expand...
Click to collapse
+1
so pros, any luck with bootloader unlocking? I'm being haunted by this error as well "Current Account is not Bound to this device"
do we need to create new mi account and then bind & unlock? I was using redmi note 3 before but that device no more listed in i.mi.com.
spikywits said:
so pros, any luck with bootloader unlocking? I'm being haunted by this error as well "Current Account is not Bound to this device"
do we need to create new mi account and then bind & unlock? I was using redmi note 3 before but that device no more listed in i.mi.com.
Click to expand...
Click to collapse
I've decided to wait for a week or so before trying. I got really mad... ?
V_v3k said:
I've decided to wait for a week or so before trying. I got really mad...
Click to expand...
Click to collapse
you're right. It took some time and I managed to unlock the device today. Happy wait :victory:
spikywits said:
you're right. It took some time and I managed to unlock the device today. Happy wait :victory:
Click to expand...
Click to collapse
Congrats mate...
should i be on developer rom only to have unlock bootloader ? or even on stable rom it work ?
kannan96 said:
should i be on developer rom only to have unlock bootloader ? or even on stable rom it work ?
Click to expand...
Click to collapse
I have not managed to unlock the bootloader on a globally stable ROM. I managed to get a global developer rom without problems waiting 72 hours after logging in. Everything went smoothly.
razjaren said:
I have not managed to unlock the bootloader on a globally stable ROM. I managed to get a global developer rom without problems waiting 72 hours after logging in. Everything went smoothly.
Click to expand...
Click to collapse
thanks for the instant reply
does xposed module works ? xposed by purifyos team on developer rom ?
In developer options after you enable OEM unlock bootloader option, you have to bind the account in (Mi Unlock status). Remove Mi account from your device, then come here and then add the account, but ensure that you login with account id(not email and phone). After that leave it for 7 days to be safe and it can be unlocked.Phew...
Got mine this way, finally.
spikywits said:
so pros, any luck with bootloader unlocking? I'm being haunted by this error as well "Current Account is not Bound to this device"
do we need to create new mi account and then bind & unlock? I was using redmi note 3 before but that device no more listed in i.mi.com.
Click to expand...
Click to collapse
Buzz off 86006
There is no way that this can get solved.
Tried Developer Rom option, didn't work.
Tried Login with User ID, didn't work.
Just nothing works
any other way I can remove this error! It hurts from the Root lover point of view
When I apply to unlock this came . What to do?
So ,I flashed miui9 via updater app and applied via stock browser , I am able to apply for unlocking now.
jordann_f1 said:
There is no way that this can get solved.
Tried Developer Rom option, didn't work.
Tried Login with User ID, didn't work.
Just nothing works
Click to expand...
Click to collapse
The process can b e a realy tricky one indeed.
Whats your rom?
Ever had another xiaomi device unlock request?
jordann_f1 said:
any other way I can remove this error! It hurts from the Root lover point of view
Click to expand...
Click to collapse
I suceeded in unlocking bootloader but it was difficult, i must say.
Sorry for my bad english, its not my native language.
I just ordered a Mediapad M3 8.4 and I should receive it in a couple of days. I plan to update it to whatever is the latest firmware, add TWRP and also root it. Are there any first steps or gotcha's I should be aware of? For example, should I root first or apply updates first? The reason I ask is that I've had some devices that could be rooted in one version but could not be rooted after updating the bootloader.
Any suggestions appreciated.
Firstly check what hardware oem location the tablet has as this effects it. To root or change that you need to get the bootloader unlocked. This is done via a code request website on the Huawei site. After that you can go TWRP, backup and so on.
Check the oeminfo/country ID and flash the appropriate rom for that if you want. If you want to change region, the partition oem files are online and can be done via twrp command line.
Thanks, that's what I needed to know!
Just for the sake of other people who may just be starting out with this tablet, it turns out that it does matter whether you update first or unlock first. You will not be able to get a bootloader unlock code from the Huawei website after you upgrade to EMUI 5.0, so if you plan to root your tablet, make sure you unlock the bootloader before you upgrade. Otherwise, you will have to downgrade to an earlier version.
woody1 said:
Just for the sake of other people who may just be starting out with this tablet, it turns out that it does matter whether you update first or unlock first. You will not be able to get a bootloader unlock code from the Huawei website after you upgrade to EMUI 5.0, so if you plan to root your tablet, make sure you unlock the bootloader before you upgrade. Otherwise, you will have to downgrade to an earlier version.
Click to expand...
Click to collapse
I upgraded first and still got a code. I have the LTE version. In order to get the code, I had to choose "phone" and not "tablet". It could be that with wifi-only version it won't work because you can't provide the IMEI.
Here are some notes from my experience with starting out on my new BTV-DL09 (4G version, bought in Europe):
1) I upgraded the brand new tablet to EMUI 5.0. At the end of the upgrade, I got an error message. But after reboot it seemed to work fine. Bluetooth does not work with EMUI 5.0 but I don't need Bluetooth on it.
2) I unlocked the bootloader. Had to choose "phone" on the Huawei site to get the code because there was no matching tablet with EMUI 5.
3) Installed Magisk 14 using twrp.
4) Systemless hosts doesn't work in Magisk because /system/etc/hosts is a symlink to /vendor/etc/hosts
5) remounted /system as rw, deleted /system/etc/hosts, copied /vendor/etc/hosts to /system/etc/hosts, remounted at ro
6) disabled magisk systemless hosts, re-enabled it, installed adblock hosts module, everything has worked since then.
7) changed dpi to 360 or so. 350 was nice because it made it look exactly like my Galaxy Tab S, but unfortunately the settings app didn't display the left side anymore. So I have larger icons now, but things still run in tablet mode.
If there is ever any update coming for this, I hope it will work if I undo my /system modification (put the symlink back)
I have to say, so far I'm very satisfied with this tablet! It runs super smooth, has great battery life, display, and the speakers sound great. Out of the box it's barely usable and very frustrating to use - I would not really recommend it to anyone if they don't plan on rooting it.
EDIT: just read I can get bluetooth working by upgrading first to B010 then B303, so I guess I gotta start all over again Thanks @30adi for that post: https://forum.xda-developers.com/showpost.php?p=73470572&postcount=380
adibadi said:
2) I unlocked the bootloader. Had to choose "phone" on the Huawei site to get the code because there was no matching tablet with EMUI 5.
Click to expand...
Click to collapse
It has been a while since i did unlocking. But is there a phone model to use when choosing "phone"?
fallen_13 said:
It has been a while since i did unlocking. But is there a phone model to use when choosing "phone"?
Click to expand...
Click to collapse
If you choose "Since EMUI 5.0" you have the following options:
Smartphone (not possible to change this)
Product Serial number
Product IMEI or MEID
Product ID
If you choose "Before EMUI 5.0" you have these options:
Smartphone (can change to Tablet 3G or to Tablet wifi)
Product Model
Product Serial number
Product IMEI or MEID
Product ID
So you don't need to provide the product model when choosing "since EMUI 5.0", but I'm not sure if they will accept one with no IMEI, as in the wifi-only tablet case.
adibadi said:
If you choose "Since EMUI 5.0" you have the following options:
Smartphone (not possible to change this)
Product Serial number
Product IMEI or MEID
Product ID
If you choose "Before EMUI 5.0" you have these options:
Smartphone (can change to Tablet 3G or to Tablet wifi)
Product Model
Product Serial number
Product IMEI or MEID
Product ID
So you don't need to provide the product model when choosing "since EMUI 5.0", but I'm not sure if they will accept one with no IMEI, as in the wifi-only tablet case.
Click to expand...
Click to collapse
Ah ok. I unlocked mine back before EMUI 5 was released. So i had to choose the "Product model" for Mediapad M3. Didn't know that the generic "smartphone" would just do for unlocking EMUI5. That's very helpful and does away with the need to do downgrading. Thank you.
adibadi said:
EDIT: just read I can get bluetooth working by upgrading first to B010 then B303, so I guess I gotta start all over again
Click to expand...
Click to collapse
So after downgrading back to Marshmallow, I got an update message which sent me back to B303 with an OTA, and bluetooth works now. I didn't have to go to B010 then to B303.
I'm not sure what was up with my original version which came preloaded on the tablet, but it didn't show this update - it told me that I was on on the latest version. The update screen appeared at first boot even before I could sign in to gmail. It's called OTA-BTV-DL09C100B009_B303
OK, I have the wifi only tablet, so maybe the unlock will work with the LTE version, but not with wifi-only after an upgrade to EMUI 5.0. Has anybody been successful in unlocking a wifi-only tablet which was already on EMUI 5.0? (BTW, Bluetooth works fine for me on Android 7.)
So your recommendation is to Unlock bootloader before upgrade? Does the OTA upgrade work afterward or can you do it through TWRP?
ScruffMcG said:
So your recommendation is to Unlock bootloader before upgrade? Does the OTA upgrade work afterward or can you do it through TWRP?
Click to expand...
Click to collapse
From what other people have said, the OTA will work while rooted, but I haven't tried it myself yet.
Didn't you say you upgrade to 7.0? Or did you re-lock bootloader to do that (or just stay on stock bootloader?). Just ordered so I have a couple days to figure the process out, but want to make sure I don't upgrade if I will be losing the ability to root afterward.
ScruffMcG said:
Didn't you say you upgrade to 7.0? Or did you re-lock bootloader to do that (or just stay on stock bootloader?). Just ordered so I have a couple days to figure the process out, but want to make sure I don't upgrade if I will be losing the ability to root afterward.
Click to expand...
Click to collapse
Ok, here's what happened to me:
I upgraded to EMUI 5.0/Android 7. Then, I went to the Huawei website to get the bootloader code. I was not able to get the bootloader code, because it appears that the website is not properly set up to give a bootloader unlock code for a tablet with EMUI 5.0 or greater, at least not for the wifi-only version. I'm guessing this is just a problem with the website not being updated to support the latest version.
So far, I'm trying to figure out if there's an option to get the bootloader code without downgrading first. If I can't find another way, I will downgrade, then get the bootloader code, then upgrade back to Android 7. As far as I know, there is not a problem upgrading after you've unlocked the bootloader, but I haven't personally gotten to that point.
woody1 said:
Ok, here's what happened to me:
I upgraded to EMUI 5.0/Android 7. Then, I went to the Huawei website to get the bootloader code. I was not able to get the bootloader code, because it appears that the website is not properly set up to give a bootloader unlock code for a tablet with EMUI 5.0 or greater, at least not for the wifi-only version. I'm guessing this is just a problem with the website not being updated to support the latest version.
So far, I'm trying to figure out if there's an option to get the bootloader code without downgrading first. If I can't find another way, I will downgrade, then get the bootloader code, then upgrade back to Android 7. As far as I know, there is not a problem upgrading after you've unlocked the bootloader, but I haven't personally gotten to that point.
Click to expand...
Click to collapse
I thought that the unlock code isn't tied to the emui version, but to the hardware, but I could be wrong. Is the requested data for 4.x wifi-only not available in your 5.0 emui?
adibadi said:
I thought that the unlock code isn't tied to the emui version, but to the hardware, but I could be wrong. Is the requested data for 4.x wifi-only not available in your 5.0 emui?
Click to expand...
Click to collapse
No the data is all available. The problem is that the Huawei website is not set up to provide a code for a wifi-only tablet that's on EMUI 5.0. It appears to be purely a problem with the website, not an issue with the code itself.
woody1 said:
No the data is all available. The problem is that the Huawei website is not set up to provide a code for a wifi-only tablet that's on EMUI 5.0. It appears to be purely a problem with the website, not an issue with the code itself.
Click to expand...
Click to collapse
What I meant was to just select emui 4 on the website.
Yes, it seems like that should work, but when I put in my data, I get a message saying that something is incorrect. Now that you mention it, I don't know how Huawei could know which version is installed. I wonder if the Product Number changes when you upgrade the EMUI version? Maybe that's the problem. Does anybody know about that?
woody1 said:
Yes, it seems like that should work, but when I put in my data, I get a message saying that something is incorrect. Now that you mention it, I don't know how Huawei could know which version is installed. I wonder if the Product Number changes when you upgrade the EMUI version? Maybe that's the problem. Does anybody know about that?
Click to expand...
Click to collapse
Not sure if it's the same thing, but I had to try a few times until the captcha worked, that thing was impossible to read. The error message said nothing about captcha, everything else was actually correct but it told me to check my serial numbers and stuff.
adibadi said:
Not sure if it's the same thing, but I had to try a few times until the captcha worked, that thing was impossible to read. The error message said nothing about captcha, everything else was actually correct but it told me to check my serial numbers and stuff.
Click to expand...
Click to collapse
If I put in a bad capcha, I get a message saying the capcha is wrong. If I put in the right capcha, I get a message saying "check your information" or something like that. Looks like the problem is not the capcha, but something else.
Oh boy, Huawei trying to screw us all over. Magisk apparently is no longer working, so no root for once a new OTA installs for Huawei devices.
https://forum.xda-developers.com/showpost.php?p=77415750&postcount=6555
https://forum.xda-developers.com/showpost.php?p=77418253&postcount=6557
New issue on Huawei Phones - Mate 10, Mate 10 Pro, P9 - Huawei roll out a new OTA called: "patch01". In the changelog is some fix mentioned (example: mms...) but the main patch is to disable the possibility of Root.
That means: if someone flash Magisk with TWRP, or flash patched_boot.img to ramdisk and reboot the phone, Phone get stuck on the splash screen: "Your device cannot be trusted..."
Only flashing back the original Huawei ramdisk.img helps to boot again to system. But no Root with Magisk is anymore possible.
Downgrade helps (if available, because for some Phones like Mate 10 it is dangerous to downgrade, if the Downgrade Firmware has another Xloader.img... but this is another story)
→ So, for Users of Huawei Phones it is better not to install OTA with Patch01 and disable Systemupdate in /system/app/HwOUC - rename HwOUC.apk to HwOUC.bak
I attach here the patch from Huawei for P9 - may you take a look, thanks
Click to expand...
Click to collapse
I have dm-verity always off (not enabled in Magisk Manager) and I have also avb disabled in /vendor/etc/fstab.ext4.hi.... and fstab.f2fs.hi.... (I have different Huawei devices)
To make the issue clearer here is another summary:
I made a Rebrand Thread for Huawei P9-EVA here: https://forum.xda-developers.com/p9/...9-eva-t3820849
The main reason for this is to allow users to unofficially update their device to Android 8 Oreo. Huawei has rolled out the Oreo OTA update in China, but has no plans to release this update outside of China. Although Oreo runs much better on the devices.
To make this possible, root is an important part, otherwise the mobile network will not work on the rebranded devices. Many users were very happy because they can now also use Oreo Treble Roms by the Open Kirin Team.
Okay → Devices rebranded to EVA-AL10 and updated to the official Oreo Firmware b528. With some modification everything is working fine.
→ Yesterday OTA Patch01 was available. I flashed the unmodified original Huawei ramdisk.img, uninstalled Magisk Manager and flashed the original EMUI Recovery. Then I agreed to the OTA update. The update was succesful installed.
After that I flashed the Magisk patched_ramdisk.img again, but the phone did not boot → it booted only with original b528 ramdisk.img
We were three people who tested it. Me and @dkionline and @zgfg We tried everything that came to our mind. → flashing first original ramdisk and kernel.img and booted to system. Then flashing patched ramdisk.img b528 with Magisk 16, Magisk 16.7 with flag "force encryption" and without "force encryption" (related to - if device is with data encrypted or data decrypted)
Flashing TWRP was not a problem, and together with the original Huawei ramdisk.img phone was able to start to system. To get Root again, we must downgraded to b528 without this Patch.
→ The Patch includes a Fix for mms and Fix for gaming (changes a Line in a local.prop) and it includes also a Kernel patch.
Looking back, we should have tested a little more. What we did not test → making dd with TWRP from ramdisk.img after the OTA Patch and then patch the "dump" ramdisk.img with Magisk. → Maybe that would have worked - we do not know it now and I do not feel like reproducing it again. But perhaps @zgfg can try this in a view days (he did not downgrade yet, because he is outside).
With this last test we could say it for sure, if the Kernel patch includes something to make Huawei Phones unbootable together with Magisk.
And coincidentally I read then in the Mate 10 forum that there also a user (with ALP-L29c636) got an OTA with a Patch01 and similar problem " I got a patch notification so I download it, rebooted and the patch installed (phone booted and I checked version and it was patch1). Cool. So then I rooted using magisk and phone was soft bricked..." : https://forum.xda-developers.com/sho...&postcount=256
My first thought was simple, Huawei is now trying to prevent root with this patch01 and much confirms this theory....
→ Bootloader Unlock Site closed
→ TrustSpace is a new App in system which definitely check and disable Root (we had this app disabled and two of us has it deleted in system)
→ Downgrade with unofficial methods become danger for hardbrick, because of two different Xloader.img in the Firmware (Mate 10)
Click to expand...
Click to collapse
Big thanks to @Tecalote for bringing this to my attention.
Not sure if this will hit the Honor 7x, it probably will. I am prepared for the worst, really hate it when Huawei does this.
Its looking like Huawei just shot themselves in the foot on this if its infact the case, there is nothing worse then developers getting middle fingered and scorned. If you think a Developer using a fork (github joke) is dangerous just wait till they nuke that commit/submit button! This is not going to bold well for honor/huawei
As i have already stated if this turns out to be Honor/Huawei out right middle fingering devs and users choice I will be looking for another phone pronto.
Click to expand...
Click to collapse
Holy shiet
Yes, i can confirm this, please do not flash that Patch01, it will make your device stuck on boot message after you flash magisk.
I'm on Huawei Nova 2s.
How to root in Patch01 update : https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
heindrix said:
How to root in Patch01 update : https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
Click to expand...
Click to collapse
How can you tell if you've gotten the Patch01 update?
My phone is currently BND-L24 8.0.0.341(C567), with a July 1 2018 Android security patch.
For the link you posted im assuming id have to use "B) If the TWRP for your device has not access to encrypted /data then you can do the following:"
The site here http://pro-teammt.ru/firmware-database/?firmware_model= that has firmware doesn't seem to show 8.0.0.341? Should I use BND-L24AC567B330 (8.0.0.330) because it seems to be an update from May, and when I google my build number Huawei tweeted that it was a May security update? Or will using that brick my phone? Of the availible BND-L24 firmwares, which one should I use?
Also do I already need TWRP installed? can I do that on my unrooted device?
battleforce said:
How can you tell if you've gotten the Patch01 update?
My phone is currently BND-L24 8.0.0.341(C567), with a July 1 2018 Android security patch.
For the link you posted im assuming id have to use "B) If the TWRP for your device has not access to encrypted /data then you can do the following:"
The site here http://pro-teammt.ru/firmware-database/?firmware_model= that has firmware doesn't seem to show 8.0.0.341? Should I use BND-L24AC567B330 (8.0.0.330) because it seems to be an update from May, and when I google my build number Huawei tweeted that it was a May security update? Or will using that brick my phone? Of the availible BND-L24 firmwares, which one should I use?
Also do I already need TWRP installed? can I do that on my unrooted device?
Click to expand...
Click to collapse
You can see it in System->About.
See at Build Number section, it will be printed XXX-XXXX X.X.X.XXX(XXXPatch01).
You can use Huawei Firmware Finder : https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Go to Common Base menu, and set (click gear button) this value (G:2649 g:1699), that value is identifier for Honor 7x.
And type L24 in the search box.
After that, click on search button (magnifier glass button), you'll see all available updates for Honor 7x.
And there you go, all of firmware lists for Honor 7x L24.
I made some screenshot for you.
Enjoy.
I would do some tests with TWRP/OF and maybe root it. Few questions:
a) Can I lock the bootloader once I decided to go with stock firmware?
b) do I need a real email for the MI account (that seems to be required to unlock)
Is this the right way to go?
How to Unlock Bootloader on Any Xiaomi Devices Using Mi Flash Tool
Why We have to Unlock Bootloader on Any Xiaomi Device? Basically, you need the Mi Flash Unlock Toolkit and few other things before you can start doing it. This particular method works on devices such as Xiaomi Mi 4C, Xiaomi Redmi Note 4, Xiaomi Mi 5C, Xiaomi Mi 4S, Redmi Note 3, Mi Note Pro, and...
www.getdroidtips.com
How to Install TWRP Recovery on Xiaomi Poco M3 and Root it
On this page, we will guide you to install the TWRP Recovery on Xiaomi Poco M3. This guide contains both the written instruction and a vi
www.getdroidtips.com
starbright_ said:
Can I lock the bootloader once I decided to go with stock firmware?
Click to expand...
Click to collapse
Yes, I have done it. I unlocked the bootloader to install Magisk, but it was too difficult to update the phone with Magisk installed, so I used Mi Flash Tool to reflash the stock ROM and locked the bootloader.
(When the bootloader is locked, it will only boot if it the ROM is fully stock, do not lock the bootloader without reflashing the stock ROM.)
starbright_ said:
b) do I need a real email for the MI account (that seems to be required to unlock)
Click to expand...
Click to collapse
These are the steps for unlocking the bootloader.
1. You need to have a real email and a real phone number to create a Mi account.
2. Login the Mi account in the phone (with email address), go to settings, about phone, and tap MIUI Version (For POCO) 7 times to enable developer options.
3. In settings, go to more settings, developer options, and at there you can bind the Mi account to this phone (Mi Unlock status), you will need a real sim card with mobile data to do it.
4. After binding the Mi account to the phone, you need to wait for 15 days before you can unlock the bootloader. (7 days if you have enabled find device.)
5. Download Mi Unlock on your PC, and reboot the phone into fastboot mode (can be done with adb shell commands, or by long pressing the power and volume down buttons at the same time), unlock the phone with Mi Unlock, all data will be erased after unlocking the bootloader.
(If you have not waited for 15 days, or 7 days, during the unlocking process, Mi Unlock will tell you to wait. Unlocking the bootloader could be dangerous, it could brick the phone if something goes wrong, please be careful, backup your data, and make sure you know how to use Mi Flash to install the stock ROM if the phone gets soft bricked.)
Thank you - and for the warning about re-lock.
I need a phone number for unlock? And what is needed to lock - the same email and phone-nr? Or can this be done with a tip? Waiting for 15days is strange. A lot of time to think it over
starbright_ said:
I need a phone number for unlock? And what is needed to lock - the same email and phone-nr?
Click to expand...
Click to collapse
You need a phone number (sim card with mobile data) to create the Mi account for unlocking and binding. To lock the bootloader after unlocking, an account is not required, you only need to choose "clean all and lock" in Mi Flash Tool.
starbright_ said:
Waiting for 15days is strange.
Click to expand...
Click to collapse
There is no way to unlock it earlier using the official way.
It is because in China, Xiaomi phones did not have locked bootloader, unofficial sellers would install modified ROMs (with a lot of bloatware or malware) on Xiaomi phones, and sell those phones to people who did not know the ROM was modified.
(Source: China Xiaomi Community)
it's 7 days to wait.
Why did you find TWRP hard to install ?
Noru29 said:
it's 7 days to wait.
Click to expand...
Click to collapse
I was told to wait for 15 days (360 hours) when I used Mi Unlock to unlock my M3.
OK... it was 168 hours for both of my phones.
Is your Mi account fully secured (100 points) and "Find device" option fully fonctionnal ?
Noru29 said:
OK... it was 168 hours for both of my phones.
Is your Mi account fully secured (100 points) and "Find device" option fully fonctionnal ?
Click to expand...
Click to collapse
My Mi account has 100 points for security, but I did not enable find device for my M3.
It's important and doing it without Wifi activated, just with data.
cbw said:
Yes, I have done it. I unlocked the bootloader to install Magisk, but it was too difficult to update the phone with Magisk installed, so I used Mi Flash Tool to reflash the stock ROM and locked the bootloader.
(When the bootloader is locked, it will only boot if it the ROM is fully stock, do not lock the bootloader without reflashing the stock ROM.)
These are the steps for unlocking the bootloader.
1. You need to have a real email and a real phone number to create a Mi account.
2. Login the Mi account in the phone (with email address), go to settings, about phone, and tap MIUI Version (For POCO) 7 times to enable developer options.
3. In settings, go to more settings, developer options, and at there you can bind the Mi account to this phone (Mi Unlock status), you will need a real sim card with mobile data to do it.
4. After binding the Mi account to the phone, you need to wait for 15 days before you can unlock the bootloader.
5. Download Mi Unlock on your PC, and reboot the phone into fastboot mode (can be done with adb shell commands, or by long pressing the power and volume down buttons at the same time), unlock the phone with Mi Unlock, all data will be erased after unlocking the bootloader.
(If you have not waited for 15 days, during the unlocking process, Mi Unlock will tell you to wait. Unlocking the bootloader could be dangerous, it could brick the phone if something goes wrong, please be careful, backup your data, and make sure you know how to use Mi Flash to install the stock ROM if the phone gets soft bricked.)
Click to expand...
Click to collapse
Hey!! After unlocking bootloader, the Play Protect certification (Device is certified) persists or not??
If no, can it be again certified after relocking bootloader??
(Xiaomi ft. Redmi Note 10 series)
PJB1906 said:
the Play Protect certification (Device is certified) persists or not
Click to expand...
Click to collapse
It will become not certified with unlocked bootloader if you are using official ROM, and after relocking bootloader it will be certified.
But if you want to keep your bootloader unlocked and still want the phone to be certified, you can use the Xiaomi.eu custom ROM, or install Magisk in the official ROM and enable MagiskHide.
cbw said:
It will become not certified with unlocked bootloader if you are using official ROM, and after relocking bootloader it will be certified.
But if you want to keep your bootloader unlocked and still want the phone to be certified, you can use the Xiaomi.eu custom ROM, or install Magisk in the official ROM and enable MagiskHide.
Click to expand...
Click to collapse
Actually I want to install the Indonesian ROM, flashing the stock (Indian) ROM.
Then what to do so that there will not be any issue?? Plz. help.
PJB1906 said:
Actually I want to install the Indonesian ROM,
Click to expand...
Click to collapse
If you are installing the official fastboot ROM of a different region, you should be able to relock bootloader and the phone will still work. (As long as it is not the China version of hardware.)
Just use the tgz fastboot ROM file, extract it into a folder, and select that folder in Mi Flash, choose clean all and lock, and start flashing. (Make sure bootloader is unlocked before flashing.)
I have installed Taiwan ROM on the global version of both POCO M3 and Redmi 9T, after relocking bootloader, the phones still work without software problems.
cbw said:
If you are installing the official fastboot ROM of a different region, you should be able to relock bootloader and the phone will still work. (As long as it is not the China version of hardware.)
Just use the tgz fastboot ROM file, extract it into a folder, and select that folder in Mi Flash, choose clean all and lock, and start flashing. (Make sure bootloader is unlocked before flashing.)
I have installed Taiwan ROM on the global version of both POCO M3 and Redmi 9T, after relocking bootloader, the phones still work without software problems.
Click to expand...
Click to collapse
Have you faced any performance issue or some sensor not working issue or any other??
BTW what is tgz?
PJB1906 said:
Have you faced any performance issue or some sensor not working issue or any other??
BTW what is tgz?
Click to expand...
Click to collapse
No, the phone works well, all sensors still work, and with the MIUI dialer in Taiwan ROM, now I also have an option to record calls automatically.
It just feels the same as a phone that is from Taiwan.
tgz is the format of the compressed fastboot ROM file.