Database Info

Relock bootloader help

I have an f8331 n I didn't back up the TA. IS there any way to relock the bootloader? Or to at least remove the message that say "device has been unlocked cannot be trusted" . . It's in Android nougat version 7.0 plz help

Use flashtool
Relock bootloader
Wait for flashtool to reflash your software it takes some time to finish.
After done retart your phone the warning is gone and your ohonenstart normally but drm is gone

For the flash tool would I use sonys flash tool "Emma" or should I use the one from
karrouma said:
Use flashtool
Relock bootloader
Wait for flashtool to reflash your software it takes some time to finish.
After done retart your phone the warning is gone and your ohonenstart normally but drm is gone
Click to expand...
Click to collapse
For the flash tool would I use sonys flash tool "Emma" or should I use the one from flashtool. Net??

Tech 101 said:
For the flash tool would I use sonys flash tool "Emma" or should I use the one from flashtool. Net??
Click to expand...
Click to collapse
From flastool select blue the second line , second option on the left

i did it n my device says it has failed verification and will power off

Tech 101 said:
For the flash tool would I use sonys flash tool "Emma" or should I use the one from flashtool. Net??
Click to expand...
Click to collapse
but keep in mind relocking BL will render the stock camera unusable, and you'd be getting this annoying error : "camera in use by another app"

i fix it
Tech 101 said:
I have an f8331 n I didn't back up the TA. IS there any way to relock the bootloader? Or to at least remove the message that say "device has been unlocked cannot be trusted" . . It's in Android nougat version 7.0 plz help
Click to expand...
Click to collapse
1- relock it using flash tool
2-go to xperia companion => software repair (make sure to backup what you need on pc).
3- put your device on flash mode and start (it will take 10-20 min) (it will give you android 7.1.1), dont start it yet.
4- unlock the bootloader on fasboot mode [turn it off, volume up, put usb and write the cmd code in adb folder (hold shift and right click) (fastboot -i 0x0fce oem unlock 0x(your code)) and restart it.
5-Install kernel for your device - thanks to "AndroPlus": "https://drive.google.com/drive/folders/0B0j3VJ1Xp5N8Y1FZSmMwM1BOZDQ" download xz_andropluskernel_v23.zip, open it and put the img file in the adb folder, and flash on cmd (fastboot flash boot boot.img) then restart it.
6-now the cam will work normally, you can also flash twrp, download it , put it in the adb folder, open cmd and write (fastboot flash recovery twrp-3.1.0-0-kagura.img) and restart it.
7- you can also install supersu 2.79 from twrp and you will have root
-- you can download adb/fasboot tools from here (downloadmirror.co/29Xn/adb-setup-1.4.3.exe[

This way he will end up in exactly the same point he has started Repairing w Xperia Companion doesn't bring back DRM keys. Also, after unlocking bootloader again the message "device has been unlocked cannot be trusted" will still pop up at boot.

S1gma said:
This way he will end up in exactly the same point he has started Repairing w Xperia Companion doesn't bring back DRM keys. Also, after unlocking bootloader again the message "device has been unlocked cannot be trusted" will still pop up at boot.
Click to expand...
Click to collapse
it will always pop up, you either have it with rooted 7.1.1 drm fixed all working
or you need to lock bootloader, flash stock 6.0.1, recover the ta img and upgrad it to 7.1.1 normally with no root.

Ok, let's clarify a bit. The OP stated he don't have TA backup. So there are two ways to choose:
1) Leave bootloader unlocked and use DRM fix (eg. Androplus Kernel).
This way the message "device has been unlocked cannot be trusted" will still pop up at boot, but OP will be able to use DRM based features (super-vivid screen, sound enchantment, low-light camera).
2) Lock bootloader. This way OP will get rid of "device has been unlocked cannot be trusted" message but also will loose drm based functions. Also there is possibility, that the camera will stop working at all.
To lock bootloader you have to:
1) Flash unmodified firmware using flashtool (eg. newest Android 7.1.1) wiping all data (check all marks under "wipe")
{
"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"
}
2) Using flashtools BLU icon lock bootloader.
The phone should boot up. You don't have to downgrade to lock/unlock bootloader.
As for the failed verification error - just unlock bootloader using flashtool and start over (either with 1. or 2.).

Huawei-Solution Unlock OEM or Frp Google (EMUI 8.0.0)

