Database Users

[solved] Can't unlock bootloader / flash recovery

EDIT:
Soulution
If you stumble upon this thread while searching for your problem...
There is no specific solution for this problem.
Allthough the phone isn't bricked, you still should do the unbreaking Method 3 in Naman Bhalla's thread on the OnePlus forums (LINK)
The phone is working perfectly again.
Also, if this problem appeared when you tried flashing OOS 3.0, check out this guide.
I did a lot of google research, found a lot of stuff and I'm still stuck at my problem.
Some background information:
I wanted to flash the new Oxygen OS 3.0 Community Build, decided to perform a clean install (full wipe with system, cache, dalvik and data).
Went into TWRP, wiped phone, installed OOS 3.0 - worked.
Made my initial setup, then I wanted to boot into recovery - didn't work.
Then I booted into fastboot, tried fastboot oem unlock, it said:
fastboot oem unlock
...
OKAY [ 0.014s]
finished. total time: 0.014s
Click to expand...
Click to collapse
Afterwards I checked fastboot oem device-info:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.080s]
finished. total time: 0.080s
Click to expand...
Click to collapse
That means still locked.
The phone won't boot up by itself.
I had to go in fastboot, and then use "fastboot continue" to get into the OS.
At the beginning, I forgot to enable the 'Allow OEM unlock' option in developer settings, it is now enabled but effect remains the same.
My question:
How do I fix my obviously broken recovery? How can I reflash it with a locked bootloader or how do I even unlock the bootloader.
PLEASE do not link me to the unbrick guides - the device is NOT bricked - it boots up with fastboot continue and also shows up as ONE A2003 when connected to pc.
What works:
+ getting into the OS (via fastboot continue)
+ getting into fastboot
What doesn't work:
- unlocking via fastboot oem unlock
- flashing a recovery (device is locked)
- booting into recovery
Thanks in advance for your help & ideas!

Hi man, what a mess did you did
I have been in that situation. (Stock in fastboot/boot logo with bootloader locked and oem unlocking disabled in seetings).
The only thing that worked for me was the naman bahlla tutorial to unbrick hard bricked devices. (The 3rd method).
The link is this one: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Anyway you can ask naman bhalla help in that thread. He will help you.
TS

Tierri said:
Hi man, what a mess did you did
I have been in that situation. (Stock in fastboot/boot logo with bootloader locked and oem unlocking disabled in seetings).
The only thing that worked for me was the naman bahlla tutorial to unbrick hard bricked devices. (The 3rd method).
The link is this one: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Anyway you can ask naman bhalla help in that thread. He will help you.
TS
Click to expand...
Click to collapse
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003

GerRudi said:
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
Click to expand...
Click to collapse
hum. Ask Naman Bahlla for help.

