[Urgent] [Hardbrick] Don't update on Stock rom with unlocked bootloader - Moto G5 Guides, News, & Discussion

This is very important, many devices are dying because of this issue, and the solution is unknown at the moment.
If you did unlocked bootloader, and want to roll back to original Stock Rom, do not update the device, or else, you will get an permanent hardbrick.
As far as I know, this is a problem caused by partition divergence, and at the moment, there is no tutorial teaching how to reverse it.
The only fix would be Blank Flash or QFIL, but none of these methods are available for the device for a lack of files.
What we can do is wait for Motorola to release the Blank-Flash files from the device.
USEFUL LINKS FOR FIXING THE PROBLEM
Possible fix 1: https://forum.xda-developers.com/g5/how-to/guide-hard-brick-t3689904
Possible fix 2 (this was fixed): https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
Possible fix 3: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

Motorola won't release the blank files , they get leaked u could try potters blank flash but use our gpt.bin

In xt1676 cedric none of these three methods works.

Thanks!

But could you update if you've locked the bootloader manually?

Exanneon said:
But could you update if you've locked the bootloader manually?
Click to expand...
Click to collapse
I don't think so.

Question?
CypherPotato said:
I don't think so.
Click to expand...
Click to collapse
Has anyone already tried the botloader.img method from micro sd with success?
alguien ya probo el metodo de botloader.img desde micro sd con exito?

Related

[TOOL] One-Click bootloader unlock (no root required)

