Database Develop

oreo twrp install error

Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?

kadirc5 said:
Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?
Click to expand...
Click to collapse
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)

CarlosAG10 said:
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)
Click to expand...
Click to collapse
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED

kadirc5 said:
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED
Click to expand...
Click to collapse
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory

CarlosAG10 said:
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory
Click to expand...
Click to collapse
Yes, shows a number
How can ı check?

kadirc5 said:
Yes, shows a number
How can ı check?
Click to expand...
Click to collapse
Download the files again and make sure you are correctly using fastboot

since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere

Striike said:
since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere
Click to expand...
Click to collapse
Im gonna try at the weekend thanks

Help bricked mi a2

I was trying to install stock rom after installing RR rom. MiFlash said "flashing is not allowed for critical partitions" and when i did "fastboot flashing unlock_critical" from cmd i got "remote: Flashing Unlock is not allowed". I then used the allinone tool from xda and pressed "lock loader" to unlock it again and ended up bricking the device as it now shows "your device is corrupt. it can't e trusted and will not boot" I can't enter recovery either only fastoot and nothing works. PLEASE HELP FAST

have you tried flaashing via edl mode ?

medkim said:
have you tried flaashing via edl mode ?
Click to expand...
Click to collapse
how to do that

Hammad1029 said:
how to do that
Click to expand...
Click to collapse
reboot into edl mode and flash stock rom by mifilash tool

medkim said:
reboot into edl mode and flash stock rom by mifilash tool
Click to expand...
Click to collapse
how do I reboot into edl mode without dissembling the phone

Hammad1029 said:
how do I reboot into edl mode without dissembling the phone
Click to expand...
Click to collapse
reboot into bootloader then issue this command via adb
fastboot oem edl

medkim said:
reboot into bootloader then issue this command via adb
fastboot oem edl
Click to expand...
Click to collapse
it gives "FAILED (remote: 'Device is already locked!')"

@__harmeet reply here please

Hammad1029 said:
it gives "FAILED (remote: 'Device is already locked!')"
Click to expand...
Click to collapse
friend
first of all, you shoud unlock the bootloader
try with this guide

medkim said:
friend
first of all, you shoud unlock the bootloader
try with this guide
Click to expand...
Click to collapse
@Hammad1029 He Is Right, Firstly Unlock The Bootloader, Then Unlock Its Critical Partition And Boot Up Into EDL Mode By Typing "fastboot oem edl#

medkim said:
friend
first of all, you shoud unlock the bootloader
try with this guide
Click to expand...
Click to collapse
have tried already it says "FAILED (remote: Flashing Unlock is not allowed"

bump...

Dude, how many threads do you need to create, it won't make it any more likely that anyone will help you
Your problem is caused by that you only unlocked the bootloader and not critical partitions
Which stock rom were you on before flashing a custom one?

Nebrassy said:
Dude, how many threads do you need to create, it won't make it any more likely that anyone will help you
Your problem is caused by that you only unlocked the bootloader and not critical partitions
Which stock rom were you on before flashing a custom one?
Click to expand...
Click to collapse
I created the 2nd thread in desperation of restoring my only phone so sorry. How do I unlock the ootloader it shows the error I mentioned above

Hammad1029 said:
I created the 2nd thread in desperation of restoring my only phone so sorry. How do I unlock the ootloader it shows the error I mentioned above
Click to expand...
Click to collapse
I asked you what stock rom you were on

Nebrassy said:
I asked you what stock rom you were on
Click to expand...
Click to collapse
10.0.2

Hammad1029 said:
10.0.2
Click to expand...
Click to collapse
Are you sure?, if so, manually flash boot, system and vendor using fastboot to your current slot
Fastboot flash boot_a boot.img
Or boot_b if active slot is B etc...
Then go to developer options and enable oem unlocking, if you can't enable that option, lock the bootloader, enable the option then unlock bootloader and critical flashing