GerRudi said:
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
Click to expand...
Click to collapse
When you try to flash a recovery, what error message do you get? Curiosity question.
But I'm gonna have to echo Tierri to use that unbricking method. I get you're not bricked, but that will work to fix your issue. To get the Qualcomm device thing to show in device manager, power down your phone completely. Then connect the USB cable and press VOL UP (don't press power). You should hear the Windows connection chime. Also make sure you're booted up with Windows Device Driver Signature check turned off.
EDIT: I've followed these directions in the past: http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543

I did the same thing.
Only way is boot to system (fastboot continue) backup all files from internal memory to pc,
Restore device completly as Tierri said using method 3 unbrick guide.
Unlock bootloader in system (oos 2.2.1 or 2.2.0).
and flash oos 3.0 beta with twrp from that thread: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/

Thanks for all your replies!
As you all suggested, I decided to go through the Bhallas unbricking guide on the OnePlus forums.
This seemed to be the quickest solution out there.
I'll update the Original post with the solution, thanks.
If mods see this, thread can be closed, tagge the thread as solved.

The real op oem fix
follow these steps:
1. launch your cmd
2. plug out your phone
3. power it off
4. power into fastboot
5. plug it into the pc
6. type these commands
"adb start-server"
"fastboot devices" (your device should show in fastboot)
"fastboot oem lock" (this will reboot your phone and reset everything make sure you backup if you need to)
7. skip all OP setup steps(skipping these steps saves your time cause this process will have to be done twice also put into DEV mode and allow usb debugging)
8. once you on your homescreen power off your OP
9. plug it out of the pc
10. put it back into fastboot
11. type these commands before plugging back into pc
"adb kill-server"
"adb start-server"
12. plug it back into the pc and type these commands
"fastboot devices"
"fastboot oem unlock" (sometimes it will prompt you in some kind of asian language asking if you want to reset all your data just click the first option this will also reset your phone again)
that should fix the OEM boot unlocker now
i made this solution my self after troubleshooting like crazzy cause i had the same problem like you but didnt have to do all the extra bs with download random crap that does not really help
~xjinx216

is your bootloader unlocked now after following naman's process? please help, i've been having the same problem for ages.

I'm having this issue as well. Tried every driver and just can't seem to unlock bootloader. Adb seems to work, can boot into fastboot but then it always says fastboot cannot be detected when I try anything. Or it gets stuck on waiting for device. I just want to get this thing rooted????

Im having the same issue and my device IS bricked (and im sure i may have somehow deleted my OS) And i can't do anything to fix it, but if i deleted/corrupted my OS can it still be oem locked?

Solution
GerRudi said:
EDIT:
Soulution
If you stumble upon this thread while searching for your problem...
There is no specific solution for this problem.
Allthough the phone isn't bricked, you still should do the unbreaking Method 3 in Naman Bhalla's thread on the OnePlus forums (LINK)
Click to expand...
Click to collapse
I had about the same problems with my phone (oem unlock shows okay but doesn't unlock, directly booted the not working recovery) i was then able to boot to system with "fastboot continue".
Solution i found (root needed): flash stock recovery (from oneplus 2 downloads section) in rom with "dd" command and do a oem unlock, it will then boot to stock recovery, where you have to confirm the unlock (works with all roms but only with stock recovery).
command used to flash recovery (in android terminal emulator, adb should work too): dd if="location of recovery.img to flash" of=/dev/block/bootdevice/by-name/recovery
You can also flash twrp on a locked bootloader like this (just make sure to have a stock recovery ready on the device).
You might want to include this in front page.

GerRudi said:
EDIT:
What works:
+ getting into the OS (via fastboot continue)
+ getting into fastboot
What doesn't work:
- unlocking via fastboot oem unlock
- flashing a recovery (device is locked)
- booting into recovery
Click to expand...
Click to collapse
I got into exactly the same situation now, the problem is that "Method 3 in Naman Bhalla's thread" is not working for me as it break on "sahara error". Actually the message says to restart phone and retry, but I'm always getting into this error again and again. I already tried to reinstall drivers many times and I'm running in testing mode... what else I can try to solve this? (Windows 10 Pro)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Problem after flashing rom..Soft brick ?

So here's what I did: I had already flashed this bugless rom on my lenovo a6000 (was running stock lollipop before) . However,rom caused heavy games to stutter,so I decided to install update8 version.
I installed new twrp 2.8.7 and apparently it said something about partition,which I ignore and went back to menu.I wiped system,data,dalvik and cache,then flashed gapps and rom.Then,I wiped cache once again and pressed reboot,and then phone got stuck.I believe the problem is with twrp..
After that my phone gets stuck on lenovo powered by android screen and my computer/adb doesn't recognize device. Help please ?? :crying::crying:
P.S. I can get into fastboot mode..
EDIT: SOLVED!!
Here's what I did wrong: I flashed update of rom after deleting system and data,instead of flashing it over rom.To solve,go to fastboot mode,install drivers of lenovo adb,then enter cmd,and boot recovery.img

MASK10101012 said:
So here's what I did: I had already flashed this bugless rom on my lenovo a6000 (was running stock lollipop before) . However,rom caused heavy games to stutter,so I decided to install update8 version.
I installed new twrp 2.8.7 and apparently it said something about partition,which I ignore and went back to menu.I wiped system,data,dalvik and cache,then flashed gapps and rom.Then,I wiped cache once again and pressed reboot,and then phone got stuck.I believe the problem is with twrp..
After that my phone gets stuck on lenovo powered by android screen and my computer/adb doesn't recognize device. Help please ?? :crying::crying:
P.S. I can get into fastboot mode..
Click to expand...
Click to collapse
fastboot is all you ever gonna need
I see you have tried twrp 2.8.7.7
So give cwm a try
http://www15.zippyshare.com/v/j9lHGdJf/file.html
After you extract this cwm recovery.. Paste it in minimal adb and fastboot folder
And then "fastboot boot cwm.img"
Make sure you rename the cwm image first
And then you can try flashing the cm12.1 zip
Most of the a6k users are using twrp but for me cwm always gets me out of a situation like yours

Lolitas

sasukay said:
fastboot is all you ever gonna need
I see you have tried twrp 2.8.7.7
So give cwm a try
http://www15.zippyshare.com/v/j9lHGdJf/file.html
After you extract this cwm recovery.. Paste it in minimal adb and fastboot folder
And then "fastboot boot cwm.img"
Make sure you rename the cwm image first
And then you can try flashing the cm12.1 zip
Most of the a6k users are using twrp but for me cwm always gets me out of a situation like yours
Click to expand...
Click to collapse
But my pc doen't recognize device :crying: Also adb devices command shows no devices

MASK10101012 said:
But my pc doen't recognize device :crying:
Click to expand...
Click to collapse
Its because you havent installed fastboot drivers
Connect your device in fastboot mode and in adb type
"fastboot devices"
Check if your device is listed

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sasukay said:
Its because you havent installed fastboot drivers
Connect your device in fastboot mode and in adb type
"fastboot devices"
Check if your device is listed
Click to expand...
Click to collapse
Doesn't work.Installed drivers from xda,then ran adb and typed both 'fastboot devices' and then adb devices.
Both didnt work,shows nothing
A small confirmation,fastboot mode is where it shows lenovo powered by android and then underneath its written "Powerkey long press can reboot phone" right ??

Im able to get into twrp from time to time,but I dont seem to know the accurate button to press.Help please ???

MASK10101012 said:
Doesn't work.Installed drivers from xda,then ran adb and typed both 'fastboot devices' and then adb devices.
Both didnt work,shows nothing
A small confirmation,fastboot mode is where it shows lenovo powered by android and then underneath its written "Powerkey long press can reboot phone" right ??
Click to expand...
Click to collapse
You dont have drivers correctly installed
Try these
https://drive.google.com/file/d/0B1k7jnFdJrUzajhnMmJaMGZxUE0/edit?pref=2&pli=1
"adb devices" wont work in fastboot mode
And yeah thats exactly the fastboot mode with the "lenovo logo and powerkey long press can reboot your phone"

sasukay said:
You dont have drivers correctly installed
Try these
https://drive.google.com/file/d/0B1k7jnFdJrUzajhnMmJaMGZxUE0/edit?pref=2&pli=1
"adb devices" wont work in fastboot mode
And yeah thats exactly the fastboot mode with the "lenovo logo and powerkey long press can reboot your phone"
Click to expand...
Click to collapse
I entered twrp third time today.I did the steps correctly this time,but when I pressed reboot it shows lenovo screen again.Oh,and this time,adb and pc recognise device,but adb says its unauthorized.,..
Another thing,your software doesn't work;I run Win10 64Bit...

MASK10101012 said:
I entered twrp third time today.I did the steps correctly this time,but when I pressed reboot it shows lenovo screen again.Oh,and this time,adb and pc recognise device,but adb says its unauthorized.,..
Click to expand...
Click to collapse
Why are you trying to reboot..?
Since you've cleared your /system you phone is stuck into bootloop
And adb commands wont work until you choose flash zip from adb sideload

sasukay said:
Why are you trying to reboot..?
Since you've cleared your /system you phone is stuck into bootloop
And adb commands wont work until you choose flash zip from adb sideload
Click to expand...
Click to collapse
Okay,so what am I supposed to do ? I already said that your driver doesn;t install..

MASK10101012 said:
Okay,so what am I supposed to do ? I already said that your driver doesn;t install..
Click to expand...
Click to collapse
Brother actually Im outside right now....wait for 15-20mins
---------- Post added at 02:26 PM ---------- Previous post was at 01:57 PM ----------
MASK10101012 said:
Okay,so what am I supposed to do ? I already said that your driver doesn;t install..
Click to expand...
Click to collapse
Can you tell me the exact error being shown on your pc
It could be driver signing problem or os compatability
---------- Post added at 02:32 PM ---------- Previous post was at 02:26 PM ----------
And yeah....if you have figured to get into twrp recovery
Then put cm12.1 zip and gapps zip in your internal memory
Boot into twrp recovery
First clear cache, dalvik cache, system, data
And then flash cm12.1 and gapps zip(s)
You dont need a pc for that

sasukay said:
Brother actually Im outside right now....wait for 15-20mins
---------- Post added at 02:26 PM ---------- Previous post was at 01:57 PM ----------
Can you tell me the exact error being shown on your pc
It could be driver signing problem or os compatability
---------- Post added at 02:32 PM ---------- Previous post was at 02:26 PM ----------
And yeah....if you have figured to get into twrp recovery
Then put cm12.1 zip and gapps zip in your internal memory
Boot into twrp recovery
First clear cache, dalvik cache, system, data
And then flash cm12.1 and gapps zip(s)
You dont need a pc for that
Click to expand...
Click to collapse
I did that but doesn't work.... Getting into twrp works one in 25 times or so,even then re-flashing the roms did not work.As for the driver installer,it loads infinitely..Maybe the roms are corrupted ?

MASK10101012 said:
I did that but doesn't work.... Getting into twrp works one in 25 times or so,even then re-flashing the roms did not work.As for the driver installer,it loads infinitely..Maybe the roms are corrupted ?
Click to expand...
Click to collapse
Please elaborate
How Im gonna be able to help you if you dont tell me what exactly is your problem
1) tell me what error twrp is showing and more accurately, till which step are you able to follow
2) with pc thing...whats the error...there are only two errors usually. First, when you click the setup it says OS is not supported or second, it says installing drivers for the device and then after a while drivers could not be installed

