Huami started to lock the bootloader of the Amazfit watch in their official release 1.2.13 and 1.3.2b onwards.
If you want to keep the possibilty to flash custom software on your watch, DO NOT UPGRADE TO THESE VERSIONS. You will not be able to flash any other firmware afterwards.
PACEfied firmware is safe, and does NOT lock your bootloader.
UPDATE 14.07.17:
We have heard several times now via inofficial sources that Huami is working on an official bootloader unlocking service. So far, we, however, have no official information here.
On the other hand, Olivier (french developer on xda) has spent a significant amount of time to understand the unlocking process and we have succeeded to successfully unlock two watches. We are currently in the process of setting up a (free) unlocking web service, allowing individual xda users to unlock their watches for private usage (and accepting loss of warranty from Huami).
In case, Huami may ever come out with their service, we will stop our service, as we do not want to compete with Huami here, just filling the gap if Huami doesn't move forward with their unlocking service.
Please give us some time (we expect 2-3 weeks) to setup the unlock service.
UPDATE 7.08.17:
The unlock service is live now. Head over to https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unlock-bootloader-warning-void-t3654011, if you want your bootloader unlocked!
Fastboot oem unlock
And the command to unlock the bootloader does not work?*
Code:
Fastboot oem unlock
scrubber said:
And the command to unlock the bootloader does not work?*
Code:
Fastboot oem unlock
Click to expand...
Click to collapse
No, neither does
Code:
fastboot flashing unlock
I wouldn't expect Huami to put efforts into locking the bootloader and at the same time making it that easy to unlock it again. This is no coincidence. They saw our work and reacted. That's what happened. Very sad
Neuer_User said:
No, neither does
Code:
fastboot flashing unlock
I wouldn't expect Huami to put efforts into locking the bootloader and at the same time making it that easy to unlock it again. This is no coincidence. They saw our work and reacted. That's what happened. Very sad
Click to expand...
Click to collapse
Perhaps we need to find the Fastboot oem command, they can be different for different devices
https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
scrubber said:
Perhaps we need to find the Fastboot oem command, they can be different for different devices
https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
Click to expand...
Click to collapse
Well, the strings dump shows that the "oem unlock" command seems to exist, but it indicates that an unlock code is necessary, probably based on the serial number of the watch:
strings dump extract:
Code:
oem:
unlock
serial no length is null
magic_serialno:%s
, len:%d
%02x
uncrypted_str_serialno:%s
Unlocked code sucess
Unlocked code is error
Unsupport oem cmd
FAILED: The command is not recongized
So, we have three possibilities:
We find the method on how the code is calculated based on the serial of the watch
We find the location, where u-boot stores the variable, if the device is locked or not (EDIT: I would expect that in the Misc partition.)
We just reflash the old bootloader (easiest, but only temporary until next OTA update)
Neuer_User said:
So, we have three possibilities:
We find the location, where u-boot stores the variable, if the device is locked or not (EDIT: I would expect that in the Misc partition.)
Click to expand...
Click to collapse
Drop me stock ota 1.2.11c and 1.2.13
scrubber said:
Drop me stock ota 1.2.11c and 1.2.13
Click to expand...
Click to collapse
You will only need the bootloaders (rest of the OTA is just modified apks). I will send them both (old and new one) to you via PM. It would be necessary to disassemble and understand the new bootloader (the old one does not have any OEM commands and also did not read the serial no at all, instead displayed always a dummy serial).
The serial is stored on the misc partition, so the bootloader now needs to read this partition. That's why I believe they probably stored the lock/unlock flag also there. We just need to know which byte.
Of course, if there were someone with a functioning unlock code, he could dump his misc partition before and after unlocking. That would make it pretty clear
so I now have no way to flash a stable version starting from 1.2.13?
It's safe to update 1.3.2b ? English version
zbuh said:
It's safe to update 1.3.2b ? English version
Click to expand...
Click to collapse
No, also locks bootloader. But there is a good chance that we can unlock or reflash the bootloader, if someone wants to switch firmware later.
I also have this problem. I accidentally updated my Amazfit to the latest version official rom. Now I wanted to upgrade to PACEfied, but the bootloader is locked.
Do you have any ideas how to unlock it?
Hi neur_user will I be losing the interval timer and countdown timer app that I installed in pace 1.3.1m rom if update it to 1.3.2b since you said it is bootloader locked? And can you still install developers app in 1.3.2b?
powerforward said:
Hi neur_user will I be losing the interval timer and countdown timer app that I installed in pace 1.3.1m rom if update it to 1.3.2b since you said it is bootloader locked? And can you still install developers app in 1.3.2b?
Click to expand...
Click to collapse
Instalation of additional apps like those timer apps should still work.
barciol said:
I also have this problem. I accidentally updated my Amazfit to the latest version official rom. Now I wanted to upgrade to PACEfied, but the bootloader is locked.
Do you have any ideas how to unlock it?
Click to expand...
Click to collapse
I have an idea how we can unlock the bootloader. In the weekend I will see if I can post a tutorial.
Well, I don't know what I could gain by flashing PACEified FW on my watch... all I've really been looking for is working notifications from my phone to the watch. I'm coming from wearing a Samsung Gear Live that's now worn-out, and it integrated into my life by bringing notifications to my wrist. The Amazfit was perfect for fitness, runtime, and notifications -- but notifications have never worked despite all my hacking and flashing (originally came with Chinese ROM). My saga so far is detailed here: https://www.reddit.com/r/amazfit/comments/61w4ga/most_notifications_not_coming_through_facebook
I flashed the English ROM to it tonight, and proceeded to OTA it (because newer is better, right?). The update failed as I still had the Chinese recovery on it. When it failed, I decided to try intercepting the update bundle before it rebooted. I succeeded, by kicking it into Fastboot mode using the power-button trick, then I pulled the 1.3.2b update.zip file through the "mod recovery". That file is here: https://mega.nz/#!nIBDhLrR!7nQlWsn-TF4bsMNBSaTOfimY-vo-Z2R3dSavrDp1wsA
I fixed my recovery with help of another thread, and OTA'd again to success - the darn thing took a good solid 10 minutes to run the ~33MB update! The progress bar hung the longest (~2 mins each) near the "w", "c", and at the end of "watch" in the message about not powering off the watch. Rather surprising, and wasn't sure if it hung due to my mods or what it was doing...
Hopefully this helps someone interested in looking into how the bootloader gets locked (IDK if Amazfit expected someone to intercept this, being as it's near impossible to intercept except with a MitM on WiFi), perhaps in exchange for some help with these notifications?
Neuer_User said:
I have an idea how we can unlock the bootloader. In the weekend I will see if I can post a tutorial.
Click to expand...
Click to collapse
I'm stuck in 1.2.13 dev, if u want i can test the unlock
Cracklydisc said:
I'm stuck in 1.2.13 dev, if u want i can test the unlock
Click to expand...
Click to collapse
OK, will prepare it today and send it to you.
Neuer_User said:
OK, will prepare it today and send it to you.
Click to expand...
Click to collapse
I also want test the unlock. Please contact with me
barciol said:
I also want test the unlock. Please contact with me
Click to expand...
Click to collapse
Just to clarify: Technically, it is not "unlocking" the bootloader. It just reflashes the old one (which did not have the locking function). That implies that the "unlocked" bootloader will only stay "unlocked" until you install the next official OTA update (which again flashes the locked bootloader). If you move to PACEfied, then that is ok, as PACEfied certainly does not lock your bootloader.
Related
I have an x10a, and I have for a while. But, its getting old, and boring. I wanted to spice it up with a custom ROM, namely Cyanogenmod. But going through the steps, xflashtool doesn't seem to want to play ball, informing me that "Your phone bootloader cannot be officially unlocked".
I've flashed it before, but only back to stock. This time I want something new.
Now, I've googled around and I've found a few pieces of information about this, but nothing concrete, and certainly nothing very in-depth.
I need to know;
- Does this mean that my attempts at a custom ROM are just at a halt completely? Too bad for me, try a different phone?
- If not, can I force the bootloader to be unlocked, and will it remove my ability to use the radio capability in the phone? (as I have read in a few places now), because my phone isn't a lot of good without the ability to do phone things.
- If I can force it, how, and are there any downsides?
and bonus round;
- Why are there certain phones that just can't have the bootloader unlocked.
Cheers in advance guys, I'd really like to hear some good news about this, but anything is better than what I have at this point.
AzzaMan said:
I have an x10a, and I have for a while. But, its getting old, and boring. I wanted to spice it up with a custom ROM, namely Cyanogenmod. But going through the steps, xflashtool doesn't seem to want to play ball, informing me that "Your phone bootloader cannot be officially unlocked".
I've flashed it before, but only back to stock. This time I want something new.
Now, I've googled around and I've found a few pieces of information about this, but nothing concrete, and certainly nothing very in-depth.
I need to know;
- Does this mean that my attempts at a custom ROM are just at a halt completely? Too bad for me, try a different phone?
- If not, can I force the bootloader to be unlocked, and will it remove my ability to use the radio capability in the phone? (as I have read in a few places now), because my phone isn't a lot of good without the ability to do phone things.
- If I can force it, how, and are there any downsides?
and bonus round;
- Why are there certain phones that just can't have the bootloader unlocked.
Cheers in advance guys, I'd really like to hear some good news about this, but anything is better than what I have at this point.
Click to expand...
Click to collapse
1st: you still can flash custom rom, look for the one that have stated (for locked bootloader)
2nd: yes you can, there is testpoint method (correct me If I'm wrong)
3rd: no afaik
Bonus: because there are carrier locked, or just plain damn unlucky
Sent from my GT-P3110 using xda app-developers app
TakuyaZ said:
1st: you still can flash custom rom, look for the one that have stated (for locked bootloader)
2nd: yes you can, there is testpoint method (correct me If I'm wrong)
3rd: no afaik
Bonus: because there are carrier locked, or just plain damn unlucky
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Champion. Cheers for the lightning fast reply, didn't expect to hear back for a day or two. I'm gonna begin my search for a copy of cyanogenmod for x10's that are for locked bootloaders. This should be fun
AzzaMan said:
Champion. Cheers for the lightning fast reply, didn't expect to hear back for a day or two. I'm gonna begin my search for a copy of cyanogenmod for x10's that are for locked bootloaders. This should be fun
Click to expand...
Click to collapse
Cyanogen mod cant be installed in locked bootloader, due to cm require an custom kernel
Sent from my GT-P3110 using xda app-developers app
TakuyaZ said:
Cyanogen mod cant be installed in locked bootloader, due to cm require an custom kernel
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Damn it... Any suggestions for a good alternative? I'd like something either really fancy, or really low RAM and Battery usage.
TakuyaZ said:
...
Bonus: because there are carrier locked, or just plain damn unlucky
Click to expand...
Click to collapse
My X10i is carrirer locked, and I could unlock the boot loader without any problems.
The problem with those who lose their radio capability, is, as I suspect it to be, because they tried SIM-unlock their devices with third party methods in a way that are not supposed to be done. (A "bad" hack method of some kind). Once they unlock the boot loader, they lose that poor third party hack, and the device reverts back to a SIM-locked state. Since most of the people who do SIM-unlock their devices, uses a different carrier, will also lose the radio because of the carrier/SIM lock.
One can safely unlock the boot loader if:
* The device remains SIM-locked and haven't been touched by poor, unknown SIM-lock hacks.
* The device isn't SIM-locked in the first place. (Device was delivered in an unlocked state)
* The device is SIM-unlocked with the proper method, where one get proper unlock codes from their original carrier matched with the IMEI code.
SysGhost said:
One can safely unlock the boot loader if:
* The device remains SIM-locked and haven't been touched by poor, unknown SIM-lock hacks.
* The device isn't SIM-locked in the first place. (Device was delivered in an unlocked state)
* The device is SIM-unlocked with the proper method, where one get proper unlock codes from their original carrier matched with the IMEI code.
Click to expand...
Click to collapse
My phone was delivered locked to... Vodaphone? I think. I unlocked it a long time ago. But, I unlocked it by given them my IMEI, and getting the unlock code from them. So, as legit as it gets really. I am still not allowed to just unlock my bootloader. Based on what I've seen in this thread, and a couple of other places, if I force the bootloader to unlock by "less sturdy" means, I should be fine with my sim-unlock, or be able to just contact them again and get a new unlock code.
So, this Testpoint method that TakuyaZ mentioned, anyone able to point me in the right direction for that or an alternative? I can't seem to find a decent tutorial anywhere.
AzzaMan said:
My phone was delivered locked to... Vodaphone? I think. I unlocked it a long time ago. But, I unlocked it by given them my IMEI, and getting the unlock code from them. So, as legit as it gets really. I am still not allowed to just unlock my bootloader. Based on what I've seen in this thread, and a couple of other places, if I force the bootloader to unlock by "less sturdy" means, I should be fine with my sim-unlock, or be able to just contact them again and get a new unlock code.
So, this Testpoint method that TakuyaZ mentioned, anyone able to point me in the right direction for that or an alternative? I can't seem to find a decent tutorial anywhere.
Click to expand...
Click to collapse
What method did you try to unlock the bootloader with? As far as I know your SIM-unlocked status shouldn't be affected at all, as it is properly unlocked, with the radio accepting all carriers. (Radio part of the device is semi-isolated from the rest of the system)
Try this method, and you should be fine: (But I cannot promise anything. If you do try it, you're on your own.)
http://forum.xda-developers.com/showthread.php?t=1253277
It's the method I used on a few X10i devices. Works on SIM-locked devices (They'll remain SIM-locked after, as it should be), as well as unlocked devices that previosly has been SIM-locked, but unlocked with the proper codes from the carrier. They remained SIM-unlocked after unlocking the boot loader. Good news that is.
So if you really know that your device has been properly SIM-unlocked with codes delivered from the carrier that locked the device in the first place, you should be fine. A.f.a.i.k, the only ones that lost their radio on their devices, are the ones who used improper third party hacking methods to SIM-unlock their devices.
Warning: If you are not 100% sure about what method that has been used to SIM-unlock your device. Stop. And turn back.
Alright, attempting the method posted above, I have hit a snag. I then proceeded to hit the same snag over and over again, trying minutely different methods.
My problem is with the qsd8250_semc tool.
The most I can get out of it is;
"
Process requires standard 2.x android firmware.
Press any key to continue...
Getting ROOT rights.
error: protocol fault (no status)
error: device not found
error: device not found.
Waiting...
"
Any suggestions? At this point I've tried the methods listed on the sites below, but nothing is working.
http://forum.xda-developers.com/showthread.php?t=1253277
http://www.modaco.com/topic/346145-how-toguideunlock-x10-bootloader-permanently/
AzzaMan said:
Alright, attempting the method posted above, I have hit a snag. I then proceeded to hit the same snag over and over again, trying minutely different methods.
My problem is with the qsd8250_semc tool.
The most I can get out of it is;
"
Process requires standard 2.x android firmware.
Press any key to continue...
Getting ROOT rights.
error: protocol fault (no status)
error: device not found
error: device not found.
Waiting...
"
Any suggestions? At this point I've tried the methods listed on the sites below, but nothing is working.
http://forum.xda-developers.com/showthread.php?t=1253277
http://www.modaco.com/topic/346145-how-toguideunlock-x10-bootloader-permanently/
Click to expand...
Click to collapse
Did you try with Flashtool? Don't use the newest version, you need 0.9.10 release. From http://androxyde.github.io/ There is a thread on here some where ill inbox you the link if I find it.
But it is easy as to do. By memory I think you click the padlock in flashtool to root phone then click on the plugins and you have the option to unlock boot loader with a click. Not sure if you have to add recovery first? Get the older version of flashtool though.
I'm sure someone will remember and help :good:
Found this http://forum.xda-developers.com/showthread.php?t=1254087
Hey mate this is the thread I used http://forum.xda-developers.com/showthread.php?t=1821750
doodownunda said:
Did you try with Flashtool? Don't use the newest version, you need 0.9.10 release. From http://androxyde.github.io/ There is a thread on here some where ill inbox you the link if I find it.
But it is easy as to do. By memory I think you click the padlock in flashtool to root phone then click on the plugins and you have the option to unlock boot loader with a click. Not sure if you have to add recovery first? Get the older version of flashtool though.
I'm sure someone will remember and help :good:
Found this http://forum.xda-developers.com/showthread.php?t=1254087
Hey mate this is the thread I used http://forum.xda-developers.com/showthread.php?t=1821750
Click to expand...
Click to collapse
The only things needed on the X10 part is it to have original (Stock) firmware with Android 2.1 or 2.2, with the original 2.6.29 kernel.
Also one need to enable debugging over USB (Debug Bridge) in the developer settings. And lastly need the drivers installed if using Windows. (Which I assume is the case here)
Once that's done, it should all work.
I've written a Linux script if anyone needs it. Still need the other files from the original qsd8250.7z toolset from the_laser's thread. See attached files.
Place qsd8250_semc.bash in the same director as qsd8250_semc.cmd, then execute it.
One also need Linux-version of the adb command, and in the system PATH variable.
Hello guys,
I've been trying to root this phone since i've bought it, problem is every option i read on the web doesnt work because phone's bootloader is locked, and all methods get to this point when u have to unlock ur phone bootloader but in order to do that u have to get in the phone bootloader wich is locked. So who the hell is giving advices like these i dont know. Problem is that i am motivated to still root it, nothing its impossible.
So i am asking, did anyone from EU, with the EU ROM (full of mallware) MIUI 8, managed to unlock its bootloader and then managed to root it ?! please lets discuss here the options that work and the options that didnt work so we can make it through and solve this problem, everything thats on web at this moment 27-11-2016 doesnt work on the False EU MIUI 8.
Thanks.
CatalinSava said:
Hello guys,
I've been trying to root this phone since i've bought it, problem is every option i read on the web doesnt work because phone's bootloader is locked, and all methods get to this point when u have to unlock ur phone bootloader but in order to do that u have to get in the phone bootloader wich is locked. So who the hell is giving advices like these i dont know. Problem is that i am motivated to still root it, nothing its impossible.
So i am asking you did anyone from EU, with the EU ROM (full of mallware) MIUI 8, managed to unlock its bootloader and then managed to root it ? please lets discuss here the options that work and the options that didnt work so we can make it through and solve this problem, everything thats on web at this moment 27-11-2016 doesnt work on the False EU MIUI 8.
Thanks.
Click to expand...
Click to collapse
Not posibble without unlocked bootloader. Even the pre-rooted China Developer rom needs phone with unlocked bootloader. Good luck with unlocking the bootloader.
EU ROM full of malware?!?! Where did you get that idea? Completely false.
Anyway as said, yes you do need to unlock bootloader. Impossible any other way, because the system has dm-verity (similar to HTC S-On) which prevents modification to /system. So if you can't modify system or boot partition then you can't put Superuser binaries anywhere. Unlocked bootloader allows to put Superuser on boot pertition.
Sent from my Redmi Note 4 using Tapatalk
CosmicDan said:
EU ROM full of malware?!?! Where did you get that idea? Completely false.
Anyway as said, yes you do need to unlock bootloader. Impossible any other way, because the system has dm-verity (similar to HTC S-On) which prevents modification to /system. So if you can't modify system or boot partition then you can't put Superuser binaries anywhere. Unlocked bootloader allows to put Superuser on boot pertition.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Can't we just flash a recovery-that can disable dm-verity using SP Flash and root the phone that way?
I am guessing not because no one has said it works
I'm getting rly impatient because I still havent got my bootloader unlock request approved yet lol
asusm930 said:
Can't we just flash a recovery-that can disable dm-verity using SP Flash and root the phone that way?
I am guessing not because no one has said it works
I'm getting rly impatient because I still havent got my bootloader unlock request approved yet lol
Click to expand...
Click to collapse
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
CosmicDan said:
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
Click to expand...
Click to collapse
have you atempted to see what actually happens when a bootloader is unlocked? Like what does the miunlocker do/flash on the phone?
---------- Post added at 05:20 AM ---------- Previous post was at 05:04 AM ----------
CosmicDan said:
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
Click to expand...
Click to collapse
I'm gonna try to flash a twrp recovery using this guide http://en.miui.com/thread-371349-1-1.html
and replace the recovery file with TWRP. Will report if it works
Yea it doesnt work haha
CosmicDan said:
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
Click to expand...
Click to collapse
Hey can you upload you miunlock tool folder here? Want to see if the miunlock tool downloaded anything that enabled the bootloader unlock
asusm930 said:
Hey can you upload you miunlock tool folder here? Want to see if the miunlock tool downloaded anything that enabled the bootloader unlock
Click to expand...
Click to collapse
You can download it for free, just search for MiFlash - it's not a secret tool or anything.
Attempting to see what actually happens...? Even if I had the skills to reverse engineer MediaTek security, I wouldn't do it.
You're trying to do such simple things to trick the system but you need to realize that this hardware has been verified by Google themselves as secure and safe enough for Android Pay and SafetyNet and such. It *can not* be easily cracked, accept it.
Replacing recovery.img with TWRP? Seriously? How dumb do you think these companies are? Sorry for being rude but you really are just being silly.
You are wasting your own time, and now mine too... Sorry but I'm going to unsubscribe now because these questions are just getting silly.
Sent from my Redmi Note 4 using Tapatalk
CosmicDan said:
You can download it for free, just search for MiFlash - it's not a secret tool or anything.
Attempting to see what actually happens...? Even if I had the skills to reverse engineer MediaTek security, I wouldn't do it.
You're trying to do such simple things to trick the system but you need to realize that this hardware has been verified by Google themselves as secure and safe enough for Android Pay and SafetyNet and such. It *can not* be easily cracked, accept it.
Replacing recovery.img with TWRP? Seriously? How dumb do you think these companies are? Sorry for being rude but you really are just being silly.
You are wasting your own time, and now mine too... Sorry but I'm going to unsubscribe now because these questions are just getting silly.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Man, I did not know that xiaomi actually put that much effort on making their mediatek phones actually google levels of secure.
Was always under the impression that they sorta skimped out on their mediatek lines (as they had before).
Now I'll just not try to unlock it unofficially lol
asusm930 said:
Man, I did not know that xiaomi actually put that much effort on making their mediatek phones actually google levels of secure.
Was always under the impression that they sorta skimped out on their mediatek lines (as they had before).
Now I'll just not try to unlock it unofficially lol
Click to expand...
Click to collapse
They had before sure, but in the recent year or so (since they started actually locking bootloaders) things changed - they want to target international market too.
Only reason the devices are not sold globally is because of some Mediatek patent/legal battle or something, not too sure (it's literally the only reason why they have snapdragon "pro" versions). But the device has a global firmware sold in Taiwan and some other places, and it is Google CTS certified (preinstalled with Google Play) and, since it's Marshmallow, requires all kinds of Google-approved security measures these days, which a lot of countries need legally too, so yeah.
Glad you understand. I read that if it takes too long to get unlock code, you should try/already be flashed on China dev ROM - so do that if you have not already.
Have you tried the unlocking link on this link? http://xiaomi-mi.com/redmi-note-4/
i am getting a brand new huawei mate 10 pro returning my current brand new one as it got updated to the latest emui which prevents bootloader unlocking, how do i succesfully unlock the bootloader on the next mate 10 pro?
1.how do i prevent it from updating and ruining my chances of unlocking the bootloader Before i have a chance to unlock it, will it force update?
2.how do i keep the bootloader locked will i have to flash some other rom on it to prevent it from updating ota or can i update it ota and keep the bootloader unlocked with twrp or will it be permanently locked if i attempt to ota update after twrp is installed and after the bootloader is unlocked
3.i read that it can restore the default recovery on first boot can anyone explain this to me
since the latest emui prevents the bootloader from being unlocked i only have one chance, and if it somehow updates to the latest emui then it's locked forever, so how do i unlock the bootloader permanently without worrying about it unlocking ever again, i thought that once the bootloader is unlocked and twrp is installed then it will stay like that, but then i read that it can get overitten just with an ota update and once it updates then i can never unlock it again.
zzcool said:
i am getting a brand new huawei mate 10 pro returning my current brand new one as it got updated to the latest emui which prevents bootloader unlocking, how do i succesfully unlock the bootloader on the next mate 10 pro?
1.how do i prevent it from updating and ruining my chances of unlocking the bootloader Before i have a chance to unlock it, will it force update?
2.how do i keep the bootloader locked will i have to flash some other rom on it to prevent it from updating ota or can i update it ota and keep the bootloader unlocked with twrp or will it be permanently locked if i attempt to ota update after twrp is installed and after the bootloader is unlocked
3.i read that it can restore the default recovery on first boot can anyone explain this to me
since the latest emui prevents the bootloader from being unlocked i only have one chance, and if it somehow updates to the latest emui then it's locked forever, so how do i unlock the bootloader permanently without worrying about it unlocking ever again, i thought that once the bootloader is unlocked and twrp is installed then it will stay like that, but then i read that it can get overitten just with an ota update and once it updates then i can never unlock it again.
Click to expand...
Click to collapse
1. Set up device, but don't plug in SIM or enable WiFi. Go to settings and check patch level.
Depending on Cust of course, but generally July or later can't be downgraded (If downgrade is needed). This is due to updated bootloader.
If May/June or earlier you should be able to use HCU-client directly to get unlock code.
For example, BLA-L29C432B145 (June) can be downgraded to B142 (May) where HCU works. This is using dload firmware from androidhost.ru (requires an OTG-cable and USB-stick 8gb min or a OTG usb hub and USB-stick 8gb min).
B146+ can't be downgraded to old bootloader due to updated bootloader.
2. When you have the unlock code you can use it, always, no matter what firmware (At least as it is now, this might change in the future)
Firmware don't normally lock bootloader.
3. To restore stock recovery you would either:
Extract it from your firmwares update.app, acquired from firmware finder. This is extracted using Huawei Update Extractor.
Stock recovery is named recovery_ramdisk and can be flashed through fastboot.
OR
You can 'dd' erecovery_ramdisk to recovery_ramdisk (both partitions are the same, different 'entry' points). This is using terminal in TWRP
dd if=/dev/block/bootdevice/by-name/erecovery_ramdisk of=/dev/block/bootdevice/by-name/recovery_ramdisk
I would suggest using the update.app approach if you're not comfortable using terminal. 'dd' is a potentially dangerous command.
But your device should ship with an already HCU compatible firmware, so you should be able to get code right away, as long as you don't connect to the internet first.
ante0 said:
1. Set up device, but don't plug in SIM or enable WiFi. Go to settings and check patch level.
Depending on Cust of course, but generally July or later can't be downgraded (If downgrade is needed). This is due to updated bootloader.
If May/June or earlier you should be able to use HCU-client directly to get unlock code.
For example, BLA-L29C432B145 (June) can be downgraded to B142 (May) where HCU works. This is using dload firmware from androidhost.ru (requires an OTG-cable and USB-stick 8gb min or a OTG usb hub and USB-stick 8gb min).
B146+ can't be downgraded to old bootloader due to updated bootloader.
2. When you have the unlock code you can use it, always, no matter what firmware (At least as it is now, this might change in the future)
Firmware don't normally lock bootloader.
3. To restore stock recovery you would either:
Extract it from your firmwares update.app, acquired from firmware finder. This is extracted using Huawei Update Extractor.
Stock recovery is named recovery_ramdisk and can be flashed through fastboot.
OR
You can 'dd' erecovery_ramdisk to recovery_ramdisk (both partitions are the same, different 'entry' points). This is using terminal in TWRP
dd if=/dev/block/bootdevice/by-name/erecovery_ramdisk of=/dev/block/bootdevice/by-name/recovery_ramdisk
I would suggest using the update.app approach if you're not comfortable using terminal. 'dd' is a potentially dangerous command.
But your device should ship with an already HCU compatible firmware, so you should be able to get code right away, as long as you don't connect to the internet first.
Click to expand...
Click to collapse
can i set it up without a Connection? from what i remember setting it up the first time it forced me to connect to the internet, as for unlocking that seems really complicated, from what i saw i can use dc unlocker with the click of a few buttons so i don't quite understand these methods, so you mean this is better than dc unlocker, does that mean once i get the code i can update emui and relock the bootloader and then unlock it? no need for any software or anything once i have the code then it's like an official code so i never have to worry about not being able to unlock the bootloader again can i then unlock the bootloader no matter how new emui if i want, and what firmware will it have if it comes brand new should it have the firmware it shipped with on release?
let's say the phone comes with Before may security patch can i then easily just get the code without much complication and then it's the same code as if i were to get it directly from huawei meaning i don't have to worry about updating emui and having the bootloader locked permanently? this is all news to me as i thought you needed to use dc unlocker as a workaround and that this only works on older emui meaning if i unlock the bootloader update emui then it's locked forever.
zzcool said:
can i set it up without a Connection? from what i remember setting it up the first time it forced me to connect to the internet, as for unlocking that seems really complicated, from what i saw i can use dc unlocker with the click of a few buttons so i don't quite understand these methods, so you mean this is better than dc unlocker, does that mean once i get the code i can update emui and relock the bootloader and then unlock it? no need for any software or anything once i have the code then it's like an official code so i never have to worry about not being able to unlock the bootloader again can i then unlock the bootloader no matter how new emui if i want, and what firmware will it have if it comes brand new should it have the firmware it shipped with on release?
let's say the phone comes with Before may security patch can i then easily just get the code without much complication and then it's the same code as if i were to get it directly from huawei meaning i don't have to worry about updating emui and having the bootloader locked permanently? this is all news to me as i thought you needed to use dc unlocker as a workaround and that this only works on older emui meaning if i unlock the bootloader update emui then it's locked forever.
Click to expand...
Click to collapse
Hcu-Client is made by DC-Unlocker, but it works for newer phones. Its the same procedure as using DC-Unlocker, and uses the same credits. Just follow the instructions found in the program.
The downgrade would only be needed it your firmware is higher than the supported ones, and still on old bootloader.
I can't say for sure the unlock code will work for all eternity, but at least for now it will work after you update (and if phone for some reason locks after update).
If it works or not on future firmware is up to Huawei. My phone stayed unlocked when flashing Pie beta anyway....
When you have the code you it will be like the official one, so keep it somewhere safe.
I'm pretty sure you can skip through the whole set up without connecting to the Internet.
I can't remember what firmware my phone came with, it might have been on C432B127 or C432B129...
DC unlocker/HCU is only to get the unlock code as Huawei closed their site to get it. You can safely update after getting it.
ante0 said:
Hcu-Client is made by DC-Unlocker, but it works for newer phones. Its the same procedure as using DC-Unlocker, and uses the same credits. Just follow the instructions found in the program.
The downgrade would only be needed it your firmware is higher than the supported ones, and still on old bootloader.
I can't say for sure the unlock code will work for all eternity, but at least for now it will work after you update (and if phone for some reason locks after update).
If it works or not on future firmware is up to Huawei. My phone stayed unlocked when flashing Pie beta anyway....
When you have the code you it will be like the official one, so keep it somewhere safe.
I'm pretty sure you can skip through the whole set up without connecting to the Internet.
I can't remember what firmware my phone came with, it might have been on C432B127 or C432B129...
DC unlocker/HCU is only to get the unlock code as Huawei closed their site to get it. You can safely update after getting it.
Click to expand...
Click to collapse
oh so no need for a Cable or anything after i received the code, once i received it on the appropriate firmware then i can update emui, this means anything i do doesn't do anything to the phone itself, i don't need to do any modification on my phone i just use it to get the code then i update emui like normal and then when i feel like it i unlock the bootloader with the code, so i can get the code and just forget about it afterwards unless huweai invalidates it in the future?
simply put
1.i unbox the phone and set it up with no sim card or internet skip all logins
2.i connect it to a pc and get the code through hcu however that is done
3. i reset the phone and set it up like i normally would with internet and a simcard and then update it ota
then when i feel like it i can unlock the bootloader on the newest firmware and then install a custom rom
Hello guys, I need to read bootloader code in my mate 10 pro with dc-unlocker but they write in the site "Huawei Mate 10 Pro BLA-xxx upgraded to Android 8x not supported".. what do they main? Mate 10 pro was launched with android 8.0
Inviato dal mio ASUS_T00J utilizzando Tapatalk
L3onX said:
Hello guys, I need to read bootloader code in my mate 10 pro with dc-unlocker but they write in the site "Huawei Mate 10 Pro BLA-xxx upgraded to Android 8x not supported".. what do they main? Mate 10 pro was launched with android 8.0
Inviato dal mio ASUS_T00J utilizzando Tapatalk
Click to expand...
Click to collapse
It means it's not supported since May/June. I guess they just write that so they don't have to investigate into which firmware exactly.
It works on May patch firmware and earlier. Some cust even works on June.
Since your signature is Italian I guess you have C432?
If so, last build it worked on was B142. If you're on B145 you can downgrade to B142. If you're on B146 or later you can't get unlock code. (at least for now)
ante0 said:
It means it's not supported since May/June. I guess they just write that so they don't have to investigate into which firmware exactly.
It works on May patch firmware and earlier. Some cust even works on June.
Since your signature is Italian I guess you have C432?
If so, last build it worked on was B142. If you're on B145 you can downgrade to B142. If you're on B146 or later you can't get unlock code. (at least for now)
Click to expand...
Click to collapse
My signature is Italian but I have buyed brand tim that should be C55. The phone is arriving today so i do not know the build yet...this brand is updated slower than the others so i hope to be in an old build
L3onX said:
My signature is Italian but I have buyed brand tim that should be C55. The phone is arriving today so i do not know the build yet...this brand is updated slower than the others so i hope to be in an old build
Click to expand...
Click to collapse
It most likely will be then. If its B133 or even B135 it should work with DC out of the box. Just don't update before getting code
ante0 said:
It most likely will be then. If its B133 or even B135 it should work with DC out of the box. Just don't update before getting code
Click to expand...
Click to collapse
Of course, I will set up the device without wifi and sim as suggested
NEWS: I've just received the phone. It is bla-l09 8.0.0.128(c55) with January patch. I can read the bootloader code using DC software without doing anithing else, right?
L3onX said:
Of course, I will set up the device without wifi and sim as suggested
NEWS: I've just received the phone. It is bla-l09 8.0.0.128(c55) with January patch. I can read the bootloader code using DC software without doing anithing else, right?
Click to expand...
Click to collapse
If DC-Unlocker doesn't work, use HCU-client. I can't remember if Mate 10 Pro is too new for DC-unlocker.
It's the same credits anyway, and it won't use credits if phone is not supported in DC-unlocker (You won't get the Bootloader code option anyway).
It may ask you to factory reset in HCU to get code, if it does just comply.
You will need 4 credits, which equals $4
i spoke to the developers of dc unlocker i was told they have no idea if the code will work after emui is updated, they suggest i unlock the bootloader as soon as i receive the code.
ante0 said:
If DC-Unlocker doesn't work, use HCU-client. I can't remember if Mate 10 Pro is too new for DC-unlocker.
It's the same credits anyway, and it won't use credits if phone is not supported in DC-unlocker (You won't get the Bootloader code option anyway).
It may ask you to factory reset in HCU to get code, if it does just comply.
You will need 4 credits, which equals $4
Click to expand...
Click to collapse
I've just gain my bootloader code in my mate 10 pro with DC-unlocker I confirm that it works perfectly with bla-l09 8.0.0.128(c55)! Can I update my smartphone and use the code in future when want? there is b137 now aviable. Thanks for the support
L3onX said:
I've just gain my bootloader code in my mate 10 pro with DC-unlocker I confirm that it works perfectly with bla-l09 8.0.0.128(c55)! Can I update my smartphone and use the code in future when want? there is b137 now aviable. Thanks for the support
Click to expand...
Click to collapse
Yes, it should work forever. I say should because it's Huawei and you never know if they decide to lock all unlocked phones and make the unlock codes invalid....
zzcool said:
i spoke to the developers of dc unlocker i was told they have no idea if the code will work after emui is updated, they suggest i unlock the bootloader as soon as i receive the code.
Click to expand...
Click to collapse
It should work in updated EMUI, atleast in Oreo.
What Huawei did, what I found out anyway, that made unlock code generation not working anymore is changing the key needed to generate it.
It's the same with the backdoor they use, it needs a new key to work. So technically all old unlock codes should work as the end result when generating an unlock code would be the same regardless of what key is needed to generate it. I guess anyway.
ante0 said:
Yes, it should work forever. I say should because it's Huawei and you never know if they decide to lock all unlocked phones and make the unlock codes invalid....
It should work in updated EMUI, atleast in Oreo.
What Huawei did, what I found out anyway, that made unlock code generation not working anymore is changing the key needed to generate it.
It's the same with the backdoor they use, it needs a new key to work. So technically all old unlock codes should work as the end result when generating an unlock code would be the same regardless of what key is needed to generate it. I guess anyway.
Click to expand...
Click to collapse
i just received the device it's on c3432 and Android 8.0 june patch can i unlock it?
zzcool said:
i just received the device it's on c3432 and Android 8.0 june patch can i unlock it?
Click to expand...
Click to collapse
B145?
If so you have to downgrade to B142, firmware is available on androidhost.ru.
You will also need an otg cable and a memory stick/usb adapter and minimum 8gb memory. (Samsungs USB-C to USB-A works fine for this if you happen to have one)
Or a USB hub.
Then extract your downloaded firmware zip, just cut and paste "sd_update" folder to external memory stick and start phone in dload mode.
There are instructions that come with the firmware on how you flash it (dload mode, folder structure etc.)
External memory is needed as Mate 10 Pro can't read internal while in recovery.
tried Reading bootloader code
2018-09-24 18:33:41.333 Autodetect COM port and phone type start!
2018-09-24 18:33:44.010 Found COM port: COM6
2018-09-24 18:33:44.017 Found phone type: Huawei Android phone (HiSilicon CPU)
2018-09-24 18:33:44.149 Connecting to server...
2018-09-24 18:33:44.409 Connected!
2018-09-24 18:33:44.420 Open COM port COM6 (Android Adapter PCUI (COM6))...
Read bootloader code fail!
Not supported/unknown chipset!
so i guess thats it then?
wait you mean i can downgrade it?
bla l29 8.0.0.145 c432
and yeah i have that otg samsung adapter
so i download the firmware put the folder in the root of the usb stick and then simply downgrade?, will it still work after i attempted to get the bootloader code right now?
zzcool said:
tried Reading bootloader code
2018-09-24 18:33:41.333 Autodetect COM port and phone type start!
2018-09-24 18:33:44.010 Found COM port: COM6
2018-09-24 18:33:44.017 Found phone type: Huawei Android phone (HiSilicon CPU)
2018-09-24 18:33:44.149 Connecting to server...
2018-09-24 18:33:44.409 Connected!
2018-09-24 18:33:44.420 Open COM port COM6 (Android Adapter PCUI (COM6))...
Read bootloader code fail!
Not supported/unknown chipset!
so i guess thats it then?
wait you mean i can downgrade it?
bla l29 8.0.0.145 c432
and yeah i have that otg samsung adapter
so i download the firmware put the folder in the root of the usb stick and then simply downgrade?, will it still work after i attempted to get the bootloader code right now?
Click to expand...
Click to collapse
Yes, just downgrade, get the unlock code and then unlock. It doesn't matter that you tried to get the code while on B145.
would you mind giving the most stupid easy to understand guide just to make it simpler for me so you mean it is certain i can do this.
zzcool said:
would you mind giving the most stupid easy to understand guide just to make it simpler for me so you mean it is certain i can do this.
Click to expand...
Click to collapse
Download this firmware - > http://androidhost.ru/3b5 <- and follow @ante0 advices for the downgrade procedure.
It took 28 days an a number of fails an misstarts. My hardest cellphone to unlock boot loader ever.
I finally had success with a guy off youtube an waited 168hrs.
MiFlash Unlock Unofficial by KK World.
Link for those of you who struggled like me here is the link to a bootunlocking software that actually shows a countdown.
That was my issue i think. Miunlock showed a bunch of Chinese characters with no countdown.
KK world unofficial was the only one that showed an hr countdown.
Good luck everyone
MiFlash Unlock Unofficial by KK World - Google Search
This is an isolated case. Most of the users on this forum have unlocked their X3 using the official Xiaomi app with no issues.
I suggest people who read this post stick to the updated and official app. Unofficial apps may only serve to increase your waiting time.
Revontheus said:
This is an isolated case. Most of the users on this forum have unlocked their X3 using the official Xiaomi app with no issues.
I suggest people who read this post stick to the updated and official app. Unofficial apps may only serve to increase your waiting time.
Click to expand...
Click to collapse
I found stock miunlock did not work as I was never able to get an English countdown. I cannot be the only one who had this issue? There are all different skill levels buddy. It says senior member but I am anything but. I cannot even compile code lol.
Just trying to help.
Revontheus said:
This is an isolated case. Most of the users on this forum have unlocked their X3 using the official Xiaomi app with no issues.
Click to expand...
Click to collapse
Can't talk about other, but as a Linux user the only solution I found was xiaomitool V2
Counter-example here: with an European v1.0.4.0 stock ROM, I was able to unlock the bootloader after the customary 7 days delay with the regular Mi Unlock tool. Seems YMMV.
pnin said:
Counter-example here: with an European v1.0.4.0 stock ROM, I was able to unlock the bootloader after the customary 7 days delay with the regular Mi Unlock tool. Seems YMMV.
View attachment 5178567
Click to expand...
Click to collapse
Well, I got about 21 days on Global Nfc then I try it again after 2 days Then Got only 92 hours.
Is there any way to unlock the bootloader under Linux? I tried to install a Windows VM and set up USB pass through to use the tool but my computer is to poorly spec'd to run a VM. During the unlock process is the connected as a USB device or does it present as a serial port?
You must do it under windows unfortunately.
Send an email to Xiaomi and put some pressure on them to develop a linux tool or simply allow bootloader unlock using fastboot.
J-Mizzle said:
I tried to install a Windows VM and set up USB pass through to use the tool but my computer is to poorly spec'd to run a VM.
Click to expand...
Click to collapse
Maybe creating a Windows VHD will run good enough for you. FYI, here's a step-by-step that may be of help...
Boot from VHD
pnin said:
Maybe creating a Windows VHD will run good enough for you. FYI, here's a step-by-step that may be of help...
Boot from VHD
Click to expand...
Click to collapse
Thanks, I'll look into that option.
Bryceicle1971 said:
It took 28 days an a number of fails an misstarts. My hardest cellphone to unlock boot loader ever.
I finally had success with a guy off youtube an waited 168hrs.
MiFlash Unlock Unofficial by KK World.
Link for those of you who struggled like me here is the link to a bootunlocking software that actually shows a countdown.
That was my issue i think. Miunlock showed a bunch of Chinese characters with no countdown.
KK world unofficial was the only one that showed an hr countdown.
Good luck everyone
MiFlash Unlock Unofficial by KK World - Google Search
Click to expand...
Click to collapse
Technical Experience Right there
Running-___--Elephants said:
Technical Experience Right there
Click to expand...
Click to collapse
I'm an amateur man. Cellphones are a hobby. No idea why xda have decided I'm a 'senior member' next to my name I drive forklifts for a living an enjoy custom roms. I can't even write code lol.
I just found this bootloader extremely difficult to unlock. Every other Xiaomi device I've had it has been about a week.
I got 168 hours for my bootloader unlock. I assume I can continue using my device and then use the unlock tool again in a week for a successful unlock?
Anybody? I have never had a device with MIUI so the bootloader unlocking seems strange.
J-Mizzle said:
I got 168 hours for my bootloader unlock. I assume I can continue using my device and then use the unlock tool again in a week for a successful unlock?
Click to expand...
Click to collapse
Ur correct....just not unbound ur Mi account from ur phone all this period.
J-Mizzle said:
Anybody? I have never had a device with MIUI so the bootloader unlocking seems strange.
Click to expand...
Click to collapse
same with huawei bootloader unlocking process they give you oem unlock key via email ... they making bootloader unlocking so complicated
Unlocked my bootloader and flashed crDroid. I get a message saying the current user is unable to edit apn setting, so I am unable to get my data working. This happens no matter what rom I install. Any way to fix this issue?
J-Mizzle said:
Unlocked my bootloader and flashed crDroid. I get a message saying the current user is unable to edit apn setting, so I am unable to get my data working. This happens no matter what rom I install. Any way to fix this issue?
Click to expand...
Click to collapse
format data partition??
ineedroot69 said:
format data partition??
Click to expand...
Click to collapse
I did. No dice.
So the unofficial one version 3 unlock the phone instantly without wait time?
Any other newer tool to unlock the bootloader for Poco X3 NFC ?
Hello,
After receiving my new Motorola x40 I realized that I wasn't able to use my GooglePay nor did it have other language support. So I decided to unlock my x40 bootloader via https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your- device-a
It all worked. I managed to install a global rom with all the google apps and extra language support.
However, Global rom didn't allow my GooglePlay to use my cards or backup via googleOne since the flashing was unlocked. So I went to fastboot to " fastboot flashing lock". After which my cards were able to work.
After few days of using global rom I decided to go back to chinese one since I found it a bit easier to navigate.
So when I decided to go back to my old chinese rom, in "Developer Options" OEM unlocking says "Connect to the internet or contact your operator" and it is greyed out.
I tried using " fastboot flashing/oem unlock" in fastboot however it tells me that i need to unlock it in " developer options " first.
My phone has already been connected to wifi for around 90 hours on a Global rom And around a week before I transitioned from Chinese room over to global rom.
How long do I need to be connected to the internet or what operator do I need to contact to unlock my OEM again? Or maybe there is another way to unlock OEM without waiting?
Things I tried and failed:
1) Factory reset
2) Wipe/Cache reset via recovery3) "fastboot flashing/oem unlock" via bootloader
Global rom used: https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETGB/
Have same problem.
cryptm said:
Have same problem.
Click to expand...
Click to collapse
How many days are you in this state? maybe you are closer to 7 days than I am
The toggle to unlock the bootloader is now enabled for me after 8 days. I have the Edge 40 Pro.
mine too, didn't look before, i own mine since 14 april
Ok so the theory is that once you get a global rom and "fastboot oem lock", it will act like new phone and will only unlock after 7-8 days. Guess will have to wait to test this theory out.
zeakey said:
Ok so the theory is that once you get a global rom and "fastboot oem lock", it will act like new phone and will only unlock after 7-8 days. Guess will have to wait to test this theory out.
Click to expand...
Click to collapse
Any update whether you can toggle OEM Unlocking?
Also, as someone who have been using Moto phones from China for years, CN ROM is way way way better the Global ROM when it comes to features and software updates. One useful feature is the built in Motorola Wallet app where I can use my phone as keycard and transpo card.
ijuanp03 said:
Any update whether you can toggle OEM Unlocking?
Also, as someone who have been using Moto phones from China for years, CN ROM is way way way better the Global ROM when it comes to features and software updates. One useful feature is the built in Motorola Wallet app where I can use my phone as keycard and transpo card.
Click to expand...
Click to collapse
Nope. Still not unlocked. Waiting for new firmware updates. So far EU region didn't get any.
zeakey said:
Nope. Still not unlocked. Waiting for new firmware updates. So far EU region didn't get any.
Click to expand...
Click to collapse
Supposedly OTA updates are being released, some can update successfully, others can't. Keep us updated if you're able to successfully update.
JustHereForNow said:
Supposedly OTA updates are being released, some can update successfully, others can't. Keep us updated if you're able to successfully update.
Click to expand...
Click to collapse
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
zeakey said:
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
Click to expand...
Click to collapse
I'm assuming it's a Motorola issue. I'm assuming maybe even real Edge 40 Pro devices can't unlock yet? Honestly if OTA works and so do all features (banking, 5g, etc) then I have no problem doing the conversion.
zeakey said:
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
Click to expand...
Click to collapse
Does this mean you were able to update to 20-28 even with the locked bootloader (and locked OEM)?
Zechosenjuan said:
Does this mean you were able to update to 20-28 even with the locked bootloader (and locked OEM)?
Click to expand...
Click to collapse
I also updated without problem with bootloader closed and oem blocked and everything fine in the same way I solved the vpn and everything at 100 on the computer
ziggmax said:
I also updated without problem with bootloader closed and oem blocked and everything fine in the same way I solved the vpn and everything at 100 on the computer
Click to expand...
Click to collapse
What tools\steps did you take to update while bootloader and OEM are locked?
Zechosenjuan said:
What tools\steps did you take to update while bootloader and OEM are locked?
Click to expand...
Click to collapse
Using TinyFastbootScript flashing the reteu rom But when I installed it I blocked the bootloader thinking that it could be opened again to my surprise I could no longer activate the box so I have to wait and see if with any update I can go back To activate that option To activate that option
ziggmax said:
Using TinyFastbootScript flashing the reteu rom But when I installed it I blocked the bootloader thinking that it could be opened again to my surprise I could no longer activate the box so I have to wait and see if with any update I can go back To activate that option To activate that option
Click to expand...
Click to collapse
You won't be able to unlock the bootloader twice, impossible it's done by design by motorola.
You can only unlock your bootloader once
jody2k said:
You won't be able to unlock the bootloader twice, impossible it's done by design by motorola.
You can only unlock your bootloader once
Click to expand...
Click to collapse
does this mean the phone that went through unlock\lock of the BL will never get a firmware update (whether OTA or manual)?
Zechosenjuan said:
does this mean the phone that went through unlock\lock of the BL will never get a firmware update (whether OTA or manual)?
Click to expand...
Click to collapse
It's possible that we won't get OTA, only will know for sure in the future, i'm in the same situation.
But you can always manually update your firmware with rescue tool or through ADB as long it's the official firmware. You don't need a unlocked bootloader for that
jody2k said:
It's possible that we won't get OTA, only will know for sure in the future, i'm in the same situation.
But you can always manually update your firmware with rescue tool or through ADB as long it's the official firmware. You don't need a unlocked bootloader for that
Click to expand...
Click to collapse
This gives hope. Can you link me to flashing through adb? So far have only seen fastboot and magisk.
Zechosenjuan said:
This gives hope. Can you link me to flashing through adb? So far have only seen fastboot and magisk.
Click to expand...
Click to collapse
I think this method would work:
I screwed up...moto X40 bricked / Any EDL mode available?
Hi guys sadly I completely softbricked my motorola X40 phone i'm a idiot. I flashed to a wrong firmware file (edge 30 pro) and re-locked bootloader then found it phone doesn't properly boot anymore. I can boot it in fastboot mode but flashing in...
forum.xda-developers.com
But I think this will erase all your data so it's not a real "upgrade firmware" method
I also found out there is an "software update" in the lenovo rescue tool
Maybe it's worth the shot to try this out too, but for me it's says I have the latest firmware already (which is correct) so I can't test it out right now.