Nebrassy said:
Are you sure?, if so, manually flash boot, system and vendor using fastboot to your current slot
Fastboot flash boot_a boot.img
Or boot_b if active slot is B etc...
Then go to developer options and enable oem unlocking, if you can't enable that option, lock the bootloader, enable the option then unlock bootloader and critical flashing
Click to expand...
Click to collapse
can I claim warranty on this issue

Hammad1029 said:
can I claim warranty on this issue
Click to expand...
Click to collapse
Hi , sorry for my bad English , if you can open you phone and enter to EDL MODE and flash the stock rom of your device may be solve your problem ,
(I get the same problem trying to install a custom rom)
If you can't acces to EDL via ABD i think that you only can enter to EDL disasembly your phone .. Suertee xd
Yo también me desesperé

same problem
i got the same problem, won't start normally, hangs in boot screen so can't enter the phone to put it in usb debugging, only responce is through fastboot mode. Every attempt is failing due to locked state and unlocking is not allowed.

[Q] Twrp not working

Hello guys no matter what i flash the twrp even its success i cant boot to twrp i followed many instructions but the same i cant boot to twrp some one help please

Arrenlaxmali said:
Hello guys no matter what i flash the twrp even its success i cant boot to twrp i followed many instructions but the same i cant boot to twrp some one help please
Click to expand...
Click to collapse
Can you share us a screenshot when we can see what are you doing to install TWRP recovery?

sakilxda said:
Can you share us a screenshot when we can see what are you doing to install TWRP recovery?
Click to expand...
Click to collapse
Yow hello bro as always you are active helper . I did thisfastboot oem nubia_unlock NUBIA_NX629J
Then fast boot flash recovery recovery.img " i rename the twrp with recovery.img and i cant boot to twrp why im confused i follow the instructions here in xda

Arrenlaxmali said:
Yow hello bro as always you are active helper . I did thisfastboot oem nubia_unlock NUBIA_NX629J
Then fast boot flash recovery recovery.img " i rename the twrp with recovery.img and i cant boot to twrp why im confused i follow the instructions here in xda
Click to expand...
Click to collapse
its for chines version only
if you have Chinese version you have to unlock the bootloader first and then you will be able to flash the twrp recovery
unlocking the bootloader should be on the setting
you cant unlock the bootloader using the oem command in fastboot , you have to unlock it from the setting in developer option
and then enter fastboot and enter the command
fastbooot flashing unlock
remember unlocking the bootloader will erase all your data

em90256 said:
its for chines version only
if you have Chinese version you have to unlock the bootloader first and then you will be able to flash the twrp recovery
unlocking the bootloader should be on the setting
you cant unlock the bootloader using the oem command in fastboot , you have to unlock it from the setting in developer option
and then enter fastboot and enter the command
fastbooot flashing unlock
remember unlocking the bootloader will erase all your data
Click to expand...
Click to collapse
It was unlock bro still i cant enter twrp my rm3 version is 2.27

Arrenlaxmali said:
It was unlock bro still i cant enter twrp my rm3 version is 2.27
Click to expand...
Click to collapse
am in version 2.27 and twrp working fine with me
you have to enter the command
fastboot flashing unlock
and when you boot there is a yellow warning message showing that you have unlocked the bootloader
after that just flash the right twrp file posted on the fourm
good luck

em90256 said:
am in version 2.27 and twrp working fine with me
you have to enter the command
fastboot flashing unlock
and when you boot there is a yellow warning message showing that you have unlocked the bootloader
after that just flash the right twrp file posted on the fourm
good luck
Click to expand...
Click to collapse
I did but look it was success but i cant boot to twrp

Arrenlaxmali said:
I did but look it was success but i cant boot to twrp
Click to expand...
Click to collapse
you doing it wrong, please copy my commands ,
first you have to unclock oem in developer option under settings this is important and then please copy this
fastboot devices
fastboot flashing unlock
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash recovery recovery.img
in your photo you have only used this command
fastboot oem nubia_unlock NUBIA_NX629J
but this is wrong
you have to use
*
fastboot flashing unlock
*
this is important
and then you will be able to flash twrp recovery

