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/
Related
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
I have access to an engineering bootloader for the Tmo Note8 and I would like to know how to test if it is unlocked.
Is there a specific process to determine if the bootloader is locked? Are there steps to permanently unlock the bootloader from an engineering bootloader?
I've searched all the Note8 forums and haven't found any answers.
Sent from my SM-G892U using Tapatalk
reukiodo said:
I have access to an engineering bootloader for the Tmo Note8 and I would like to know how to test if it is unlocked.
Is there a specific process to determine if the bootloader is locked? Are there steps to permanently unlock the bootloader from an engineering bootloader?
I've searched all the Note8 forums and haven't found any answers.
Click to expand...
Click to collapse
Flashing it and then checking if you can unlock it would be how to go about it. Except you can't flash unsigned images without unlocking so it's a catch 22 really. And it may just brick your phone even if you flashed it successfully. No way of knowing if that bootloader will even boot your device or play nice with the other partitions.
Gizmoe said:
Flashing it and then checking if you can unlock it would be how to go about it. Except you can't flash unsigned images without unlocking so it's a catch 22 really. And it may just brick your phone even if you flashed it successfully. No way of knowing if that bootloader will even boot your device or play nice with the other partitions.
Click to expand...
Click to collapse
The eng bootloader is signed, so there is no problem flashing the eng bootloader. I just do not know how to test if it is unlocked, as I can't find a recovery image to flash, and I do not know how to create one myself.
Sent from my SM-G892U using Tapatalk
reukiodo said:
The eng bootloader is signed, so there is no problem flashing the eng bootloader. I just do not know how to test if it is unlocked, as I can't find a recovery image to flash, and I do not know how to create one myself.
Sent from my SM-G892U using Tapatalk
Click to expand...
Click to collapse
probably just the combo files that are used for samfail imo. if you want to upload and have me check them lmk but more then likely all you have is the combo firmware we have been using since day one
Team DevDigitel said:
probably just the combo files that are used for samfail imo. if you want to upload and have me check them lmk but more then likely all you have is the combo firmware we have been using since day one
Click to expand...
Click to collapse
https://drive.google.com/file/d/1PIVZs-uB8kKb9YbY_fAcYJCGIfdb27W5/view?usp=drivesdk
This might only work on the T-Mobile version.
reukiodo said:
https://drive.google.com/file/d/1PIVZs-uB8kKb9YbY_fAcYJCGIfdb27W5/view?uk
This might only work on the T-Mobile version.
Click to expand...
Click to collapse
Do you have the boot.img that matches this?
Unable to check the rest without as it won't boot the combo img.
Yes it is a eng img.
We are on multi csc devices so all are same for flashing sake, as long as it's not the exynos.
Please remove the public link and we can move to pm/telegram and speak further
Team DevDigitel said:
Do you have the boot.img that matches this?
Unable to check the rest without as it won't boot the combo img.
Yes it is a eng img.
We are on multi csc devices so all are same for flashing sake, as long as it's not the exynos.
Please remove the public link and we can move to pm/telegram and speak further
Click to expand...
Click to collapse
I disabled the link, though not sure why I should? I haven't gotten telegram yet. I just want to know if it is unlocked for flashing custom recovery such as TWRP.
reukiodo said:
I disabled the link, though not sure why I should? I haven't gotten telegram yet. I just want to know if it is unlocked for flashing custom recovery such as TWRP.
Click to expand...
Click to collapse
No one has compiled twrp for snapdragon because we dont have a unlocked bl. Removing link is primarily to avoid people flashing this or reposting it with incorrect info and causing confusion.
If I can get the boot.img as well that is compiled for this bootloader I can get a running system and see if it can be unlocked. Otherwise without it there's no way to determine some of the important factors here. Just flashing against device to test is quite risky.
The bl is compatible with all snapdragon and does install correctly but it won't boot with the combo imgs we use for samfail or a stock img.
Link is still active fyi and I've sent you a pm with telegram info. It's a group for us and a few other devs that can work with us to get things sorted.
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
DroidisLINUX said:
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
Click to expand...
Click to collapse
I'm wondering if after flashing this engineering bootloader we can root phone just by simply using command prompt and sideloading root files. Any ideas? I don't know enough to do this.
Sent from my [device_name] using XDA-Developers Legacy app
Eudeferrer said:
I'm wondering if after flashing this engineering bootloader we can root phone just by simply using command prompt and sideloading root files. Any ideas? I don't know enough to do this.
Click to expand...
Click to collapse
I don't believe so, until we can get it unlocked, when in download mode it says the boot loader is still locked and says system secure in red and official binaries but if we can get the boot loader to say unlocked then I believe it will probably be possible. At least it says eng boot loader and tells us it's locked and that means it can be unlocked it's just a matter of time until someone gets it unlocked now
I am glad I haven't updated to boot loader 3 now, this is bootloader 2 so if you go to oreo you won't be able to use this when and if it's unlocked
DroidisLINUX said:
I don't believe so, until we can get it unlocked, when in download mode it says the boot loader is still locked and says system secure in red and official binaries but if we can get the boot loader to say unlocked then I believe it will probably be possible. At least it says eng boot loader and tells us it's locked and that means it can be unlocked it's just a matter of time until someone gets it unlocked now
I am glad I haven't updated to boot loader 3 now, this is bootloader 2 so if you go to oreo you won't be able to use this when and if it's unlocked
Click to expand...
Click to collapse
Has anyone tried the same procedure/comands used to unlock the Pixel XL? Would they even work I this phone if it had this eng bootloader? I wish I knew enough about this stuff to try it out or even know if it would work.
Sent from my [device_name] using XDA-Developers Legacy app
DroidisLINUX said:
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
Click to expand...
Click to collapse
you could test,
but if you look under the info on the boot up screen, secure boot is still set to : enabled
IE: each and every boot it checks for a modified boot.img and if found it fails secure check.
I never tested the oem unlock options etc, or waiting any time frame, just mostly seeing what we could use with it.
The phone wont boot a modified system as well. has to be unrooted stock system + stock boot.img to boot with the eng bootloader.
Unfortunately i havent heard anything back, was hoping we could get the boot.img that is ENG so we can boot the entire setup and go.
Hi friends!
I'm new in Mi 8 Lite community. I wonder a thing. If i unlock my bootlader, can i lock it again ?
Thanks for your answers.
Absolutely you can
https://youtu.be/O6qU57iGhBg
hamidezat20 said:
https://youtu.be/O6qU57iGhBg
Click to expand...
Click to collapse
Will this work on Mi 8 Lite ?
Yes this method works on all xiaomi devices
Hello!
Some people claim that locking up the bootloader on newer Xiaomi devices could brick the phone.
Does this information proceed?
Has anyone tested?
---------- Post added at 08:51 PM ---------- Previous post was at 08:31 PM ----------
hamidezat20 said:
https://youtu.be/O6qU57iGhBg
Click to expand...
Click to collapse
This video shows how to install stock ROM. But no to lock bootloader.
I dont understand the language. So, I dont see when he lock bootloader.
Sorry! Bad english... ::laugh:
alxsduarte said:
Hello!
Some people claim that locking up the bootloader on newer Xiaomi devices could brick the phone.
Does this information proceed?
Has anyone tested?
---------- Post added at 08:51 PM ---------- Previous post was at 08:31 PM ----------
This video shows how to install stock ROM. But no to lock bootloader.
I dont understand the language. So, I dont see when he lock bootloader.
Sorry! Bad english... ::laugh:
Click to expand...
Click to collapse
This video don´t show how to lock bootloader so the essential part is missed, maybe the guy is talking about but most of users won´t understand what he says and is not reflected on the options that he is using.
If you want to lock bootloader using MiFlashTool then at time to flash a stock rom you have to check on "Clean All and Lock" option down at the right in the tool.
Locking bootloader can´t never brick device by itself, the problem is that some users tried to do it using a custom rom, a custom recovery, rooted or with a cross-firmware that was not released originally in the device and happened that after device was locked again then refuses to boot to android system so bootloader detects that some partition/s was/were altered.
If you only unlocked bootloader and you are using all stock and non rooted you can relock it without need of use mi flash but using only the typical fastboot command
Code:
fastboot oem lock
then check if it was correct with
Code:
fastboot oem device-info
BUT never try to lock it of this way if some non-stock file was flashed and currently using on your device be custom rom, custom recovery, root, logo, custom kernel, etc.
SubwayChamp said:
This video don´t show how to lock bootloader so the essential part is missed, maybe the guy is talking about but most of users won´t understand what he says and is not reflected on the options that he is using.
If you want to lock bootloader using MiFlashTool then at time to flash a stock rom you have to check on "Clean All and Lock" option down at the left in the tool.
Locking bootloader can´t never brick device by itself, the problem is that some users tried to do it using a custom rom, a custom recovery, rooted or with a cross-firmware that was not released originally in the device and happened that after device was locked again then refuses to boot to android system so bootloader detects that some partition/s was/were altered.
If you only unlocked bootloader and you are using all stock and non rooted you can relock it without need of use mi flash but using only the typical fastboot command
Code:
fastboot oem lock
then check if it was correct with
Code:
fastboot oem device-info
BUT never try to lock it of this way if some non-stock file was flashed and currently using on your device be custom rom, custom recovery, root, logo, custom kernel, etc.
Click to expand...
Click to collapse
Thank you, bro!
All my doubts are clear now!
you cant lock bootloader if you firmware was originally chinese and you have changed to global..
if your firmware was global and you unlocked , yes you can lock it again using flashtool and oficial GLOBAL fastboot rom,developer or stable..:good:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock, I've tried multiple drivers and disabling driver signature in Windows 10. It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it? I've searched many times on Google and Youtube but with no success.
I had requested an unlock from Xiaomi and disabled all my other devices from my account.
Any help would be appreciated as this has become unnecessarily complicated, Thanks!
Shillopellos9 said:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock, I've tried multiple drivers and disabling driver signature in Windows 10. It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it? I've searched many times on Google and Youtube but with no success.
I had requested an unlock from Xiaomi and disabled all my other devices from my account.
Any help would be appreciated as this has become unnecessarily complicated, Thanks!
Click to expand...
Click to collapse
Check again if it´s correctly binded your MiAccount on Developer Options and try with other MiUnlock version.
Shillopellos9 said:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock [...] It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it?
Click to expand...
Click to collapse
Yes, I had the same issue and got it solved by using Mi Unlock on another PC. My main PC is using AMD Ryzen 2700 CPU, my laptop Intel Core i7-4712HQ. Wasted like 2 hours on my PC, while it worked first try on my laptop. Please note, the software told me to now wait 360 hours - it didn't unlock right away (this looks like expected behavior).
tolga9009 said:
Yes, I had the same issue and got it solved by using Mi Unlock on another PC. My main PC is using AMD Ryzen 2700 CPU, my laptop Intel Core i7-4712HQ. Wasted like 2 hours on my PC, while it worked first try on my laptop. Please note, the software told me to now wait 360 hours - it didn't unlock right away (this looks like expected behavior).
Click to expand...
Click to collapse
Soo i saw your reply and straight away tried unlocking with stock drivers on freshly bought laptop (today) with a Celeron, it worked straight away, Thanks! (i have a Ryzen 1600 desktop)
Witch version of Mi unlock software you suggest for unlocking bootloader?
I have China phone redmi note 8..and i want to flash global ROM but all Google say that if u lock the bootloader again...the phone will brick...so help me
Also, i have a question! My phone is on EU version, but i prefer the global version. Can i lock the bootloader back after i flash the version in fastboot mode?
Flash Mi 8 Lite image with mi flash tool and make sure you select clean all and lock in right bottom..
ThePscho said:
Hi friends!
I'm new in Mi 8 Lite community. I wonder a thing. If i unlock my bootlader, can i lock it again ?
Thanks for your answers.
Click to expand...
Click to collapse
You can flash fastboot ROM and set to clean all and lock, then the bootloader will be locked by a script from fastboot ROM
alicization said:
You can flash fastboot ROM and set to clean all and lock, then the bootloader will be locked by a script from fastboot ROM
Click to expand...
Click to collapse
Once i unlocked the bootloader, after i set a new password and fp it just kept saying that i need to enter my password every 0 hours. Tbh it did warn me when i accepted the oem unlocking that security features like fp, face recognision and find device will be disabled. So here is the question, is there any way at all to lock the bootloader without factory resetting?
P.S. : I have flashed twrp and miui 12, because i destroyed the miui 11 [:
I know it's only early day but has anyone found a root solution for the moto e6 plus?
Needing a new phone (hardware failure) and want one that can be easily rooted preferably with Twrp and Magisk,
McTRASH692 said:
I know it's only early day but has anyone found a root solution for the moto e6 plus?
Needing a new phone (hardware failure) and want one that can be easily rooted preferably with Twrp and Magisk,
Click to expand...
Click to collapse
I hope someone supports this device, since it is compatible with Proiect Treble
P o
I am planning to buy this, hope there is TWRP and Root soon!
Probably wont get support, cuz of the mediatek chip! I hope I am wrong [emoji1431]
Verstuurd vanaf mijn moto e(6) plus met Tapatalk
blanxlr said:
Probably wont get support, cuz of the mediatek chip! I hope I am wrong [emoji1431]
Verstuurd vanaf mijn moto e(6) plus met Tapatalk
Click to expand...
Click to collapse
The most E4 had a mediatek chipset and it had a few various root solutions,
yes, I'm waiting to root
Root is possible. The way I achieved it is first to follow the official bootloader unlock method given by Motorola. Then install Magisk Manager V 7.5.1 (latest as of today). After that have magisk patch the boot image and recovery image, and flash them both through fastboot. It will say the boot partition is signed but when you Flash it to the recovery partition it will tell you the image is either not signed or corrupt. Don't worry about this, it does not affect loading back into system or back into the bootloader or recovery. Remember, after this you will have to boot through recovery every time you reboot or you will not have root until you do. Unfortunately I am still trying to work on TWRP, and it is going rather slow as this is my first attempt at compiling a custom recovery and I am no developer, and am learning as I go... Hope I helped!!!
Hey guys, I Need some help, I'm trying to unlock bootloader, but my device doesn't recognize fastboot commands like "fastboot oem get_unlock_data" Or "fastboot oem flashing_unlock", why?
Ps: Motorola drivers ok, usb cable ok, oem unlock and usb debugging ok
Root
Hi extrnoob! Could you explain this process step by step? Inexperienced people like me don't understand your language xD
extrnoob said:
Root is possible. The way I achieved it is first to follow the official bootloader unlock method given by Motorola. Then install Magisk Manager V 7.5.1 (latest as of today). After that have magisk patch the boot image and recovery image, and flash them both through fastboot. It will say the boot partition is signed but when you Flash it to the recovery partition it will tell you the image is either not signed or corrupt. Don't worry about this, it does not affect loading back into system or back into the bootloader or recovery. Remember, after this you will have to boot through recovery every time you reboot or you will not have root until you do. Unfortunately I am still trying to work on TWRP, and it is going rather slow as this is my first attempt at compiling a custom recovery and I am no developer, and am learning as I go... Hope I helped!!!
Click to expand...
Click to collapse
I couldn't unlock bootloader. When i type the command fastboot devices i get a string, but when i type fastboot oem get_unlock_data, i get this message “FAILED (remote: unknown command)”.
risss said:
I couldn't unlock bootloader. When i type the command fastboot devices i get a string, but when i type fastboot oem get_unlock_data, i get this message “FAILED (remote: unknown command)”.
Click to expand...
Click to collapse
I have the same error ;_;
U are using CMD as admin, not PowerShell?
Vsx06 said:
U are using CMD as admin, not PowerShell?
Click to expand...
Click to collapse
I tried both ; -;
You can't unlock the bootloader. Don't bother with it. If you want something proper, get any device that's NOT from China, and especially form Lenovo (which is Motorola now).
**** LENOVO **** CHINA FREE HONG KONG.
I don't know if there's a moto e6 plus with enabled oem fastboot commands, it seems like Motorola didn't add support for oem unlock in this phone but maybe if we could get a hold of the download agent for Sp flash tool (since the device is a Mediatek powered device) and the auth file, we could get root via magisk patched boot.img
I searched for a little and i found nothing. I hope that someone manages to get a hold of those files, since the firmware is already available online.
Well, i managed to flash patched boot.img, but dm-verity is enabled and fstab is not on ramdisk because of project treble... now what
hookgab said:
You can't unlock the bootloader. Don't bother with it. If you want something proper, get any device that's NOT from China, and especially form Lenovo (which is Motorola now).
**** LENOVO **** CHINA FREE HONG KONG.
Click to expand...
Click to collapse
I beg to differ, as in developer option on the moto e6 plus there is a toggle for OEM unlocking,
I believe you need to get a code from Motorola to complete the unlock though,
I have not yet tested as I want to preserve warranty,
However with my moto e4 I was able to unlock bootloader and root without any issues,
Hell at one point I had to rebuild the entire system from an empty chip, (OS took me 4 Days) including rewriting the original imei numbers (that took me 2 weeks)
So no, lenovo is not as locked down as you seem to think it is,
As a side not, most phone are made with components that are built/assembled in China so it is actually quite hard to get a device that isn't at least partially made in China,
uanesgtgt2 said:
Well, i managed to flash patched boot.img, but dm-verity is enabled and fstab is not on ramdisk because of project treble... now what
Click to expand...
Click to collapse
I know the moto e4 required a no-verity flash to accept root,
Unsure if there is one that would work for the e6 yet,
Certainly something to look for,
uanesgtgt2 said:
I don't know if there's a moto e6 plus with enabled oem fastboot commands, it seems like Motorola didn't add support for oem unlock in this phone but maybe if we could get a hold of the download agent for Sp flash tool (since the device is a Mediatek powered device) and the auth file, we could get root via magisk patched boot.img
I searched for a little and i found nothing. I hope that someone manages to get a hold of those files, since the firmware is already available online.
Click to expand...
Click to collapse
It was added, it's hidden away in developer options,
May require an unlock code from Motorola though,
Hello.
I downloaded Fastboot images of miui 12 for my remi note 9s but, cannot flash the images because the first error is something like "lock state" when Fastboot tried yo erase boot.
My device is almost 2 months in my hands and cannot unlock bootloader because I will loose warranty.
Search Google but there's a lot of similar problems with other models too.
Impoetant, my device ia updated to miui 12 stable but downloaded 720mb and the Fastboot images are almost 6 gb
Thanks.
Hakkinen3K said:
Hello.
I downloaded Fastboot images of miui 12 for my remi note 9s but, cannot flash the images because the first error is something like "lock state" when Fastboot tried yo erase boot.
My device is almost 2 months in my hands and cannot unlock bootloader because I will loose warranty.
Search Google but there's a lot of similar problems with other models too.
Impoetant, my device ia updated to miui 12 stable but downloaded 720mb and the Fastboot images are almost 6 gb
Thanks.
Click to expand...
Click to collapse
You have to unlock your bootloader before flashing anything iirc, even if it's the Xiaomi approved, signed, original factory firmware. You can re-lock the bootloader afterwards and everything should be the same. I don't think Xiaomi phones have a "digital fuse" or something that permanently marks a phone as having been unlocked once (or that service centers care), but don't quote me on that.
Limezero said:
You have to unlock your bootloader before flashing anything iirc, even if it's the Xiaomi approved, signed, original factory firmware. You can re-lock the bootloader afterwards and everything should be the same. I don't think Xiaomi phones have a "digital fuse" or something that permanently marks a phone as having been unlocked once (or that service centers care), but don't quote me on that.
Click to expand...
Click to collapse
Thanks for answer. I think I'm gonna stick with the update installed, don't want to unlock yet. Besides, is working fine at the moment.
?
Sent from my Redmi Note 9S using XDA Labs
Hakkinen3K said:
Thanks for answer. I think I'm gonna stick with the update installed, don't want to unlock yet. Besides, is working fine at the moment.
?
Click to expand...
Click to collapse
The unlock process is made by xiaomi so you dont loose warranty