Database Users

[HOW-TO]Unlock the Bootloader on the Nvidia Shield

Introduction
The purpose of this guide is to provide you with step-by-step instructions on how to unlock the bootloader on your Nvidia Shield.
Why Would I want to Unlock my Bootloader?
Unlocking your bootloader allows you to modify all aspects of your device to suite your needs which includes but is not limited to, installing custom Recovery images such as Clockworkmod Recovery or Team Win Recovery Project, installing custom ROM's, custom Kernels, as well as other MOD's and patches.
Will Unlocking my Bootloader Void my Warranty?
Warning: Unlocking your Nvidia Shield's bootloader will void the warranty, please note that even if you re-lock the bootloader the bootloader still show a flag that the device is voided for warranty.
This warning being given please also see this post by JordanKeyes regarding warranty information as it relates to hardware issues or hardware failures.
Unlocking your Bootloader
1. Backup everything on your device that you don't want to loose such any apps (And there respective data), pictures, videos, music, etc. as unlocking your devices bootloader will erase all data on the device. You can fully backup your devices contents without root using ADB's backup command or by using the Holo Backup Tool.
2. Download and install the ADB and Fastboot drivers for your Shield, the drivers can be downloaded here. You can also follow along with wwjoshdew's excellent video tutorial on how to properly install the ADB and Fastboot drivers for your Shield on Windows.
3. Make sure you have ADB and Fastboot setup and installed on your computer. If you haven't already setup and installed ADB and Fastboot a simple ADB and Fastboot installer can be downloaded from here.
4. Fully power off your Shield by long pressing on the Power button until the power menu appears, then select the "Power off" option.
5. Boot your Shield into Fastboot mode using one of the following ways:
5. A. Power on your Shield while simultaneously holding the Power button + Back button + Home button. Release the buttons once the Fastboot bootloader screen appears.
5. B. Run the following ADB command from a command prompt window (USB cable must already be connected from your Shield to your Computer):
Code:
adb reboot bootloader
6.Now that you are at the Fastboot bootloader screen, connect your Shield to your computer using your USB cable. Make sure that your USB cable is plugged into a USB 2.0 port directly connected to your motherboard as sometimes USB 3.0 ports can cause problems and front panel USB connections can be unreliable.
7. Open up a command prompt window (cmd) in the directory where installed ADB and Fastboot to. For example if I installed ADB and Fastboot to a folder on my Desktop which is on my D: drive I would open a command window in "D:\Desktop\Fastboot_ADB".
8. From the command prompt windows enter the following command:
Code:
fastboot devices
If you device is detected and it shows your devices serial number you are ready to move on to the next step. If no device is shown make sure you have the correctly installed the ADB and Fastboot drivers from step number 2.
9. Now that your device is detected by Fastboot the following command is used to unlock your bootloader:
Code:
fastboot oem unlock
10. You will now be presented with the bootloader unlock menu. After reading the disclaimer, use the Back button and the Home button to navigate to the "Unlock" option. Once the "Unlock" option has been highlighted use the Shield button to confirm your selection of unlocking your bootloader. It's important to remember that unlocking the bootloader will wipe all your data from the device, and that a flag showing your warranty is void will appear at the bootloader screen.
11. Once your bootloader has finished being unlocked, you will be taken back to the fastboot bootloader screen. From here you can power off your Shield.
Re-locking your Bootloader
To re-lock your bootloader you can following steps 4-8 of the procedure listed above and when you come to step 9 run the following command instead of "fastboot oem unlock":
Code:
fastboot oem lock
The above command will re-lock your Shield's bootloader. Note: As previously mentioned re-locking your Shield's bootloader will not restore your warranty or remove the warranty void flag on your device's bootloader.
Conclusion
Now that you have successfully unlocked the bootloader on your Nvidia Shield you are free to flash custom Recoveries, ROM's, Kernel's, MOD's etc. enjoy :good:.
If you are stuck with the bootloader unlocking procedure I would recommend checking out this great video tutorial by wwjoshdew.

I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Edit: followed the instructions in the following video and all is dandy now. http://www.youtube.com/watch?v=XSisjVwcPbE&hd=1

themichael said:
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Click to expand...
Click to collapse
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.

fastboot error
chevyowner said:
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
Click to expand...
Click to collapse
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.

gogul1 said:
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
Click to expand...
Click to collapse
Nvidia just released a new set of USB drivers in their Tegra for Android Development Pack which you can download from here. I would recommend installing the development pack and the drivers it includes.

ok
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148

gogul1 said:
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
Click to expand...
Click to collapse
From that pic you posted the mount command failed because you were not root.

chevyowner said:
From that pic you posted the mount command failed because you were not root.
Click to expand...
Click to collapse
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.

shimp208 said:
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
Click to expand...
Click to collapse
Huh??????????
EDIT
Were you trying to answer this post

chevyowner said:
Huh??????????
EDIT
Were you trying to answer this post
Click to expand...
Click to collapse
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!

shimp208 said:
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
Click to expand...
Click to collapse
No problem.
I had to change to oil in my car in a parking lot earlier because it was cheaper to change it then it would have been add 3-4 quarts and change it when I got home. My car need 5 quarts of oil. I was not in a a good mood then.

I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs

thx. works nice.

wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: [
How To Root the Nvidia Shield: []
Click to expand...
Click to collapse
Sweet thanks

wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Click to expand...
Click to collapse
I tried another proggie to root and got jammed up.. following the videos josh did had me rooted in minutes. Great job and thanks!

why?
Code:
C:\Users\Thomas>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I tried it with the Shield RAM tool, but won't work either..

so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.

mr.dude5660 said:
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
Click to expand...
Click to collapse
Where did you find the towelroot apk? Been searching for over a month with no success.
Sent from my VS980 4G using Tapatalk

BTW, bootloader mode on the tablet:
- Hold "Volume Down" -> Press "Power" and continue to hold "Volume Down" until device boots into bootloader mode.
There is no home or back button to press while the device is off.

Sorry for bump this thread, but i have to.
I want to unlock my bootloader to revert back into KK and then try to do a clean installation of LP. Reading this guide and watching the videos, and also looking into the img downloaded from nvidia, it says i have to install the fastboot drivers. The problem is that i have already installed fastboot and adb drivers since i have some other devices as a Xperia and stuff. For me, there is no Yellow sign as shown in the video, my device is recognized as Portable Device and it already says "Shield Tablet" MTP.
I've tried going into bootloader to see if it prompts any new devices but i got nothing. adb devices show my device, but i'm not sure if i need more.

[GUIDE] Root Stock N using jcadduono's Recowvery tool. H830.

Using the following method I was able to successfully ROOT my H830 running stock 20A NOUGAT. With this root method you will get TWRP Recovery and SuperSU. This method WILL wipe your internal storage, so please BACKUP!​
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, or lost photographs.
Please do some research if you have any concerns about root!​
I used jcadduono's method which he describes on the V20 forum [Easy Recowvery ALL CREDITS TO THE AUTHOR. PLEASE GO RATE HIS THREAD AND CLICK THANKS IF THIS WORKS FOR YOU!] https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594​
1. Bootloader Unlock
For this method to work you must have an unlocked bootloader. Despite the fact that I already had an unlocked bootloader, after the upgrade to stock N, jcadduono's script failed to work initially and gave me an error message saying my bootloader was locked. To fix this I had to manually relock and unlock my bootloader one more time. Unlocking/Locking your bootloader will wipe the internal storage of the devices so backup before this step. If you however, already have an unlocked bootloader, feel free to skip this step and go on, although in the end you might have to return to it if you get a "bootloader locked" message in the Recowvery script. If you do skip these steps, don't forget to download the LG Drivers from below.
1. Download and install the latest LG Drivers from HERE
2. Download the minimal adb and fastboot tool from HERE. I recommend the portable version, which you can extract to your desktop.
3. On your phone, go to Developer Options and turn on Enable OEM Unlock.
4. Enter fastboot mode: Turn off your device, press and hold the volume down button, while holding the volume down button connect your phone to your computer by USB, continue holding the volume down button until your device enters into fastboot mode.
5. On your computer go to the folder which you extracted in step 2. Open a command window by holding down SHIFT, right clicking with you mouse inside the folder, and selecting "Open command window here"
6. In the command window type "fastboot oem unlock" to unlock your bootloader, this will erase all of your data.
7. Type "fastboot reboot" to reboot to system.
2. Installing TWRP using Recowvery
Prior to this step I HIGHLY recommend factory resetting your device, if you just unlocked your bootloader, your device was automatically factory reset so you are good to go. Once your phone turns on after a factory reset, I suggest signing into your google account and setting up your phone as if you are going to use it, we will not be factory resetting after this step. However do not download any apps or mess with the settings yet, you can do that later, once your device is successfully rooted.
1. On your computer, download Recowvery from HERE and extract the folder to your desktop.
2. Now on your phone enable USB Debugging in Developer Options.
3. Connect your phone to the computer and make sure File Transfer is chosen in the "Use USB connection for" pop-up.
4. On your computer, download the latest version of TWRP: H830 or H850
5. Rename the downloaded file to "recovery.img" and place it on your phone's internal storage [/storage/emulated/0]
6. On your computer, open the Recowvery folder you extracted in step 1, and click on EasyRecowvery.
7. Once there, type option "5" and "ENTER", in the "Extras and Advanced Tools Menu" disable integrity verification by typing option "7" and "ENTER". Return to the main Menu of Recowvery by typing option "0" and "ENTER"
6. After disabling integrity verification, run the exploit by choosing option "1"
7. Follow the prompts in Recowvery, your phone should reboot about two times in the process.
8. DO NOT Wipe Cache while in TWRP.
8. Once finished, your device should reboot to system and will have TWRP recovery, instead of the stock recovery. The only thing left now is to install SuperSU.
3. Installing SuperSU through TWRP
Although Recowvery does give you an option to install SuperSU through its interface, doing so caused problems in my case. Therefore I recommend manually booting into TWRP and installing SuperSU from there.
1. Download the latest version of SuperSU from HERE and place the .ZIP file on your phone's internal storage.
2. To boot into TWRP, go into the adb and fastboot folder, which I described in the very first steps of this tutorial. There, once again open a command window and type "adb reboot recovery".
3. You should now be in TWRP, there select Install, find the .ZIP file of SuperSU in the file explorer, and install it. DO NOT Wipe Cache after the installation.
4. Reboot to sytem, you should now have a rooted LG G5 with TWRP and SuperSU installed!
Credits:
jcadduono - Recowvery
RealPariah - Compiled Recowvery zip for LG G5
shimp208 - Minimal ADB
TWRP
SuperSU​

[Reserved]

I'll try this later tonight, I spent the whole night yesterday trying that. Thanks in advance. ???

Didn't work for me. Thanks for this though. The script actually made it's way through this time (multiple times at this point), but whenever I try to adb reboot recovery I get the "No Command" screen (which I believe is still the stock recovery?). Success all the way through. Don't know what I could be missing.
Also tried manually pushing the recovery image via adb thinking there might be an "Internal Storage" (as seen by pc) vs "/storage/emulated/0" on the phone. No dice either way.

Dumboguy03 said:
Didn't work for me. Thanks for this though. The script actually made it's way through this time (multiple times at this point), but whenever I try to adb reboot recovery I get the "No Command" screen (which I believe is still the stock recovery?). Success all the way through. Don't know what I could be missing.
Also tried manually pushing the recovery image via adb thinking there might be an "Internal Storage" (as seen by pc) vs "/storage/emulated/0" on the phone. No dice either way.
Click to expand...
Click to collapse
To me it seems like your recovery is not flashing, make sure to download the latest version of TWRP, rename it "recovery.img", and place on the internal storage of the device. If still doesn't work, try a complete clean start. Relock and unlock your bootloader again.

To be safe, I would remove "others try at your own risk" as it will not work and could possibly brick any model other than the H830 and H850. All other models are bootloader locked and I have tested myself; it won't work on anything else.

It worked! Thank you so much.

It worked! Thank you!!!👍👍👍
Sent from my LG-H830 using XDA-Developers mobile app

If you however, already have an unlocked bootloader, feel free to skip this step and go on, although in the end you might have to return to it if you get a "bootloader locked" message in the Recowvery script.
What do you mean with thiz sentence? We cant unlock our bootloader its not supported, can we still try this method?

Will this trigger some flag or fuse? Or with the flash of the firmware though lgup and locking the bootloader will create a Perfect stock device?

Can someone confirm it works on H850

yken said:
If you however, already have an unlocked bootloader, feel free to skip this step and go on, although in the end you might have to return to it if you get a "bootloader locked" message in the Recowvery script.
What do you mean with thiz sentence? We cant unlock our bootloader its not supported, can we still try this method?
Click to expand...
Click to collapse
No, you have to have an unlocked bootloader. I meant if you already unlocked your bootloader, you can skip this step. Possibly it will work once we get bootloader unlocks for other variants of the G5.

Do I have driver issues? Adb recognizes phone when turned on. When in fastboot only waits for device to connect.
Sent from my LG-H830 using Tapatalk

Tinbender418 said:
Do I have driver issues? Adb recognizes phone when turned on. When in fastboot only waits for device to connect.
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
The drivers in the post should work for both fastboot and adb. What do you mean, "when in fastboot only waits for device to connect"? You can run the "fastboot devices" command there to see if the device is recognized.

Will not let me run any commands. Just says waiting for device. Crazy, I know.
Sent from my LG-H830 using Tapatalk

Looks like hd on pc is going.
Sent from my LG-H830 using Tapatalk

adb and fastboost not recognizing my phone even after installing drivers

Finally got root back. My problem was getting adb to work but I had no problems with minimal adb and fastboot. Thanks for the tutorial.

Will we be able to flash the current roms that our out?
Sent from my LGE LG-H830 using XDA Labs

Running in normal exploit mode
Press any key to continue . . .
- - - Making sure we're good to go - - -
Checking permissions in the EasyRecowvery directory...Checking that the exploit files exist...SUCCESS!
Locating adb.exe... SUCCESS!
Looking for ADB device...
This device doesn't look like a T-mobile V20. Proceed anyway? (DANGEROUS!)
(Y/N) y
Checking unlock status... error: device '*' not found
FAILED!
Your device does not appear to be unlocked.
Please boot into fastboot mode and run:
fastboot oem unlock
From your computer, then try again.
http://i.imgur.com/2BhNatP.png
Press any key to continue . . .
so this is what i am running into. I know with 100% certainty that the device is oem unlocked. I get the whole, "your device software can not be checked for corruption" screen and everything.
i started the process completely stock, with oem locked. I unlocked it as per your instructions and followed everything closely as far as I can tell. i have tried to re-lock oem . reboot and then unlock it again twice, as well as rebooting pc and G5 multiple times. usb debugging is turned on, and usb options are set to file transfer. still same result.
Any ideas?
EDIT: i will leave the whole post up in case some one makes the same mistakes i did and this helps them out. What i needed to do to fix this was simply set "use usb connection for " to photo transfer instead of file transfer.
Now i am stuck on :\Users\test\Desktop\LgG5 RooT\minimal_adb_fastboot_1.4.1_portable>adb reboot recovery
error: no devices/emulators found like another person before me. hopefully this will be figured out soon
EDIT#2: used adb reboot recovery command with phone turned on and on main screen of launcher, not fast boot, like i was trying at first. and twrp loaded up fine.
dont have a sd card to put superuser.zip on and it seems like i can't reach the internal storage download folder through twrp, or atleast i could not find it, so i ended up sideloading it by going to sideload in twrp and typing "adb sideload SR1-SuperSU-v2.79-SR1-20161221223537.zip"
into it.
i hope that documenting all my mistakes and solutions for everyone to see will help someone running into the same problems i was.

Boot loop after Android O DP2 update

I installed Android O DP2 update via OTA yesterday. The phone updated, rebooted to the new build and restarted abruptly and since then has been stuck in a boot loop. The Google logo shows up, goes to the android animation step and then Google logo appears again.
I don't have bootloader unlocked, don't have TWRP and have done OTA updates. I am able to get into the stock recovery mode.
How do I fix this, i.e. make it work in any way without erasing the user data? I don't mind extreme steps (without erasing user data) because I was planning to reflash 7 with unlocking & rooting today.

Try to wipe cache from recovery - in recovery hold volume-down and select "Wipe cache partition". Should do the trick

I tried, didn't work. Had to factory reset in the end. Also opted out of beta

I just read that some people that took the update from certain builds had boot loops due to the update only replacing part of the OS but leaving the 7.x.x system in place causing it to boot loop. I think it was like on android authority or something like that.
Sent from my Nexus 6P using XDA-Developers Legacy app

I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks

citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
POWER BUTTON + VOLUME DOWN BUTTON
Click to expand...
Click to collapse
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.

Mavelos said:
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.

citifone said:
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
Click to expand...
Click to collapse
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.

FAILED (remote: OEM unlock is not allowed)
Mavelos said:
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
Click to expand...
Click to collapse
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.

Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?

citifone said:
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
Click to expand...
Click to collapse
To unlock you first need to have ticked the allow OEM unlock from developer menu within the OS. It won't work otherwise.

Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.

Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here [="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?

Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.

scorneil said:
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
Click to expand...
Click to collapse
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Lord Aguacate said:
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Click to expand...
Click to collapse
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.

i have the same problem with this, and i cannot unlock it too, is there anyway to unlock this phone?

OTG works Perfect! But.....
Mavelos said:
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
Click to expand...
Click to collapse
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards

Lord Aguacate said:
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Click to expand...
Click to collapse
You're welcome. Get your phone fixed and return to the flashing community.

last night i my phone inside my freezer hehehe and this morning i tried to turn it on, and it pass the google logo boot normally but it only lasted for a few minute and then turn off and bootloop again. so i guess my 6p has a hardware faulty

How to Stock FW and Relock Bootloader? OP5

Hi all,
I've wanted to go back to Stock OS but when i type "fastboot oem lock" it says "FAILED <remote: Flashing Lock is not allowed."
Everything boots normally to OS 4.5.2. In DEV options the Unlock Bootloader is greyed out and says bootloader is already unlocked.
What can i do?
Cheers

These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5

reayard said:
These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5
Click to expand...
Click to collapse
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).

r1card0amr said:
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).
Click to expand...
Click to collapse
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..