{
"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"
}
Code:
[B][FONT="Tahoma"][COLOR="Black"]/*
* I Do not Become Responsible For The Bad Installation
* Now Your Warranty Is Mine, Before Flashing Investigate
* You Decide to Make All These Modifications to Your Device
* Under Your Own Risk, If You Spoil Your Device, I Will Laugh At You
*/[/COLOR][/FONT][/B]
Requirements:
-Bootloader Unlocked
-Activate USB Debugging
-Activate Unknown Applications
-Install Recovery Twrp For P20 Lite
-Only For Free Versions (Dual Sim) And (Single Sim)
-Huawei P20 Lite ANE-LX1,L01,L01A,LX1A,LX3,L03,LXX,Etc :good:
Huawei P20 Lite-Recovery Twrp EMUI 8.0.0
-Decompress File:
We turn Off The Phone And Enter The Fastboot Mode,We Open The Cmd Window And Write These Codes:
https://mega.nz/#!Tp9GxQrb!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Code:
[B][FONT="Tahoma"][COLOR="Black"] fastboot flash recovery_ramdisk RECOVERY-V2.img[/COLOR][/FONT][/B]
INSTALLATION:
We Copy The Frp_Unlock_For Android 7 And 8 And All Hi6250.zip To The SD Card
We Turn Off The Phone,And Enter Recovery Twrp
-Flash Frp Unlock EMUI 8.0.0 (Delay Around 30 Seconds)
-When Finish, We Give In Reboot System...
Initial Configuration,Initial Start And Enjoy.... ​
Telegram Group:
Here Will Support for All Hi6250 Devices:
Huawei Mate 10 Lite,Huawei P20-P10 Lite,Honor 6X,Honor 7X,Honor 8 Lite
Honor 5C,Huawei P9 Lite 2017 And 2016 https://t.me/joinchat/HH00UkNvNQYbZDjlDcrhHw
XDA:DevDB Information
Tool/Utility For The Huawei P20 Lite
Contributors
KingOfMezi
Chisetdel31260
Neondragon1909
vovan1982
ginnocenti
-KangVIP Framework & Team HRT
-Team Win Recovery Project For P10 Lite
-Huawei Technologies Co, Ltd. 华为技术有限公司
ROM OS Version: Android 8.0.0 Oreo
ROM Kernel: Linux 4.4.23+
ROM Firmware Required: EMUI 8.0.0
Version Information
Status: Stable
Current Stable Version: 2018-07-04
Stable Release Date: 2018-07-04
Created: 2018-07-04
Last Updated: 2018-07-04

Downloads
Frp Unlock EMUI 8.0.0 https://mega.nz/#!6FxwXQ4T!-pfJaLqWVtLiUDi7-RMZm6J-EZU7wQ8VDE50eDXZruI

help , i cannot unlock my bootloader, p20 lite
thats the only barier in flashing my p20 lite to twrp

i couldn't get FRP unlock using your method ,
the phone keeps rebooting .

AJ said:
i couldn't get FRP unlock using your method ,
the phone keeps rebooting .
Click to expand...
Click to collapse
you have to install a firmware through twrp to unlock the frp in some cases it happens
https://forum.xda-developers.com/hu...ompilation-firmware-flash-emui-8-0-0-t3819642

KingOfMezi said:
you have to install a firmware through twrp to unlock the frp in some cases it happens
https://forum.xda-developers.com/hu...ompilation-firmware-flash-emui-8-0-0-t3819642
Click to expand...
Click to collapse
did your suggestion and still i have no oem unlock in settings nor FRP unlock

AJ said:
did your suggestion and still i have no oem unlock in settings nor FRP unlock
Click to expand...
Click to collapse
if it works it was tested with the p20 lite, p10 lite, mate 10 lite,honor 7x ,huawei p9 lite 2016 and 2017 etc.
I will not answer any questions +
https://forum.xda-developers.com/huawei-p20-lite/how-to/guide-frp-unlock-twrp-t3827277

KingOfMezi said:
if it works it was tested with the p20 lite, p10 lite, mate 10 lite,honor 7x ,huawei p9 lite 2016 and 2017 etc.
I will not answer any questions +
https://forum.xda-developers.com/huawei-p20-lite/how-to/guide-frp-unlock-twrp-t3827277
Click to expand...
Click to collapse
You don't seem to understand , i don't have any words in the bootloader under "phone unlocked" , no FRP locked no nothing , nor i have oem unlock in developer settings , all this happened when i flashed AOSP 9 Experimental .