I've made simplier way to unlock the bootloader of ZE551ML/ZE550ML.
Update! Version 2.
Now it's not required to flash/downgrade droidboot.img. But you still need to flash one of compatible ROM.
Currently compatible versions are:
For ZE551ML: v2.19.40.18, v2.19.40.20, v2.19.40.22 and future newer versions unless opposite mentioned.
For ZE550ML: v2.19.40.12, v2.19.40.13, v2.19.40.23 and future newer versions unless opposite mentioned.
For example, you can flash full ROM v2.19.40.22 and then use unlocker v2.
Just unzip everything from attached archive and then start unlock_one_click_v2.bat
If you've enable USB debugging then phone will automatically reboot to bootloader and will unlock the bootloader. If you didn't enable USB debugging, then you need to reboot to bootloader manually (Turn the phone off and disconnect USB, then press Power+VolumeUp keys at the same time and keep it pressed till you see ASUS logo, then you may connect USB cable).
Either way, unlock_one_click_v2.bat will proceed to unlock in fully automated way.
If initial boot splash screen become inverted, then bootloader has been unlocked!
If you don't like white boot screen, then you can flash original black one:
http://forum.xda-developers.com/zen...-black-white-splashscreen-twrp-flash-t3141945
Originally, it's developed for WW firmware but should work on any region.
Works on CN firmware. Confirmed by @corrsea
Based on unlock method discovered by @shakalaca
Based on fastboot hack by @social-design-concepts
Version 1 (old)
To use this version, you need to flash ROM not older than v2.19.40.18 for ZE551ML, and v2.19.40.12 for ZE550ML. And then downgrade (if required) droidboot to compatible droidboot.img
Code:
fastboot flash fastboot droidboot.img
For ZE551ML, known compatible droidboot.img versions are 2.19.40.18, 2.19.40.20.
For ZE550ML, known compatible droidboot.img versions are 2.19.40.12.
Important note for Stock ROM lovers:
Although, unlocker v2 works with v2.19.40.22, there is no warranty, it will continue to work on future versions. It is up to ASUS decision. Unlocking process still requires several files from /system partition including special version of if.bin (/system/etc/firmware/if.bin). These files are still supplied with v2.19.40.22, but in the future they can be removed by ASUS together with disable of downgrade ability for if.bin.
So, if you will flash future stock ROM through official update procedure (which includes bootloader update - from ifwi.zip) then you may loose unlocked bootloader! And of course, ASUS may completely block unlocking procedure (at least unofficial way).
So, if unlocked bootloader is important for you, then
1) unlock it ASAP while current firmware allows.
2) don't use official updates. You need to remove all lines from update script containing ifwi.zip references and then flash through TWRP (you need to remove lines checking recovery version as well).
thank you very much for making this way easier, hope it will help many people, good job bro
@sorg, thanks for the tool. One ques. Will it wipe off the data? And does it keeps OTA taking ability or will it break off? If it breaks, what can be done to get it back?
itskapil said:
@sorg, thanks for the tool. One ques. Will it wipe off the data? And does it keeps OTA taking ability or will it break off? If it breaks, what can be done to get it back?
Click to expand...
Click to collapse
you will continue receiving OTA update.
---------- Post added at 05:20 AM ---------- Previous post was at 05:12 AM ----------
sorg said:
Important note for Stock ROM lovers:
Although, unlocker v2 works with v2.19.40.22, there is no warranty, it will continue to work on future versions. It is up to ASUS decision. Unlocking process still requires several files from /system partition including special version of if.bin (/system/etc/firmware/if.bin). These files are still supplied with v2.19.40.22, but in the future they can be removed by ASUS together with disable of downgrade ability for if.bin.
So, if you will flash future stock ROM through official update procedure (which includes bootloader update - from ifwi.zip) then you may loose unlocked bootloader! And of course, ASUS may completely block unlocking procedure (at least unofficial way).
So, if unlocked bootloader is important for you, then
1) unlock it ASAP while current firmware allows.
2) don't use official updates. You need to remove all lines from update script containing ifwi.zip references and then flash through TWRP (you need to remove lines checking recovery version as well).
Click to expand...
Click to collapse
Hi
Is there anyway other than installing a third-party recovery to verify if the boot-loader is unlocked or locked ?
will it void warranty of the phone.
If you unlock the bootloader it will void the warranty, as there's no way currently to lock the bootloader again.
Hi
Is there anyway other than installing a third-party recovery to verify if the boot-loader is unlocked or locked ?
will it void warranty of the phone.
Click to expand...
Click to collapse
Are there news for the ZE500CL version?
I currently have .22 via OTA, so I can just proceed with unlocking the bootloader without any issues? because in the other thread, they are still saying there is no way to unlock bootloader without downgrading to .20 or .18.. TIA!
jarjarbingie said:
I currently have .22 via OTA, so I can just proceed with unlocking the bootloader without any issues? because in the other thread, they are still saying there is no way to unlock bootloader without downgrading to .20 or .18.. TIA!
Click to expand...
Click to collapse
can you read what i've wrote in first post?
For example, you can flash full ROM v2.19.40.22 and then use unlocker v2.
Click to expand...
Click to collapse
man, a simple "yes" would have been easier to type and more polite.. of course, I've read it, same with all the threads here.. that's why I've seen a conflicting statement in the bootloader thread, hence the attempt to "clarify".. not everyone here is as good as you are.. thanks anyway..
great tool ! thanks
So im on v2.19.40.22 and ran Version 2
Phone rebooted went into stock recovery but it did nothing on there. The prompt on the PC said it was unlocked.
I manually rebooted my phone and the splashed looked the same.
Did i do something wrong?
Am i unlocked?
Can i verify if it's unlocked?
Thank You for you help.
Major
sorg said:
Now it's not required to flash/downgrade droidboot.img. But you still need to flash ROM not older than v2.19.40.18 for ZE551ML, and v2.19.40.12 for ZE550ML.
For example, you can flash full ROM v2.19.40.22 and then use unlocker v2.
Click to expand...
Click to collapse
Hello,
I am a little confused by these 2 lines.
The first line says:
But you still need to flash ROM not older than v2.19.40.18 for ZE551ML, and v2.19.40.12 for ZE550ML.
The second line says:
For example, you can flash full ROM v2.19.40.22 and then use unlocker v2.
So do I need a ROM no older than 2.19.40.18 or does 2.19.40.22 works fine?. As far as I know. 2.19.40.22 is older than 2.19.40.18.
Please clarify for me.
Thanks
Jeannette
V1 for anything under x.20
V2 for x.22
I think this is what it means but i may be wrong. Flash at your own risks
Sent from my ASUS_Z00AD using XDA Free mobile app
.18 is older than .22 I believe..
jeanne8fr said:
Hello,
I am a little confused by these 2 lines.
The first line says:
But you still need to flash ROM not older than v2.19.40.18 for ZE551ML, and v2.19.40.12 for ZE550ML.
The second line says:
For example, you can flash full ROM v2.19.40.22 and then use unlocker v2.
So do I need a ROM no older than 2.19.40.18 or does 2.19.40.22 works fine?. As far as I know. 2.19.40.22 is older than 2.19.40.18.
Please clarify for me.
Thanks
Jeannette
Click to expand...
Click to collapse
jarjarbingie said:
.18 is older than .22 I believe..
Click to expand...
Click to collapse
Which makes it even more confusing.
Why don't you say which rom we can use instead of which we cannot.
jeanne8fr said:
Which makes it even more confusing.
Why don't you say which rom we can use instead of which we cannot.
Click to expand...
Click to collapse
Because I've made unlocker not for one specific ROM version, but for any existing starting from .18 and newer.
.18 is older than .22, where is confusing?
I understand, that we live in time of smart phones and stupid people, but try to be on par with your phone at least. I've tried my best to explain in the OP what ROM versions you can use. I've made some bold text, some red text to take some attention. I've wrote example especially for .22 version! If it doesn't help, then i don't know what else can i do. How .18 cannot be obviously older than .22?
I've updated the OP, wrote compatible (as of today) versions. If even this is not clear enough, then i give up.
Awesome Work Mate. U ROCK!!!

[Q] How to Root?