mohan_kr said:
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..
Click to expand...
Click to collapse
Hello. I first thing I do always is to install drivers. I start by connecting the phone to the laptop in charge mode, then in transfer files mode, MTP or camera. In this way he will recognise all the drivers your laptop needs.
Also I enter in fastboot mode and recovery so the laptop can recognise the drivers and always reboot laptop and phone just to double check.
What I did was: go to Developer Options and enabled Unlock Bootloader and USB Debugging.
Then I accepted the laptop request on my phone and all drives were OK.
I run CMD and typed fastboot devices to see if it recognises my phone and it displayed a serial number. So I proceed next to type fastboot oem unlock and the process went OK and on my phone it asked Yes or No to unlock and I choose yes.
Then I flash a twrp image by typing on CMD: fastboot flash recovery recovery.img (my twrp I'm had other name so I rename it. You need to enable "Show file extensions" in Windows so you can see what the extension is).
I then type fastboot boot recovery.img and the phone entered in Recovery Mode in this case TWRP.
My phone was always connected to the laptop and he open the internal storage window so I drag the supersu inside.
Then on TWRP I wiped dalvik and cache and I went to Install and installed the SupeSU on my internal memory root.
The phone then rebooted and ready to go.
But then I went to developer options and the Unlock bootloader was greyed out. I unroot my phone and flashed a stock recovery for OP5 and the stock image 4.5.2 and when I type fastboot oem lock it always says it can't be flashed.
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Just installed supersu to try an app. I never install 3rd party roms.

r1card0amr said:
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Click to expand...
Click to collapse
the warranty is not voided with unlocked bootloader..
https://oneplus.net/hk/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty

I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.

r1card0amr said:
I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.
Click to expand...
Click to collapse
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.

Hogyoku said:
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.
Click to expand...
Click to collapse
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.

I rooted my device with Magisk, and now I want to restore it to factory state.
I flashed stock recovery and OOS several times, wiped everything but fastboot oem lock failed all times (FAILED (remote: Flashing Lock is not allowed)).
Can you help me?
What should I do to relock bootloader?

here is your solution
r1card0amr said:
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.
Click to expand...
Click to collapse
here in this video u can see in detail how to lock bootloader. hope this help you
https://www.youtube.com/watch?v=CQYCSdDUdAU

HOW TO RELOCK..
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled"
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.

I usually do it this way (successfully):
Wipe everything but OTG in TWRP
Format data
Reboot to TWRP
Flash the full stock OOS zip
Reboot to fastboot
Flash stock recovery
Lock bootloader with the fastboot lock command

Has anyone made any progress with this? I too am having the issue as described and have tried the solution by Ricyksydhu, along with solutions from various other places around the net.

[GUIDE] Root Huawei Honor 5C and install TWRP custom recovery (EMUI 5.X)

Did not find any post mentioning rooting for 5C on EMUI. If there are any, let me know and I will take down this thread.
Note-
Applicable for Windows 7, Windows 8 and Windows 10
Similar steps are applicable for EMUI 4.X as well but TWRP file will change.
Saw many user on Honor 5C FB page and on XDA struggling to get root working on EMUI 5. most of the cases I saw, were for EMUI 5.X. I followed the steps mentioned or as applicable for any devices and I did not face any issue so though of compiling this guide for new users who may have faced issue or not able to root the phone. (may be mainly because of correct and working TWRP issue) . I will just simplify the steps so that any new users can do this without any problem and without any prior experience to rooting, it may be long but will be the simple enough for all the users.
Prerequisites-
Enable the developer option in settings-
Go to Settings--> About Phone-->Tab build number 7 times to enable this setting.
Go back in setting page, just above system update, you will see a new menu as -Developer Options
Scroll for the debugging section and enable the USB Debugging
You will be prompted for the confirmation with RSA key, just accept it.
Enable OEM Unlock in Developer Options (just above the USB debugging option) – Most probably this option will not be there on EMUI 5.0 (only few have seen on EMUI but it was there on EMUI 4.1 for all but rarely on EMUI 5.0 or may be because I have used dload most of the time which grayed out this)
Installation of required Drivers.
Connect your phone to PC and install Hi Suite on PC and it will additionally install all the necessary drivers to PC and HiSUite on Mobile.
Download and Install ADB from Link
Accept all the prompts and install ADB drive system wise.
Once installation is completed, if default options are chosen, it will be under C:\adb
Downloading the necessary files.
Download TWRP from Link Thanks to @OldDroid for his Original Thread . Rest of the contributor and credit in original thread by OldDroid.
Move the downloaded file under C:\adb or wherever you have installed the ADB.
Download the SuperSU file from this Link and put it in SD card or keep handy on PC so that you can copy to internal memory later.
Get the unlock as mentioned in this thread
Actual Procedure
Unlocking the bootloader-
Backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
On windows machine, go to folder C:\adb or wherever you installed the adb drivers.
Press shift+right click together and select Open command prompt here
Run - adb reboot bootloader (this command may prompt for acceptance of RSA key if not already accepted)
This will boot the phone into bootloader mode.
Run - fastboot oem unlock <16 digit unlock code- Put your actual code you obtained from Huawei site > (This step will unlock the bootloader and will erase all your data)
Phone will restart automatically.
Installing TWRP
Once on the system, open the PowerShell or command prompt again in ADB folder (can use the previous instance as well)
Run - adb reboot bootloader
Once in bootloader, Run - fastboot flash recovery twrp-3.1.1-0-venus.img (This will install the TWRP recovery for EMUI 5.0 on your phone)
Once done with the flashing the TWRP, Run - fastboot reboot
Rooting
Once booted to system, open the PowerShell or command prompt in ADB folder (can use the previous instance as well)
Run - adb reboot recovery
And your phone will boot into the TWRP recovery.
Copy the SuperU file downloaded to SD card or Internal memory.
Install the SuperSU zip.
Reboot and enjoy.
Happy Flashing.

working twrp on NEM-L21 https://github.com/OpenKirin/android...0-2-hi6250.img
working supersu on NEM-L21 https://drive.google.com/file/d/0BxW...9ZRGxBTUE/view

Voutsjude said:
working twrp on NEM-L21 https://github.com/OpenKirin/android...0-2-hi6250.img
working supersu on NEM-L21 https://drive.google.com/file/d/0BxW...9ZRGxBTUE/view
Click to expand...
Click to collapse
Page not found for first and file not found for 2nd.
The links and the files mentioned in this thread will work on any honor 5C and are live files.

Nice and Thankssss
shashank1320 said:
did not find any post mentioning rooting for 5c on emui. If there are any, let me know and i will take down this thread.
note-
applicable for windows 7, windows 8 and windows 10
similar steps are applicable for emui 4.x as well but twrp file will change.
saw many user on honor 5c fb page and on xda struggling to get root working on emui 5. Most of the cases i saw, were for emui 5.x. I followed the steps mentioned or as applicable for any devices and i did not face any issue so though of compiling this guide for new users who may have faced issue or not able to root the phone. (may be mainly because of correct and working twrp issue) . I will just simplify the steps so that any new users can do this without any problem and without any prior experience to rooting, it may be long but will be the simple enough for all the users.
prerequisites-
enable the developer option in settings-
go to settings--> about phone-->tab build number 7 times to enable this setting.
go back in setting page, just above system update, you will see a new menu as -developer options
scroll for the debugging section and enable the usb debugging
you will be prompted for the confirmation with rsa key, just accept it.
enable oem unlock in developer options (just above the usb debugging option) – most probably this option will not be there on emui 5.0 (only few have seen on emui but it was there on emui 4.1 for all but rarely on emui 5.0 or may be because i have used dload most of the time which grayed out this)
installation of required drivers.
connect your phone to pc and install hi suite on pc and it will additionally install all the necessary drivers to pc and hisuite on mobile.
download and install adb from link
accept all the prompts and install adb drive system wise.
once installation is completed, if default options are chosen, it will be under c:\adb
downloading the necessary files.
download twrp from link thanks to @olddroid for his original thread . Rest of the contributor and credit in original thread by olddroid.
move the downloaded file under c:\adb or wherever you have installed the adb.
download the supersu file from this link and put it in sd card or keep handy on pc so that you can copy to internal memory later.
get the unlock as mentioned in this thread
actual procedure
unlocking the bootloader-
backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
on windows machine, go to folder c:\adb or wherever you installed the adb drivers.
press shift+right click together and select open command prompt here
run - adb reboot bootloader (this command may prompt for acceptance of rsa key if not already accepted)
this will boot the phone into bootloader mode.
run - fastboot oem unlock <16 digit unlock code- put your actual code you obtained from huawei site > (this step will unlock the bootloader and will erase all your data)
phone will restart automatically.
installing twrp
once on the system, open the powershell or command prompt again in adb folder (can use the previous instance as well)
run - adb reboot bootloader
once in bootloader, run - fastboot flash recovery twrp-3.1.1-0-venus.img (this will install the twrp recovery for emui 5.0 on your phone)
once done with the flashing the twrp, run - fastboot reboot
rooting
once booted to system, open the powershell or command prompt in adb folder (can use the previous instance as well)
run - adb reboot recovery
and your phone will boot into the twrp recovery.
copy the superu file downloaded to sd card or internal memory.
install the supersu zip.
reboot and enjoy.
Happy flashing.
Click to expand...
Click to collapse
works perfect at me , thank you so much
here is my phone model and android version

Thank you so much... Love ya for this! I wish u all the success for future works..
shashank1320 said:
Did not find any post mentioning rooting for 5C on EMUI. If there are any, let me know and I will take down this thread.
Note-
Applicable for Windows 7, Windows 8 and Windows 10
Similar steps are applicable for EMUI 4.X as well but TWRP file will change.
Saw many user on Honor 5C FB page and on XDA struggling to get root working on EMUI 5. most of the cases I saw, were for EMUI 5.X. I followed the steps mentioned or as applicable for any devices and I did not face any issue so though of compiling this guide for new users who may have faced issue or not able to root the phone. (may be mainly because of correct and working TWRP issue) . I will just simplify the steps so that any new users can do this without any problem and without any prior experience to rooting, it may be long but will be the simple enough for all the users.
Prerequisites-
Enable the developer option in settings-
Go to Settings--> About Phone-->Tab build number 7 times to enable this setting.
Go back in setting page, just above system update, you will see a new menu as -Developer Options
Scroll for the debugging section and enable the USB Debugging
You will be prompted for the confirmation with RSA key, just accept it.
Enable OEM Unlock in Developer Options (just above the USB debugging option) – Most probably this option will not be there on EMUI 5.0 (only few have seen on EMUI but it was there on EMUI 4.1 for all but rarely on EMUI 5.0 or may be because I have used dload most of the time which grayed out this)
Installation of required Drivers.
Connect your phone to PC and install Hi Suite on PC and it will additionally install all the necessary drivers to PC and HiSUite on Mobile.
Download and Install ADB from Link
Accept all the prompts and install ADB drive system wise.
Once installation is completed, if default options are chosen, it will be under C:\adb
Downloading the necessary files.
Download TWRP from Link Thanks to @OldDroid for his Original Thread . Rest of the contributor and credit in original thread by OldDroid.
Move the downloaded file under C:\adb or wherever you have installed the ADB.
Download the SuperSU file from this Link and put it in SD card or keep handy on PC so that you can copy to internal memory later.
Get the unlock as mentioned in this thread
Actual Procedure
Unlocking the bootloader-
Backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
On windows machine, go to folder C:\adb or wherever you installed the adb drivers.
Press shift+right click together and select Open command prompt here
Run - adb reboot bootloader (this command may prompt for acceptance of RSA key if not already accepted)
This will boot the phone into bootloader mode.
Run - fastboot oem unlock <16 digit unlock code- Put your actual code you obtained from Huawei site > (This step will unlock the bootloader and will erase all your data)
Phone will restart automatically.
Installing TWRP
Once on the system, open the PowerShell or command prompt again in ADB folder (can use the previous instance as well)
Run - adb reboot bootloader
Once in bootloader, Run - fastboot flash recovery twrp-3.1.1-0-venus.img (This will install the TWRP recovery for EMUI 5.0 on your phone)
Once done with the flashing the TWRP, Run - fastboot reboot
Rooting
Once booted to system, open the PowerShell or command prompt in ADB folder (can use the previous instance as well)
Run - adb reboot recovery
And your phone will boot into the TWRP recovery.
Copy the SuperU file downloaded to SD card or Internal memory.
Install the SuperSU zip.
Reboot and enjoy.
Happy Flashing.
Click to expand...
Click to collapse
Thank you so much... Love ya for this! I wish u all the success for future works..

tahahaiyat said:
Thank you so much... Love ya for this! I wish u all the success for future works..
Click to expand...
Click to collapse
Thanks for lovely wishes

Hi all.
I need help with installation ADB. Download file, start installation, accept all the prompts but 0 files copied and dont have file under C:\adb.
What is wrong? How install ADB?
Thanks

outcastWBC said:
Hi all.
I need help with installation ADB. Download file, start installation, accept all the prompts but 0 files copied and dont have file under C:\adb.
What is wrong? How install ADB?
Thanks
Click to expand...
Click to collapse
Method is same as given in instructions. It shoukd install without issue buddy

Hello,
I had the NEM-L51 from my mother running EMUI 4.0x, and decided to upgrade it to the latest version.
It was unlocked, with TWRP as recovery, and rooted.
I did flash back the stock recovery (from HuaweiUpdateExtractor/Update.app), rebooted the device, and applied the OTA (B350 first, then latest B357).
Until then everything is fine, but when I try to flash the TWRP recovery, it doesn't work :
D:\Android\platform-tools>fastboot flash recovery D:\Downloads\twrp-3.1.1-0-venus.img
target reported max download size of 471859200 bytes
sending 'recovery' (24464 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.734s
D:\Android\platform-tools>fastboot flash recovery D:\Downloads\twrp-3.2.1-0-nemo.img
target reported max download size of 471859200 bytes
sending 'recovery' (21972 KB)...
OKAY [ 0.672s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.672s
D:\Android\platform-tools>fastboot flash recovery D:\Downloads\twrp-3.1.1-0-nemo.img
target reported max download size of 471859200 bytes
sending 'recovery' (21918 KB)...
OKAY [ 0.641s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.656s
Click to expand...
Click to collapse
Neither the recommended Venus one, or the current / previous nemo one can be flashed.
Phone and FRP status in fastboot mode both shows Unlocked / Unlock, and the OEM Unlock option in EMUI Developper Settings is also enabled (I toggled it just to be sure).
I'm not sure what's wrong.
Would the update mess with the OEM unlock (by relocking and showing a wrong status) ?
I'd rather not try fastboot OEM unlock with the code (still have it somewhere) and lose data.
Thanks for any advice

Fr33L4nc3r said:
Hello,
I had the NEM-L51 from my mother running EMUI 4.0x, and decided to upgrade it to the latest version.
It was unlocked, with TWRP as recovery, and rooted.
I did flash back the stock recovery (from HuaweiUpdateExtractor/Update.app), rebooted the device, and applied the OTA (B350 first, then latest B357).
Until then everything is fine, but when I try to flash the TWRP recovery, it doesn't work :
Neither the recommended Venus one, or the current / previous nemo one can be flashed.
Phone and FRP status in fastboot mode both shows Unlocked / Unlock, and the OEM Unlock option in EMUI Developper Settings is also enabled (I toggled it just to be sure).
I'm not sure what's wrong.
Would the update mess with the OEM unlock (by relocking and showing a wrong status) ?
I'd rather not try fastboot OEM unlock with the code (still have it somewhere) and lose data.
Thanks for any advice
Click to expand...
Click to collapse
This should work fine but if not, can try Hassan's recovery

shashank1320 said:
This should work fine but if not, can try Hassan's recovery
Click to expand...
Click to collapse
Before trying that recovery, I just tried to flash the stock one from NEM-L51C432B357 full OTA package, and it doesn't work either
D:\Android\platform-tools>fastboot flash recovery D:\Android\HuaweiUpdateExtractor_0.9.9.5\RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (35570 KB)...
OKAY [ 0.932s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.954s
Click to expand...
Click to collapse
So it's not a recovery issue.
How useful is the HiSuite backup ?
If I make a backup with it, will it be able to restore most user app's and system's data ?
I'd rather not re set everything up, and I'm afraid I'll have to retry to OEM unlock the device (so force wipe), even if it says it's unlocked (which it should have remained in the first place)

Fr33L4nc3r said:
Before trying that recovery, I just tried to flash the stock one from NEM-L51C432B357 full OTA package, and it doesn't work either
So it's not a recovery issue.
How useful is the HiSuite backup ?
If I make a backup with it, will it be able to restore most user app's and system's data ?
I'd rather not re set everything up, and I'm afraid I'll have to retry to OEM unlock the device (so force wipe), even if it says it's unlocked (which it should have remained in the first place)
Click to expand...
Click to collapse
Hisuite can be used for back.. reliable one but not same as titanium backup. Backup WhatsApp on local and g drive. Zip the WhatsApp folder in internal memory and then copy to pc.
Rest other apps, via hisuite (can backup WhatsApp as well here).

Fr33L4nc3r said:
Before trying that recovery, I just tried to flash the stock one from NEM-L51C432B357 full OTA package, and it doesn't work either
So it's not a recovery issue.
How useful is the HiSuite backup ?
If I make a backup with it, will it be able to restore most user app's and system's data ?
I'd rather not re set everything up, and I'm afraid I'll have to retry to OEM unlock the device (so force wipe), even if it says it's unlocked (which it should have remained in the first place)
Click to expand...
Click to collapse
You file should be in path D:\Android\platform-tools\ and not D:\Android\HuaweiUpdateExtractor_0.9.9.5\
I hope adb is installed under D:\Android\platform-tools\, if not, it will be udner C drive as C:\adb\
copy the recovery file whereever the adb is installed and then run the command
fastboot flash recovery twrp-3.1.1-0-venus.img (replace name with your actual file name)

Ok, so in fact fastboot OEM unlock status was not accurate, and something I didn't notice was the absence of dm-verity warning when booting (showing when it's actually unlocked)

Fr33L4nc3r said:
Ok, so in fact fastboot OEM unlock status was not accurate, and something I didn't notice was the absence of dm-verity warning when booting (showing when it's actually unlocked)
Click to expand...
Click to collapse
May be. try moving the files and then flashing from that folder and see if it works.

stopin phone
hello.please help me.last night i unlocked my gt3 and reseted factory data.but after these my phone stopped in page that typed "your device is booting now..." . but nothing going change.
when i hold power key or power key with volume up down , my phone get restart and show huawei mark and after that show the pervious page that i stoped in it and nothing change again.what can i do? :crying::crying::crying::crying:

please help me, my device is Huawei GT3 (honor 5c) (NMO L31) it was unlock bootloader before i bought it and now i want to install twrp, so i have to learn a lot of website and Follow me, I downloaded and installed Adb, installed the driver, then downloaded the twrp version with nemo honor for honor 5c, then open CMD or powershell to write commands like adb reboot bootloader then adb fastboot flash recovery twrp.img is under the writing that says Failed (remote: image verification error), I previously copied the twrp 3.0 file ... into the adb folder and renamed to twrp. Now I have to do to install twrp on my device. Please help me.

Hello, I have an NMO_L31 (honor 5c - huawei gr5 mini) device and I have experienced a Failed (remote: image verification error) error when installing TWRP while my phone was unlocked before. have searched from a lot of technology pages to find remedies but all failed. But my God, Jehovah listened to my plea and brought me to @shashank123, I contacted him through XDA and I got him a phone number to make friends on the telegram, he helped me out I and I have overcome the above error. I would like to explain how to overcome the error that I tried. First, I went back to emui 4.1.2 (you can see the instructions then allow OEM unlock, then I update the OTA to emui 5, allow usb debugging when the update is complete. Shift + Right click on CMD (or powershell) and enter "adb devices" to see the connected device, then enter "adb reboot bootloader" then enter "fastboot oem get-bootinfo" To check if the bootloader has been unlocked, then enter the command "fastboot oem unlock (code)" to unlock if the relock bootloader, then if the bootloader has been unlocked then the purpose of the command to factory reset. If that is the case, then go to the phone and see if factory reset is complete. Then develop and reconnect to adb, check the device connected to the "adb devices" command then go to the "adb reboot bootloader" command to get to the fastboot and then use the command "fastboot flash recovery recovery_name.img" (for example : Twrp) "Finally, if the word OKEY appears, you are successful. If you can not solve this problem, please send a message to @shashank123 in XDA and ask for his phone number to make friend through telegram and regular help message because he does not often use XDA. Thank you very much Shashank for helping me. Thanks be to my god JESU CHRIST and JEHOVAH.

tanhoang1702 said:
Hello, I have an NMO_L31 (honor 5c - huawei gr5 mini) device and I have experienced a Failed (remote: image verification error) error when installing TWRP while my phone was unlocked before. have searched from a lot of technology pages to find remedies but all failed. But my God, Jehovah listened to my plea and brought me to Shashank123, I contacted him through XDA and I got him a phone number to make friends on the telegram, he helped me out I and I have overcome the above error. I would like to explain how to overcome the error that I tried. First, I went back to emui 4.1.2 (you can see the instructions then allow OEM unlock, then I update the OTA to emui 5, allow usb debugging when the update is complete. Shift + Right click on CMD (or powershell) and enter "adb devices" to see the connected device, then enter "adb reboot bootloader" then enter "fastboot oem get-bootinfo" To check if the bootloader has been unlocked, then enter the command "fastboot oem unlock (code)" to unlock if the relock bootloader, then if the bootloader has been unlocked then the purpose of the command to factory reset. If that is the case, then go to the phone and see if factory reset is complete. Then develop and reconnect to adb, check the device connected to the "adb devices" command then go to the "adb reboot bootloader" command to get to the fastboot and then use the command "fastboot flash recovery recovery_name.img" (for example : Twrp) "Finally, if the word OKEY appears, you are successful. If you can not solve this problem, please send a message to Shashank123 in XDA and ask for his phone number to make friend through telegram and regular help message because he does not often use XDA. Thank you very much Shashank for helping me. Thanks be to my god JESU CHRIST and JEHOVAH.
Click to expand...
Click to collapse
No problem at all mate. Helping through telegram was quick in real time rather multiple post or message and then waiting for response from each other. Due to time crunch, I opted to quick help rather keep you waiting all day long
Good you got your phone as per your requirement and able to do what you wanted. Thanks and Enjoy.
You can edit your comment to say "@shashank1320" (use without double quotes) rather Shashank123 as users may send message or qoute him and get no response as that user may or may not exist :silly:

grand.mohammad said:
hello.please help me.last night i unlocked my gt3 and reseted factory data.but after these my phone stopped in page that typed "your device is booting now..." . but nothing going change.
when i hold power key or power key with volume up down , my phone get restart and show huawei mark and after that show the pervious page that i stoped in it and nothing change again.what can i do? :crying::crying::crying::crying:
Click to expand...
Click to collapse
Boot to bootloader again and see the bootloader state if locked or unlocked. Try unlocking it again.