em90256 said:
you doing it wrong, please copy my commands ,
first you have to unclock oem in developer option under settings this is important and then please copy this
fastboot devices
fastboot flashing unlock
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash recovery recovery.img
in your photo you have only used this command
fastboot oem nubia_unlock NUBIA_NX629J
but this is wrong
you have to use
*
fastboot flashing unlock
*
this is important
and then you will be able to flash twrp recovery
Click to expand...
Click to collapse
I did all of this but still the same why i dont understand. When i reboot to recovery its show just a fastboot mode why

Arrenlaxmali said:
I did all of this but still the same why i dont understand. When i reboot to recovery its show just a fastboot mode why
Click to expand...
Click to collapse
You can find the solutions here.
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page7

sakilxda said:
You can find the solutions here.
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page7
Click to expand...
Click to collapse
I mean i can boot to system but i cant boot to recovery to twrp

Arrenlaxmali said:
I mean i can boot to system but i cant boot to recovery to twrp
Click to expand...
Click to collapse
Twrp recovery is only for Chinese firmware, did you know?
What's your problem exactly? What do you want to do?

sakilxda said:
Twrp recovery is only for Chinese firmware, did you know?
What's your problem exactly? What do you want to do?
Click to expand...
Click to collapse
Since i csnt update using OTA. I want to flash twrp so i can flash cn roms or global, yes i am cn firmware. i dont understand why i cant update in OTA and flash twrp. Look at the photo failt ota and successful twrp flash but i still i cant boot to twrp

Bro, step by step...
First, lock again the bootloader.
Second, unlock bootloader again.
Third, flash the archives from Europe or Chinese ROM, all the from the same firmware. (Boot, recovery, system, parameters, etc...)
You can see that in the other link.
If you get do all ok, try flash with OTG since Recovery.

sakilxda said:
Bro, step by step...
First, lock again the bootloader.
Second, unlock bootloader again.
Third, flash the archives from Europe or Chinese ROM, all the from the same firmware. (Boot, recovery, system, parameters, etc...)
You can see that in the other link.
If you get do all ok, try flash with OTG since Recovery.
Click to expand...
Click to collapse
Okay bro thanks i will do it

Arrenlaxmali said:
Okay bro thanks i will do it
Click to expand...
Click to collapse
Did you succes?
I have a problem with twrp to, after finish with all step twrp shown once after boot then when I try to reboot twice twrp gone.

Arrenlaxmali said:
Okay bro thanks i will do it
Click to expand...
Click to collapse
Did it work? I have the same problem with my global version.

Honor 9 lite with weird error wile booting: Func NO : 15 (bl31 image) |I Func NO : 1 (security verify failed!)

Hi,
First of all, I hope this is the correct place to ask for help. I didn't see a better place
I own a honor 9 lite phone. I opened bootloader using PotatoNV and testpoints. Everything worked like a charm
But yesterdayy I tried to update it to Treble and after flashing a rom, I faced this error just after restarting the phone:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Func NO : 1 (security verify failed!)
And it keeps restarting all the time
I tried to flash system image from multiple roms, even stock. Also I tried to flash multiple recovery images, boot images, and so on.. but nothing seems to work
The only way I can use thee phone is via fastboot. NO TWRP and no OFFICIAL RECOVERY using Vol+ and Vol-
Please, I need you help
Thank you in advance
Regards

oloco2 said:
Hi,
First of all, I hope this is the correct place to ask for help. I didn't see a better place
I own a honor 9 lite phone. I opened bootloader using PotatoNV and testpoints. Everything worked like a charm
But yesterdayy I tried to update it to Treble and after flashing a rom, I faced this error just after restarting the phone:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Func NO : 1 (security verify failed!)
And it keeps restarting all the time
I tried to flash system image from multiple roms, even stock. Also I tried to flash multiple recovery images, boot images, and so on.. but nothing seems to work
The only way I can use thee phone is via fastboot. NO TWRP and no OFFICIAL RECOVERY using Vol+ and Vol-
Please, I need you help
Thank you in advance
Regards
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Try something from the following:
A) in fastboot mode use command
fastboot erase userdata
reboot and try to flash stock recovery_ramdisk and flash full stock FW via dload
B) try to update your phone via eRecovery - turn off, plug the cabel and press and hold Power + Vol Up. In eRecovery's menu select "Download latest etc etc."
C) fully discharge the battery and try previous methods
(in your case little chance, this method works with error 11/2, you have 15/1)
D) use testpoint method
E) paid services (dc-phoenix etc.)