Hi guys,
Anyone know a way to make root in Moto X Play it work?
Or can you use the method of CF-Root Moto X (2014)?
I did unlock the bootloader through the website of Motorola. It worked.
Tks.
(Sorry for my bad english)
Obs. ROOT process in post # 14
No TWRP/Root available as of yet. Give it some time, I guarantee you that XDA will basically be the first place it's posted when it happens. Keep in mind that the phone is just starting to roll out, but not in the US so it might take a while longer for somebody to get on it.
nourez said:
No TWRP/Root available as of yet. Give it some time, I guarantee you that XDA will basically be the first place it's posted when it happens. Keep in mind that the phone is just starting to roll out, but not in the US so it might take a while longer for somebody to get on it.
Click to expand...
Click to collapse
Tks nourez, In Brazil it was released on August 12. I'll wait longer.
lmsantiago said:
Hi everyone. ?Just a point: When doing 'Unlock the bootloader' for root ou flash custom roms, you agree to void your warranty.
Click to expand...
Click to collapse
Most people on this site could care less about warranty... Its a developer site after all
Sent from my Nexus 6 or Note 4
Even still, unless you REALLY screw something up, most of the time you can get away with it. (not sure how Moto X devices show the unlocked bootloader status and such).
....Note: Don't take that comment as fact. Your mileage may vary
Curious how developers figure out how to root. Is there something that's needed (besides having the phone, obviously), do we need kernel images from Motorola?
Devhux said:
Curious how developers figure out how to root. Is there something that's needed (besides having the phone, obviously), do we need kernel images from Motorola?
Click to expand...
Click to collapse
I don't have the device, so I won't be making a recovery for it, but it's not a particularly difficult process to make one. It took me around an hour to port TWRP to the 2015 Moto G, and it should be similar for this device. You can use a prebuilt kernel if sources are not available, but I think the 2015 Moto G kernel will actually work on this device. Moto will be releasing the proper kernel sources for this device soon anyway.
You just need to create a device tree and compile a recovery (such as TWRP). The recovery device tree doesn't need to be very thorough (the way ROM device trees are). It just needs to specify information about partition names and locations and kernel boot parameters etc. It should be a trivial modification to make my 2015 Moto G TWRP device tree work on this device.
Once you have a working recovery, just flash SuperSU with it and you'll be rooted.
squid2 said:
I don't have the device, so I won't be making a recovery for it, but it's not a particularly difficult process to make one. It took me around an hour to port TWRP to the 2015 Moto G, and it should be similar for this device. You can use a prebuilt kernel if sources are not available, but I think the 2015 Moto G kernel will actually work on this device. Moto will be releasing the proper kernel sources for this device soon anyway.
You just need to create a device tree and compile a recovery (such as TWRP). The recovery device tree doesn't need to be very thorough (the way ROM device trees are). It just needs to specify information about partition names and locations and kernel boot parameters etc. It should be a trivial modification to make my 2015 Moto G TWRP device tree work on this device.
Once you have a working recovery, just flash SuperSU with it and you'll be rooted.
Click to expand...
Click to collapse
This makes me happy and sad. Lol. Looking forward to root so I can drop DPI.
I would love to root it. I miss Viper4Android
Sent from my Golden Zenfone 2
I would love to root it too, I'm just wondering if we'll still have the possibility to install firmware upgrade if you root it and unlock the bootloader?
Nico3d3 said:
I would love to root it too, I'm just wondering if we'll still have the possibility to install firmware upgrade if you root it and unlock the bootloader?
Click to expand...
Click to collapse
A quick glance through the other Moto forums here on XDA would give us a good clue. I'm too tired to check at the moment, but if nobody else does by the time I wake up, I'll check then.
Good News! My Moto x play is rooted with the Moto G 2015 method.
Below process we did and it worked:
1- Through the forum: http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
I downloaded "TWRP-osprey-2.8.7-test1.img"
2 UPDATE-SuperSU-v2.46.zip downloaded at: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
[Copy to your internal SDcard]
3 Place your Moto-x in fastboot mode [Power + Vol. down]
3- install TWRP-osprey-2.8.7-test1.img with the command: fastboot boot TWRP-osprey-2.8.7-test1.img
[Installation is temporary, I tried to permanently install but did not work].
4. The recovery will open automatically, browse to the location where you saved the SuperSU and flash UPDATE-SuperSU-v2.46.zip
5. Restart.
I did this procedure and managed to get root, I'm not responsible for any damage caused to your phone.
Did you have to unlock bootloader before installing it? On my phone, I have an unlocked bootloader and it did work but perhaps people would be interested in trying it with a locked bootloader (less risk of voiding the warranty).
Nico3d3 said:
Did you have to unlock bootloader before installing it? On my phone, I have an unlocked bootloader and it did work but perhaps people would be interested in trying it with a locked bootloader (less risk of voiding the warranty).
Click to expand...
Click to collapse
My bootloader is also unlocked.
I believe you can not do without unlocking the OEM. since it would not be possible to install recovery.
If someone is on a locked bootloader and want to test, we can see if it works. But I believe that is not possible.
I'll gladly test it with a locked bootloader when I get home in a few hours, if it hasn't already been tested by then.
Just tried it with locked bootloader, no joy. Device downloads the boot.IMG but errors booting it and just stays in bootloader mode. Guessing needs the bootloader unlocking first.
Sent from my Nexus 9 using XDA Premium HD app
Good to know. Thanks @CharlesW123 for checking!
Anybody know if we are able to flash a logo to replace the unlocked bootloader warning on the X Play yet?
Sevael said:
Good to know. Thanks @CharlesW123 for checking!
Anybody know if we are able to flash a logo to replace the unlocked bootloader warning on the X Play yet?
Click to expand...
Click to collapse
Yep the method shown here does work on the Moto X Play, you will get back to the normal boot logo.
has anyone tested installing Xposed after rooting yet? I'm assuming the same procedure should work (fastboot boot recovery.img > flash xposed.zip)?
nourez said:
has anyone tested installing Xposed after rooting yet? I'm assuming the same procedure should work (fastboot boot recovery.img > flash xposed.zip)?
Click to expand...
Click to collapse
The Xposed is a .zip file, you need to install the TWRP via flash.
But still I am not the courage to try. I have no backup ROM error.