sasukay said:
Please elaborate
How Im gonna be able to help you if you dont tell me what exactly is your problem
1) tell me what error twrp is showing and more accurately, till which step are you able to follow
2) with pc thing...whats the error...there are only two errors usually. First, when you click the setup it says OS is not supported or second, it says installing drivers for the device and then after a while drivers could not be installed
Click to expand...
Click to collapse
Let me restart from the beginning.The whole problem began since I flashed new twrp.You see,entering recovery is tough(When I press volume plus+volume minus+power button then release power when logo is shown)works only once every ~25-30 times or so.After entering TWRP the first time,it showed something like unmount partition or something shown in this video at 4:16.Then
,I wipe system,data,cache,dalvik;then I flashed rom and gapps,then wipe caches and reboot.I have done this same procedure twice. Third time,I did the thing in the video then wiped caches,system,data then flashed zip files.Then I rebooted.[Everything is succesful up to this point] However,when I rebooted,it got stuck on boot screen again..
At first,your driver installer recognised my device as lenovo a6000,but got stuck while installing.
Now(after a few reboots and trials to enter twrp),my device is recognised as 'Android' device only,and your driver says 'no device found'
....I'll attach screenshot..

MASK10101012 said:
Let me restart from the beginning.The whole problem began since I flashed new twrp.You see,entering recovery is tough(When I press volume plus+volume minus+power button then release power when logo is shown)works only once every ~25-30 times or so.After entering TWRP the first time,it showed something like unmount partition or something shown in this video at 4:16.Then
,I wipe system,data,cache,dalvik;then I flashed rom and gapps,then wipe caches and reboot.I have done this same procedure twice. Third time,I did the thing in the video then wiped caches,system,data then flashed zip files.Then I rebooted.[Everything is succesful up to this point] However,when I rebooted,it got stuck on boot screen again..
At first,your driver installer recognised my device as lenovo a6000,but got stuck while installing.
Now(after a few reboots and trials to enter twrp),my device is recognised as 'Android' device only,and your driver says 'no device found'
....I'll attach screenshot..
Click to expand...
Click to collapse
Send the screenshot of the error you get while installing drivers. And how did you flashed the twrp in the first place.
And what device are you having
Lenovo or redmi
---------- Post added at 04:19 PM ---------- Previous post was at 03:22 PM ----------
MASK10101012 said:
Let me restart from the beginning.The whole problem began since I flashed new twrp.You see,entering recovery is tough(When I press volume plus+volume minus+power button then release power when logo is shown)works only once every ~25-30 times or so.After entering TWRP the first time,it showed something like unmount partition or something shown in this video at 4:16.Then
,I wipe system,data,cache,dalvik;then I flashed rom and gapps,then wipe caches and reboot.I have done this same procedure twice. Third time,I did the thing in the video then wiped caches,system,data then flashed zip files.Then I rebooted.[Everything is succesful up to this point] However,when I rebooted,it got stuck on boot screen again..
At first,your driver installer recognised my device as lenovo a6000,but got stuck while installing.
Now(after a few reboots and trials to enter twrp),my device is recognised as 'Android' device only,and your driver says 'no device found'
....I'll attach screenshot..
Click to expand...
Click to collapse
Okay...so you are gonna remove any driver you have installed previously and install these. I'm 100% sure these will work.
https://drive.google.com/file/d/0B0I-ww-JUkrJeDFESnRqT3pXdzg/edit?pref=2&pli=1
These wont have any problem in installation but if there's any, you can always ask me :fingers-crossed:

