Hi!
Today I tried for a few hours the official bootloader unlock method and I never succeded, or so it seems???
I always got stuck at 50% and never reached 100%.... But once I was in fastboot after trying for a few hours I could see that the bootloader was unlocked by typing
fastboot oem device-info
So can I in some way see if the device is unlocked by the official method, or that I actually got it unofficial unlocked from the seller (geekbuying).
More than likely it is unofficial unlocked by your seller.
Check you MIUI Version: - Settings - About Phone - MIUI Version
Report what you find there, you may also have a vendor rom!
corkiejp said:
More than likely it is unofficial unlocked by your seller.
Check you MIUI Version: - Settings - About Phone - MIUI Version
Report what you find there, you may also have a vendor rom!
Click to expand...
Click to collapse
MIUI Global 8.0 Stable 8.0.1.0.0 (LHOCNDG)
Are you sure? Cause it might have still "worked" while I was testing... If it helps to answer the question MI Unlock says "Couldn't verify device - No need to unlock this device"
katolo said:
MIUI Global 8.0 Stable 8.0.1.0.0 (LHOCNDG)
Are you sure? Cause it might have still "worked" while I was testing... If it helps to answer the question MI Unlock says "Couldn't verify device - No need to unlock this device"
Click to expand...
Click to collapse
It is a Vendor Rom!
Official roms come with four numbers (x.x.x.x)!
And since you can only unlock the bootloader on official roms. It has definitely been unlocked by the unofficial method.
Vendor roms may come with spyware/adware, so I would advise you to flash an official rom as soon as possible.
As your unlocked unofficially take care how you flash roms.
If you flash the latest Marshmallow roms, your bootloader may be locked again.
See the linked wiki above and read some of the threads here.
corkiejp said:
It is a Vendor Rom!
Official roms come with four numbers (x.x.x.x)!
And since you can only unlock the bootloader on official roms. It has definitely been unlocked by the unofficial method.
Vendor roms may come with spyware/adware, so I would advise you to flash an official rom as soon as possible.
As your unlocked unofficially take care how you flash roms.
If you flash the latest Marshmallow roms, your bootloader may be locked again.
See the linked wiki above and read some of the threads here.
Click to expand...
Click to collapse
Ok. Thanks.. But what would you recommend? I want to unlock the offical way. So should I flash the Marshmallow rom and let it lock and I unlock via the official?
@katolo That is a good question, which I don't have an answer for.
It may work, but also you may end up with a device you can not unlock officially.
See here :- https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
And this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Flash Alka TWRP and make backup of all partitions first.
corkiejp said:
@katolo That is a good question, which I don't have an answer for.
It may work, but also you may end up with a device you can not unlock officially.
See here :- https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
And this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Flash Alka TWRP and make backup of all partitions first.
Click to expand...
Click to collapse
Just for info for other people... I just flashed the MIUI Global DEV ROM and went into fastboot and checked the bootloader and now it is LOCKED again.
Now I will try to unlock it officially. Crappy geekbuying putting ****ty ROM on phone..
Thanks for the help.
katolo said:
Hi!
Today I tried for a few hours the official bootloader unlock method and I never succeded, or so it seems???
I always got stuck at 50% and never reached 100%.... But once I was in fastboot after trying for a few hours I could see that the bootloader was unlocked by typing
fastboot oem device-info
So can I in some way see if the device is unlocked by the official method, or that I actually got it unofficial unlocked from the seller (geekbuying).
Click to expand...
Click to collapse
corkiejp said:
@katolo That is a good question, which I don't have an answer for.
It may work, but also you may end up with a device you can not unlock officially.
See here :- https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
And this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Flash Alka TWRP and make backup of all partitions first.
Click to expand...
Click to collapse
Just got to be a bit careful here. I'd recommend flashing "Safe TWRP" recovery once you have backed up all your partitions with alka TWRP.
@katolo Report back if you can successfully unlock by the official method.
Plenty of threads here on the steps required to do so.
corkiejp said:
@katolo Report back if you can successfully unlock by the official method.
Plenty of threads here on the steps required to do so.
Click to expand...
Click to collapse
Worked perfectly. Thanks for the help.
I'm on MM MIUI now... Will flash ALKA TWRP > FULL BACKUP > CM13 (goodix) then I'm set...
Jeanz Sensation said:
Just got to be a bit careful here. I'd recommend flashing "Safe TWRP" recovery once you have backed up all your partitions with alka TWRP.
Click to expand...
Click to collapse
Can I use Safe TWRP to flash CM13/CM14 and MIUI roms?
What is the difference between ALKA and SAFE TWRP?
katolo said:
Can I use Safe TWRP to flash CM13/CM14 and MIUI roms?
What is the difference between ALKA and SAFE TWRP?
Click to expand...
Click to collapse
If your bootloader is unlocked officially then you can use either of the recoveries. But if the bootloader has been unlocked unofficially then strictly use SAFE TWRP if you are flashing MIUI ROM.
The main difference between SAFE and Alka is that Alka gives you the option to backup few more partitions within the phone's memory as compared to SAFE. Bear in mind that these extra partitions may not be necessary for you to backup, hence eliminating the need for Alka recovery at all.
Jeanz Sensation said:
If your bootloader is unlocked officially then you can use either of the recoveries. But if the bootloader has been unlocked unofficially then strictly use SAFE TWRP if you are flashing MIUI ROM.
The main difference between SAFE and Alka is that Alka gives you the option to backup few more partitions within the phone's memory as compared to SAFE. Bear in mind that these extra partitions may not be necessary for you to backup, hence eliminating the need for Alka recovery at all.
Click to expand...
Click to collapse
Ok. Thanks.
I was unofficially unlocked. But after I flashed MIUI via edl method it got locked again. So then I officially unlocked it.
I guess I can keep alka then. Or?
Sent from my Redmi Note 2 using XDA-Developers mobile app
Related
Hello, various posts say kenzo roms could be used on kate, but without modem files. Many users already tried flashing manually modified roms, bricking or having issues. Is there a full tutorial to how effectively:
- unlock bootloader (only unofficial way for what i understand...)
- root the phone (only flashing supersu via TWRP? what version of TWRP?)
- possibly modify existent kenzo roms to use them on kate (not only CM.... there are so many roms with various kernels too...are they working without problems on kate?)
so far i've been scouring the net for any possible guide, but there are really few to none specific for kate, and none answering clearly the previous questions....and i am sure i'm not alone as more and more people are buying right now the international version, and keep asking the same questions. Could somebody shed a light? thanks.
Following this thread. I bought international version and can't wait to flash CM
Inviato dal mio MI 2S utilizzando Tapatalk
You need to unlock bootloader and then flash TWRP. Once that's done all you need to do is flash CM13, CM13Firmware, Opengapps ARM64 and modem file for Kate (NON-HLOS from fastboot of MIUI8 Kate). Also can flash latest SuperSU for root.
To flash modem once CM13 is installed boot fastboot and then enter:
fastboot flash modem NON-HLOS.bin
Full guide
Is it possible to just install twrp and supersu and use miui roms?
http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
I wish there was a TWRP specifically for "kate" though. Because TWRP will think "kate" is "kenzo" for now.
is its possible to unlock the Kate version on the official way? Because in the Guide from Xiaomi ist the Point "You must on China Dev Firmware" but this versions isnt available for the kate version?
dadonali said:
is its possible to unlock the Kate version on the official way? Because in the Guide from Xiaomi ist the Point "You must on China Dev Firmware" but this versions isnt available for the kate version?
Click to expand...
Click to collapse
Until today, no one confirmed to have had success with official unlock. Even though it should be possible to unlock with the Mi Flash Unlock tool on every ROM, it is very likely that it can only reliable unlock when using a Chinese Developer ROM, which doesn't exist for Kate.
Most people are getting an error message in the above utility, saying that the MI account in the phone and the one used in the utility don't match, even if they do.
DPyro said:
Full guide
Click to expand...
Click to collapse
You found my guide.
Is there any good reason to wait for a reliable way to officially unlock the bootloader? Or any downside to go with the unofficial unlock method?
I got my phone yesterday and just found out today I actually had the Kate version. I don't really plan on going back to MIUI and from what I understand, the official unlock method would only make it easier to switch back to MIUI. Is that right?
(It's not my first time playing with custom ROMs, I have flashed multiple roms / kernels in the past but I always owned Nexus phones and it was quit dummy proof on these phones.)
BigBlarg said:
I don't really plan on going back to MIUI and from what I understand, the official unlock method would only make it easier to switch back to MIUI. Is that right?
Click to expand...
Click to collapse
That's my understanding, yes. Interestingly, when I had a Kenzo and unlocked it officially, the bootloader got relocked whenever I flashed something like CM. With Kate (unofficially unlocked), the bootloader wasn't relocked after flashing CM. In that sense, unlocking it via unofficial means may be advantageous.
Pumpino said:
That's my understanding, yes. Interestingly, when I had a Kenzo and unlocked it officially, the bootloader got relocked whenever I flashed something like CM. With Kate (unofficially unlocked), the bootloader was relocked after flashing CM. In that sense, unlocking it via unofficial means may be advantageous.
Click to expand...
Click to collapse
Thanks Pumpino!
I just followed your guide and successfully flashed CM 13 stable release without any issue.
It's only been a few minutes but everything seems to be working (much better than MIUI) so far.
BigBlarg said:
Thanks Pumpino!
I just followed your guide and successfully flashed CM 13 stable release without any issue.
Click to expand...
Click to collapse
You're welcome. I'm glad it went smoothly.
I've just edited my previous post, as "was" should have said "wasn't". ie. "With Kate (unofficially unlocked), the bootloader wasn't relocked after flashing CM."
Followed the guide and can't get the bootloader to unlock. Any ideas?
Downloaded the updated/modified emmc_appsboot.mbn, put it into the rom folder and flashed fine. Won't unlock.
BobSlob said:
Followed the guide and can't get the bootloader to unlock. Any ideas?
Downloaded the updated/modified emmc_appsboot.mbn, put it into the rom folder and flashed fine. Won't unlock.
Click to expand...
Click to collapse
I made a mistake at this part and it wouldn't allow me to unlock the bootloader. The guide to unlock the bootloader doesn't explicitly mention one important detail. In the screen where you have to allow USB debugging, you must also enable the option saying "Allow OEM unlock" or something like that. I didn't enable that option at first and in fastboot it would tell me I was not allowed to unlock the bootloader. So I had to reboot the phone normally, go through all the MIUI setup and finally re-enable USB Debugging and enable "Allow OEM unlock".
BigBlarg said:
I made a mistake at this part and it wouldn't allow me to unlock the bootloader. The guide to unlock the bootloader doesn't explicitly mention one important detail. In the screen where you have to allow USB debugging, you must also enable the option saying "Allow OEM unlock" or something like that. I didn't enable that option at first and in fastboot it would tell me I was not allowed to unlock the bootloader. So I had to reboot the phone normally, go through all the MIUI setup and finally re-enable USB Debugging and enable "Allow OEM unlock".
Click to expand...
Click to collapse
You sir are my hero! That was the issue. Many thanks.
One other question, when flashing the rom is it safe to put it on the SD card, or does it need to be on internal?
BigBlarg said:
The guide to unlock the bootloader doesn't explicitly mention one important detail. In the screen where you have to allow USB debugging, you must also enable the option saying "Allow OEM unlock".
Click to expand...
Click to collapse
Good point, although on mine, "Allow OEM Unlocking" was enabled by default. I used the developer ROM. Is it possible that it's not enabled by default on the stable ROM?
BobSlob said:
One other question, when flashing the rom is it safe to put it on the SD card, or does it need to be on internal?
Click to expand...
Click to collapse
Yes, totally safe. That's how I did it and that's also how I flashed multiple other Android devices using TWRP. Never had any issue putting the ROMs on the SD card.
Pumpino said:
Good point, although on mine, "Allow OEM Unlocking" was enabled by default. I used the developer ROM. Is it possible that it's not enabled by default on the stable ROM?
Click to expand...
Click to collapse
I did use the stable ROM, so that could explain it.
Alright, another problem. TWRP (tried a few versions) is unable to mount and wipe any partitions... any ideas? =P
Edit "Cofface TWRP Fix" as linked in the guide boot loops me
BobSlob said:
Alright, another problem. TWRP (tried a few versions) is unable to mount and wipe any partitions... any ideas? =P
Edit "Cofface TWRP Fix" as linked in the guide boot loops me
Click to expand...
Click to collapse
Did you try flashing first the Safe TWRP?
Seems the standard TWRP worked fine, disaster avoided
Hi people,
I just bought a new Redmi note 3, and I would like to pass him into cyanogenmod.
Here what i'm attending to do.
Safe the stock room
unlock the bootloader (unofficialy)
root the phone
install the CyanogenMod
1 : For doing the backup I was there are many versions of TWRP.. so which one use ?
2: I don't want to wait half month or even more just the unlock the bootloader ! so i guess I will go unofficially any good link
# I just saw that topic apparently it's possible to flash the TWRP without unlocking the bootloader.. is that method is compatible to put CyanogenMod after ?
3: Any good method, link will be welcome
Thank folks.
1. Alka twrp can backup the most partitions
2. Backup request will be accepted within hours lately.. but yeah that method is possible
Have to agree with that. Officially unlocking bootloader is a mostly painless process nowadays.It's quite possible to unlock your bl officially in less than a week. Since it looks like you know what you're talking about, I'm sure I don't need to tell you the possible benefits of having an offically unlocked bl over the unoffically unlocked one.
Personally, I think the best method is as follows:
Unlock bl officially
flash twrp through fastboot
flash twrp Alka
backup all partitions into sd card
flash appropriate cm firmware
flash rom, gapps, etc
flash apollo sound mod(cause it's great)
Please feel free to disagree.
Ivanlai I don't know If I will still unlock the Bootloader -> New method to flash Twrp recovery !! without unlock bootloader ! (kate/kenzo) safe ! by supercowz
Cleaning this up and clarifying as my original post was vague:
It is recommended that you unlock your bootloader before the 7.0 Nougat update. Although it will still be possible the process will be more difficult and risky afterwards.as you will need to use one of the edl mode tools (axon7backup, axom7tool).
The easiest way is to download this kit f you have the A2017U: (I can't speak to other models) (This kit and instructions are thanks to @jcadduono)
https://build.nethunter.com/misc/axon7/AXON7-A2017U-BL-UNLOCK-KIT.zip
https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
The basic steps, which the above zip with take you through in detail are:
1. Flash Official B20 , enable OEM UNLOCKING after flashing.
2. Flash BLFastboot zip provided by ZTE when they had unlock method.
3. Enable OEM UNLOCKING in Developers Option
4. Boot to Bootloader
5. type : fastboot oem unlock
6. Done
Note: If you do not have the OEM UNLOCKING flag set in developer options you will get a soft brick. Also bear in mid this will wipe data.
All that being said I've heard Nougat to is going to be great from those in the know. In their words ”Well worth the wait! Hang in there!” from a HIGHLY credible source.
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
lokissmile said:
For anyone looking to bootloader unlock, I've heard that the methods might change when the N update rolls out. It's a major update and although I personally don't have N and can't get a direct answer because those who know for sure are under NDA. I can tell you that the advice given to me is to not re-lock. So if you are thinking of unlocking your bootloader I'd do it soon while the methods are stable. Google confirmed that daydream is certified in an upcoming update so the daydream version of the stock ROM has been through googles QA. Might as well get ready now, we will probably have another surge of custom ROMS shortly after. I'm just sharing what I think is a best practice.
Click to expand...
Click to collapse
OK, so just to make it quick, for everyone, unlock your bootloader sooner than later. It is safe since you can revert it to a locked state at any time later.
lafester said:
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
Click to expand...
Click to collapse
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
lokissmile said:
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
Click to expand...
Click to collapse
No need to bootloader lock an Axon 7 to get SafetyNet (Android Pay, PoGo, etc). Just do it the XDA way. But never relock!!!!
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong?
Regards,
mischa_martin
mischa_martin said:
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong? [emoji14]
Regards,
mischa_martin
Click to expand...
Click to collapse
Read the OP.
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
stevecaboose said:
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
Click to expand...
Click to collapse
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
tzbigworm said:
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
Click to expand...
Click to collapse
@stevecaboose
Unlocking Bootloader = Yes to OTA's.
Modding System and Boot = NO OTA's
hope that clear things up.
Close enough lol!
To be clear, it would be best to unlock before N is pushed out. I have it on good authority that unlocking your bootloader after you update to N will be more difficult and risky. Relocking would put you in the same situation. It's trivial to return to stock system+boot with an unlocked bootloader and TWRP and then the OTA will come through just fine. Or you can just wait for the TWRP flashable N stock ROM.
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
ScaryBugThing said:
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
Click to expand...
Click to collapse
TWRP/BL unlock doesn't affect OTA, ROOT does.
raystef66 said:
TWRP/BL unlock doesn't affect OTA, ROOT does.
Click to expand...
Click to collapse
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
I think the OP was trying to say that it's possible current tools will not work to unlock the bootloader after the 7.x ota is installed.
DrakenFX said:
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
Click to expand...
Click to collapse
I'm not fully agreed with that. You can install OTA's when you receive it, download it, install it when first booted into twrp cache. Only if you're not rooted. When you're rooted first unroot and in principle this should work.
There are several cases on internet about that. Even I did it with an unrooted but TWRP-ed Zopo C2. Received an OTA and installed it.
Im always glad to learn but IMO there are some possibilities to do the ota after all. But I am willing to accept it's a general fact that twrp could affect the normal OTA.
Edit : let's wait and see when B10 is rolling out and if I get a notification about that and if I can install it as a normal OTA(not with SD) with TWRP. Keep you updated:cyclops:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
felipe.vella said:
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
Click to expand...
Click to collapse
1- Download Official B20 from ZTE SITE (look Software Updates for the 6gb variant)
2- look in the forum for the B20fastboot zip file
3- Move both files to your SDCARD.
4- Enable OEM Unlocking under Developers Option
5- boot to stock recovery.
6- Install B20 official update via SDCARD (this will wipe Data)
7- boot and re-enable OEM Unlocking
8- boot to recovery and install B20fastboot zip
9- boot to Bootloader and Unlock bootloader using this command.
Code:
fastboot oem unlock
If I remember correctly will reboot and factory reset the device , you'll need to re-enable OEM UNLOCKING and boot to Bootloader to flash TWRP 3.0.3 USING fastboot commands
Hi everyone,
So here's my query
Back in March I have unlocked my redmi note 3 bootloader by OFFICIAL way of redmi. But I now I m thinking what was the use of doing with official way why not unofficial.
In simple words can someone tell me down in comments section
What benefits I can get over official rather someone who has unlocked unofficially!!
Thanks
Best way is to unlock it by official method .
Read here an answer from an advanced user from miui forum:
"Hello,
Official way of unlocking is considered as the safest way of unlocking bootloader since it is done with MiUnlock Tool, and if the BL is unlocked then it won't relock during an OTA update or while flashing an incremental rom and the only way to relock BL is to flash fastboot rom through Miflash, but you have to get permission from Xiaomi for unlockin and it will take sometime.But on the otherhand unofficial way doesn't required any permission and risk factor is involved in this method, where you have to use stock rom emmc file to replace miui emmc and need to flash through Miflash, many users reported that they have bricked their device by following the same. In order to flash rom's, everytime you have to replace emmc, if you forgot then you will end up in bootloop. I guess I have cleared your doubt.
Thank you. "
cristiandiaconu6 said:
Best way is to unlock it by official method .
Read here an answer from an advanced user from miui forum:
"Hello,
Official way of unlocking is considered as the safest way of unlocking bootloader since it is done with MiUnlock Tool, and if the BL is unlocked then it won't relock during an OTA update or while flashing an incremental rom and the only way to relock BL is to flash fastboot rom through Miflash, but you have to get permission from Xiaomi for unlockin and it will take sometime.But on the otherhand unofficial way doesn't required any permission and risk factor is involved in this method, where you have to use stock rom emmc file to replace miui emmc and need to flash through Miflash, many users reported that they have bricked their device by following the same. In order to flash rom's, everytime you have to replace emmc, if you forgot then you will end up in bootloop. I guess I have cleared your doubt.
Thank you. "
Click to expand...
Click to collapse
Yes
Thanks man
As there are different steps and threads all over xda as to how to go about rooting redmi note 3 and then installing a custom ROM, I was wondering if someone could list or direct me to the correct working method to unlock bootloader, root, and install a custom ROM.
Note: I haven't done any tampering with the device, no TWRP, no unlocking bootloader via the hack or official method. I have only installed OTA updates sent to the device via Xiaomi.
Current Device Specifications: (Snapdragon)
Android Version: 6.0.1 MMB29M
MIUI Version: MIUI Global 8.5 | Stable 8.5.7.0(MHOMIED)
Kernel Version: 3.10.84-perf-g9105347
Apply for unlock permission and unlock using miunlock first
apexashwin said:
Apply for unlock permission and unlock using miunlock first
Click to expand...
Click to collapse
Are you suggesting that because the unofficial method is unreliable or because you think I am a beginner?
Both.. official method is simple and with unofficial u may get into firmware probs later while flashing roms which leads to soft/hard brick
Official unlock is recommended to avoid something bad for your device
apexashwin said:
Both.. official method is simple and with unofficial u may get into firmware probs later while flashing roms which leads to soft/hard brick
Click to expand...
Click to collapse
Thanks, I'll go for the official method, then. But I figure that method takes weeks? How much time did it for your phone?
pumpkins12 said:
Official unlock is recommended to avoid something bad for your device
Click to expand...
Click to collapse
Thanks!
apexashwin said:
Both.. official method is simple and with unofficial u may get into firmware probs later while flashing roms which leads to soft/hard brick
Click to expand...
Click to collapse
So, I got the permission from Xiaomi. But, I can't run the Unlock tool on Linux. I tried using VMware Player but the device is still not recognized. Have you had any luck using the official method on Ubuntu?
NealSchwartz said:
So, I got the permission from Xiaomi. But, I can't run the Unlock tool on Linux. I tried using VMware Player but the device is still not recognized. Have you had any luck using the official method on Ubuntu?
Click to expand...
Click to collapse
Forget it if you don't have windows. Xiaomi's unlock tool does not support linux. So you can't go with official method.
And the unofficial method requires a modded fastboot ehich is only available for windows. You can't go with this way too.
So, no way out if you don't have windows.
Also don't think of unlocking it unofficially if you don't have windows because most of the unofficial unlocked devices get locked which again requires the modded fastboot to unlock it.
The last problem, seriously and sadly, doesn't have any other solution
I am unofficially unlocked and few days back i had clean installed ubuntu on my pc but now i am back on windows. Why?? Because my device got locked and i couldn't help but install windows. You have been warned!
deepjyoti30 said:
I am unofficially unlocked and few days back i had clean installed ubuntu on my pc but now i am back on windows. Why?? Because my device got locked and i couldn't help but install windows. You have been warned!
Click to expand...
Click to collapse
Can the device get locked even after installing a custom ROM? What happens when it gets re-locked? ("Soft brick?")
NealSchwartz said:
Can the device get locked even after installing a custom ROM? What happens when it gets re-locked? ("Soft brick?")
Click to expand...
Click to collapse
Yes it can. Actually it hapoens mostly when we flash firmwares which have the unmodified emmc_appsboot.mbn file.
When we unlock unofficially this file is modified.
Thus flashing the firmware locks it.
I would not call it softbrick. When that happens you cannot boot anymore. Only fastboot mode is available and it doesn't allow us to flah any files since the device got locked again.
So we again need to go to edl mode which is only accessible by the modified fastboot available only for windows.
Enjoy linux?