No IMEI, bootloader locked, no root, no sim working

Hi,
I have an EU G7 L01, followed this guy's tutorial (http://ministryofsolutions.com/2016...ade-marshmallow-europe-asia.html#comment-2438) to update to marshmallow, replacing the "oeminfo" file with a turkish version, to trick the phone into updating. The new file had no IMEI in it, and after the update I was left with a locked bootloader, no root and no way to replace that file with my backup, to make the phone accept the sim card. From what I see, I'm either left with a small tablet or I have to replace the motherboard to make it work again.
Any other ideas would be appreciated.
swangoose said:
Hi,
I have an EU G7 L01, followed this guy's tutorial (http://ministryofsolutions.com/2016...ade-marshmallow-europe-asia.html#comment-2438) to update to marshmallow, replacing the "oeminfo" file with a turkish version, to trick the phone into updating. The new file had no IMEI in it, and after the update I was left with a locked bootloader, no root and no way to replace that file with my backup, to make the phone accept the sim card. From what I see, I'm either left with a small tablet or I have to replace the motherboard to make it work again.
Any other ideas would be appreciated.
Click to expand...
Click to collapse
To get your device to its original state, you need to downgrade to B340 of the Turkish firmware: http://download-c.huawei.com/download/downloadCenter?downloadId=74865&version=273720&siteCode=tr
Do a forced update with B340, root the device using Kingroot, replace your original oeminfo file, then install the official EU firmware.
If you really want to use marshmallow, then the only way will be to pay for your bootloader to be unlocked. On the source post, it clearly states that there was a problem with unlocking the bootloader, and HCU Client should be used to unlock it. The problem with that guide is that the bootloader unlock code only works a certain amount of tries before it becomes unusable, and the only way to replace your original oeminfo file is to have root, which is only possible on marshmallow with an unlocked bootloader.
I would suggest you let the guy who wrote the article know about your issue. Regardless of whether he stated that it is done at your own risk, he either needs to amend his article to that of the source, or remove it completely, as many people will not be able to pay $5 to get the bootloader unlock code.
Good luck!
miz_pimp said:
To get your device to its original state, you need to downgrade to B340 of the Turkish firmware: http://download-c.huawei.com/download/downloadCenter?downloadId=74865&version=273720&siteCode=tr
Do a forced update with B340, root the device using Kingroot, replace your original oeminfo file, then install the official EU firmware.
If you really want to use marshmallow, then the only way will be to pay for your bootloader to be unlocked. On the source post, it clearly states that there was a problem with unlocking the bootloader, and HCU Client should be used to unlock it. The problem with that guide is that the bootloader unlock code only works a certain amount of tries before it becomes unusable, and the only way to replace your original oeminfo file is to have root, which is only possible on marshmallow with an unlocked bootloader.
I would suggest you let the guy who wrote the article know about your issue. Regardless of whether he stated that it is done at your own risk, he either needs to amend his article to that of the source, or remove it completely, as many people will not be able to pay $5 to get the bootloader unlock code.
Good luck!
Click to expand...
Click to collapse
So, are you saying that I will be able to root without unlocked bootloader?
Thx!
swangoose said:
So, are you saying that I will be able to root without unlocked bootloader?
Thx!
Click to expand...
Click to collapse
Only when downgrading back to the Turkish B340 Lollipop, using Kingroot.
miz_pimp said:
Only when downgrading back to the Turkish B340 Lollipop, using Kingroot.
Click to expand...
Click to collapse
Yey, my IMEI is back, thx a lot!
You're welcome! Glad I could help! ☺

Bootloader unlock without unlock code from Huawei