The title says that you've got the solution to unlock the bootloader ( OEM ), but in the requirements, you're mentioning that the bootloader has to be unlocked, am I missing something here :fingers-crossed: ?

s43 said:
The title says that you've got the solution to unlock the bootloader ( OEM ), but in the requirements, you're mentioning that the bootloader has to be unlocked, am I missing something here :fingers-crossed: ?
Click to expand...
Click to collapse
Unlock Bootloader = PHONE Unlocked
OEM Unlocking enable = FRP Unlock
FRP - Factory Reset Protection
You can check it the purpose of FRP in the first three paragraphs in this link https://www.xda-developers.com/android-8-1-factory-reset-protection/
Nowadays to unlock bootloader with DC-Unlocker you have to downgrade your firmware.
In P20 lite I never face any problem with FRP Unlock but in other device after flash/factory reset the "OEM unlocking" become greyed out and was not possible to change.

kilroystyx said:
Unlock Bootloader = PHONE Unlocked
OEM Unlocking enable = FRP Unlock
FRP - Factory Reset Protection
You can check it the purpose of FRP in the first three paragraphs in this link https://www.xda-developers.com/android-8-1-factory-reset-protection/
Nowadays to unlock bootloader with DC-Unlocker you have to downgrade your firmware.
In P20 lite I never face any problem with FRP Unlock but in other device after flash/factory reset the "OEM unlocking" become greyed out and was not possible to change.
Click to expand...
Click to collapse
Thanks for the information, but I do know the difference between FRP & Bootloader unlock ( oem ).
You've got me interested by this downgrading the firmeware, but how can I do that while the bootloader is locked ? ( DC Unlocker doesn't support Huawei P90 Lite ).

s43 said:
Thanks for the information, but I do know the difference between FRP & Bootloader unlock ( oem ).
You've got me interested by this downgrading the firmeware, but how can I do that while the bootloader is locked ? ( DC Unlocker doesn't support Huawei P90 Lite ).
Click to expand...
Click to collapse
You can downgrade with bootloader locked, check this tread https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557

Not working this method, my frp is locked!

AJ said:
I couldn't get frp to unlock using your method,
the phone keeps rebooting.
Click to expand...
Click to collapse
go to dev options on ur device, enable USB debugging, boot into fastboot/rescue mode using platform tools for ADB and fastboot. it should say that your FRP is unlocked.

good

[A/B][TREBLE][9.0][A530F/A530W/A730F]SaR patch and kernel for Pie Vendor

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this patch
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
INFO:
This is a patch and SaR kernel made for @prashantp01's Vendor Dumpster V1.1.
SaR (System as Root) means the system partition is mounted as the root filesystem.
This allows our phone to boot System-as-Root (also labelled as A/B) GSIs which are the only type of GSIs still supported officially by Google.
There are two types of boot images I'm providing:
Android 9 style ramdiskless SaR
Android 10 style 2-stage init SaR
In general, you should use the Android 9 version for Android 9 based GSIs, and use whichever you want for Android 10 or newer.
The kernel is a modified version of @prashantp01's Quantum Kernel v4.0.
Source code for it is available here: github.com/VDavid003/universal7885_SaR
If you are used to using PHH-Magisk, now you don't have to: you can use normal Magisk on A/B GSIs.
NOTE:The patch and kernel are currently not tested on A530W and A730F. Please tell me if it works or not!
BUGS:
-Basically every bug that is present in the original Vendor Dumpster V1.1
-Secure lock screen can't be set (no pattern/pin/password unlock)
-Seems like Android 11 Developer Preview 2 and later does not currently work. DP1 works fine tho, you can download it here.
INSTALL INSTRUCTIONS:
Follow the instructions to install Vendor Dumpster V1.1.
Flash the SaR Patcher zip from TWRP(this will still let you boot non-SaR GSIs, but it will make the vendor compatible with SaR GSI)
Install a SaR boot.img (P or Q) for your model. (TWRP -> Install -> Install Image -> Select your boot.img -> Select Boot from the list -> Swipe to flash)
Flash an A/B or SaR GSI as you would do normally.
DOWNLOADS:
The root folder contains the vendor patcher zip, and the boot.img folder contains boot.imgs
Naming scheme for them: boot_[MODEL]_[P/Q].img
DOWNLOAD HERE
SPECIAL THANKS:
@prashantp01 for his vendor and kernel. Go support him!
Everyone involved in his vendor/kernel.