sasukay said:
Send the screenshot of the error you get while installing drivers. And how did you flashed the twrp in the first place.
And what device are you having
Lenovo or redmi
---------- Post added at 04:19 PM ---------- Previous post was at 03:22 PM ----------
Okay...so you are gonna remove any driver you have installed previously and install these. I'm 100% sure these will work.
https://drive.google.com/file/d/0B0I-ww-JUkrJeDFESnRqT3pXdzg/edit?pref=2&pli=1
These wont have any problem in installation but if there's any, you can always ask me :fingers-crossed:
Click to expand...
Click to collapse
Ok after installing driver, command'adb devices' shows xxxxxxx offline.Typing 'fastboot devices' returns nothing.PC now detects device as MTP,basically,an empty shell.:crying::crying: Oh yeah,I retried installing the previous driver you gave me,it says : 'waitng for DevMgr'....

MASK10101012 said:
Ok after installing driver, command'adb devices' shows xxxxxxx offline.Typing 'fastboot devices' returns nothing.PC now detects device as MTP,basically,an empty shell.:crying::crying: Oh yeah,I retried installing the previous driver you gave me,it says : 'waitng for DevMgr'....
Click to expand...
Click to collapse
Well, install the drivers which i told you to in the last post. Open fastboot mode on your phone and then type "fastboot devices". There you will have your device listed.
Then flash the recovery which you want by "fastboot flash recovery recovery.img" where recovery is the name of the recovery image and which you have to place in the adb and fastboot folder, before flashing

sasukay said:
Well, install the drivers which i told you to in the last post. Open fastboot mode on your phone and then type "fastboot devices". There you will have your device listed.
Then flash the recovery which you want by "fastboot flash recovery recovery.img" where recovery is the name of the recovery image and which you have to place in the adb and fastboot folder, before flashing
Click to expand...
Click to collapse
I think I just said that typing fastboot devices returns nothing? Like,blank ? AFTER installing drivers in last post ?

MASK10101012 said:
I think I just said that typing fastboot devices returns nothing? Like,blank ? AFTER installing drivers in last post ?
Click to expand...
Click to collapse
Restart your phone in "FASTBOOT MODE"
Until then fastboot wont recognize your phone
For fastboot you just press VOL DOWN + POWER KEY for a few secs

Fix bootloop in redmi note 3 (no recovery ,no edl mode)

