Related
My P20Pro was booting into the error mode and was able to booting into the fastboot mode, failed into recovery/erecovery.
So I'd like to flash the stock recovery/erecovery back. I had flashed RECOVERY_RAMDIS.img/RECOVERY_VBMETA.img/RECOVERY_VENDOR.img successfully via below commands,
fastboot flash recovery_ramdisk x:\RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta x:\RECOVERY_VBMETA.img
fastboot flash recovery_vendor x:\VENDOR.img
But I had no idea what're the partition names of ERECOVERY_KERNE.img/ERECOVERY_RAMDI.img/ERECOVERY_VBMET.img/ERECOVERY_VENDO.img. Got the error message "Writing erecovery_ramdisk' FAILED (remote: partition length get error)".
Does anyone know the partition names?
Found something interesting, ERECOVERY_RAMDI.img and RECOVERY_RAMDIS.img have the same hash value, same as ERECOVERY_KERNE.img and KERNEL.img, ERECOVERY_VENDO.img and RECOVERY_VENDOR.img. Are they the same file?
Did you have luck with that? If so, could you help me with something?
+
castiwo said:
Did you have luck with that? If so, could you help me with something?
Click to expand...
Click to collapse
Me too
Why don't you guys post your question in the main page, some people in this forum are very helpful
So you can't boot to erecovery to download the stock rom?
Did you succeed?
Hello everyone since 2 days i'm looking for a good solution to fix my rom problem
First i've unlocked the bootloader and rooted my phone with a custom rom for now exellent !
But some things doesn't work after that like the developper mode or the uninstall of apps so
i decided to flash a rom stock to come back like before and my bad i downloaded wrong roms
and now my phone is in bootloop
SO now my phone can boot in fastboot mode but only that ! the erecovery is working but can't do anything
exept reboot and shut down
And when i try to flash an other recovery.img from or boot.img from the update app extract only this happend :
FAILED (remote: partition length get error) and i can try different size of files to inject but allways the same i tryed many roms and allways the same :crying:
flashing of boot and recovery (in fastboot&rescue mode) : prntscr.com/k7ebuq
btw: i'm using SRK tool for huawei i think this is one of the most usefull program to flash recoverys etc...
And why i try to flash the system.img it works perfect :silly:
btw i cant remember the number of my stock rom i only know that is a huawei p8 lite 2017 PRA-LX1 and i found my rom list here
pro-teammt.ru/firmware-database/?firmware_model=PRA-LX1&firmware_page=0
So if you need more informations tell me i'm allways here to wath the thread (and btw i'm a newbie on flashing roms and i'm french so sorry for mistakes) and help me please after 2 days of try's now i give up you are probably better than me
UPDATE !!!
FIXED PLEASE READ MY RESPONSE
RedFiredu29 said:
Hello everyone since 2 days i'm looking for a good solution to fix my rom problem
First i've unlocked the bootloader and rooted my phone with a custom rom for now exellent !
But some things doesn't work after that like the developper mode or the uninstall of apps so
i decided to flash a rom stock to come back like before and my bad i downloaded wrong roms
and now my phone is in bootloop
SO now my phone can boot in fastboot mode but only that ! the erecovery is working but can't do anything
exept reboot and shut down
And when i try to flash an other recovery.img from or boot.img from the update app extract only this happend :
FAILED (remote: partition length get error) and i can try different size of files to inject but allways the same i tryed many roms and allways the same :crying:
flashing of boot and recovery (in fastboot&rescue mode) : prntscr.com/k7ebuq
btw: i'm using SRK tool for huawei i think this is one of the most usefull program to flash recoverys etc...
And why i try to flash the system.img it works perfect :silly:
btw i cant remember the number of my stock rom i only know that is a huawei p8 lite 2017 PRA-LX1 and i found my rom list here
pro-teammt.ru/firmware-database/?firmware_model=PRA-LX1&firmware_page=0
So if you need more informations tell me i'm allways here to wath the thread (and btw i'm a newbie on flashing roms and i'm french so sorry for mistakes) and help me please after 2 days of try's now i give up you are probably better than me
Click to expand...
Click to collapse
Do you have single or dual sim device? The custom rom you mentioned was Oreo?
---------- Post added at 04:18 PM ---------- Previous post was at 03:59 PM ----------
You need microSD card. Copy these files to microSD, make new folder "Oreo" and put all 4 zip files inside.
-Download update.zip.
-Download update_data_full_public.zip (rename to ''update_data_public'').
If you have single sim device, then
-Download update_full_PRA-L11_hw_eu.zip (rename to ''update_all_hw'').
If you have dual sim device, then
-Download update_full_PRA-L31_hw_eu.zip (rename to ''update_all_hw'').
-Download HuRUpdater
-Download Oreo version of TWRP
Boot in fastboot mode.
Run this command to flash TWRP
fastboot flash recovery_ramdisk recovery_1105.img
Reboot with fastboot reboot
Boot now into TWRP, click install, select microSD, select to flash ONLY HuRUpdater.zip.
Reboot.
Yes man i did it pretty well !so for the peoples who got the same problem than me and got stuck
on the fastboot&rescue mode when VOLUME- + POWER for like 5 seconds with the phone off
(for the peoples who can't power off your device you can download the "universal fastboot and ADB tool" app and then click on reboot phone in the fastboot part)
the solution is to :
-Download the rom stock Oreo android 8.0 stechguide.com/huawei-p8-lite-2017-b370-oreo-firmware/
-exctract all files from the HuaweiUpdateExtractor find it on google it's easy just download update.zip
-extract and put the UPDATE.APP in the HuaweiUpdateExtractor
-run srk tool for huawei
-type 000 and press enter
-and now you have to flash all partitions that you have received from HUE commands are here:
[dont worry if some of theese are not working it's because certains commands are not allowed to use and certains commands are out of date :/ but dont worry the phone will boot correctly after ]
Code:
fastboot flash cache CACHE.img
fastboot flash crc CRC.img
fastboot flash curver CURVER.img
fastboot flash dts DTS.img
fastboot flash efi EFI.img
(i'm not putting erecorery imgs cause we cannot touch them it's an ultimate security from os :) )
fastboot flash fastboot FASTBOOT.img
fastboot flash hifi HIFI.img (only if you are the wifi is not working ;) )
fastboot flash kernel KERNEL.img
fastboot flash modem_fw MODEM_FW.img
fastboot flash modemnvm_update MODEMNVM_UPDATE.img
fastboot flash odm ODM.img
fastboot flash package_type PACKAGE_TYPE.img
fastboot flash product PRODUCT.img
fastboot flash ramdisk RAMDISK.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 system SYSTEM.img
fastboot flash teeos TEEOS.img
fastboot flash trustfirmware TRUSTFIRMWARE.img
fastboot flash vbmeta VBMETA.img
fastboot flash vendor VENDOR.img
fastboot flash verlist VERLIST.img
fastboot flash xloader XLOADER.img
Now you have loader all partitions of an huawei p8 lite 2017 android 8.0 gg !
you just have to make a fastboot reboot to reboot your phone and enjoy !
notes:Everything is working properly after 3 day of use not any missing data some calls bugs but nothing hard
you will loose your TWRP recovery mode AND DO NOT INSTALL ONE OF THEM FOR NOW they are outdated for oreo wait some months (september on some sources)
you will loose all your data and the root (some sites prupose root methods for oreo p8 lite 2017 (and soft root this time :laugh:
idk about the bootloader but i keeped my imei number ^^
Thanks for your time and if anyone got questions i'm still here ^^
RedFiredu29 and vive la france WE ARE CHAMPIONS !
btw that was my first tutorial tell me if it's good ^^
RedFiredu29 said:
Yes man i did it pretty well !so for the peoples who got the same problem than me and got stuck
on the fastboot&rescue mode when VOLUME- + POWER for like 5 seconds with the phone off
(for the peoples who can't power off your device you can download the "universal fastboot and ADB tool" app and then click on reboot phone in the fastboot part)
the solution is to :
-Download the rom stock Oreo android 8.0 stechguide.com/huawei-p8-lite-2017-b370-oreo-firmware/
-exctract all files from the HuaweiUpdateExtractor find it on google it's easy just download update.zip
-extract and put the UPDATE.APP in the HuaweiUpdateExtractor
-run srk tool for huawei
-type 000 and press enter
-and now you have to flash all partitions that you have received from HUE commands are here:
[dont worry if some of theese are not working it's because certains commands are not allowed to use and certains commands are out of date :/ but dont worry the phone will boot correctly after ]
Code:
fastboot flash cache CACHE.img
fastboot flash crc CRC.img
fastboot flash curver CURVER.img
fastboot flash dts DTS.img
fastboot flash efi EFI.img
(i'm not putting erecorery imgs cause we cannot touch them it's an ultimate security from os :) )
fastboot flash fastboot FASTBOOT.img
fastboot flash hifi HIFI.img (only if you are the wifi is not working ;) )
fastboot flash kernel KERNEL.img
fastboot flash modem_fw MODEM_FW.img
fastboot flash modemnvm_update MODEMNVM_UPDATE.img
fastboot flash odm ODM.img
fastboot flash package_type PACKAGE_TYPE.img
fastboot flash product PRODUCT.img
fastboot flash ramdisk RAMDISK.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 system SYSTEM.img
fastboot flash teeos TEEOS.img
fastboot flash trustfirmware TRUSTFIRMWARE.img
fastboot flash vbmeta VBMETA.img
fastboot flash vendor VENDOR.img
fastboot flash verlist VERLIST.img
fastboot flash xloader XLOADER.img
Now you have loader all partitions of an huawei p8 lite 2017 android 8.0 gg !
you just have to make a fastboot reboot to reboot your phone and enjoy !
notes:Everything is working properly after 3 day of use not any missing data some calls bugs but nothing hard
you will loose your TWRP recovery mode AND DO NOT INSTALL ONE OF THEM FOR NOW they are outdated for oreo wait some months (september on some sources)
you will loose all your data and the root (some sites prupose root methods for oreo p8 lite 2017 (and soft root this time :laugh:
idk about the bootloader but i keeped my imei number ^^
Thanks for your time and if anyone got questions i'm still here ^^
RedFiredu29 and vive la france WE ARE CHAMPIONS !
btw that was my first tutorial tell me if it's good ^^
Click to expand...
Click to collapse
Hello, what if I accidentally wiped eRecovery partition with TWRP? I swear i had the phone in my pocket and fml i saw it wiped right in that partition :V
Chueven said:
Hello, what if I accidentally wiped eRecovery partition with TWRP? I swear i had the phone in my pocket and fml i saw it wiped right in that partition :V
Click to expand...
Click to collapse
I saw you have to let the phone shutdown itself ( battery to 0 ) and then plug it to charger or PC and the recovery will return, don't know if it will work for you but just my 2 cents.
I had the same problem after replacing the recogery with *fastboot flash recovery2 recovery.img* but my phone booted to android out of the blue so I didn't use that command, yet.
I myself accidentally installed another TWRP.img to my recovery_ramdisk partition. Although my phone boots up and I can use it, I can't boot into my recovery anymore. It just stays at the "Your device has been unlocked" screen.
Fixes?
I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好，我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img（adb >> fastboot flash system system.img中的命令）
2. boot.img（adb 中的命令，如#1，更改 img 文件的名称）直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img（选择twrp与你要安装的rom兼容）
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b
I was upgrading to EMUI 9.1 and relocking bootloader, but ended up with botloop ony my P20 Pro.
Fastboot - working.
Bootloader - unlocked.
FRP - not visible (was unlocked).
Erecovery - "Getting package info failed."
HiSuite 9.1.0.305 - "System recovery isn't available on this device."
TWRP flashing - can't enter it after fastboot reboot.
Code:
fastboot oem get-build-number
(bootloader) :CLT-L09 8.1.0.164(EEAC782)
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :CLT-L09 9.0.0.195(C432E5R1P9)
I was trying to use Huawei Update Extractor with 8.1.0.164(EEAC782), 9.0.0.195(C432E5R1P9), CLT-LGRP2-OVS 9.1.0.325 as following:
Code:
fastboot flash cache cache.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
Sadly it didn't brought any result.
Please help me with resolving this issue.
Did you try with the dload method?
aka.petteri said:
Did you try with the dload method?
Click to expand...
Click to collapse
Dload was my thought, but i didn't got OTG cable yet.
aka.petteri said:
Did you try with the dload method?
Click to expand...
Click to collapse
I tried dload method.
With 8.1.0.164, 9.0.0.195, 9.1.0.325 i'm getting "Software install failed".
I managed to boot too TWRP.
I had to patch it from fastboot, then boot to recovery with VolUP, then make wipe and hold still VolUp.
Seems like EMUI patched, so P20 is back!
Cinceres1989 said:
I managed to boot too TWRP.
I had to patch it from fastboot, then boot to recovery with VolUP, then make wipe and hold still VolUp.
Seems like EMUI patched, so P20 is back!
Click to expand...
Click to collapse
Hi,
How did you manage it to bring it back?
I have the same issue, in fastboot I see my phone, but can't get into bootloader nor erecovery..
Everything unlocked, but I have a black screen!
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