CHANGELOG
1.0:
-Initial release with some stuff accidentally left out
1.1:
-Fixed RIL (temporary fix currently), and enabled the media codec fix I forgot to enable in 1.0

TESTING WITH AB GSI ROMs
It works on the SM-A730F when flashing the android 10 boot image with an AB android 10 GSI but mobile services doesn't work, unfortunately and also it messed up the system time a bit but everything else works

Kaduah13 said:
It works on the SM-A730F when flashing the android 10 boot image with an AB android 10 GSI but mobile services doesn't work, unfortunately and also it messed up the system time a bit but everything else works
Click to expand...
Click to collapse
Mobile services should work now with 1.1, but what do you mean by messing up the system time?

VDavid003 said:
Mobile services should work now with 1.1, but what do you mean by messing up the system time?
Click to expand...
Click to collapse
I use GMT but it often switches to EAT even though I set it back to GMT
after every reboot I made.

VDavid003 said:
Mobile services should work now with 1.1, but what do you mean by messing up the system time?
Click to expand...
Click to collapse
The version 1.1 works but for mobile services, only one SIM slot works.

Hi! Android 10 QQ2A.200405.005 descendant x samsung a8+ not working fingerprint. Thanks !

OEM unlocked in developer option but RMM state paranormal in Download Mode
3 weeks ago i accidentally installed a ROM, without installing RMM patch in TWRP mode.
Phone bricked, then i installed pie room with Odin.
what I saw in developer option after installing new pie room, there was OEM unlock option, but even after enabling it, i was getting as below :
KG state checking
RMM state paranormal
FRP lock off
oem lock off
i waited for a week then KG state gone only RMM state left, what is saw was:
RMM state paranormal
FRP lock off
oem lock off
i waited one more week after 168 hours , RMM state is still there even after OEM unlocked in development option.
Please help me i can not downgrade too because is have boot-loader U7 .
Help me to downgrade or help me to install twrp.
one thing i want to add is, when i turned on oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock off
when i turned off oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock on
---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------
OEM unlocked in developer option but RMM state paranormal in Download Mode
OEM unlocked in developer option but RMM state paranormal in Download Mode
3 weeks ago i accidentally installed a ROM, without installing RMM patch in TWRP mode.
Phone bricked, then i installed pie room with Odin.
what I saw in developer option after installing new pie room, there was OEM unlock option, but even after enabling it, i was getting as below :
KG state checking
RMM state paranormal
FRP lock off
oem lock off
i waited for a week then KG state gone only RMM state left, what is saw was:
RMM state paranormal
FRP lock off
oem lock off
i waited one more week after 168 hours , RMM state is still there even after OEM unlocked in development option.
Please help me i can not downgrade too because is have boot-loader U7 .
Help me to downgrade or help me to install twrp.
one thing i want to add is, when i turned on oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock off
when i turned off oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock on

Question How re-lock bootloader asus rog 5?

Hello.. I opened the bootloader
How do I re-lock it again?
And if I close it, can I open again?
Thank you

have u try fastboot oem lock ?

Edit: The lock command has been found.
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com

twistedumbrella said:
Code:
fastboot oem asus-lock
Click to expand...
Click to collapse
I tried it. Not working error code in fastboot.. But on rog phone 3 work fine..
Any solution?

mustafa.devel said:
I tried it. Not working error code in fastboot.. But on rog phone 3 work fine..
Any solution?
Click to expand...
Click to collapse
Is there a specific error code or does it just say "error code"?

twistedumbrella said:
Is there a specific error code or does it just say "error code"?
Click to expand...
Click to collapse
I don't remember exactly. But i think says Command wrong

Edit: The lock command has been found.
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com
mustafa.devel said:
I don't remember exactly. But i think says Command wrong
Click to expand...
Click to collapse
Same for "lock"?
Always possible they didn't have time (or decided against) their custom command

I am getting this error whenever I try to relock my bootloader
{
"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"
}

phaw16 said:
I am getting this error whenever I try to relock my bootloader
View attachment 5388779
Click to expand...
Click to collapse
That means you are in the wrong fastboot.
There is bootloader and (userspace) fastboot. Use the one you weren't in when you got that error.
And again... You can't change your mind later. This is the third and final warning.