Is it possible to unlock the bootloader without the unlock code coming from Huawei itself?
I want to unlock the bootloader. Many pages on the web (and on this forum as well) say I need to get the unlock code from huawei, but... it seems that huawei is not collaborative any more: Honor/Huawei’s bootloader unlock page disappears with no explanation
Can I work it out without the code?
Actually, what I really want to do is...
Actually, what I really want to do is...: install a different firmware.
I'm a real noob in the world of modding & custom rom.
As far as I understand, unlocking bootloader is required in order to install a different ROM: is it right? or can I install it somehow even with bootloader locked? Also, can I root the P8 without unlocking the bootloader?
My P8 is on the latest firmware I recently received OTR from Huawei: GRA-L09C02B405. The phone is starting to have some problems: hight battery drenage, UI freezing and rebooting from time to time.
I'd like to install a previous version of Huawei official firmware, or different a custom ROM (I read about some of them in this forum: any suggestion?). But as far a I understand, unlocking bootloader is required, and it seems that without the code from Huawei I'm blocked
Ik zit met de zelfde vraag, ook mijn P8 kan ik niet unlocken website van Huawei met deze optie is verdwenen.
I have the same question, also my P8 I can't unlock Huawei's website with this option is gone.
You now have to contact Huawei and request it, providing IMEI, SN, Product Code, Model, and reason why you wish to unlock it.
Here is a link to contact the UK (most people say this is more successful than others) :- https://consumer.huawei.com/uk/contact-us/
Thanks @Sparkrite, I will try that way.
Can you help me also with my second post in this thread? I mean, do I have to unlock the bootloader in order to flash a custom rom and / or to root the phone?
ModNoob33 said:
Thanks @Sparkrite, I will try that way.
Can you help me also with my second post in this thread? I mean, do I have to unlock the bootloader in order to flash a custom rom and / or to root the phone?
Click to expand...
Click to collapse
For both, yes, you need to unlock your phone. For rooting, you have to flash a new boot.img, and for a custom ROM you have to flash the system.img too.
Without the unlocked bootloader you are unable to flash the images /partitions
ModNoob33 said:
Thanks @Sparkrite, I will try that way.
Can you help me also with my second post in this thread? I mean, do I have to unlock the bootloader in order to flash a custom rom and / or to root the phone?
Click to expand...
Click to collapse
For both NO, however it tends to be a bit easier if the bootloader is unlocked. Some third party rooting apps may or may not work, depending on what version OS you have installed, without changing the recovery partition.
However it is usually easier to root by flashing with TWRP etc. which necessitates an unlocked bootloader to allow you to flash the said recovery.img and then flashing SU.zip for example.
The same goes for flashing a system.img ( does not need an unlocked bootloader ) eg. use fastboot mode and an ADB shell or even DLOAD if it has the correct signatures. The caveat is that most if not all custom ROMs use a proprietary boot.img so an unlocked BL will be required in this case.
Hope that clears it up for you.
Sparkrite said:
For both NO, however it tends to be a bit easier if the bootloader is unlocked. Some third party rooting apps may or may not work, depending on what version OS you have installed, without changing the recovery partition.
However it is usually easier to root by flashing with TWRP etc. which necessitates an unlocked bootloader to allow you to flash the said recovery.img and then flashing SU.zip for example.
The same goes for flashing a system.img ( does not need an unlocked bootloader ) eg. use fastboot mode and an ADB shell or even DLOAD if it has the correct signatures. The caveat is that most if not all custom ROMs use a proprietary boot.img so an unlocked BL will be required in this case.
Hope that clears it up for you.
Click to expand...
Click to collapse
Isn't it? Oh, damn, all time I thought it necessary to do this. Sorry
Sparkrite said:
For both NO, however it tends to be a bit easier if the bootloader is unlocked. Some third party rooting apps may or may not work, depending on what version OS you have installed, without changing the recovery partition.
However it is usually easier to root by flashing with TWRP etc. which necessitates an unlocked bootloader to allow you to flash the said recovery.img and then flashing SU.zip for example.
The same goes for flashing a system.img ( does not need an unlocked bootloader ) eg. use fastboot mode and an ADB shell or even DLOAD if it has the correct signatures. The caveat is that most if not all custom ROMs use a proprietary boot.img so an unlocked BL will be required in this case.
Hope that clears it up for you.
Click to expand...
Click to collapse
I asked Huawei for the code, now I'm waiting for reply.
So, if I understand correctly, even without unlocking bootloader I should be able to flash a previous version of an official firmware, ain't it? I can consider that option if I don't get the code from Huawei
Thanks a lot, you are being really helpful
Bootloader unlocking is not needed for upgrading official firmware, unfortunately, normally it is a completely different matter when trying to downgrade .
Sparkrite said:
Bootloader unlocking is not needed for upgrading official firmware, unfortunately, normally it is a completely different matter when trying to downgrade .
Click to expand...
Click to collapse
So, it seems that I really need Huawei help to do something more or less useful for me. They made something such a "unhackable" phone which can be hacked only with their support. And more or less every other vendor I assume.
Quite weird I think.
AFAIK Huawei are/were the only vendors that made it so easy to unlock the BL, esp. when their code generator was online.
Have you heard back from them yet, some people report getting the code within 12 hours ?
Sparkrite said:
AFAIK Huawei are/were the only vendors that made it so easy to unlock the BL, esp. when their code generator was online.
Have you heard back from them yet, some people report getting the code within 12 hours ?
Click to expand...
Click to collapse
I got a first mail the day after I wrote, with them asking to add the reason for the code request.
This morning I answered them them that I wanted to play with root rights & custom rom, and that I was aware of the risks implied.
now (6 hours later) they sent me the code.
Quite a good support I'd say
ModNoob33 said:
I got a first mail the day after I wrote, with them asking to add the reason for the code request.
Click to expand...
Click to collapse
Yes indeed, the reason why, as I said in my first post, wonder why they're interested ?
Sparkrite said:
You now have to contact Huawei and request it, providing IMEI, SN, Product Code, Model, and reason why you wish to unlock it.
Click to expand...
Click to collapse
Any way you have it now, I assume it worked OK.
The product id in a custom firmware is the same as de original firmware?
i use this method to see product id *#*#1357946#*#* but in a custom firmware,because i lost the code but only want to save it,try the unlock page but i dont get code only errors.
Cientista2018 said:
The product id in a custom firmware is the same as de original firmware?
i use this method to see product id *#*#1357946#*#* but in a custom firmware,because i lost the code but only want to save it,try the unlock page but i dont get code only errors.
Click to expand...
Click to collapse
Try here for your product code :- www.imei24.com
well they dont give anymore codes for bootloader... my huawei p8 lite RIP
djokagg said:
well they dont give anymore codes for bootloader... my huawei p8 lite RIP
Click to expand...
Click to collapse
u sure there's absolutely no way?
AcidCat said:
u sure there's absolutely no way?
Click to expand...
Click to collapse
i'm struggling with the same issue. UK support doesn't want to give me the unlock code even if my P8Max is blocked on all google related stuff. I can't even get Google services
after the last OTA update ( DAV-703LC233B226 ) installed anymore. But still they persist that I should send back the unit ...
You can unlock your bootloaders by using DC Unlocker.

