Related
hello guys pretty new to the flashing scene and ive made a mistake. ive tried flashing different twrp.img files and nothing and i mean nothing will make the recovery work, dont have access to the standard recovery either. my model is VTR-L09C440 unlocked bootloader. ive tried every possible solution that i can find and nothing works. Please help thanks
edit
i can flash kernals and recovery imgs via fastboot but still wont load up
apparently my system is 8.0.0.046(0BZC
any help? been here for like 10 hours trying to fix this!
no help i see......
How did you flash twrp ?
fastboot flash recovery_ramdisk yourtwrp.img
Blackball said:
How did you flash twrp ?
fastboot flash recovery_ramdisk yourtwrp.img
Click to expand...
Click to collapse
yeah i think i did it like that but it won't allow me to go in twrp itself by doing the commands volume up. keeps showing
ERROR MODE
ATTENTION!
PLEASE UPDATE SYSTEM AGAIN
ERROR!
FUNC NO:11 {RECOVERY IMAGE}
ERROR NO:2 {LOAD FAILED}
absynteZero said:
Hello Cloud,
arff fianl fantasy 7....arff arfffff so many hours without sleepin...sin is defeated!
it seems you don't flash well the TWRP.
frist you need the good,
https://forum.xda-developers.com/p10/development/recovery-twrp-3-2-1-0-emui-8-0-4-04-2018-t3773449
verify drivers.
verify that files you want to flash are in the fastboot.exe computer folder (the better is system root c
Go to fastboot mode
try
fastboot erase recovery_ramdisk
flash as
fastboot flash recovery_ramdisk nameofTWRPfile.img
and try again.
if you're really bricked, try as
fastboot flash recovery nameofTWRPfile.img
?
after this, if issue persist, maybe try to extract ramdisk.img from official update from Firmware finder with YOUR soft version.
and flash it before flash TWRP as
fastboot erase ramdisk
and
fastboot flash ramdisk RAMDISK.img
take the manufacturers cables not noname , and try to change usb
Click to expand...
Click to collapse
ive had no luck trying that. will give the huawei Multi tool a shot see if that can fix my problem
Solved Successfully flashed the update.app files with dc phoenix app. but it still says im on fromfuture which i dont understsnd considering i flashed a clean
So, I rebranded from C782 to C432 which worked perfectly fine no issues.
Then I decided to unofficially update to EMUI 9 using the method from the following post: https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-how-to-install-emui-9-android-9-t3839316
Whilst looking for a way to downgrade I booted in to TWRP (unofficial) and went to wipe data when my device decided to switch off during the process. Unfortunately I am now no longer able to get past the 'Your device has been unlocked' screen and the 'Your device is booting now' message. I can't get back in to TWRP, unless I flash I official version (which itself only gets me to the TWRP logo page).
Huawei support has told me they want to charge for a repair, and as far I am aware you can't unbrick from Fastboot with FunkyHuawei right?
So am I dealing with a permanent soft-brick for now or is there anything else I can try to restore my device at all?
EDIT: Now fixed. In case anyone has a similar issue, I flashed in fastboot the stock recovery_ramdisk found in the UPDATE.APP I extracted with the Huawei update extractor, then ran fastboot -w to erase userdata and it booted successfully.
MrDanMak said:
So, I rebranded from C782 to C432 which worked perfectly fine no issues.
Then I decided to unofficially update to EMUI 9 using the method from the following post: https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316
Whilst looking for a way to downgrade I booted in to TWRP (unofficial) and went to wipe data when my device decided to switch off during the process. Unfortunately I am now no longer able to get past the 'Your device has been unlocked' screen and the 'Your device is booting now' message. I can't get back in to TWRP, unless I flash I official version (which itself only gets me to the TWRP logo page).
Huawei support has told me they want to charge for a repair, and as far I am aware you can't unbrick from Fastboot with FunkyHuawei right?
So am I dealing with a permanent soft-brick for now or is there anything else I can try to restore my device at all?
Click to expand...
Click to collapse
Have you tried eRecovery?
danifilth4king said:
Have you tried eRecovery?
Click to expand...
Click to collapse
Yeah same issue with 'your device is booting now...'
MrDanMak said:
Yeah same issue with 'your device is booting now...'
Click to expand...
Click to collapse
Hmm that's not good. Maybe you've wiped/flashed over the eRecovery partition (I think it's recovery2, not recovery_ramdisk) try downloading the latest update.zip from firmware finder that matches your model number and unzip, then use Huawei update extractor to extract recovery2.img from UPDATE.APP and try flashing it through fastboot
fastboot flash recovery2 *filename*.img
Then reboot to eRecovery and see if you can recover?
This is just a guess based on what you've told me and may not work. Attempt at your own risk ?
---------- Post added at 06:24 PM ---------- Previous post was at 06:03 PM ----------
MrDanMak said:
So, I rebranded from C782 to C432 which worked perfectly fine no issues.
Then I decided to unofficially update to EMUI 9 using the method from the following post: https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316
Whilst looking for a way to downgrade I booted in to TWRP (unofficial) and went to wipe data when my device decided to switch off during the process. Unfortunately I am now no longer able to get past the 'Your device has been unlocked' screen and the 'Your device is booting now' message. I can't get back in to TWRP, unless I flash I official version (which itself only gets me to the TWRP logo page).
Huawei support has told me they want to charge for a repair, and as far I am aware you can't unbrick from Fastboot with FunkyHuawei right?
So am I dealing with a permanent soft-brick for now or is there anything else I can try to restore my device at all?
EDIT: Now fixed. In case anyone has a similar issue, I flashed in fastboot the stock recovery_ramdisk found in the UPDATE.APP I extracted with the Huawei update extractor, then ran fastboot -w to erase userdata and it booted successfully.
Click to expand...
Click to collapse
Just seen your edit. Glad you got it fixed!
I have you found a solution i have the same issue?
It's the factory reset with twrp to provoque the issue...
I was able the get the same problem. I am just able to get into fastboot mode... Now I am unable to find out which files for emui 8 erecovery are needed -.- If I try to flash erecovery_ramdis.img to recovery2 just get a error which tells me partition length error.
I am mad now xD
Fixed it with just flashing every sinlge .img which I extracted out of the updater.app xD Some errors while flashing occured but it worked xD
Kaffee4Eck said:
Fixed it with just flashing every sinlge .img which I extracted out of the updater.app xD Some errors while flashing occured but it worked xD
Click to expand...
Click to collapse
***
how did you that? im trying but every single img sais something like this
fastboot.exe flash fastboot FASTBOOT.img
Sending 'fastboot' (3351 KB) OKAY [ 0.234s]
Writing 'fastboot' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.344s
Luis2k33-XDA said:
***
how did you that? im trying but every single img sais something like this
fastboot.exe flash fastboot FASTBOOT.img
Sending 'fastboot' (3351 KB) OKAY [ 0.234s]
Writing 'fastboot' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.344s
Click to expand...
Click to collapse
There is no fastboot.img to be flashed.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img
Yes but you said you flashed all the img files from the update.app, is near of 20 or 30, i only can flash, cust.img, kernel.img, recovery ramdisk and system.img but do nothing, still not booting
Kaffee4Eck said:
There is no fastboot.img to be flashed.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img
Click to expand...
Click to collapse
---------- Post added at 11:40 AM ---------- Previous post was at 11:05 AM ----------
I mean what all imgs you had flashed? i flashed cust.img kernel.img recovery_ramdis.img and system.img but didnt boot :/
QUOTE=Kaffee4Eck;78461118]There is no fastboot.img to be flashed.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img[/QUOTE]
download firmware
Where do iget the firmware from?
The downloads
Kaffee4Eck said:
There is no fastboot.img to be flashed.
from firmware finder dont finish downloadin or are corrupted.
fastboot flash recovery_ramdisk fastboot.img (maybe you mean this)
fastboot flash recovery_ramdisk recovery.img
Click to expand...
Click to collapse
So i tried to change the global rom of my red magic 3 to the Chinese rom, i put the Chinese rom zip in the phone and i proceed to update it manually so it can be load, but when it was installing for the first time this error appears "your device is corrupt. it cant be trusted and will not boot", as i sais this error appears since the first time i tried to install it so did not have the opportunity to activate the developer options and check usb debugging and OEM unlock, i can use the bootloader to unlock the phone by using the command "fastboot oem nubia_unlock NUBIA_NX629J" but when i try to flash it by using this command "fastboot flashing unlock" this error appears "FAILED: (remote: flashing Unlock is not allowed)" so im stuck here, what can i do to continue or to go back to factory settings, i hope some one can help me.
im sorry for my bad English
Have you tried changing back to global rom using recovery mode through OTG cable?
kelv55l said:
Have you tried changing back to global rom using recovery mode through OTG cable?
Click to expand...
Click to collapse
i have not tried that, can you linkme how to do it?
Sinuhejrz said:
i have not tried that, can you linkme how to do it?
Click to expand...
Click to collapse
I went to this link https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527
So basically you want to go into fastboot mode either using command "adb reboot bootloader" while plugging the phone into the computer or by holding down the volume down - and power button until it goes into fastboot mode.
Once you are in fastboot mode you go to "reboot to recovery mode" navigate while using the volume buttons and select by using the power button.
Now in recovery mode navigate by using volume buttons and select by using power button again. Its optional, but you can "wipe data" by wiping userdata partition and cache partition. I wiped data when I booted like this. Download the global from here https://global.redmagic.gg/blogs/news/red-magic-3-global-rom-flash-instructions I downloaded the North America version because that was the only version that worked for me. Put the zip file you downloaded into a flash drive USB. then connect the usb to the OTG cable you can buy from ebay, amazon or a nearby tech store. Then connect all that to your phone and click "Choose Update Package" and then click "Choose From OTG Device" then select the rom that you put in the usb drive and then everything should take care of itself from there.
Hope this helps!
kelv55l said:
I went to this link https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527
So basically you want to go into fastboot mode either using command "adb reboot bootloader" while plugging the phone into the computer or by holding down the volume down - and power button until it goes into fastboot mode.
Once you are in fastboot mode you go to "reboot to recovery mode" navigate while using the volume buttons and select by using the power button.
Now in recovery mode navigate by using volume buttons and select by using power button again. Its optional, but you can "wipe data" by wiping userdata partition and cache partition. I wiped data when I booted like this. Download the global from here https://global.redmagic.gg/blogs/news/red-magic-3-global-rom-flash-instructions I downloaded the North America version because that was the only version that worked for me. Put the zip file you downloaded into a flash drive USB. then connect the usb to the OTG cable you can buy from ebay, amazon or a nearby tech store. Then connect all that to your phone and click "Choose Update Package" and then click "Choose From OTG Device" then select the rom that you put in the usb drive and then everything should take care of itself from there.
Hope this helps!
Click to expand...
Click to collapse
i cant go into recovery mode when i select that option the phone restarts and the same message appears "your device is corrupt. it cant be trusted and will not boot" , what can i do?
Sinuhejrz said:
i cant go into recovery mode when i select that option the phone restarts and the same message appears "your device is corrupt. it cant be trusted and will not boot" , what can i do?
Click to expand...
Click to collapse
Damn that happened to me to when I tried rooting my phone. My recovery mode was corrupt too. You can try to use the instructions given on this page https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057/page2. Extract all img and bin files from the Global ROM and place them into the folder where the "cmd-here.exe" is. Also you need "system.img" you can download that here https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm, but dont download the other files they might be the Chinese files.
After you extracted the img and bin files and placed them into the folder where the cmd is placed connect your phone to the computer, open the cmd exe and run the commands
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
After all that you should be able to go into recovery mode through fastboot mode if not then try and flash dtbo.img and vbmeta.img in the line of commands so for example "fastboot flash dtbo dtbo.img" and "fastboot flash vbmeta vbmeta.img" looking something like this...
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash system system.img
fastboot reboot
This was the line of commands I used when my recovery mode was corrupt and somehow worked
I hope this helps and let me know if it worked or if the issue is still there. Also the forum has several posts on this matter and they might have the answer you are looking for as it helped me with this issue. Good Luck!
kelv55l said:
Damn that happened to me to when I tried rooting my phone. My recovery mode was corrupt too. You can try to use the instructions given on this page https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057/page2. Extract all img and bin files from the Global ROM and place them into the folder where the "cmd-here.exe" is. Also you need "system.img" you can download that here https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm, but dont download the other files they might be the Chinese files.
After you extracted the img and bin files and placed them into the folder where the cmd is placed connect your phone to the computer, open the cmd exe and run the commands
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
After all that you should be able to go into recovery mode through fastboot mode if not then try and flash dtbo.img and vbmeta.img in the line of commands so for example "fastboot flash dtbo dtbo.img" and "fastboot flash vbmeta vbmeta.img" looking something like this...
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash system system.img
fastboot reboot
This was the line of commands I used when my recovery mode was corrupt and somehow worked
I hope this helps and let me know if it worked or if the issue is still there. Also the forum has several posts on this matter and they might have the answer you are looking for as it helped me with this issue. Good Luck!
Click to expand...
Click to collapse
OMG OMG OMG it works thank you so much dude you are THE MAN now i have more than an expensive weight-paper, i really appreciate it dude, the second code lines also works for me the only problem i encounter was in this code line "fastboot flash system system.img" throw this message "C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi"
but i keep with the rest of the lines and works perfectly after that.
again thank you so much dude for the help :good::crying:
Sinuhejrz said:
OMG OMG OMG it works thank you so much dude you are THE MAN now i have more than an expensive weight-paper, i really appreciate it dude, the second code lines also works for me the only problem i encounter was in this code line "fastboot flash system system.img" throw this message "C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi"
but i keep with the rest of the lines and works perfectly after that.
again thank you so much dude for the help :good::crying:
Click to expand...
Click to collapse
Awesome! glad I could help you out
kelv55l said:
Awesome! glad I could help you out
Click to expand...
Click to collapse
tnx man i really appreciate it, so could you change the ROM of you phone to the Chinese one?
Sinuhejrz said:
tnx man i really appreciate it, so could you change the ROM of you phone to the Chinese one?
Click to expand...
Click to collapse
Sorry man I haven't tried changing my ROM to Chinese yet. Don't want to risk corrupting my phone again :crying:
But I'll let you know if I decide to change my rom.
Sinuhejrz said:
tnx man i really appreciate it, so could you change the ROM of you phone to the Chinese one?
Click to expand...
Click to collapse
Pretty simple to change the ROM to chinese. Download the chinese ROM, place it in an OTG or the phone's root directory. You can either do it via local update from the system.update feature in settings or use the stock recovery and install it via the OTG. Personally I would.prefer you install it via the OTG.
Please help me !!! I have same problem with my rm3
Sinuhejrz said:
So i tried to change the global rom of my red magic 3 to the Chinese rom, i put the Chinese rom zip in the phone and i proceed to update it manually so it can be load, but when it was installing for the first time this error appears "your device is corrupt. it cant be trusted and will not boot", as i sais this error appears since the first time i tried to install it so did not have the opportunity to activate the developer options and check usb debugging and OEM unlock, i can use the bootloader to unlock the phone by using the command "fastboot oem nubia_unlock NUBIA_NX629J" but when i try to flash it by using this command "fastboot flashing unlock" this error appears "FAILED: (remote: flashing Unlock is not allowed)" so im stuck here, what can i do to continue or to go back to factory settings, i hope some one can help me.
im sorry for my bad English
Click to expand...
Click to collapse
Please help me !!! I have same problem with my rm3 :crying::crying::crying: PLEASE
---------- Post added at 09:57 PM ---------- Previous post was at 09:49 PM ----------
kelv55l said:
Awesome! glad I could help you out
Click to expand...
Click to collapse
PLEASE HELP ME Bro !!! I have same problem :crying::crying::crying:
hanif9067 said:
Please help me !!! I have same problem with my rm3 :crying::crying::crying: PLEASE
---------- Post added at 09:57 PM ---------- Previous post was at 09:49 PM ----------
PLEASE HELP ME Bro !!! I have same problem :crying::crying::crying:
Click to expand...
Click to collapse
Give me your address, I'll come to your house to fix the phone!
hanif9067 said:
Please help me !!! I have same problem with my rm3 :crying::crying::crying: PLEASE
---------- Post added at 09:57 PM ---------- Previous post was at 09:49 PM ----------
PLEASE HELP ME Bro !!! I have same problem :crying::crying::crying:
Click to expand...
Click to collapse
What seems to be the problem are you able to go into recovery mode?
If not then flashing the appropriate img and bin files should allow you to go back to recovery mode as explained on previous posts on this thread.
kelv55l said:
What seems to be the problem are you able to go into recovery mode?
If not then flashing the appropriate img and bin files should allow you to go back to recovery mode as explained on previous posts on this thread.
Click to expand...
Click to collapse
Mine has the same problem and tried all the steps in this thread. Not able to go into recovery mode, can go into fastboot mode and flash everything but phone is still corrupt and can not boot. New phone now no good, OH well
re-flashed the phone using the first version of the Chinese ROM v2.12 now can use the OTG update option. just need to get a usb adapter now
I'm hoping someone can help me. I've followed the fix on earlier pages and used the files including system.img a user uploaded.
Now when booting my phone I get a device is corrupt and cannot be trusted message. I read somewhere else that the command 'Fastboot flashing unlock' may solve this but I get an error message.
Would really appreciate some help, maybe I've done something wrong but I've followed the instructions and used the files an xda user uploaded.
Many thanks.
Johnnio said:
I'm hoping someone can help me. I've followed the fix on earlier pages and used the files including system.img a user uploaded.
Now when booting my phone I get a device is corrupt and cannot be trusted message. I read somewhere else that the command 'Fastboot flashing unlock' may solve this but I get an error message.
Would really appreciate some help, maybe I've done something wrong but I've followed the instructions and used the files an xda user uploaded.
Many thanks.
Click to expand...
Click to collapse
Have you tried to erase and then reflash again?
try something like this according from this user
em90256 said:
try this
fastboot -w
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
try your stock recovery image
Click to expand...
Click to collapse
leipnacht said:
Have you tried to erase and then reflash again?
try something like this according from this user
Click to expand...
Click to collapse
Thanks but I managed to fix it yesterday, I had to flash the system image using 'fastboot flash -S 100M system system.img', turns out that although it reported flash as successful it wasn't actually sent correctly unless split into smaller chunks.
Johnnio said:
Thanks but I managed to fix it yesterday, I had to flash the system image using 'fastboot flash -S 100M system system.img', turns out that although it reported flash as successful it wasn't actually sent correctly unless split into smaller chunks.
Click to expand...
Click to collapse
Oh new information. What does "-S 100M" on fastboot command do?
I tried to flash anyone recovery by fastboot with the command fastboot flash recovery recovery.img but the result Is "image not signed and CORRUPT". help me.
copeye said:
I tried to flash anyone recovery by fastboot with the command fastboot flash recovery recovery.img but the result Is "image not signed and CORRUPT". help me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g5s-plus/help/solution-to-lock-oem-moto-g5s-plus-t4065619
copeye said:
I tried to flash anyone recovery by fastboot with the command fastboot flash recovery recovery.img but the result Is "image not signed and CORRUPT". help me.
Click to expand...
Click to collapse
Use latest twrp
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