After trying to flash the latest 7.1.1 cm 14 ropms many people ended up in bootloop where your phone switch on ,shows mi logo and rebbot again. Many where not able to enter recovey mode also.. Now i come up with a perfect soluton for you all on how to fix these issues in your phone..Lets Get started..
If anything goes wrong iam not responsible.Do it At your Own Risk.
Requirements
------------------
1. Enter edl .rar (attached below)
2.Miui Stock Rom (FastBoot). Download it from(only use this version) here
3.Phone Must have Charge of 50% or more.
4.Unlock Boot loader.zip (Attched Below)
6.MIPhone Tools and install it .Get it from here
6.Extract all the file
7. PDA Net.(Optional,but installing will be useful). Get it from here
Once you have all of the file we can move on
Steps
------
1. Put Your Phone into fastboot mode by pressing Vol Down and power button at same time.
2.Connect your Phone With Your PC
3.Run EDL Mode.exe from the zip Enter edl.. Now your phone must be in edl mode. You can see a light blinking at the top of your phone.
4. From the Unlock Boot Loader folder copy "emmc_appsboot.mbn" to the rom folder ie)
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global--> images--> paste it there (replace/overwrite if existing)
5. Once the above step is done, Open MIFlash tool as administrator. Browse the folder
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global and select it..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6.From the drop Down Menu Select Advanced.
7.Set Fastboot Script As Flash_ALL.Bat.
8.Set Flash Programmer As prog_emmc_firehose_8976_ddr.mbn from images folder.
9. Set RAW Xml File as rawprogram*.xml from images folder
10. Set Patch XML File as patch*.xml from images folder.
11. Video Help HERE.... Watch from 2.40 (Ignore the other portion,We dont need that Part)
Special [email protected] for the video.. I didn't made that video..
12. Once The Above step is done. Click REFRESH OPTION,and you will see Phone detected By The Name COMXX.(XX will be a number)
13.Click Flash and Wait for some time and allow the phone to reboot.
14.Once all the step is done your phone will be good to use..:fingers-crossed: :fingers-crossed:
UNLOCKING BOOT LOADER AND INSTALLING TWRP AGAIN
-------------------------------------------------------------------------
1.Once Your Phone Reboots successfully enable USB Debugginf From Developer Option.
2.Connect Your phone to your PC and Open CMD as administrator.
3.Type in "adb devices".
4. Cmd will show a random number and Device (Everyone will be knowing this,but for info only iam writing it here)
5.Type "adb reboot bootloader". Now your phone will boot into fastboot mode.
6.Type "fastboot oem device-info" to get device status.
7.Type "fastboot oem unlock-go" to unlock bootloader.
8.Again type "fastboot oem device-info" to check to find if device is unlocked.(Do not reboot YET)
9. Now Downlaod TWRP from HERE
10. Now Got to the folder containig TWRP . By holding the Shift Key Of key Board ,right click the mouse and select OPEN COMMAND WINDOW HERE.
11. Type "fastboot flash recovery recovery_filename.img"
12.Type "fastboot reboot".
You Phone will be good to go. If anything goes wrong or you have any doubt Comment Below do not pm me..i will not reply..
If this thread helpef you thumbs up and do comment and shre this post

So i do not need to unlock the boot loader before using MiTool to flash phone via EDL

ahh988 said:
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
Click to expand...
Click to collapse
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool

adithyan25 said:
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
Click to expand...
Click to collapse
I did that but phone is still stuck . I'm getting infinite boot animation ?

ahh988 said:
I did that but phone is still stuck . I'm getting infinite boot animation ?
Click to expand...
Click to collapse
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed

adithyan25 said:
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
Click to expand...
Click to collapse
I am stuck at boot animation with the three white dots spinning for ever ? will try to do as you said

I tried fastboot oem unlock-go but i get response: token verification failed and device still stuck on bootanimation

well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful

nitephoenix said:
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
Click to expand...
Click to collapse
always my pleasure
For some mi unlock stucks at 50%.. I was one of them...every time I try fails...so I found this was the only way for those who can't access it using mi unlock

tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted

nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
Yeah...I know that...but it does not support volte. .only abhisheks fw sprt volte

nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks

Pleroma said:
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Click to expand...
Click to collapse
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe

nitephoenix said:
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
Click to expand...
Click to collapse
I used to flash it via twrp ..(by deleting bootllader file) followed by flashing lazyflasher...I didn't faced any prblm yet

Mine behaves different
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.

sarabeshsab said:
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
Click to expand...
Click to collapse
Probably the problem with bootloader file

not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.

Jjleininger said:
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Click to expand...
Click to collapse
Download eiter China based ROM or ROM from post.
Mi flash tool have many prolems.
Some tips:-
Make sure driver enforcement is disabled in PC.
All drivers including PDA net is installed.
Copy paste the unlocked bootloade file inside images folder and replace original one. Even after tryig this method it fails try my other method unbrick viafasrboot

uhm, this does not work for some reason...
i did everything as you said but in the end it just says cathasrophic error and something

After flashing i get Mi logo, vibration and reboot, please help

[Z2/Z2 Plus] [Z2131/2] Ultimate Bootloader Unlock & TWRP Install Guide

There are many guides for unlocking bootloader and installing TWRP and there are many misconceptions redarding these.
This is the ultimate guide put together to clear all those.
*Use Mozilla Firefox to get the unlock_bootloader image* Chrome isn't working due to bugs in site
Things you need:
1. ZUK Z2 (Z2131/Z2132) [Obviously]
2. "unlock bootlader.img" from developer.zuk.com
3. Minimal ADB and Fastboot from Here
4. Latest TWRP from Here
5. If you want to root download SuperSU from Here
6. MI Flash Tool from Here
Unlocking bootloader factory resets the device, so backup your files before hand.
Getting the Unlock Image:
This one thing is a big problem to attain for many users.
1. Head to developer.zuk.com (Use Chrome to translate the page)
2. Click Login and use the following details
Username: [email protected]
Password: zukaccount!
Account doesn't work anymore, but you can easily create an account now.
(Login before heading to unlock page)
3 .Click Unlock at the top.
4. Click NEXT on Step 1.
5. Select Z2 from dropdown list.
6. Type in your Serial Number. (You can find it at Settings > About > Status > Serial Number)
If you have a 6 character serial number, add two zeros at end
If you have a 7 character serial number, add one zero at end
7. Give your email ID (Gmail works too)
8. Accept the conditions and click NEXT.
9. A Dialog Box opens up stating that you will recieve an email with the bootloader image.
10. Check your Inbox and Spam folders.
Unlocking Bootloader:
1. Install Minimal ADB and MI Flash (to ensure you get all drivers)
2. Place the "unlock_bootloader.img" in the fastboot installation folder.
3. Run following commands.
(a) adb devices [Your device should be listed, if not, check drivers]
(b) adb reboot bootloader
(c) fastboot -i 0x2b4c flash unlock unlock_bootloader.img
You should see this:
"target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.037s]
writing 'unlock'...
OKAY [ 0.053s]
finished. total time: 0.090s"
(d) fastboot -i 0x2b4c oem unlock-go
You should see this:
"OKAY [ 0.041s]
finished. total time: 0.041s"
(e) fastboot reboot
4. You should end up with an unlocked bootloader.
Installing TWRP:
1. Place TWRP downloaded from official site in the fastboot installation folder.
2. Run the following commands.
(a) adb reboot bootloader
(b) fastboot -i 0x2b4c flash recovery twrp.img
(c) fastboot reboot
3. You have successfully installed TWRP
Rooting using SuperSU.zip
1. Place the downloaded "SuperSU.zip" into the root folder of phone to. (That would be easy to find while installing)
2. Reboot to TWRP
3. Select Install and locate SuperSU.zip
4. Swipe to flash.
You should end up with a unlocked and rooted Z2.
Comment for flaws or if you want me to add more info at a specific step.
Note:
If you get a message saying "Daemon started succesfully" re-run the previous command.
TWRP Links:
TWRP 3.1.0
TWRP 3.1.1
TWRP 3.2.1
Thanks to Balraj at zukfans.eu for Login Details
Goodluck Unlocking :good:
Hit thanks if this helped you.

