Hello,
After the screen of my Huawei P8 Lite (ALE-L21) stopped responding when touching it (displayed ok) while I was riding my bike in the rain*, I hit Power + Volume Down to see if it did anything.
What it did, is enter the "RESCUE MODE Func NO: 8 (hifi image) Error NO: 1 (security verify failed!)" screen:
{
"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"
}
Since it wouldn't go any further, I let the battery run dry, recharged it, and managed to use the "wipe data/factory reset" option.
At this point, with the phone plugged into my computer:
Keep Power button pressed: "RESCUE MODE Attention!"
Keep Power + Volume Up buttons pressed : "RESCUE MODE Attention!"
Keep Power + Volume Down pressed: "FASTBOOT&RESCUE MODE
FWIW, the phone has a MicroSD port, the phone is listed by Device Manager in Windows 7 (Android Device > Android ADB Interface) when in FASTBOOT&RESCUE mode, and I have HiSuite installed but it says "Device not connected".
Provided the screen was not broken by the rain drops… what do you recommend I do at this point to recover the stock Huawei ROM?
Thank you.
* I did protect it with my rain cape as much as I could, so we're just talking a bit of rain drops, nothing major. This is not the first time I do this, and I had no problem so far
---
Edit: FWIW, I downloaded firmware C432B564 from Huawei's site, copied the \dload directory on the MicroSD card and inserted it while the phone is still running since it won't turn off, and rebooted with POWER + VOLUME UP/DOWN pressed per the PDF: The phone stills displays the "RESCUE MODE" Func NO 8 + Error NO 1 screen. So it looks like a forced upgrade doesn't work.
---
Edit: I followed this tutorial to extract the four IMG files from UPDATE.APP, but after running "fastboot reboot" (instead of the non-existent "fastboot restart"), the phone is back to the RESCUE MODE screen above, ie. nothing changed.
Is this phone bricked?
---
Edit: I followed this message to run a few fastboot commands:
Code:
C:\adb>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: ALE-L21 V100R001C432B046
C:\adb>fastboot oem get-product-model
(bootloader) ALE-L21
OKAY [ 0.078s]
C:\adb>fastboot oem get-psid
(bootloader) SN:W3D7N1563000…
(bootloader) IMEI:8666300297…
IMEI:8666300297…
OKAY [ 0.062s]
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
C:\adb>fastboot oem check-rootinfo
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1454277839
OKAY [ 0.094s]
C:\adb>fastboot oem get-build-number
(bootloader) :ALE-L21C432B602
OKAY [ 0.062s]
C:\adb>fastboot oem device-info
FAILED (remote: Command not allowed)
Try again with the img files. I've had it happen to me as well. If it doesn't work try persona's method too https://forum.xda-developers.com/p8lite/help/fix-bootloop-freeze-logo-t3639688
Thank you.
Using another way (forgot what it was), I got Android to start the factory reset, but the screen would still not respond to touch, meaning the phone was probably dead.
So I got a new phone and tossed the P8 Lite. I'll pay more attention not get the phone wet in the rain.
Thank you.
Related
So I'm trying to root my huawei p9 lite vns-l31 but had no luck
I did ulock bootloader and i do get the message when i reboot
but why i try to boot into the twrp from fastboot i get FAILED (remote: Command not allowed)
also the thing when you press the power button and vol up it will jsut reboot it
I tried many TWRP files none woked also I have android 7.0 and emui 5.0
P.S. sorry for bad english
Unlock bootloader again with ADB command:
"Fastboot oem unlock YOUR_CODE"
Reboot and flash a good version of TWRP for you.
Done!
Therand said:
Unlock bootloader again with ADB command:
"Fastboot oem unlock YOUR_CODE"
Reboot and flash a good version of TWRP for you.
Done!
Click to expand...
Click to collapse
Not working for me aswell
chakalovski2 said:
Not working for me aswell
Click to expand...
Click to collapse
What's not work?
ADB command?
Or fastboot?
What's return of command?
Error text?
What did you make on your phone?
How do you want help without explaining your problem?..
Hello,
When I try to send a command as flashing through fastboot it's telling me command not allowed it's kind of impossible to write or send data like a flash to my phone. Though the drivers are installed and adb too.
help me pls Command Not Allowed
I have bootloader code but when I write the command fastboot oem unlock ******* I get the command not allowed error 210 stock rom is not loaded with the three key method I want to install a twrp in vendor, system, product invalid argument error how to fixed pls help me (sorry my bad english) i can not open the oem lock because i do not know how to use the usb debug mode
Elite Rom 5.1 (Hassan Mirza) came to me after I uploaded it and I could not fix it again
TEL: P9 LİTE VNS-L31
{
"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"
}
Please help me
did you fixed that error
Failed (Remote: Command not allowed)
If yes How?
Because i am also in same problem...:crying::crying::crying:
Revert to stock OS, then go to Developer settings and enable OEM unlock.
Then repeat hte process.
How can I get the stock OS without TWRP? I tryed dload method, but theres is allways a problem when eRecovery tries to install the update.zip... Idon't know what to do.. My bluetooth is not working, that my problem
Good afternoon guys, sorry my english
My Mi A1 appeared this photo error below.
{
"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"
}
E: Failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: Operation not permitted
it is blocked and does not have root.
I used Miflash with the last room but it did not work.
I tried to make a wipe but without success.
I tried unlocking the bootloader, it also was not, I need the oem function unlocked in android.
I used the EDL mode with the latest rom version, it does all the worry, but it does not replace anything.
any help is valid.
Thank you.
Can you boot to the recovery?
Yes I can enter, but this error appears above, I can not do wipe.
Did you find any solution... I am also facing the same issue...
Flash stock recovery from fastboot on both slots. See what happen.
bandity said:
Good afternoon guys, sorry my english
My Mi A1 appeared this photo error below.
E: Failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: Operation not permitted
it is blocked and does not have root.
I used Miflash with the last room but it did not work.
I tried to make a wipe but without success.
I tried unlocking the bootloader, it also was not, I need the oem function unlocked in android.
I used the EDL mode with the latest rom version, it does all the worry, but it does not replace anything.
any help is valid.
Thank you.
Click to expand...
Click to collapse
Hi i also have this problem.. my phone have this bootloop. I tried to fix by repairing ES in miracle tool but nothing happen. I tried fastboot via cmd by unlocking the bootloader but still the same. it just restarted the phone and still in MI Logo stuck.
i try to reset it, but it says
API 3:
E: Failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: Operation not permitted
i try miracle tool to unlock oem it says
Code:
oem unlock
Reading info..
Auto detection Enabled..
Found: MSM8953
serial: 0xd33a613d
hw id: 0x000460e1
but still nothing happen.
it just rebooted the phone at the same state. i also tried using fastboot unlock bootloader in cmd. just the same.
Code:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.064s]
finished. total time: 0.064s
i tried using mi flash the it saying " the device is locked"
i tried mi unlock it says " cant get info to the phone"
Last chance i tried flashing EDL Mode using 2 pins to detect Qualcomm USB
But still nothing happens. please help.
my phone still in bootloop and i can only access recovery mode and fastboot.
Please help anyone??please..
Same thing happened to me yesterday, the device just freezed and now it doesn't boot.
I tried to do a factory reset via stock recovery but it stuck at formating /data.
I think the memory is dead
same with my phone iots freezed and then cat load, I am in stuck at formating/data
Hello,
I have a small problem with my old phone. After ~3 months ago of the last use I decided to launch P8 Lite. Yesterday I just wanted to flash LineageOS on it. Unfortunately, everytime that I'm trying to launch this phone, it welcomes me with just a red lightning symbol and with an animation of huawei logo.
Some details about my phone:
- P8 Lite has an unlocked bootloader
- Command "fastboot oem get-bootinfo" sends "(bootloader) unlocked" message.
Okay, let's go.
At first - I've downloaded stock ROM. I've exported cust, recovery, boot, and system (.img) files with HuaweiUpdateExtractor from update.app.
Unfortunately, when I've tried to flash boot and recovery, fastboot sends unpleasant output in the console.
HTML:
$ ./fastboot flash boot BOOT.img
Sending 'boot' (22672 KB) OKAY [ 0.590s]
Writing 'boot' FAILED (remote: 'flash writeprim vrl failure')
fastboot: error: Command failed
It doesn't look good.
Corrupted flash memory isn't the option too, because when I've tried to flash modded BOOT and RECOVERY files from xda - fastboot passed me with flashing.
Trying to flash CUST and SYSTEM's .img files goes well.
Let's try the other way. Let's check if "./fastboot erase data" is working.
HTML:
$ ./fastboot erase data
Erasing 'data' FAILED (remote: 'Command notallowed')
fastboot: error: Command failed
It doesn't work too.
If the stock recovery can't be flashed to my phone, how about flashing the other recovery, like TWRP?
HTML:
$ ./fastboot flash recovery twrp/RECOVERY.img
Sending 'recovery' (36166 KB) OKAY [ 0.940s]
Writing 'recovery' OKAY [ 0.634s]
Finished. Total time: 1.622s
Well, It works! But, I think that P8 Lite doesn't want to work with me aswell.
{
"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"
}
The errors shown on the bottom side of the screen can be different - depending on the img file that I've flashed as recovery.
Well, so let's try to boot TWRP manually using "fastboot boot" command
HTML:
$ ./fastboot boot twrp/RECOVERY.img
Sending 'boot.img' (36166 KB) OKAY [ 0.941s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Maybe let's try to check if I have unlocked bootloader for sure.
Let's try to relock my bootloader... nah
HTML:
$ ./fastboot oem lock
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
===
$ ./fastboot oem relock
FAILED (remote: 'data parse fail')
fastboot: error: Command failed
So... self-factory reset from sdcard is the only way?
Unluckily, this option isn't available too. I've removed all files from my SD Card, I've created "dload" folder and I've put update.app file in it.
Interestingly, when I'm holding VOL+, VOL- and POWER button at once during the launch - phone moves to the Huawei's eRecovery screen.
As long as "clear cache" option is possible to do, "wipe data & factory reset" option is undoable. Trying that option shows red, exclamation mark and "Operation was unsuccesful" label on the screen.
Moreover, huawei corrupted my SD Card. How? I don't know, but on every phone that I'm trying to mount this SD Card - they doesn't detect it
At this moment I don't have any ideas. I'm determined to repair this P8 Lite, but the question is - what should I do? I need help for 3 questions:
1. What steps should I do to unbrick my phone?
2. Is there any way to pass over "Command not allowed" message in he fastboot, so I could do anything?
3. How can I turn back my SD Card to work?
Here is the list of commands that returns "Command not allowed" message to me:
HTML:
./fastboot boot
./fastboot oem - in some cases
./fastboot erase
./fastboot flashing unlock
Thanks for every help!
UP
Try to uncompress a update.app folder and flash erecovery, there is a tool to transfer update.app onto .IMG on xda
yzena said:
Try to uncompress a update.app folder and flash erecovery, there is a tool to transfer update.app onto .IMG on xda
Click to expand...
Click to collapse
I did that arleady. I've exported 4 files (which I've mentioned above) with HuaweiUpdateExtractor. Trying to flash CUST and SYSTEM images passes, but when I'm trying to flash BOOT and RECOVERY - Fastboot is stopping me with an output that I mentioned above aswell ("flash writeprim vrl failure" problem).
Bump
Refresh
Still looking for answers!
Refresh!
Refresh
Refresh!
I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?
rsshilli said:
I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/
Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
{
"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"
}
rsshilli said:
Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
Click to expand...
Click to collapse
It seems that your USB debugging or OEM unlock toggle was un-ticked.
Do you have recovery available to format/reset device?
RSDLite doesn't work with your model?
Negative
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .
rsshilli said:
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .
Click to expand...
Click to collapse
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!
Well, that's weird
Huh. I tried LMSA tonight again just for fun and it worked fine this time. It found the image, downloaded it, and reflashed the phone to factory settings. Yay! I'm back in. I tried it many times before. I know my firmware updated on the phone a few days before this happened. I guess I just needed to wait for a bit. Thank you everybody.
Ryan
WoKoschekk said:
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!
Click to expand...
Click to collapse
For next time, how does one find the exact firmware needed? I could never figure that out.
rsshilli said:
For next time, how does one find the exact firmware needed? I could never figure that out.
Click to expand...
Click to collapse
Code:
fastboot getvar all
Hi
Long story short
i got my leeco le pro 3 x720
i got it from aliexpress and this is how it looks :
{
"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"
}
So When i received the phone i went and installed the usb drivers and the adb tool ofc after i did my research
so in the adb and after checking for the devices there , i reboot into fastboot mode and checked for the device and it was recognized , i sent "fastboot oem unlock-go" to unlock the boot loader , i received this :
...
OKAY [ 0.008s]
finished. total time: 0.009s
then i checked with "fastboot oem device-info"
and i got :
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.084s
now into the problem
when i reboot and check again with "fastboot oem device-info" :
i receive :
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.084s
So i went and did everything again but instead of reboot i flashed the latest twrp from the official stie
then i did "fastboot boot [recoveryname]" to boot to the recovery , that did work and i got into the twrp
but when i shut my device and enter to the recovery via "power button and volume up"
i get the leeco logo + recovery underneath it , then everything turns black
when i connect to the adb and check for adb devices it says recovery
but the screen stays black until I reboot to to the system again
so heres what i tried ( another twrp version "old ones" and didnt work i tried the stock recovery again and it did not work)
i get the same black screen when I get to the recovey i can access the recovery only via "fastboot boot recovery.img"
even if i did "adb reboot recovery" i get black screen
i tried All in one tool to check with the bootloader again when i check the statue of the boot loader nothing happens
when i try to unlock it it says failed , i didnt wont to press lock bootloader cause i dont know how to use the tool yet.
and one more thing : when i got to twrp on the first time via "fastboot boot...." when i try to flash i get vendor errors and stuff.
so please help me , i spent two days or more searching for any clue :'(
its my first time into custom roms and i really want to flash the leeco le pro 3 into a better rom
i even tried to flash my Lg stylo 2 plus to 8.1 oreo and that was a piece of cake i got it running in less than an hour
as a test subject.
HELP !
Yep, EUI will restore the stock recovery. You have to do the TWRP installation this way, especially step 5:
Installation:
1. Make sure your bootloader is unlocked
2. Download the recovery image from above
3. Reboot into fastboot
4. Run this command (Change the .img to whatever the name of file is you downloaded): fastboot flash recovery twrp-3.5.0_9-1-zl1.img
5. Once it is flashed, please force a reboot to recovery by holding down the Power and Volume Up buttons at the same time until the phone reboots and you see the LeEco logo and the word "recovery" underneath it. (This is because if you allow normal boot after flashing TWRP while you are using EUI and your phone reboots to EUI it will overwrite the recovery with the stock EUI recovery. Forcing a reboot from the bootloader to recovery prevents this issue)
is it okay if the bootloader unlock temporarily ? i did try unlocking the bootloader then flashing the twrp then rebooting to recovery with the power key and volume but same issue the screen turns black after the leeco logo with the recovery word , the only way i can access twrp by fastboot boot "name".img , but i dont know if its the correct way
Ehm, sorry, right now I see that you didi not flash the bootloader. You have to do this with:
fastboot flash recovery.img
did everything you suggested , still when i go to recovery i get a black screen cant install my roms like this , im sad now
No, I think we missed something. Check this step by step guide completly:
https://www.getdroidtips.com/unlock-bootloader-leeco-le-pro-3/
Did you OEM unlock before you unlock the boitloader?
i did every single thing oem unlock usb debugin my pc is recognizing the phone in adb and fastboot
i unlocked the bootloader with the command fastboot oem unlock-go
then checked with fastboot oem device-info
then i flashed latest twrp recovery with "fastboot boot recovery [name].img
then i pressed and hold power and volume up untill i got leeco logo + recovery word then the screen goes black thats it
So first part should be OK. But you did not flash the recovery. fastboot boot recovery.img is just to started the recovery from memory and not to install it. The correct command to flash is: fastboot flash recovery.img
After this you have to do the force reboot.
i typed the wrong command xD i really flash it with fastboot flash you can check the whole steps i did in the main thread above , anyways i found the problem and got everything working all i need to do was to flash a new firmware to unlock the bootloader and thats it , thank you for helping :3
Well done. Wih the the new firmware you removed EUI. So the bootloader isn't reset anymore. Have fun with the device.
THANK YOU SO MUCH !!