Look and unlock bootloader with official method

In other posts there is procedure , for device with bootloader unlocked with unofficial method, for look and unlook officially, but is confused and in other arguments.
Is possible have this post for this argument, with clear guide , because I think is important question.
This maybe procedure:
1. miflash to official China Beta rom first. Flash without relock.
1b. Download from PC VPN app, install on phone and set connection to China. Then you are able to active usb developer options
2. re-lock bootloader with official China Beta rom. Flash and relock.
3. unlock bootloader again with official China Beta rom. Need to tie up with Mi account and insert a SIM card. For me, need to wait for 720 hours before MM3 can be unlocked. I checked chinese miui forum. This apparently is a new requirement. One full month later. Gosh...
4. miflash to official Global rom and stop there.
5. Do not re-lock bootloader with official Global rom""
I don't try this procedure......
What's the point of looking the bootloader just to get it unlocked again after whatever hours waiting!?
Do you experience problems with the device being unlocked unofficialy? Or this is just another "good advice/info" coming from MIUI forums...
Be happy somebody already took care of that and enjoy the unlocked bootloader freedom you get.
nijel8 said:
What's the point of looking the bootloader just to get it unlocked again after whatever hours waiting!?
Do you experience problems with the device being unlocked unofficialy? Or this is just another "good advice/info" coming from MIUI forums...
Be happy somebody already took care of that and enjoy the unlocked bootloader freedom you get.
Click to expand...
Click to collapse
The device comes unlocked but your Mi account has not permission to unlock this specific device because you never followed the official unlock procedure.
Xiaomi with its new policy does not let you use a Chinese version of a phone with a global rom and a locked bootloader. If you flash the global rom and for some reason the bootloader gets locked, your phone will stuck on the recovery with the following message "this miui version cannot be installed on this device", at this stage you must unlock the bootloader to be able to boot again, if the bootloader was unlocked officialy with you own account, you can use the mi unlock tool to unlock again and make the phone bootable, if the bootloader was unofficialy unlocked or unlocked by other account, in this case you can't unlock with the Mi unlock tool, you can't flash another rom since the bootloader is locked, you can't follow the official unlock procedure because you are stuck in recovery, the only solution is to use the test point method with EDL authorized account
Ok, I guess sounds reasonable for majority of the users.
But me personally? I could care less...
You can backup bootloader unlocked status and restore it if locked by accident...
panospc said:
The device comes unlocked but your Mi account has not permission to unlock this specific device because you never followed the official unlock procedure.
Xiaomi with its new policy does not let you use a Chinese version of a phone with a global rom and a locked bootloader. If you flash the global rom and for some reason the bootloader gets locked, your phone will stuck on the recovery with the following message "this miui version cannot be installed on this device", at this stage you must unlock the bootloader to be able to boot again, if the bootloader was unlocked officialy with you own account, you can use the mi unlock tool to unlock again and make the phone bootable, if the bootloader was unofficialy unlocked or unlocked by other account, in this case you can't unlock with the Mi unlock tool, you can't flash another rom since the bootloader is locked, you can't follow the official unlock procedure because you are stuck in recovery, the only solution is to use the test point method with EDL authorized account
Click to expand...
Click to collapse
But the procedure in first post, work in unofficial unlocked bootloader ?
If yes, after I am able to install global fastboot ROM when will be available ?
lucaxxaa said:
But the procedure in first post, work in unofficial unlocked bootloader ?
If yes, after I am able to install global fastboot ROM when will be available ?
Click to expand...
Click to collapse
My brother's Mi Max 3 came with unlocked bootloader, I just flashed china stable with clean and lock without problems.
I have seen some reports of bricked devices from people who tried to flash and lock, honestly, I do not know what went wrong in their case.
nijel8 said:
You can backup bootloader unlocked status and restore it if locked by accident...
Click to expand...
Click to collapse
Does this involves EDL mode?
As far as I know, EDL mode is locked on newer xiaomi devices.
Check this thread for more info https://www.reddit.com/r/Xiaomi/comments/98jr79/psa_a_potential_fix_for_flashing_in_edl_mode/
panospc said:
...
Does this involves EDL mode?
As far as I know, EDL mode is locked on newer xiaomi devices.
Check this thread for more info https://www.reddit.com/r/Xiaomi/comments/98jr79/psa_a_potential_fix_for_flashing_in_edl_mode/
Click to expand...
Click to collapse
It requires either root or EDL or TWRP...
And no, EDL is not locked, it's not Xiaomi's feature to lock it, it's Qualcomm business... MiFlash is locked which is irrelevant... Who needs their stupid front end when you can use Qualcomm tools...
nijel8 said:
Who needs their stupid front end when you can use Qualcomm tools...
Click to expand...
Click to collapse
Quote from the link a gave you
Users have been experimenting with older versions of MiFlash as well as Qualcomm's official flashing tool QFIL, but to no avail, they couldn't flash in EDL because the programs could not bypass the requirement for authentication.
Click to expand...
Click to collapse
Is this irrelevant?
panospc said:
Quote from the link a gave you
Is this irrelevant?
Click to expand...
Click to collapse
Maybe, we are not talking QFIL and flashing roms here. Will let you know when I get my Max 3 and test it.
your help is highly appreciated
panospc said:
The device comes unlocked but your Mi account has not permission to unlock this specific device because you never followed the official unlock procedure.
Xiaomi with its new policy does not let you use a Chinese version of a phone with a global rom and a locked bootloader. If you flash the global rom and for some reason the bootloader gets locked, your phone will stuck on the recovery with the following message "this miui version cannot be installed on this device", at this stage you must unlock the bootloader to be able to boot again, if the bootloader was unlocked officialy with you own account, you can use the mi unlock tool to unlock again and make the phone bootable, if the bootloader was unofficialy unlocked or unlocked by other account, in this case you can't unlock with the Mi unlock tool, you can't flash another rom since the bootloader is locked, you can't follow the official unlock procedure because you are stuck in recovery, the only solution is to use the test point method with EDL authorized account
Click to expand...
Click to collapse
that is exactly what just has happens with me few minutes ago.
I bought the MAX3 through Ali Express with "fake" global Rom, and open bootloader, however since the global ROM is officially released by Xiaomi so I was trying to flash it through XiaomiFalsh but, mistakenly, and unfortunately, I kept the tick mark on "clean all and lock" and now the phone is stuck on recovery, I called the service center of Xiaomi by they said since it is not officially announced in my country so it is not their baby and they asked me to contact the seller "who ali experess! no way!!"
guys who can help me to get out of this issue will be really appreciated, but keep in mind I'm not an expert.
awaiting your kindness
maherd said:
that is exactly what just has happens with me few minutes ago.
I bought the MAX3 through Ali Express with "fake" global Rom, and open bootloader, however since the global ROM is officially released by Xiaomi so I was trying to flash it through XiaomiFalsh but, mistakenly, and unfortunately, I kept the tick mark on "clean all and lock" and now the phone is stuck on recovery, I called the service center of Xiaomi by they said since it is not officially announced in my country so it is not their baby and they asked me to contact the seller "who ali experess! no way!!"
guys who can help me to get out of this issue will be really appreciated, but keep in mind I'm not an expert.
awaiting your kindness
Click to expand...
Click to collapse
Apply for unlock bootloader here: https://en.miui.com/unlock/
Wait time is 720 hours. No other way around it. Sorry, buddy.
opasha said:
Apply for unlock bootloader here: https://en.miui.com/unlock/
Wait time is 720 hours. No other way around it. Sorry, buddy.
Click to expand...
Click to collapse
There is no way to apply for unlock without a bootable phone, He must go to Developer options -> Mi Unlock status -> Add account and device but this is not possible because the phone is stuck in recovery.
The only solution right now is to use the test-point method to flash the chinese rom.
panospc said:
There is no way to apply for unlock without a bootable phone, He must go to Developer options -> Mi Unlock status -> Add account and device but this is not possible because the phone is stuck in recovery.
The only solution right now is to use the test-point method to flash the chinese rom.
Click to expand...
Click to collapse
Someone I helped fastboot flash China 8.8.9 mistakenly did this and was able to boot. Is Global rom entirely different in this situation?
opasha said:
Someone I helped fastboot flash China 8.8.9 mistakenly did this and was able to boot. Is Global rom entirely different in this situation?
Click to expand...
Click to collapse
Yes, it's different
chinese device + global rom + locked bootloader = stuck in recovery
Check my previous post here https://forum.xda-developers.com/showpost.php?p=77574305&postcount=3
panospc said:
Yes, it's different
chinese device + global rom + locked bootloader = stuck in recovery
Check my previous post here https://forum.xda-developers.com/showpost.php?p=77574305&postcount=3
Click to expand...
Click to collapse
Oh right, now I remember. This was that very big announcement. Completely forgot. Thanks for the reminder. Yes, then test point is the only option, unfortunately.
Again, this was why I urged people to steer clear of global and stick to Eu roms. More harm than good especially related to such situations (many new flashers accidentally locking bootloaders).
panospc said:
There is no way to apply for unlock without a bootable phone, He must go to Developer options -> Mi Unlock status -> Add account and device but this is not possible because the phone is stuck in recovery.
The only solution right now is to use the test-point method to flash the chinese rom.
Click to expand...
Click to collapse
Thank you so much guys for your feedback, for now I have the flowing questions:
1- the phone is stuck in recovery mode, how I shutdown the phone.
2- If I wait for Xiaomi to launch MAX3 officially in y country do you think they will be able to help me even with charged service?
3- can any of you expert guys direct me to some useful link to see how do it use the test-point method.
4- If I succeeded to unlock the bootloader through the test-point method, is it mandatory to flash the Chinese version or I can flash global Rom and keep the bootloader unlocked.
thank you in advance for your time.
maherd said:
Thank you so much guys for your feedback, for now I have the flowing questions:
1- the phone is stuck in recovery mode, how I shutdown the phone.
2- If I wait for Xiaomi to launch MAX3 officially in y country do you think they will be able to help me even with charged service?
3- can any of you expert guys direct me to some useful link to see how do it use the test-point method.
4- If I succeeded to unlock the bootloader through the test-point method, is it mandatory to flash the global Rom and keep the bootloader unlocked.
thank you in advance for your time.
Click to expand...
Click to collapse
1. Hold power and volume down until boots to fastboot mode, leave it and it should turn off automatically after few seconds.
3. You can find some information scattered to the following threads
https://en.miui.com/forum.php?mod=viewthread&tid=3667214
https://en.miui.com/thread-3765172-1-1.html
https://forum.xda-developers.com/mi-max-3/help/guess-somewhat-kinda-bricked-nitrogen-t3848922
https://forum.xda-developers.com/mi-max-3/help/help-mi-max-3-hard-bricked-anti-roll-t3834769
How to take apart Mi Max 3 https://www.youtube.com/watch?v=aQhhbzQ6l2s (check from 0:00 to 3:00 minute)
Click to expand...
Click to collapse
4. With the test-point method you can flash the chinese rom even if the bootloader is locked, after succesfully flashing the china rom you have to apply for official unlock, after getting the unlock permission you can flash global rom by leaving the bootloader unlocked.
XiaomiTool official page is proposing another solution but you need to wait for a global dev rom to be released and it is not guaranteed to work
If you get the message "this miui can't be installed on this device" and your device is bricked you might be able to recover it using xiaomiadb by first installing global developer and then installing china developer OF SAME VERSION (for example 8.8.16->8.8.16) using "xiaomiadb sideload_miui -otarom CurrentRom [ZIP_ROM_FILE]"
Click to expand...
Click to collapse
hello all, if someone can help me, i have my mi max3 with locked bootloader.
now i dont have any rom on it so trying to load a rom but getting an error ERASE is not allowed in locked state
what rom can i flash on it ?
tried to unlock bootloader via the tool, it gets stuck at 50% cannot verify phone.
had the same problem, was able to recover it with the test point method and flashing chinese rom, and switching to english language.
the procedure is described here:
https://androidfilebox.com/tips/edl-test-point-mode-redmi-note-4x/
the installation process of the qualcom drivers is special.
you have to open te backcover, which is very special too, dont forget to the 2 mini screws at the usb port and the drawer on the side . search and look on youtube.
look further, where the testpoints are on the mi max3
follow strictly the procedure, load and double extract the chinese rom for the mi max 3.
It is real work, and real danger that you break something mechanical, one shoud have a calm hand and a lot of patience, but for me all went good and the phone spang to live again.
Another solution could be this, but I have no experience with it:
https://s-unlock.com/productsandservices/server

Categories

Resources