Thank so much for your help -Alf-
Unfortunally I have to say that now my phone is not able to enter fastboot mode.
What I dd:
The comands you asked for:
fastboot oem get-build-number
(bootloader) :System 8.0.0.046(0JRE)
OKAY [ 0.007s]
Finished. Total time: 0.009s
fastboot oem get-product-model
(bootloader)
OKAY [ 0.006s]
Finished. Total time: 0.009s
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :STF-L09C10B100a
OKAY [ 0.008s]
Finished. Total time: 0.009s
As nothing changed, I used testpoints.
I had to enter fastboot oem unlock 5KKK7... in order to unlock bootloader again
But now.. Phone keeps rebooting with the same eror window as before, but I'm still unable to ener not fastboot mode not erecovery.
Now i really feel locked, as I think there's nothin else I can do.
I also unplugged battery multiple times in order to discharge all the circuit, but no news...
Any other idea, please?
Regards

oloco2 said:
Unfortunally I have to say that now my phone is not able to enter fastboot mode
Click to expand...
Click to collapse
oloco2 said:
The only way I can use thee phone is via fastboot.
Click to expand...
Click to collapse
?

Before using potatonv I was able to enter fastoot mode and perform some commands.
Now, after using it, the phone just keeps rebooting showing the errors, but even if I press the buttons, no fastboot/twrp mode...

oloco2 said:
Before using potatonv I was able to enter fastoot mode and perform some commands.
Now, after using it, the phone just keeps rebooting showing the errors, but even if I press the buttons, no fastboot/twrp mode...
Click to expand...
Click to collapse
Try this method - turn off, hold Volume Down and plug the cabel.