And finally a guide for newbies like me btw is there any tool to unlock bootloader and flash ROMs like other devices?

AkumDX said:
And finally a guide for newbies like me btw is there any tool to unlock bootloader and flash ROMs like other devices?
Click to expand...
Click to collapse
Happy that this helped you. I don't​ think there is any tool for unlocking and flashing (I think you are refering to ODIN for Samsung). But you can use QPST or MI Flash to flash Stock ROMs.

i stuck in second step
2. Place the "unlock_bootloader.img" in the fastboot installation folder.?????
where is this location
please help me
i can go in adb mode but i cant find the location
I FIND IT i am soo nood

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i cant unlock bootloader :crying: :crying:
---------- Post added 4th June 2017 at 12:33 AM ---------- Previous post was 3rd June 2017 at 11:54 PM ----------
fix it

MacGyverLarisa said:
i stuck in second step
2. Place the "unlock_bootloader.img" in the fastboot installation folder.?????
where is this location
please help me
i can go in adb mode but i cant find the location
I FIND IT i am soo nood
Click to expand...
Click to collapse
Generally it is Program Files or Program Files (x86) > Minimal ADB and Fastboot

zakaria12 said:
i cant unlock bootloader :crying: :crying:
---------- Post added 4th June 2017 at 12:33 AM ---------- Previous post was 3rd June 2017 at 11:54 PM ----------
fix it
Click to expand...
Click to collapse
Did you fix it? If not check if you have given your serial number correctly on unlock request page. You need the device specific image

sammessi10 said:
Generally it is Program Files or Program Files (x86) > Minimal ADB and Fastboot
Click to expand...
Click to collapse
Thank you for your response
After a little thought
I Put it inside the folder that I start to adb mode and it works perfectly

Is it possible to regain warranty after locking bootloader or is the warranty lost ?

Hi is it possible for any one to upload the TWRP.img file ?
I tried it with the one which is in twrp (twrp-3.1.1-0-z2_plus) app however its not working.
It showed flash completed however its still loading old recovery.
i'm currently on android 7 with boot loader unlocked.
Thanks

zakaria12 said:
i cant unlock bootloader :crying: :crying:
---------- Post added 4th June 2017 at 12:33 AM ---------- Previous post was 3rd June 2017 at 11:54 PM ----------
fix it
Click to expand...
Click to collapse
how did you fix that?

aditya1999 said:
how did you fix that?
Click to expand...
Click to collapse
i just request the bootloader Unlock image again because its was Damaged and i flash it and its work

coolsid8 said:
Is it possible to regain warranty after locking bootloader or is the warranty lost ?
Click to expand...
Click to collapse
Yeah it is possible to regain warranty. Flash the stock firmware with QPST or Miflash

akash.mahadeshwar said:
Hi is it possible for any one to upload the TWRP.img file ?
I tried it with the one which is in twrp (twrp-3.1.1-0-z2_plus) app however its not working.
It showed flash completed however its still loading old recovery.
i'm currently on android 7 with boot loader unlocked.
Thanks
Click to expand...
Click to collapse
Try to flash 3.1.0 first and then 3.1.1

zakaria12 said:
i just request the bootloader Unlock image again because its was Damaged and i flash it and its work
Click to expand...
Click to collapse
Thanks I did the same.

Thanks for the guide. Pls do add that ZUK Z2 is not recognized as a device in fastboot.
So one must specify the OEM id . The code is "-i 0x2b4c " for Zuk Z2. So any command fastboot must be suffixed with the following code: -i 0x2b4c

My device doesn't gets detected in fastboot mode by my pc. I have tried all drivers of Lenovo and other manufacturers drivers but it can't detect my device in fastboot mode. But it detects the phone in adb and gets booted to fastboot mode and when i run the command fastboot -i 0x2b4c flash unlock unlock_bootloader.img.
It shows waiting for device . Please Help anyone!.

