is there any way to insert custom recovery without unlocking bootloader On HTC?
because If the phone has lock screen. then we can remove lock from custom recovery without Losing data
as i know bootloader need to unlock for installing custom recovery
but if i unlock bootloader using htcdev.com phone will formate auto
so is there any way to insert custom recovery without unlocking bootloader On HTC?
obaid_457 said:
is there any way to insert custom recovery without unlocking bootloader On HTC?
because If the phone has lock screen. then we can remove lock from custom recovery without Losing data
as i know bootloader need to unlock for installing custom recovery
but if i unlock bootloader using htcdev.com phone will formate auto
so is there any way to insert custom recovery without unlocking bootloader On HTC?
Click to expand...
Click to collapse
No and yes:
If you're phone is S-ON and bootloader Locked (or relocked) No, it's a security feature to prevent unauthorized access to your data. Without this security, anyone with the appropriate knowledge could easily dump your phone data to a computer without having to enter a pin/password (lockscreen) and that would only take a few minutes (and it looks like that's exactly what you're trying to do... Stolen phone? Spying on your GF/BF? )
Yes only if the phone is S-OFF: you can pack a custom recovery image named "recovery.img" and the appropriate android-info.txt file inside a firmware.zip and flash it in ruu mode. Again, it will only works if the phone is S-OFF, otherwise the bootloader will refuse to flash that firmware.zip since it will not be signed with HTC's encryption key.
And BTW your question is really OT here, it's a forum section for Tasker (Tasker is an application)
alray said:
No and yes:
If you're phone is S-ON and bootloader Locked (or relocked) No, it's a security feature to prevent unauthorized access to your data. Without this security, anyone with the appropriate knowledge could easily dump your phone data to a computer without having to enter a pin/password (lockscreen) and that would only take a few minutes (and it looks like that's exactly what you're trying to do... Stolen phone? Spying on your GF/BF? )
Yes only if the phone is S-OFF: you can pack a custom recovery image named "recovery.img" and the appropriate android-info.txt file inside a firmware.zip and flash it in ruu mode. Again, it will only works if the phone is S-OFF, otherwise the bootloader will refuse to flash that firmware.zip since it will not be signed with HTC's encryption key.
And BTW your question is really OT here, it's a forum section for Tasker (Tasker is an application)
Click to expand...
Click to collapse
hahaha my Friend i'm a Mobile Technician and must need to know this and what is meaning of OT???
OT mean out of Thread? Please move it to the right section
obaid_457 said:
hahaha my Friend i'm a Mobile Technician and must need to know this and what is meaning of OT???
OT mean out of Thread? Please move it to the right section
Click to expand...
Click to collapse
OT = Off topic
But never mind, a moderator moved your thread to the correct section. :good:
Anything else you need to know about htc phones?
Related
I have been trying to lock everything back up to return my phone I am s on but was wanting to relock the bootloader and unroot. I i could not get the ruu to work I am on the new bootloader someone told me to adb oem lock so I did now my phone says tampered locked and security warning but it wont come out of the bootloader every time I try to reboot it goes back to the bootloader even if i power down it still goes back to the bootloader. please help
as of right now all i have is fastboot
shawnten said:
I have been trying to lock everything back up to return my phone I am s on but was wanting to relock the bootloader and unroot. I i could not get the ruu to work I am on the new bootloader someone told me to adb oem lock so I did now my phone says tampered locked and security warning but it wont come out of the bootloader every time I try to reboot it goes back to the bootloader even if i power down it still goes back to the bootloader. please help
as of right now all i have is fastboot
Click to expand...
Click to collapse
If the RUU doesn't work, the other two alternatives are to attempt to flash the stock system.img and stock boot.img through fastboot .. although I'm not sure this will work with S-ON, depends on whether or not the device is locked/unlocked via HTC's official method.
Also, the second alternative, could use the PG*zip file which is stored inside the RUU. the zip file can be extracted from the RUU and placed on the root of the sdcard. Then the bootloader will grab this file and flash, essentially performing the same thing as the RUU would.
So I want to know if it is possible to root the phone without going to a custom bootloader? The reason I ask is because my work phone cannot be rooted and connect to our Exchange server.
I would like to root phone, change the database settings to allow me to turn on wifi hotspot, and unroot without having to reflash all of the things it takes to reset the bootloader flags and loosing database settings from when I was root.
Additional reading has lead me to this:
http://forum.xda-developers.com/showpost.php?p=46315574&postcount=60
It may appear there is no way to do this. Is this because no one has made signed copies of .zip exploits? Or is it for some technical reason that everyone just goes in through the Bootloader first? I am just trying to enable wifi hotspot, so if someone has advice on how to do so, please give me your suggestions.
murky024 said:
Additional reading has lead me to this:
http://forum.xda-developers.com/showpost.php?p=46315574&postcount=60
It may appear there is no way to do this. Is this because no one has made signed copies of .zip exploits? Or is it for some technical reason that everyone just goes in through the Bootloader first? I am just trying to enable wifi hotspot, so if someone has advice on how to do so, please give me your suggestions.
Click to expand...
Click to collapse
HTC changed the hboot and you can no longer boot to recovery ...you have to flash it
only way to flash it is to unlock the bootloader. you unlock it through revone (s-off) or htcdev those are your options
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...??
BBEgo said:
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
Click to expand...
Click to collapse
Wonders_Never_Cease said:
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...
Click to expand...
Click to collapse
That's weird.... I thought I posted this in the Q&A forum. I was just in there looking for it and I thought it'd gotten deleted or something. Oh well.
Mods, please feel free to correct my goof.
I didn't use HTCDev to unlock. I just did Sunshine and it handled everything. S-off, unlock, and root - Talk about painless! After that I installed a custom recovery (Philz) and I was off to the races.
So I decided to SuperCID my phone so I can install whatever I want. No problem.
Then I tried to install 5.0.1 firmware (4.16.1540.8) so I could run SkyDragon, but the firmware posted on page 1 in the thread would not install- 4.16.1540.8
Kept giving me "FAILED (REMOTE:24 parsing android-info fail)"
I was able to install 4.16.401.9 with no major headaches, once I found a sensible upgrade path. That one is working fine, but I don't understand why 4.16.1540.8 would not install.
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
So now I'm S-off, locked bootloader, PhilZ recovery (put it back on with Flashify), SuperCID, on Lollipop, and I guess everything is ok. But I still don't understand why the phone wouldn't take the firmware.
Any ideas? Thanks in advance.
If you ran sunshine on it,you can run it again i believe on that same device. It should unlock it again,if not then can try htcdev as it also uses fastboot to unlock as long as you can get adb to show needed code.
BBEgo said:
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
Click to expand...
Click to collapse
In the past (at least on my One X EVITA) my understanding was that s-off meant that all security was bypassed. Meaning that bootloader check was effectively bypassed.
This isn't the case for the M8. From what I can tell a LOCKED bootloader still prevents you from flashing anything that isn't signed (anything "unofficial") even if s-off.
However, having an UNLOCKED bootloader doesn't seem to affect anything while s-off. Meaning you can do things like RUU when UNLOCKED (which normally needs to be LOCKED or RELOCKED if s-on).
In short, I don't ever recommend relocking the bootloader if s-off on this device. There isn't any reason to, as far as I can tell. Meaning, having an UNLOCKED bootloader doesn't prevent you from doing anything. However, a RELOCKED bootloader does (even when s-on) prevent some things.
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/
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