oloco2 said:
System 8.0.0.046(0JRE
Click to expand...
Click to collapse
oloco2 said:
fastboot oem get-product-model
(bootloader)
OKAY [ 0.006s]
Click to expand...
Click to collapse
oloco2 said:
failed input oem_nv_item error
Click to expand...
Click to collapse
oloco2 said:
SYSTEM_VERSION
(bootloader) :STF-L09C10B100a
Click to expand...
Click to collapse
Testpoint or dc-phoenix, bro.

-Alf- said:
Testpoint or dc-phoenix, bro.
Click to expand...
Click to collapse
I posted in the previous post that I already used testpoint using potatonv.
I only used testpoint in order to unlock bootloader, and today I used it via potatonv because you seggested it but.... is there any other use I could give to testpoint other than unlocking bootloader? Something that couldhelp in this situation?
Regards

oloco2 said:
I posted in the previous post that I already used testpoint using potatonv.
I only used testpoint in order to unlock bootloader, and today I used it via potatonv because you seggested it but.... is there any other use I could give to testpoint other than unlocking bootloader? Something that couldhelp in this situation?
Regards
Click to expand...
Click to collapse
You have to flash board software using testpoint . Google it, I have no experience with that.

Ok. Thank you -Alf-. I will have a look to google.
But in the meanwhile, if someone else coukd help me a little bit, will be more than welcome
Regards!!

Hi -Alf-
I got good news for me. I got fastboot working again. I need to use potatonv in order to get it, but anywayI think it's good news.
Please, any other idea in order to make it come back, please?
Thank you

oloco2 said:
any other idea in order to make it come back,
Click to expand...
Click to collapse
your phone has an incomplete FW (System 8.0.0.046 (0JRE)),, an unknown model and a problem with oeminfo. Do you even read what I'm writing???
https://forum.xda-developers.com/t/...-security-verify-failed.4453855/post-86982695

Yes I read.
You told me to use testpoint or DC after telling you that I was unable to enter fastmode, but now I'm able to enter again. That's why I asked you for help again, because maybe using fastboot you were able to tell me any other way to test.
Regards

oloco2 said:
Yes I read.
You told me to use testpoint or DC after telling you that I was unable to enter fastmode, but now I'm able to enter again. That's why I asked you for help again, because maybe using fastboot you were able to tell me any other way to test.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/i-bricked-my-honor-9-lite.3799176/post-76943641

Hey -Alf- !
I can ay that finally I got it working.
How I did it:
I got a full firmware for my devce and using Huawei Update extractor I extracted all the images to a folder.
Using a little script un batch I createda .txt with multiple lines:
fastboot flash cache cache.img
fastboot flash crc crc.img
fastboot flash curver curver.img
fastboot flash cust cust.img
fastboot flash dts dts.img
fastboot flash eng_system eng_system.img
fastboot flash eng_vendor eng_vendor.img
fastboot flash erecovery_kernel erecovery_kerne.img
fastboot flash erecovery_ramdis erecovery_ramdi.img
fastboot flash erecovery_vbmet erecovery_vbmet.img
fastboot flash erecovery_vendor erecovery_vendo.img
fastboot flash fastboot fastboot.img
fastboot flash fw_hifi fw_hifi.img
fastboot flash fw_lpm3 fw_lpm3.img
fastboot flash hisiufs_gpt hisiufs_gpt.img
fastboot flash boot kernel.img
fastboot flash modemnvm_update modemnvm_update.img
fastboot flash modem_fw modem_fw.img
fastboot flash odm odm.img
fastboot flash package_type.img package_type.img
fastboot flash patch patch.img
fastboot flash preas preas.img
fastboot flash preavs preavs.img
fastboot flash preload preload.img
fastboot flash product product.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash sensorhub sensorhub.img
fastboot flash sha256rsa sha256rsa.img
fastboot flash system system.img
fastboot flash teeos teeos.img
fastboot flash trustfirmware trustfirmware.img
fastboot flash userdata userdata.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash verlist verlist.img
fastboot flash version version.img
fastboot flash xloader xloader.img
And I run all the commands.
Some of them gave me some errors like partition lenght or something like that, but at the end, once rebooted, the error was gone.
Then, I updated all the firmware usong dload.
Now I'm facing a little error about oeminfo. I think itis due to the fact that the firmware I used was rusian, and my phone is from EU. I already created another thread in this forum.
I want to thank you for your tme and your ideas.
I hope this post can help someone over there with an error like mine.
Thank you very much for your time and help
Regards

No problem. Btw, why russian FW? I gave you a link with EU FW . Okay, your choice...
oloco2 said:
Now I'm facing a little error about oeminfo
Click to expand...
Click to collapse
Little?

Yes, The russian FW I flashed was yeterday. Now, after you replied to my post, I will try to upgrade FW to the EU version. I hope now everything works as it should
The "litle error" about oeminfo is:
"/preas/xxx" in some parts of the settings. I read somewhere it was due to oeminfo.I'm I wrong?
Thank you!!

I have already tried to fix the /preas/xxx "little error", but it didn't work
After flashing the EU version of lld-l31, I tested it and it seems to be showing the same error in "Compilation Number", in About
lso, in Model it says "unknow". I thing this is why when I tried to find a new OTA version, it didn't find anyone, even if using android 8
Any idea to fix "/preas/xxx"?
Thank you ad regards!!

All fixed!!
I found this oeminfo:
OEMinfo & Dump & CERT Honor 9 Lite (LLD-ALL)
OEMinfo & Dump & CERT Honor 9 Lite (LLD-AL00 / LLD-AL10 / LLD-AL20 / LLD-AL30 / LLD-TL00 / LLD-TL10 / LLD-L21 / LLD-L22 / LLD-L31 / LLD-L32 / LLD-L42). Share File Certificate, File Dump, OE…
azrom.net
After updating it, all info seems to be correct in about. Also, there's a new OTA for me!
What a road gave me this phone
I hope I'mnot comming back to here in a while
Thank you for all your help
Regards!!!

oloco2 said:
I have already tried to fix the /preas/xxx "little error", but it didn't work
After flashing the EU version of lld-l31, I tested it and it seems to be showing the same error in "Compilation Number", in About
lso, in Model it says "unknow". I thing this is why when I tried to find a new OTA version, it didn't find anyone, even if using android 8
Any idea to fix "/preas/xxx"?
Thank you ad regards!!
Click to expand...
Click to collapse
Kindly share your batch script, pls

Question Root on Android 13 ?

Hey folks,
has anyone already successfully rooted Android 13? If yes, is there an instruction available?
Thanks!

refresh5 said:
Hey folks,
has anyone already successfully rooted Android 13? If yes, is there an instruction available?
Thanks!
Click to expand...
Click to collapse
Just patch boot.img and flash it

Can we update firmware after root? If not where can we download full firmware? This is my first Sony phone so I don't know where to download full firmware and how to flash it

Adnan008 said:
Can we update firmware after root? If not where can we download full firmware? This is my first Sony phone so I don't know where to download full firmware and how to flash it
Click to expand...
Click to collapse
Xperiafirm on xda to download full fw and newflasher to flash it

King081 said:
Xperiafirm on xda to download full fw and newflasher to flash it
Click to expand...
Click to collapse
do we lose data when flashing firmware?

Adnan008 said:
do we lose data when flashing firmware?
Click to expand...
Click to collapse
You can choose using newflasher

King081 said:
Just patch boot.img and flash it
Click to expand...
Click to collapse
Can you tell me how?

zaxdamian said:
Can you tell me how?
Click to expand...
Click to collapse
Use unsin to get boot.img from stock file, then install magisk apk, use magisk to patch boot.img then flash in fastboot

King081 said:
Use unsin to get boot.img from stock file, then install magisk apk, use magisk to patch boot.img then flash in fastboot
Click to expand...
Click to collapse
I have stock file but dont know which file unsin. When I try to instal twrp, "Download is not allowed on locked devices". How to unlock bootloader? Command from cmd dosen't work

zaxdamian said:
I have stock file but dont know which file unsin. When I try to instal twrp, "Download is not allowed on locked devices". How to unlock bootloader? Command from cmd dosen't work
Click to expand...
Click to collapse
I don't know what twrp you have, because we don't have one here and clearly your phones bootloader locked, this is about root and not twrp

Ok. I cant unlock bootloader, so how to get boot.img from stock file?

Unlock bootloader:
https://developer.sony.com/open-source/aosp-on-xperia-open-devices/get-started/unlock-bootloader

I tried it. Either I'm doing something wrong or it's not working

Everything works, I unlocked it myself, I just don't remember which command:
fastboot oem unlock
or
fastboot flash unlock

fastboot devices ok
fastboot oem unlock 0xunlockcode "FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
fastboot oem unlock unlockcode the same
fastboot flash unlock "unknown partition 'unlock' fastboot: error: cannot determine image filename for 'unlock'"
I think the problem is with entering fastboot mode. When "phone is turned off and press and hold the Fastboot key Volume up* when you connect your phone to the computer" i have blue diode but in SDk no devices

On comand fastboot flash unlock i have "fastboot: error: ANDROID_PRODUCT_OUT not set"

zaxdamian said:
fastboot devices ok
fastboot oem unlock 0xunlockcode "FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
fastboot oem unlock unlockcode the same
fastboot flash unlock "unknown partition 'unlock' fastboot: error: cannot determine image filename for 'unlock'"
I think the problem is with entering fastboot mode. When "phone is turned off and press and hold the Fastboot key Volume up* when you connect your phone to the computer" i have blue diode but in SDk no devices
Click to expand...
Click to collapse
Did you do that in fastboot or fastbootD

Fastboot D