mity_dev said:
My device doesn't gets detected in fastboot mode by my pc. I have tried all drivers of Lenovo and other manufacturers drivers but it can't detect my device in fastboot mode. But it detects the phone in adb and gets booted to fastboot mode and when i run the command fastboot -i 0x2b4c flash unlock unlock_bootloader.img.
It shows waiting for device . Please Help anyone!.
Click to expand...
Click to collapse
Same with me.. i think it's beacause of nougat as this method is working fine with marshmallow.

sammessi10 said:
There are many guides for unlocking bootloader and installing TWRP and there are many misconceptions redarding these.
This is the ultimate guide put together to clear all those.
Things you need:
1. ZUK Z2 (Z2131/Z2132) [Obviously]
2. "unlock bootlader.img" from developer.zuk.com
3. Minimal ADB and Fastboot from Here
4. Latest TWRP from Here
5. If you want to root download SuperSU from Here
6. MI Flash Tool from Here
Getting the Unlock Image:
This one thing is a big problem to attain for many users.
1. Head to developer.zuk.com (Use Chrome to translate the page)
2. Click Login and use the following details
Username: [email protected]
Password: zukaccount!
(Login before heading to unlock page)
3 .Click Unlock at the top.
4. Click NEXT on Step 1.
5. Select Z2 from dropdown list.
6. Type in your Serial Number. (You can find it at Settings > About > Status > Serial Number)
If you have a 6 character serial number, add two zeros at end
If you have a 7 character serial number, add one zero at end
7. Give your email ID (Gmail works too)
8. Accept the conditions and click NEXT.
9. A Dialog Box opens up stating that you will recieve an email with the bootloader image.
10. Check your Inbox and Spam folders.
Unlocking Bootloader:
1. Install Minimal ADB and MI Flash (to ensure you get all drivers)
2. Place the "unlock_bootloader.img" in the fastboot installation folder.
3. Run following commands.
(a) adb devices [Your device should be listed, if not, check drivers]
(b) adb reboot bootloader
(c) fastboot -i 0x2b4c flash unlock unlock_bootloader.img
You should see this:
"target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.037s]
writing 'unlock'...
OKAY [ 0.053s]
finished. total time: 0.090s"
(d) fastboot -i 0x2b4c oem unlock-go
You should see this:
"OKAY [ 0.041s]
finished. total time: 0.041s"
(e) fastboot reboot
4. You should end up with an unlocked bootloader.
Installing TWRP:
1. Place TWRP downloaded from official site in the fastboot installation folder.
2. Run the following commands.
(a) adb reboot bootloader
(b) fastboot -i 0x2b4c flash recovery twrp.img
(c) fastboot reboot
3. You have successfully installed TWRP
Rooting using SuperSU.zip
1. Place the downloaded "SuperSU.zip" into the root folder of phone to. (That would be easy to find while installing)
2. Reboot to TWRP
3. Select Install and locate SuperSU.zip
4. Swipe to flash.
You should end up with a unlocked and rooted Z2.
Comment for flaws or if you want me to add more info at a specific step.
Note:
1. Unlocking bootloader factory resets the device, so backup your files before hand.
2. If you get a message saying "Daemon started succesfully" re-run the previous command.
TWRP Links:
TWRP 3.1.0
TWRP 3.1.1
Thanks to Balraj at zukfans.eu for Login Details
Goodluck Unlocking :good:
Hit thanks if this helped you.
Click to expand...
Click to collapse
Bro I have some questions
1st does Z2 (Z2131) custom ROM could be flashed on Z2 Plus(Z2132)?
2nd of yes then what is brushed ROM

shridhan varadkar said:
Bro I have some questions
1st does Z2 (Z2131) custom ROM could be flashed on Z2 Plus(Z2132)?
2nd of yes then what is brushed ROM
Click to expand...
Click to collapse
1. Yeah... Both the ROMs are interchangeable.
2. I never heard of it but if you are talking about Bshuy ROM, then it's a bloatfree stock ROM.
PS: Please don't quote the whole OP

Stuck on error mode and I don't have access to recovery mode phone p9 lite

Well I had unlock bootloader from my phone and update it to nougat then try to flash TWRP again but i made a mistake and I tried to flash TWRP for marshmallow so I didn't have access on recovery but I didn't know it because I didn't try to go to recovery mode aafter that I try to relock the bootloader because I thought it will be okay to do that... .(stupid me)
So now to open my phone I have to let the battery end elsewhere when I try to restart the dive or try to power it down and open to recovery mode it gives me the error screen with that Android logo (sorry for my English )
Thanks everyone who will help

I can't alunlock the bootloader because the program I am using to unlock it it turns off the phone and restart it and wait for the device to connect but the devise restart on error mode

SvanGlan said:
But test with fastboot oem unlock S X where you replace 'S' with your serialnumber an 'X' with your unlock password.
Click to expand...
Click to collapse
How I do that ? With ADB?

SvanGlan said:
No, no, no, nooooo! I said with fastboot, and I told you the command. You can not do it with ADB. At least what I know.
Click to expand...
Click to collapse
I am new to this so how I am going to do that?

i have similar problem.
P9 lite is in error mode. i have download update.app put it into dload folder.
But after forcing update volume + - and power only red lightning shows up, i guess battery is low.
But after connecting to charger error mode appears again and i am not sure if it is charging or not.
Any idea?
thanks

