Нужна помощь
-
Scooter
- Новичок
- Сообщения: 5
- Зарегистрирован: Вт июн 07, 2022 2:57 pm
Телефон Honor 8 lite на Kirin 655.
Проблема такая — слетела прошивка, при включении после логотипа хонор выдает ошибку
Please update system again
func no: 11 (recovery image)
error no: 2 (loaded failed)
Телефон в циклической перезагрузке. Выключаю только с помощью переподключения аккумулятора.
Не могу обновить прошивку через флешку — не заходит в режим обновления, выдает ту же ошибку, пробовал через отг результатов ноль.
Не могу зайти в режим рекавери
Но могу зайти в режим бутлоадера и компьютер телефон видит
Но бутлоадер заблокирован и фрп тоже.
Можно ли его как то реанимировать?
-
PRE-DATOR
- Мастер
- Сообщения: 1929
- Зарегистрирован: Вт дек 17, 2019 4:22 pm
- Откуда: телеграмм TwoiPredator
- Контактная информация:
Вт июн 07, 2022 3:17 pm
Scooter писал(а): ↑Вт июн 07, 2022 3:07 pm
Телефон Honor 8 lite на Kirin 655.
Проблема такая — слетела прошивка, при включении после логотипа хонор выдает ошибку
Please update system again
func no: 11 (recovery image)
error no: 2 (loaded failed)
Телефон в циклической перезагрузке. Выключаю только с помощью переподключения аккумулятора.
Не могу обновить прошивку через флешку — не заходит в режим обновления, выдает ту же ошибку, пробовал через отг результатов ноль.
Не могу зайти в режим рекавери
Но могу зайти в режим бутлоадера и компьютер телефон видит
Но бутлоадер заблокирован и фрп тоже.
Можно ли его как то реанимировать?
Драсьььььььььььььььььььььььте, изначально что делалось? кто то прошивал его я так понимаю? хотели повысить версию?
-
Scooter
- Новичок
- Сообщения: 5
- Зарегистрирован: Вт июн 07, 2022 2:57 pm
Вт июн 07, 2022 3:59 pm
Телефон достался мне таким. Прежний хозяин говорит что при обновлении прошивки по воздуху — в процессе обновления разрядилась батарея, и как итог эта вот ошибка
-
PRE-DATOR
- Мастер
- Сообщения: 1929
- Зарегистрирован: Вт дек 17, 2019 4:22 pm
- Откуда: телеграмм TwoiPredator
- Контактная информация:
Вт июн 07, 2022 4:57 pm
PRE-DATOR писал(а): ↑Вт июн 07, 2022 4:56 pm
Scooter писал(а): ↑Вт июн 07, 2022 3:59 pm
Телефон достался мне таким. Прежний хозяин говорит что при обновлении прошивки по воздуху — в процессе обновления разрядилась батарея, и как итог эта вот ошибкаНу чудес не бывает
Если есть фастбут нормальный
Считать инфу что там стоит. писал тут viewtopic.php?f=3&t=2215
, пробовать восстановить + программатор ,
Если же нет , тестпоинт + программатор
-
Scooter
- Новичок
- Сообщения: 5
- Зарегистрирован: Вт июн 07, 2022 2:57 pm
Вс июн 12, 2022 2:12 am
Загрузчик разблокировать удалось. А вот чем теперь это дело прошить, можете подсказать?
-
PRE-DATOR
- Мастер
- Сообщения: 1929
- Зарегистрирован: Вт дек 17, 2019 4:22 pm
- Откуда: телеграмм TwoiPredator
- Контактная информация:
Вс июн 12, 2022 10:50 am
Scooter писал(а): ↑Вс июн 12, 2022 2:12 am
Загрузчик разблокировать удалось. А вот чем теперь это дело прошить, можете подсказать?
Использовать тот же метод HWOTA и файлики с HH Finder
-
Scooter
- Новичок
- Сообщения: 5
- Зарегистрирован: Вт июн 07, 2022 2:57 pm
Вс июн 12, 2022 12:01 pm
Удалось !!!!Возился с ним неделю) И вот победа!
Разблокировал загрузчик программой Potato NV.
Затем по вашему видео просто прошил его board прошивкой в test point. Прошивку на мою модель пришлось поискать, но в итоге нашел.
Сейчас аппарат заряжается, как зарядится так обновлюсь. Хоть и остался последний шаг, но по моему это уже победа.
Спасибо вам за ваш канал на ютуб и поддержку!
Error func no 11 recovery image error no 2 load failed
Принесли в ремонт Honor 8 lite PRA-TL10, при включении ошибка Func no: 11 (recovery image) Error no: 2 (load failed!). При прошивке с карты памяти вываливается ошибка на 5%. В fastboot заходит, bootloader unlocked, но при попытке прошить или затереть любой раздел ошибка (remote: Command not allowed). В recovery, e-recovery не заходит.
Что делал: распаковал последнюю прошивку, прошивал напрямую в разделы по ISP (пинаут выложил здесь http://www.mcrf.ru/forum/showthread.php?p=320408#post320408). Также прошивал по вендору по этому мануалу http://www.mcrf.ru/forum/showpost.php?p=313414&postcount=3. Результата нет, кроме того, что если прошить fastboot, то аппарат не включается.
Флешка живая — после затирания и записи проверял в HEX.
Recovery, Recovery2 прошивал из распакованной прошивки — изменений нет, та же ошибка Func no: 11 (recovery image)
Просьба, по возможности, выложить живой дамп, включая ROM2. Ну и от советов не откажусь ))
И ещё один момент — в логе есть раздел P40 (BOOTFAIL_INFO) [0x3d000000 0x200000] Size: 2.0MB — это нормально? Пробовал в него прошивать boot.img, никаких изменений не было.
Z3X EasyJtag Software ver. 2.6.0.1
Loading eMMC GEN1 Firmware. IO: 1800 mV
Box S/N: ***, ,FW Ver.: 01.60
CMD Pullup Level:2165 mV
CMD Active Level:1845 mV
Box IO Level:1800 mV
CLK Rate:14000 khz
HiPower mode is off!
———- eMMC Device Information ———-
EMMC CID : 45010044463430333201AFE3B53A240C
EMMC CSD : D00F00328F5903FFFFFFFFEF8A404022
EMMC Manufacturer ID: 0045 , OEM ID: 0100
EMMC Date: 02/2017 Rev.0x1
EMMC NAME: DF4032 , S/N: 2950935866
EMMC NAME (HEX): 44463430333200
EMMC ROM1 (Main User Data) Capacity: 29820 MB
EMMC ROM2 (Boot Partition 1) Capacity: 4096 kB
EMMC ROM3 (Boot Partition 2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
EMMC Password Locked: No
Extended CSD rev 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG: 0x08] Boot from:ROM2 (Boot Partition 1)
Boot bus config [177]: 0x02 , width 8bits , Partition config [179]: 0x08.
H/W reset function [RST_N_FUNCTION]: 0x01
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x00000000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
———————————————
Backup saved: DF4032_2950935866_20170809_1942.extcsd
Caution: invalid backup GPT header, but valid main header!
Warning! Main and backup partition tables differ!n
Warning! One or more CRCs don’t match. You should repair the disk!
Partition table scan:
GPT: damaged
Caution: Found protective or hybrid MBR and corrupt GPT.
Real (Hardware) Disk/Image size: 3A3E000 sectors 29.1 GiB
Soft (Partitioned) Disk/Image size: 3A3DFDD sectors 29.1 GiB
Logical sector size: 0x200 bytes
Disk identifier (GUID): F9F21FFF-A8D4-5F0E-9746-594869AEC34E
First usable sector: 34
Last usable sector: 61071359
Found Data areas (firmware parts) count is: 49
Partition info successfully found
———————————————
P0 (VRL) [0x80000 0x40000] Size: 256.0KB
P1 (VRL_BACKUP) [0xc0000 0x40000] Size: 256.0KB
P2 (FW_LPM3) [0x100000 0x40000] Size: 256.0KB
P3 (FRP) [0x140000 0xc0000] Size: 768.0KB
P4 (FASTBOOT) [0x200000 0x400000] Size: 4.0MB
P5 (MODEMNVM_FACTORY) [0x600000 0x400000] Size: 4.0MB
P6 (NVME) [0xa00000 0x600000] Size: 6.0MB
P7 (OEMINFO) [0x1000000 0x4000000] Size: 64.0MB
P8 (RESERVED3) [0x5000000 0x400000] Size: 4.0MB
P9 (MODEMNVM_BACKUP) [0x5400000 0x400000] Size: 4.0MB
P10 (MODEMNVM_IMG) [0x5800000 0x800000] Size: 8.0MB
P11 (MODEMNVM_SYSTEM) [0x6000000 0x400000] Size: 4.0MB
P12 (SECURE_STORAGE) [0x6400000 0x2000000] Size: 32.0MB
P13 (RESERVED4) [0x8400000 0x200000] Size: 2.0MB
P14 (RESERVED5) [0x8600000 0x200000] Size: 2.0MB
P15 (PERSIST) [0x8800000 0x200000] Size: 2.0MB
P16 (RESERVED1) [0x8a00000 0xe00000] Size: 14.0MB
P17 (MODEM_OM) [0x9800000 0x2000000] Size: 32.0MB
P18 (SPLASH2) [0xb800000 0x4000000] Size: 64.0MB
P19 (MISC) [0xf800000 0x200000] Size: 2.0MB
P20 (MODEMNVM_UPDATE) [0xfa00000 0x1800000] Size: 24.0MB
P21 (RECOVERY2) [0x11200000 0x4000000] Size: 64.0MB
P22 (RESERVED2) [0x15200000 0x3c00000] Size: 60.0MB
P23 (TEEOS) [0x18e00000 0x400000] Size: 4.0MB
P24 (TRUSTFIRMWARE) [0x19200000 0x200000] Size: 2.0MB
P25 (SENSORHUB) [0x19400000 0x1000000] Size: 16.0MB
P26 (FW_HIFI) [0x1a400000 0xc00000] Size: 12.0MB
P27 (BOOT) [0x1b000000 0x2000000] Size: 32.0MB
P28 (RECOVERY) [0x1d000000 0x4000000] Size: 64.0MB
P29 (DTS) [0x21000000 0x2000000] Size: 32.0MB
P30 (MODEM_FW) [0x23000000 0x6000000] Size: 96.0MB
P31 (RESERVED7) [0x29000000 0x200000] Size: 2.0MB
P32 (RESERVED8) [0x29200000 0x200000] Size: 2.0MB
P33 (DFX) [0x29400000 0x1000000] Size: 16.0MB
P34 (RESERVED6) [0x2a400000 0x400000] Size: 4.0MB
P35 (CACHE) [0x2a800000 0x10000000] Size: 256.0MB
P36 (HISITEST0) [0x3a800000 0x200000] Size: 2.0MB
P37 (HISITEST1) [0x3aa00000 0x200000] Size: 2.0MB
P38 (HISITEST2) [0x3ac00000 0x400000] Size: 4.0MB
P39 (PATCH) [0x3b000000 0x2000000] Size: 32.0MB
P40 (BOOTFAIL_INFO) [0x3d000000 0x200000] Size: 2.0MB
P41 (RRECORD) [0x3d200000 0x1000000] Size: 16.0MB
P42 (RESERVED9) [0x3e200000 0x1e00000] Size: 30.0MB
P43 (SYSTEM) [0x40000000 0xbc000000] Size: 2.937GB
P44 (CUST) [0xfc000000 0xc000000] Size: 192.0MB
P45 (VERSION) [0x108000000 0x2000000] Size: 32.0MB
P46 (VENDOR) [0x10a000000 0x31000000] Size: 784.0MB
P47 (PRODUCT) [0x13b000000 0xc000000] Size: 192.0MB
P48 (USERDATA) [0x147000000 0x600c00000] Size: 24.11GB
—— Android information ——
Detected LINUX(Android) SYSTEM : 0x0040000000 (2.937GB)
Unable to mount SYSTEM , code : 95
———————————————
Done.
при включении ошибка Func no: 11 (recovery image) Error no: 2 (load failed!)
А потребление какое у микросхемы памяти при записичтении?
Вышло обновление z3x easy JTAG, сделайте проверку блоков еММС.
Все-таки проблема в памяти часто, особенно Huawei.
Внимательно смотрите на темы где оставляете решения. Проблематично потом перелопачивать сообщения не относящиеся к теме. Pinout перенес в соответствующую тему
Также прошивал по вендору по этому мануалу http://www.mcrf.ru/forum/showpost.php?p=313414&postcount=3. Результата нет, кроме того, что если прошить fastboot, то аппарат не включается.
лог, пожалуйста, покажите (из папки Log)
Флешка живая — после затирания и записи проверял в HEX.
запустите Random Verify Emmc на полчаса — час (в настройках на 500-700Мб).
Если не будет битых блоков, то надо будет пробовать подбирать прошивку.
А потребление какое у микросхемы памяти при записичтении?
Ммм. а как его проверить? ))
Лог записи по вендору:
14.08.2017 17:30:33> EasyJTAG API ver. 2008
14.08.2017 17:30:33> Setting IO Levels to 2.8V
14.08.2017 17:30:33> Setting frequence to 14 Mhz
14.08.2017 17:30:33> HiPower mode is OFF
14.08.2017 17:30:34> OpenUSB returned = 0
14.08.2017 17:30:34> Power Controller returned = 0
14.08.2017 17:30:35> EasyJTAG Box Serial = ***
14.08.2017 17:30:35> EasyJTAG Box Firmware = 01.60
14.08.2017 17:30:35> HiPower mode is OFF
14.08.2017 17:30:35> Frequence: 14 Mhz
14.08.2017 17:30:35> CMD Pullup Level: 1980 mV
14.08.2017 17:30:35> CMD Active Level: 2444 mV
14.08.2017 17:30:35> eMMC Init returned = 0
14.08.2017 17:30:35> EMMC Device Information :
14.08.2017 17:30:35> EMMC CID: 45010044463430333201AFE3B53A240C
14.08.2017 17:30:35> EMMC CSD: D00F00328F5903FFFFFFFFEF8A404022
14.08.2017 17:30:35> EMMC Manufacture Name: SANDISK
14.08.2017 17:30:35> EMMC Manufacture ID: 0x45 , OEM ID: 0100
14.08.2017 17:30:35> EMMC Manufacture Date: 2/2017 , Rev: 01
14.08.2017 17:30:35> EMMC NAME: DF4032 , S/N: AFE3B53A , rev. 01
14.08.2017 17:30:35> EMMC NAME (HEX): 444634303332
14.08.2017 17:30:35> EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
14.08.2017 17:30:35> EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
14.08.2017 17:30:35> EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 KB (000000400000)
14.08.2017 17:30:35> EMMC Permanent Write Protection: No
14.08.2017 17:30:35> EMMC Temporary Write Protection: No
14.08.2017 17:30:35> Extended CSD Information :
14.08.2017 17:30:35> Extended CSD rev: 1.8 (MMC 5.1)
14.08.2017 17:30:35> Boot configuration [PARTITION_CONFIG]: 0x08 , Boot from: ROM2 (Boot partition 1)
14.08.2017 17:30:35> Boot Bus Config: 0x02 , width 8bit
14.08.2017 17:30:35> H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
14.08.2017 17:30:35> Supported partition features [PARTITIONING_SUPPORT]: 0x07
14.08.2017 17:30:35> Device supports partitioning features
14.08.2017 17:30:35> Device can have enhanced technological features in partitions and user data area
14.08.2017 17:30:35> Device can have extended partitions attribute
14.08.2017 17:30:35> Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
14.08.2017 17:30:35> Backup saved: DF4032_AFE3B53A_20170814_173035.extcsd
14.08.2017 17:30:35> EMMC Init completed.
14.08.2017 17:30:35>
14.08.2017 17:30:35> Opening file: C:1DF4032_rawprogram0.xml
14.08.2017 17:30:35>
14.08.2017 17:30:35> The size of the last section has been updated
14.08.2017 17:31:29>
14.08.2017 17:31:29> Looking for EasyJTAG box.
14.08.2017 17:31:29> EasyJTAG API ver. 2008
14.08.2017 17:31:29> Setting IO Levels to 2.8V
14.08.2017 17:31:29> Setting frequence to 14 Mhz
14.08.2017 17:31:29> HiPower mode is OFF
14.08.2017 17:31:30> OpenUSB returned = 0
14.08.2017 17:31:30> Power Controller returned = 0
14.08.2017 17:31:31> EasyJTAG Box Serial = ***
14.08.2017 17:31:31> EasyJTAG Box Firmware = 01.60
14.08.2017 17:31:31> HiPower mode is OFF
14.08.2017 17:31:31> Frequence: 14 Mhz
14.08.2017 17:31:31> CMD Pullup Level: 1980 mV
14.08.2017 17:31:31> CMD Active Level: 2433 mV
14.08.2017 17:31:31> eMMC Init returned = 0
14.08.2017 17:31:31> EMMC Device Information :
14.08.2017 17:31:31> EMMC CID: 45010044463430333201AFE3B53A240C
14.08.2017 17:31:31> EMMC CSD: D00F00328F5903FFFFFFFFEF8A404022
14.08.2017 17:31:31> EMMC Manufacture Name: SANDISK
14.08.2017 17:31:31> EMMC Manufacture ID: 0x45 , OEM ID: 0100
14.08.2017 17:31:31> EMMC Manufacture Date: 2/2017 , Rev: 01
14.08.2017 17:31:31> EMMC NAME: DF4032 , S/N: AFE3B53A , rev. 01
14.08.2017 17:31:31> EMMC NAME (HEX): 444634303332
14.08.2017 17:31:31> EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
14.08.2017 17:31:31> EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
14.08.2017 17:31:31> EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 KB (000000400000)
14.08.2017 17:31:31> EMMC Permanent Write Protection: No
14.08.2017 17:31:31> EMMC Temporary Write Protection: No
14.08.2017 17:31:31> Extended CSD Information :
14.08.2017 17:31:31> Extended CSD rev: 1.8 (MMC 5.1)
14.08.2017 17:31:31> Boot configuration [PARTITION_CONFIG]: 0x08 , Boot from: ROM2 (Boot partition 1)
14.08.2017 17:31:31> Boot Bus Config: 0x02 , width 8bit
14.08.2017 17:31:31> H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
14.08.2017 17:31:31> Supported partition features [PARTITIONING_SUPPORT]: 0x07
14.08.2017 17:31:31> Device supports partitioning features
14.08.2017 17:31:31> Device can have enhanced technological features in partitions and user data area
14.08.2017 17:31:31> Device can have extended partitions attribute
14.08.2017 17:31:31> Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
14.08.2017 17:31:31> Backup saved: DF4032_AFE3B53A_20170814_173131.extcsd
14.08.2017 17:31:31> EMMC Init completed.
14.08.2017 17:31:31>
14.08.2017 17:31:31> Operation: Write by vendor (Qualcomm/HiSilicon)
14.08.2017 17:31:31>
14.08.2017 17:31:31> Creating GPT-partitioninig
14.08.2017 17:31:31> GPT-partitioning done
14.08.2017 17:31:31>
14.08.2017 17:31:41> Partition name: fw_lpm3
14.08.2017 17:31:41> Filename: fw_lpm3.bin , Offset: 000000100000 , filesize: 168320 bytes
14.08.2017 17:31:41> eMMC switching to ROM1
14.08.2017 17:31:41> Erasing partition.
14.08.2017 17:31:42> Writing partition.
14.08.2017 17:31:42> Done writing partition. Write speed: 435,31 Kb/s
14.08.2017 17:31:42> Partition name: fastboot
14.08.2017 17:31:42> Filename: fastboot.bin , Offset: 000000200000 , filesize: 3203072 bytes
14.08.2017 17:31:42> eMMC switching to ROM1
14.08.2017 17:31:42> Erasing partition.
14.08.2017 17:31:43> Writing partition.
14.08.2017 17:31:48> Done writing partition. Write speed: 756,10 Kb/s
14.08.2017 17:31:48> Partition name: modemnvm_update
14.08.2017 17:31:48> Filename: modemnvm_update.bin , Offset: 00000FA00000 , filesize: 11409084 bytes
14.08.2017 17:31:48> eMMC switching to ROM1
14.08.2017 17:31:48> Erasing partition.
14.08.2017 17:31:49> Writing partition.
14.08.2017 17:32:03> Done writing partition. Write speed: 782,62 Kb/s
14.08.2017 17:32:03> Partition name: recovery2
14.08.2017 17:32:03> Filename: recovery2.bin , Offset: 000011200000 , filesize: 36407296 bytes
14.08.2017 17:32:03> eMMC switching to ROM1
14.08.2017 17:32:03> Erasing partition.
14.08.2017 17:32:05> Writing partition.
14.08.2017 17:32:47> Done writing partition. Write speed: 846,95 Kb/s
14.08.2017 17:32:47> Partition name: teeos
14.08.2017 17:32:47> Filename: teeos.bin , Offset: 000018E00000 , filesize: 3242624 bytes
14.08.2017 17:32:47> eMMC switching to ROM1
14.08.2017 17:32:47> Erasing partition.
14.08.2017 17:32:47> Writing partition.
14.08.2017 17:32:51> Done writing partition. Write speed: 807,95 Kb/s
14.08.2017 17:32:51> Partition name: trustfirmware
14.08.2017 17:32:51> Filename: trustfirmware.bin , Offset: 000019200000 , filesize: 117632 bytes
14.08.2017 17:32:51> eMMC switching to ROM1
14.08.2017 17:32:51> Erasing partition.
14.08.2017 17:32:52> Writing partition.
14.08.2017 17:32:52> Done writing partition. Write speed: 636,40 Kb/s
14.08.2017 17:32:52> Partition name: sensorhub
14.08.2017 17:32:52> Filename: sensorhub.bin , Offset: 000019400000 , filesize: 674688 bytes
14.08.2017 17:32:52> eMMC switching to ROM1
14.08.2017 17:32:52> Erasing partition.
14.08.2017 17:32:53> Writing partition.
14.08.2017 17:32:54> Done writing partition. Write speed: 826,01 Kb/s
14.08.2017 17:32:54> Partition name: fw_hifi
14.08.2017 17:32:54> Filename: fw_hifi.bin , Offset: 00001A400000 , filesize: 2925760 bytes
14.08.2017 17:32:54> eMMC switching to ROM1
14.08.2017 17:32:54> Erasing partition.
14.08.2017 17:32:55> Writing partition.
14.08.2017 17:32:58> Done writing partition. Write speed: 803,10 Kb/s
14.08.2017 17:32:58> Partition name: boot
14.08.2017 17:32:58> Filename: boot.bin , Offset: 00001B000000 , filesize: 15880192 bytes
14.08.2017 17:32:58> eMMC switching to ROM1
14.08.2017 17:32:58> Erasing partition.
14.08.2017 17:32:59> Writing partition.
14.08.2017 17:33:18> Done writing partition. Write speed: 836,54 Kb/s
14.08.2017 17:33:18> Partition name: recovery
14.08.2017 17:33:18> Filename: recovery.bin , Offset: 00001D000000 , filesize: 36407296 bytes
14.08.2017 17:33:18> eMMC switching to ROM1
14.08.2017 17:33:18> Erasing partition.
14.08.2017 17:33:19> Writing partition.
14.08.2017 17:34:02> Done writing partition. Write speed: 837,22 Kb/s
14.08.2017 17:34:02> Partition name: dts
14.08.2017 17:34:02> Filename: dts.bin , Offset: 000021000000 , filesize: 8167424 bytes
14.08.2017 17:34:02> eMMC switching to ROM1
14.08.2017 17:34:02> Erasing partition.
14.08.2017 17:34:03> Writing partition.
14.08.2017 17:34:13> Done writing partition. Write speed: 805,60 Kb/s
14.08.2017 17:34:13> Partition name: modem_fw
14.08.2017 17:34:13> Filename: modem_fw.bin , Offset: 000023000000 , filesize: 100663296 bytes
14.08.2017 17:34:13> eMMC switching to ROM1
14.08.2017 17:34:13> Erasing partition.
14.08.2017 17:34:15> Writing partition.
14.08.2017 17:36:04> Done writing partition. Write speed: 900,32 Kb/s
14.08.2017 17:36:04> Partition name: system
14.08.2017 17:36:04> Filename: system.bin , Offset: 000040000000 , filesize: 2767271428 bytes
14.08.2017 17:36:04> eMMC switching to ROM1
14.08.2017 17:36:05> Erasing partition.
14.08.2017 17:36:50> Writing partition.
14.08.2017 17:36:50> Sparse image found v.1.0 Total chunks: 7294
14.08.2017 18:33:36> Done writing partition. Write speed: 793,58 Kb/s
14.08.2017 18:33:36> Partition name: cust
14.08.2017 18:33:36> Filename: cust.bin , Offset: 0000FC000000 , filesize: 111689368 bytes
14.08.2017 18:33:36> eMMC switching to ROM1
14.08.2017 18:33:36> Erasing partition.
14.08.2017 18:33:39> Writing partition.
14.08.2017 18:33:39> Sparse image found v.1.0 Total chunks: 309
14.08.2017 18:35:51> Done writing partition. Write speed: 827,34 Kb/s
14.08.2017 18:35:53> Partition name: vendor
14.08.2017 18:35:53> Filename: vendor.bin , Offset: 00010A000000 , filesize: 435979820 bytes
14.08.2017 18:35:53> eMMC switching to ROM1
14.08.2017 18:35:53> Erasing partition.
14.08.2017 18:36:04> Writing partition.
14.08.2017 18:36:04> Sparse image found v.1.0 Total chunks: 7980
14.08.2017 18:44:34> Done writing partition. Write speed: 835,20 Kb/s
14.08.2017 18:44:34> Partition name: product
14.08.2017 18:44:34> Filename: product.bin , Offset: 00013B000000 , filesize: 151002224 bytes
14.08.2017 18:44:34> eMMC switching to ROM1
14.08.2017 18:44:34> Erasing partition.
14.08.2017 18:44:37> Writing partition.
14.08.2017 18:44:37> Sparse image found v.1.0 Total chunks: 1287
14.08.2017 18:47:32> Done writing partition. Write speed: 846,72 Kb/s
14.08.2017 18:47:32>
14.08.2017 18:47:32> Check BOOT_PARTITION_EN for the selected vendor
14.08.2017 18:47:32>
14.08.2017 18:47:32> All done
14.08.2017 18:47:32>
В первом посте дал неверную информацию, после записи по вендору телефон не включается, возврат «родных» fastboot, boot телефон не оживляет. Прошивка фулла приводит аппарат в исходное состояние.
Random Verify показал 87,43% медленных блоков, но ни одного битого нет.
Сейчас сделал запись по вендору пофайлово, результаты такие:
1. Прошил fw_lp3 — ошибка при включении поменялась на Func NO: 16 (lpm3 image), Error NO : 1 (security verify failed)
2. Fastboot — не включается. Прошивка дампа раздела вернула в предыдущее состояние
3. Modemnvm_update — без изменений
4. Recovery2 — телефон включается, но в логе Easy появилось «Check BOOT_PARTITION_EN for the selected vendor» — оставалась после записи каждого следующего раздела
5. Teeos, trustfirmware, sensorhub — без изменений
6. Fw_hifi — ошибка при включении поменялась на Func NO: 14 (iom3 image), Error NO : 1 (security verify failed)
7. Boot, recovery — без изменений
8. Dts — не включается. Прошивка дампа раздела вернула в предыдущее состояние
9. Прошивка остальных разделов — без изменений
Файлы, которые есть в распакованной прошивке, но не записываются по вендору (разделов нет в созданном Easy файле .xml) — CRC, CURVER, EFI, PACKAGE_TYPE, SHA256RSA, VERLIST, XLOADER
Ммм. а как его проверить? ))
Лог записи по вендору:
Random Verify показал 87,43% медленных блоков, но ни одного битого нет.
Первое: флешка в 32 гига, проверено 100Мб, этого мало, я говорил 500-700 надо. В настройках измените размер.
Второе: минимальная скорость чтения десяток кб/c это очень мало, значит провалы большие флешка изношена уже прилично.
Сейчас сделал запись по вендору пофайлово, результаты такие:
В оригинальной прошивке фалы имеют расширение img, у вас в записи по вендору только bin. Вы переименовывали фалы или шили старые?
Файлы, которые есть в распакованной прошивке, но не записываются по вендору (разделов нет в созданном Easy файле .xml) — CRC, CURVER, EFI, PACKAGE_TYPE, SHA256RSA, VERLIST, XLOADER
CRC — там контрольные суммы
CURVER текстовый файл там информация о версии
EFI — это сам GPT
VERLIST — текстовый файл там модели для которой прошивка
а вот XLOADER — без него аппарат не запустится. надо в изик лепить костыль, который там частично уже сделан.
смысл в том, что xloader записывается в аппарат с адреса 20000, но он не описан в GPT разметке, поэтому он не бекапится.
поэтому через write by vendor нужно вписывать файлы поверх дампа.
или вручную вписывать xloader с адреса 20000.
Вопрос в догонку. в папке с бекапом лежит файл 8xxx_image? Если лежит — это и есть этот xloader, который надо вписать по кнопке «Write 8xxx»
Вы переименовывали фалы или шили старые
Переименовал, поменял .img на .bin
в папке с бекапом лежит файл 8xxx_image?
Нет, такого файла нет, а в логе при бэкапе написано «8xxx image is blank. Skipped».
Прошивка Xloader.bin результата не дала:
Writing to: ROM1 , start: 0x000000020000 , size: 0x000000010E00
Input file: C:2XLOADER.bin
eMMC switching to ROM1
Writing partition.
Done writing partition. Write speed: 308,26 Kb/s
Сейчас запустил Random verify на 700 мб.
Сейчас сделал запись по вендору пофайлово, результаты такие:
1. Прошил fw_lp3 — ошибка при включении поменялась на Func NO: 16 (lpm3 image), Error NO : 1 (security verify failed)
2. Fastboot — не включается. Прошивка дампа раздела вернула в предыдущее состояние
попробуйте файлы fastboot.img и fw_lpm3.img из ota
Нет, такого файла нет, а в логе при бэкапе написано «8xxx image is blank. Skipped».
Весьма любопытно тогда. Смысл в том, что 8xxx image лежит после GPT, перед первым разделом и естественно о нем нету упоминаний в GPT. Это для Qualcomm. P8 lite это HiSilicon, там его быть не должно. Вопрос, куда льётся тогда xloader
Весьма любопытно тогда.
xloader с адреса 20000.
А вот здесь в родном бэкапе одни нули.
Xloader сидит в ROM2
Да, точно, он ). Random verify долго делается, прошить смогу через пару часов.
Источник
- Forum
- Huawei Android Phones
- Huawei P9 & P9 Plus
-
Hey guys i really need your help.
So i relock my phone, and it’s shows «ERROR MODE, Please update system again!» Error! Func:NO: 11 (recovery image), (Error NO: 2 (load failed!)»I have access to phone, when im fully discharge device, and then plug in, and run. OS is starting, and everythings seems normal. I can’t go to FASTBOOT&RESCUE mode,
Android 7.0, VNS-L21C432B380.Yes, i’m know i did something wrong with triying to installing root. But please help me.
08-20-2017 12:56 AM
-
Originally Posted by DVICE_121
Hey guys i really need your help.
So i relock my phone, and it’s shows «ERROR MODE, Please update system again!» Error! Func:NO: 11 (recovery image), (Error NO: 2 (load failed!)»I have access to phone, when im fully discharge device, and then plug in, and run. OS is starting, and everythings seems normal. I can’t go to FASTBOOT&RESCUE mode,
Android 7.0, VNS-L21C432B380.Yes, i’m know i did something wrong with triying to installing root. But please help me.
bro have you got any fix?
pleASE TELL ME….CONTACT ME PLEASE12-07-2017 11:04 AM
- Forum
- Huawei Android Phones
- Huawei P9 & P9 Plus
Huawei P9 Lite «Please update system again!»
Similar Threads
-
Replies: 2
Last Post: 09-15-2017, 06:32 AM
-
Replies: 1
Last Post: 08-20-2017, 03:34 AM
-
Replies: 0
Last Post: 08-19-2017, 11:57 PM
-
Replies: 1
Last Post: 08-19-2017, 11:22 PM
-
Replies: 0
Last Post: 08-19-2017, 08:59 PM
LINK TO POST COPIED TO CLIPBOARD
Hello !
After a wrong manipulation with TWRP, my OS (and recovery) got wiped ( i think ?)
Stuck in a boot loop (phone doesn’t want to shutdown) with :
Code:
ERROR MODE : [COLOR="Red"]Attention ! Please update system again[/COLOR] [[COLOR="Lime"]Android buddy[/COLOR]] [COLOR="Red"]Error ! Func NO : 11 (recovery image) Error NO : 2 (load failed)[/COLOR]
I’m still able to got the fastboot menu (i am fully unlocked) but nothing else (no twrp, no erecovery or whatever)
and i already tried to flash a custom recovery, kernel img, system img, recovery_ramdisk… with FASTBOOT and even with the multi tool… but nothing happens (maybe i do it wrong ?)
Some people on XDA redirected me on your software but i want to be sure there is no other option before i had to purchase the soft (i am a student, i don’t have a lot of money haha)
I got a VTR-L09 8.0.0.386(C432)…
Help me buddies, i don’t know what to do… 
(Sorry for my bad english, i tried to be clear 
)
Hi, I have Huawei P10 VTRL09C432 .. I did relock bootloader and now i can not enter my phone.it stuck at Error mode.
I tried almost every methods ( buttons combination to recovery or fastboot , force upgrade) but all failed .it always comes back to error mode ( not possible to turn off , only wait batterry to discharge). I discharge the batterry and charge, if I am lucky, sometimes it will boot into the system but it will black out. I can not do anything except turn off or volume, but while it was in this stage, i could connect to pc and get detected. pc try to install MTP driver but it also failed. I tried command in adb, it also failed (waiting for devices) …. In error mode , it’s tell me to connect HiSuite to recovery but i can’t because it need fastboot.
i want to try SPtool but i couldn’t find any scatter for it . If anyone has any suggestions , how can i make my fastboot work again.i would be really appreciated it.. Please help me.
Issues :
1.boot loader locked
2.no recovery ( can not be load )
3.can not enter fastboot
4.can not force update
5.PC not detect
Attached Files
error.jpg Size: 31.52 KB Downloads: 14
Posts: 379
Threads: 5
Joined: Oct 2015
Reputation:
2
(18-09-2017, 05:38 PM)Zerety Wrote: Hi, I have Huawei P10 VTRL09C432 .. I did relock bootloader and now i can not enter my phone.it stuck at Error mode.
I tried almost every methods ( buttons combination to recovery or fastboot , force upgrade) but all failed .it always comes back to error mode ( not possible to turn off , only wait batterry to discharge). I discharge the batterry and charge, if I am lucky, sometimes it will boot into the system but it will black out. I can not do anything except turn off or volume, but while it was in this stage, i could connect to pc and get detected. pc try to install MTP driver but it also failed. I tried command in adb, it also failed (waiting for devices) …. In error mode , it’s tell me to connect HiSuite to recovery but i can’t because it need fastboot.i want to try SPtool but i couldn’t find any scatter for it . If anyone has any suggestions , how can i make my fastboot work again.i would be really appreciated it.. Please help me.
Issues :
1.boot loader locked
2.no recovery ( can not be load )
3.can not enter fastboot
4.can not force update
5.PC not detect
Your phone isn’t Mediatek so you can’t use SP Flash tool.
The error message you are getting is
Code:
Error Mode
Attention!
Please update system again
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
I want to know, did you flash a custom recovery before this happened?
You are to flash the update.app / firmware to your phone. Have you downloaded it?
Sent from my Infinix X510 using Hovatek Forum
(This post was last modified: 19-09-2017, 12:03 PM by maxxxiii.)
Zerety
Enthusiastic Member
Posts: 9
Threads: 1
Joined: Sep 2017
Reputation:
0
(19-09-2017, 11:39 AM)maxxxiii Wrote:
(18-09-2017, 05:38 PM)Zerety Wrote: Hi, I have Huawei P10 VTRL09C432 .. I did relock bootloader and now i can not enter my phone.it stuck at Error mode.
I tried almost every methods ( buttons combination to recovery or fastboot , force upgrade) but all failed .it always comes back to error mode ( not possible to turn off , only wait batterry to discharge). I discharge the batterry and charge, if I am lucky, sometimes it will boot into the system but it will black out. I can not do anything except turn off or volume, but while it was in this stage, i could connect to pc and get detected. pc try to install MTP driver but it also failed. I tried command in adb, it also failed (waiting for devices) …. In error mode , it’s tell me to connect HiSuite to recovery but i can’t because it need fastboot.i want to try SPtool but i couldn’t find any scatter for it . If anyone has any suggestions , how can i make my fastboot work again.i would be really appreciated it.. Please help me.
Issues :
1.boot loader locked
2.no recovery ( can not be load )
3.can not enter fastboot
4.can not force update
5.PC not detectYour phone isn’t Mediatek so you can’t use SP Flash tool.
The error message you are getting isCode:
Error Mode
Attention!
Please update system againError!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)I want to know, did you flash a custom recovery before this happened?
You are to flash the update.app / firmware to your phone. Have you downloaded it?Sent from my Infinix X510 using Hovatek Forum
i did flash custom recovery. i also used official update.app but after relock , all seems to be gone. Im not sure ,if i wipe something by accident. because my phone look empty. i just understand yesterday , that my phone cant be use with SP. if you have anny suggestions of , how can i make my phone go to debugging or fastboot. i appreciaed it. thank you for your replied.
Posts: 379
Threads: 5
Joined: Oct 2015
Reputation:
2
(19-09-2017, 12:51 PM)Zerety Wrote: i did flash custom recovery. i also used official update.app but after relock , all seems to be gone. Im not sure ,if i wipe something by accident. because my phone look empty. i just understand yesterday , that my phone cant be use with SP. if you have anny suggestions of , how can i make my phone go to debugging or fastboot. i appreciaed it. thank you for your replied.
I need to understand some things to ascertain where you stand.
You unlocked bootloader then flashed a custom recovery. Did you relock bootloader while still on custom recovery or you flashed stock recovery
You said you used the official update.app after relock, was this flashed successfully.
At what point did the phone get bricked and what was the last thing you recall doing that might have caused the brick
Sent from my Infinix X510 using Hovatek Forum
Zerety
Enthusiastic Member
Posts: 9
Threads: 1
Joined: Sep 2017
Reputation:
0
(19-09-2017, 05:45 PM)maxxxiii Wrote:
(19-09-2017, 12:51 PM)Zerety Wrote: i did flash custom recovery. i also used official update.app but after relock , all seems to be gone. Im not sure ,if i wipe something by accident. because my phone look empty. i just understand yesterday , that my phone cant be use with SP. if you have anny suggestions of , how can i make my phone go to debugging or fastboot. i appreciaed it. thank you for your replied.
I need to understand some things to ascertain where you stand.
You unlocked bootloader then flashed a custom recovery. Did you relock bootloader while still on custom recovery or you flashed stock recovery
You said you used the official update.app after relock, was this flashed successfully.
At what point did the phone get bricked and what was the last thing you recall doing that might have caused the brickSent from my Infinix X510 using Hovatek Forum
if i remember correctly . i flashed with HWOTA ,when the phone reboot ,it has problem with update system ( stuck at 5%).i boot in to custom recovery and wipe ( intended to flash again ) and relocked my bootloader . after it relocked , it boot to error
Posts: 379
Threads: 5
Joined: Oct 2015
Reputation:
2
(21-09-2017, 07:14 AM)Zerety Wrote: if i remember correctly . i flashed with HWOTA ,when the phone reboot ,it has problem with update system ( stuck at 5%).i boot in to custom recovery and wipe ( intended to flash again ) and relocked my bootloader . after it relocked , it boot to error
So what you’re telling me is that you locked your Bootloader while on a custom recovery
Sent from my Infinix X510 using Hovatek Forum
Zerety
Enthusiastic Member
Posts: 9
Threads: 1
Joined: Sep 2017
Reputation:
0
(21-09-2017, 11:41 AM)maxxxiii Wrote:
(21-09-2017, 07:14 AM)Zerety Wrote: if i remember correctly . i flashed with HWOTA ,when the phone reboot ,it has problem with update system ( stuck at 5%).i boot in to custom recovery and wipe ( intended to flash again ) and relocked my bootloader . after it relocked , it boot to error
So what you’re telling me is that you locked your Bootloader while on a custom recovery
Sent from my Infinix X510 using Hovatek Forum
sorry i dont really understand what its mean , locked Bootloader while on a custom recovery .. after wiped.i turned off , go to fastboot and relock.. is that how it call ? if it is , than , yes
Posts: 379
Threads: 5
Joined: Oct 2015
Reputation:
2
(21-09-2017, 12:40 PM)Zerety Wrote: sorry i dont really understand what its mean , locked Bootloader while on a custom recovery .. after wiped.i turned off , go to fastboot and relock.. is that how it call ? if it is , than , yes
Let me rephrase. Which custom recovery did you flash to your phone; TWRP, CWM, Philz ?
I also want to know if you still have the update.app file on your PC.
Sent from my Infinix X510 using Hovatek Forum
Zerety
Enthusiastic Member
Posts: 9
Threads: 1
Joined: Sep 2017
Reputation:
0
(21-09-2017, 05:31 PM)maxxxiii Wrote:
(21-09-2017, 12:40 PM)Zerety Wrote: sorry i dont really understand what its mean , locked Bootloader while on a custom recovery .. after wiped.i turned off , go to fastboot and relock.. is that how it call ? if it is , than , yes
Let me rephrase. Which custom recovery did you flash to your phone; TWRP, CWM, Philz ?
I also want to know if you still have the update.app file on your PC.Sent from my Infinix X510 using Hovatek Forum
TWRP . yes i have it. but i dont know which version was. thank you
Posts: 379
Threads: 5
Joined: Oct 2015
Reputation:
2
(21-09-2017, 06:45 PM)Zerety Wrote: TWRP . yes i have it. but i dont know which version was. thank you
Locking the Bootloader while you still had TWRP caused the Bootloop, you shouldn’t have done that.
Download Update.app extractor from http://forum.xda-developers.com/attachme…id=3966156
and follow the instructions in https://forum.xda-developers.com/showthr…?t=2433454
I want to know the contents of the update.app
Sent from my Infinix X510 using Hovatek Forum
In short words, I was rooting phone and had to unlock it, after that I set up wrong TWRP version so I messed it up and did factory reset. I got boot loop so I read few tutorials and tried to relock phone. Now it’s completely hopeless, I get boot loop and error message:
ERROR MODE, Attention! Please update system again
Error!
Func NO: 11 (recovery image)
Func NO: 2 (load failed!)
Do I have any hopes to fix it or that’s it?
08.12.17 07:59:41 pm
dude change your avatar it’s weird
Logic is the most offensive form of argument, because saying «don’t let it get to you» would be encouraging ignorance.
08.12.17 08:27:20 pm
You could at least tell your device model and which exact tutorial you tried to follow.
08.12.17 08:39:56 pm
@
_Yank:
It’s Huawei P9 Lite VNS-L21.
Tutorial (in 3rd or 4th page are instructions for boot loop I followed).
08.12.17 09:39:12 pm
Try to follow what’s being said on the last page
08.12.17 10:14:32 pm
@ _Yank: I can’t run fast boot. It keeps re-looping same ERROR MODE screen.
09.12.17 10:12:05 am
I found a thread about your smartphone and the first thing they mentioned was to NOT DO A FACTORY RESET WITH TWRP.
You messed up twice in a row, congratulations. 
And by the way, a factory reset will not help you remove a
wrong
recovery version. Factory reset only affects the OS. You have not done your homework.
Now I am quite sure you are unsure about the different modes your smartphone has and can boot into. Since you can see a message it surely boots into something, but not into the broken recovery.
4PDA has written:
1) Recovery — contains 3 options
— Reboot
— Factory reset with data reset
— Clear cache
How to enter: Disconnect the PC cable (if connected)!!! To enter recovery when the smartphone is off, press Power + Volume Up — it will vibrate and turn the screen on. Release the buttons now
You can it replace with custom recovery — TWRP — which is GOOD, but to flash (a new ROM) you need to replace it with Stock Recovery which is BAD.
2) eRecovery — contains 3 options
— Reboot
— Load last version and recover (only works on Chinese models)
— Power Off
How to enter: Turn off the smartphone, press Volume Up and connect to PC while Volume Up is pressed. Vibration and a logo will appear — release the key.
With an unlocked bootloader you can (only?) enter from a menu with a warning when booting the phone: when you see a yellow menu hold down Volume Up for at least 3 seconds and then release.
Can be replaced with custom recovery — TWRP — which is GOOD, no need to replace with Stock eRecovery for flashing which is also GOOD.
3) Fastboot
Power off the device, connect to PC while holding down Volume Down.
After you find out what of the above still works you can proceed reading in this direction. Just beware that everything you do incorrectly now could potentially kill your phone. If you don’t have 2-3 different opinions/threads to back you up — don’t do it.
Rooting and reflashing is time consuming not because it takes long to reflash but because you must be 100% certain of what you’re doing and what it will result in. Basically it’s a lot time for reading the same stuff all over again.
PS: I assume fastboot still works and you’ll need adb (Android Device Bridge) with a working Windows driver to flash a new recovery.
4PDA has written:
adb devices // check if device is connected and paired
adb reboot bootloader // boot into fastboot
fastboot oem unlock ХХХХХХХХХХХХХХХХ (bootloader code) // unlock of the bootloader
fastboot flash recovery recovery_twrp_p9lite.img // install TWRP
fastboot flash recovery recovery_stock_p9lite.img // install of stock recovery
fastboot flash boot boot.img // flash boot
fastboot flash cust cust.img // flash cust
fastboot flash system system.img // flash system
fastboot flash recovery RECOVERY.img // flash RECOVERY
fastboot reboot // reboot
10.12.17 07:00:19 pm
VADemon has written:
I found a thread about your smartphone and the first thing they mentioned was to NOT DO A FACTORY RESET WITH TWRP.
You messed up twice in a row, congratulations. And by the way, a factory reset will not help you remove a
wrong
recovery version. Factory reset only affects the OS. You have not done your homework.
Now I am quite sure you are unsure about the different modes your smartphone has and can boot into. Since you can see a message it surely boots into something, but not into the broken recovery.
4PDA has written:
1) Recovery — contains 3 options
— Reboot
— Factory reset with data reset
— Clear cache
How to enter: Disconnect the PC cable (if connected)!!! To enter recovery when the smartphone is off, press Power + Volume Up — it will vibrate and turn the screen on. Release the buttons now
You can it replace with custom recovery — TWRP — which is GOOD, but to flash (a new ROM) you need to replace it with Stock Recovery which is BAD.
2) eRecovery — contains 3 options
— Reboot
— Load last version and recover (only works on Chinese models)
— Power Off
How to enter: Turn off the smartphone, press Volume Up and connect to PC while Volume Up is pressed. Vibration and a logo will appear — release the key.
With an unlocked bootloader you can (only?) enter from a menu with a warning when booting the phone: when you see a yellow menu hold down Volume Up for at least 3 seconds and then release.
Can be replaced with custom recovery — TWRP — which is GOOD, no need to replace with Stock eRecovery for flashing which is also GOOD.
3) Fastboot
Power off the device, connect to PC while holding down Volume Down.
After you find out what of the above still works you can proceed reading in this direction. Just beware that everything you do incorrectly now could potentially kill your phone. If you don’t have 2-3 different opinions/threads to back you up — don’t do it.
Rooting and reflashing is time consuming not because it takes long to reflash but because you must be 100% certain of what you’re doing and what it will result in. Basically it’s a lot time for reading the same stuff all over again.
PS: I assume fastboot still works and you’ll need adb (Android Device Bridge) with a working Windows driver to flash a new recovery.
4PDA has written:
adb devices // check if device is connected and paired
adb reboot bootloader // boot into fastboot
fastboot oem unlock ХХХХХХХХХХХХХХХХ (bootloader code) // unlock of the bootloader
fastboot flash recovery recovery_twrp_p9lite.img // install TWRP
fastboot flash recovery recovery_stock_p9lite.img // install of stock recovery
fastboot flash boot boot.img // flash boot
fastboot flash cust cust.img // flash cust
fastboot flash system system.img // flash system
fastboot flash recovery RECOVERY.img // flash RECOVERY
fastboot reboot // reboot
Thanks for help, though I fixed this yesterday. Should have known about TWRP part, I am a newbie at this, don’t expect too much 