twistedumbrella said:
That means you are in the wrong fastboot.
There is bootloader and (userspace) fastboot. Use the one you weren't in when you got that error.
And again... You can't change your mind later. This is the third and final warning.
Click to expand...
Click to collapse
Hi sorry I'm puzzled what do you mean by this part (There is bootloader and (userspace) fastboot)
It doesn't matter for me if I lose the liberty of unlocking the boot loader in the future I just want to relock the bootloader so I can use my local apps.

phaw16 said:
Hi sorry I'm puzzled what do you mean by this part (There is bootloader and (userspace) fastboot)
It doesn't matter for me if I lose the liberty of unlocking the boot loader in the future I just want to relock the bootloader so I can use my local apps.
Click to expand...
Click to collapse
There are two interfaces for fastboot.
The one you enter when holding the volume button in the bootloader. You can get to the other using "fastboot reboot fastboot" from that one. You can also get to either using "adb reboot" and either bootloader or fastboot.
phaw16 said:
From where I am at its not the root state that's causing the issue, my phone is not rooted at the moment its running on stock ROG5 firmware the latest one still it doesn't work. Its the unlocked boot loader that's causing the issue.
Click to expand...
Click to collapse
This phone doesn't have Knox, so it's unusual that apps would be able to detect something like that. Which app is it?
The standard for developers is SafetyNet attestation. That can be patched, but only if it's done right.

Hi I tried your suggestion.
1. I did adb devices to confirm if its being read by the PC.
2. I did adb reboot fastboot and after I entered fastboot mode its showing "fastbootd
3. I typed fastboot devices and it was confirmed I am on fastboot mode but then again I am on "fastbootd"
4. I tried fastboot reboot fastboot but I only got an error which is below.

phaw16 said:
Hi I tried your suggestion.
1. I did adb devices to confirm if its being read by the PC.
2. I did adb reboot fastboot and after I entered fastboot mode its showing "fastbootd
3. I typed fastboot devices and it was confirmed I am on fastboot mode but then again I am on "fastbootd"
4. I tried fastboot reboot fastboot but I only got an error which is below.
View attachment 5389425
Click to expand...
Click to collapse
My suggestion was to use the OPPOSITE of the one you tried, not to boot into it multiple ways.

So what do you mean not boot into it multiple ways?
I tried this too:
1. booted state in my normal homescreen
2. Opened adb tools and typed adb reboot fastboot.
3. tried fastboot oem lock.
fastboot oem is being read but the "lock" part is an invalid command.

FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed

Hi again, sorry if I am such a nuisance but I think I got the point here's what I did:
1. Open State - I removed my fingerprint and passcode
2. I did adb reboot bootloader
3. I tried these commands:
- fastboot oem lock (unknown command)
- fastboot oem asus-lock (unknown command)
- fastboot flashing lock (permission denied)
It's very hard to lock the freaking bootloader.

phaw16 said:
Hi again, sorry if I am such a nuisance but I think I got the point here's what I did:
1. Open State - I removed my fingerprint and passcode
2. I did adb reboot bootloader
3. I tried these commands:
- fastboot oem lock (unknown command)
- fastboot oem asus-lock (unknown command)
- fastboot flashing lock (permission denied)
It's very hard to lock the freaking bootloader.
Click to expand...
Click to collapse
Contact Asus. They should be able to help.

Seriously? I'm not warranty after tampering with my bootloader?

phaw16 said:
Seriously? I'm not warranty after tampering with my bootloader?
Click to expand...
Click to collapse
Yes, seriously.
I would ask Asus, the people who placed the lock on the device and then provided the app to remove it, the simple question "how would I lock my bootloader after it was unlocked?"

Will do thank you!

Question Is it possible to root the Red Magic 7 Pro?

Hello all,
As the title suggests, I'm wondering if it is possible to root the Red Magic 7 Pro, and if there are any "consequences" of unlocking the bootloader like how Samsung shuts off Samsung Pay and OTA updates? I'm not too familiar with the Red Magic series.

Yes, it's pretty easy to unlock the bootloader and root.

AmmarHaseeb said:
Yes, it's pretty easy to unlock the bootloader and root.
Click to expand...
Click to collapse
I'm guessing for the rooting process I have to extract the boot.img from the official firmware, patch it in magisk and flash?

Yeah