misko0709 said:
i have similar problem.
P9 lite is in error mode. i have download update.app put it into dload folder.
But after forcing update volume + - and power only red lightning shows up, i guess battery is low.
But after connecting to charger error mode appears again and i am not sure if it is charging or not.
Any idea?
thanks
Click to expand...
Click to collapse
If you have the same problem with me with the error screen let the phone to close and then plug in the charger and press the power button to open your phone .. then charge it shut it down normally and do the thing with volume +- I guess it will work.. (I don't know)

misko0709 said:
i have similar problem.
P9 lite is in error mode. i have download update.app put it into dload folder.
But after forcing update volume + - and power only red lightning shows up, i guess battery is low.
But after connecting to charger error mode appears again and i am not sure if it is charging or not.
Any idea?
thanks
Click to expand...
Click to collapse
What you want to say is probably that you get an error when forceupdating. What I've heard there's no error mode in the 'Huawei-world'.
You're probably getting an error because the updatepackage is corrupt or not working/is not compatible with your device.
How to enter fastboot:
1. Power off your device.
2. Plug in your device with a USB cable to to your computer. (Make sure that the cable supports file transfer.)
3. Press and hold Volume up/Volume + and Power button.
4. You're probably in fastboot now.

i cannot turn off phone, it still rebooting into "error mode", even if i press powert button and both volume keys it goes to red lightinng screen and again reboot to "error mode".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

SvanGlan said:
Power off your device. Hold down VOLUME DOWN + POWER button, remember to have your USB cable connected to your PC. Boom, now you're in fastboot. Then you just put in the command.
To see serialnumber:
In fastboot type fastboot devices one of the number will be your serialnumber, probably the longest number.
Unlockpassword:
https://hwid5.vmall.com/CAS/portal/...ndex&loginChannel=22000000&reqClientType=2023
Sign in there with your Huawei ID (it has to be more than 2 weeks old for some reason) follow the onscreen instructions and after a while you'll get your unlock password.
Click to expand...
Click to collapse
When I am on fastboot in what command I am goin to write? From Windows?

It depends.
Alexpap98 said:
When I am on fastboot in what command I am goin to write? From Windows?
Click to expand...
Click to collapse
It depends on what you want to do....
Unlock bootloader:
fastboot oem unlock <Serial numberr> <unlock password>
Install TWRP:
Use my guide:
I'll have to post some more posts before I can send links....
Rough steps (Bootloader must be unlocked!) : 1. Download ADB and FASTBOOT tools. 2. Download TWRP (the one by @OldDroid is recommended). 2.5. Move the TWRP image to the same folder as ADB and FASTBOOT tools are located in. 3. Open MAF32 and type "fastboot flash recovery <thenameofyourtwrp.img>" 4. Done!
Sorry for taking so long to answer.....
---------- Post added at 07:19 AM ---------- Previous post was at 07:19 AM ----------
Alexpap98 said:
When I am on fastboot in what command I am goin to write? From Windows?
Click to expand...
Click to collapse
It depends on what you want to do....
Unlock bootloader:
fastboot oem unlock <Serial numberr> <unlock password>
Install TWRP:
Use my guide:
I'll have to post some more posts before I can send links....
Rough steps (Bootloader must be unlocked!) : 1. Download ADB and FASTBOOT tools. 2. Download TWRP (the one by @OldDroid is recommended). 2.5. Move the TWRP image to the same folder as ADB and FASTBOOT tools are located in. 3. Open MAF32 and type "fastboot flash recovery <thenameofyourtwrp.img>" 4. Done!
Sorry for taking so long to answer.....

I try fastboot OEM unlock but failed : remote command not allowed

BurnyLlama said:
It depends on what you want to do....
Unlock bootloader:
fastboot oem unlock <Serial numberr> <unlock password>
Install TWRP:
Use my guide:
I'll have to post some more posts before I can send links....
Rough steps (Bootloader must be unlocked!) : 1. Download ADB and FASTBOOT tools. 2. Download TWRP (the one by @OldDroid is recommended). 2.5. Move the TWRP image to the same folder as ADB and FASTBOOT tools are located in. 3. Open MAF32 and type "fastboot flash recovery <thenameofyourtwrp.img>" 4. Done!
Sorry for taking so long to answer.....
---------- Post added at 07:19 AM ---------- Previous post was at 07:19 AM ----------
It depends on what you want to do....
Unlock bootloader:
fastboot oem unlock <Serial numberr> <unlock password>
Install TWRP:
Use my guide:
I'll have to post some more posts before I can send links....
Rough steps (Bootloader must be unlocked!) : 1. Download ADB and FASTBOOT tools. 2. Download TWRP (the one by @OldDroid is recommended). 2.5. Move the TWRP image to the same folder as ADB and FASTBOOT tools are located in. 3. Open MAF32 and type "fastboot flash recovery <thenameofyourtwrp.img>" 4. Done!
Sorry for taking so long to answer.....
Click to expand...
Click to collapse
It's okay dude don't be sorry you trying to help
I try fastboot OEM unlock but failed : remote command not allowed

Alexpap98 said:
It's okay dude don't be sorry you trying to help
I try fastboot OEM unlock but failed : remote command not allowed
Click to expand...
Click to collapse
Okay, can you still boot into system?
BTW, SvanGlan is my friend, he asked me about answers. A tip is to ask me instead I have a Huawei P9 lite, he doesn't.
BTW do you have Discord? You can get faster answers from me there if you want. [BurnyLlama#0524]