AmmarHaseeb said:
Yeah
Click to expand...
Click to collapse
Baller thank you

Impossible to unlock the bootloader.
it always says "waiting for device"
{
"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"
}

Marcis-2k said:
Impossible to unlock the bootloader.
it always says "waiting for device"
View attachment 5611015
Click to expand...
Click to collapse
Did you try "fastboot oem unlock" or some other variant of the command?

Hi Soumy1234,
I've already try these commands :
fastboot flashing unlock
fastboot oem unlock
fastboot oem unlock NUBIA_NX709J
fastboot oem nubia_unlock NUBIA_NX709J
I think the EU version is lock or use a special fastboot command.

Marcis-2k said:
Hi Soumy1234,
I've already try these commands :
fastboot flashing unlock
fastboot oem unlock
fastboot oem unlock NUBIA_NX709J
fastboot oem nubia_unlock NUBIA_NX709J
I think the EU version is lock or use a special fastboot command.
Click to expand...
Click to collapse
It seems weird to have the EU version be locked, but I guess Samsung already does it with their NA versions. OEM unlocking is enabled tho right?

I have the EU version and i was able to unlock the bootloader and flash the patched boot.img.

Marcis-2k said:
Hi Soumy1234,
I've already try these commands :
fastboot flashing unlock
fastboot oem unlock
fastboot oem unlock NUBIA_NX709J
fastboot oem nubia_unlock NUBIA_NX709J
I think the EU version is lock or use a special fastboot command.
Click to expand...
Click to collapse
I have the EU version and i was able to unlock the bootloader and flash the patched boot.img.
Checking what you are doing i dont see if you went to the dev options and enabled "OEM unlocking".
After that, reboot on bootloader and you should be able to unlock it with the fastboot command.
You will need to recalibrate the fingerprint sensor (Recalibrate) and you will lose the ability to install OTAs.
I currently have the ROM version NX709J_EUCommon_v4.08 that has idle battery consumption issues and i can't install the OTA update NX709J_EUCommon_v4.12.
The stock recovery does not have the ability to use adb commands nor flash update.zip files, I'm checking how to make my own TWRP but its a first for me.

Lucas VT said:
I have the EU version and i was able to unlock the bootloader and flash the patched boot.img.
Checking what you are doing i dont see if you went to the dev options and enabled "OEM unlocking".
After that, reboot on bootloader and you should be able to unlock it with the fastboot command.
You will need to recalibrate the fingerprint sensor (Recalibrate) and you will lose the ability to install OTAs.
I currently have the ROM version NX709J_EUCommon_v4.08 that has idle battery consumption issues and i can't install the OTA update NX709J_EUCommon_v4.12.
The stock recovery does not have the ability to use adb commands nor flash update.zip files, I'm checking how to make my own TWRP but its a first for me.
Click to expand...
Click to collapse
By calibrate fingerprint sensor what do you mean exactly? Did you have to remove and redo the fingerprint or was there like an image file you had to flash again?

Soumy1234 said:
By calibrate fingerprint sensor what do you mean exactly? Did you have to remove and redo the fingerprint or was there like an image file you had to flash again?
Click to expand...
Click to collapse
You can check the link on my message to see the process, you will get a message when trying to use it saying that the calibration data was lost and that the sensor must be calibrated before using it.
The calibration process is a factory thing that can be accessed trough the dialer.

Lucas VT said:
I have the EU version and i was able to unlock the bootloader and flash the patched boot.img.
Click to expand...
Click to collapse
Is your device is 0123456789ABCDEF ?

Marcis-2k said:
Is your device is 0123456789ABCDEF ?
View attachment 5619121
Click to expand...
Click to collapse
Yep, exactly the same ID.
What is your hardware version?
Mine is NX709J_V1AMB

Lucas VT said:
Yep, exactly the same ID.
What is your hardware version?
Mine is NX709J_V1AMB
Click to expand...
Click to collapse
Hardware version : NX709J_V1AMB
Build : NX709J_EUCommun_V4.12
Explain me which command to root. I already have the patch boot_patched.img for the v4.12.

I have a NX709J_UNCommon_V3.14.
NX709J_V1AMB...
Phone says there is new version available, V3.17. but when I hit download and install it stops at 81% and says update package error..??
Any thoughts on it.??
When I go to the red magic page to try to download it manually the link takes me to..

Hi, do this method also work on Nubia Z40 PRO and Z40S PRO?