Database Develop

Stuck in ERROR MODE

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

Potential brick help

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

Reflash from TWRP to stock recovery.

Hy guys!
How can I reflash to Stock Recovery from TWRP?
I tried to root my phone and now its bricked (stuck at Android logo)
I want to reflash the stock android but with OST I cant..
In download mode the fastboot is working but the adb not..

szilard0933 said:
Hy guys!
How can I reflash to Stock Recovery from TWRP?
I tried to root my phone and now its bricked (stuck at Android logo)
I want to reflash the stock android but with OST I cant..
In download mode the fastboot is working but the adb not..
Click to expand...
Click to collapse
Get the boot.img correct to the version of security Patch on your phone. Than in download mode check the current slot which is on use by typing :
fastboot getvar current-slot
When you know your slot, type:
fastboot flash boot_yourslot path_to_correct_boot.img
And reboot.

czupyt said:
Get the boot.img correct to the version of security Patch on your phone. Than in download mode check the current slot which is on use by typing :
fastboot getvar current-slot
When you know your slot, type:
fastboot flash boot_yourslot path_to_correct_boot.img
And reboot.
Click to expand...
Click to collapse
current-slot: b
But where can I find the correct boot.img? I tried in google but nothing.. I think I need the october security patch.
And if I download how can I send to phone? (SD card??)

szilard0933 said:
current-slot: b
But where can I find the correct boot.img? I tried in google but nothing.. I think I need the october security patch.
And if I download how can I send to phone? (SD card??)
Click to expand...
Click to collapse
Username @Trissi puted it here: https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
Based on info you provided, download the stock one of October, rename it to boot.img and type in CMD in download mode:
fastboot flash boot_b path on your PC to boot.img
and than reboot. Of course you will loose TWRP (by the way, how can you have TWRP on October Patch) and root, if you have.

czupyt said:
Username @Trissi puted it here:
Based on info you provided, download the stock one of October, rename it to boot.img and type in CMD in download mode:
fastboot flash boot_b path on your PC to boot.img
and than reboot. Of course you will loose TWRP (by the way, how can you have TWRP on October Patch) and root, if you have.
Click to expand...
Click to collapse
Thanks for your help.
I made this now the phone is starting in Download mode. With OST I can flash it now? Beacuse how I read with TWRP Recovery its not possible to flash via OST.

szilard0933 said:
Thanks for your help.
I made this now the phone is starting in Download mode. With OST I can flash it now? Beacuse how I read with TWRP Recovery its not possible to flash via OST.
Click to expand...
Click to collapse
As far as I know, TWRP works only until you are on August Security Patch. If you had TWRP, you had to be maximum on August Patch. Maybe you used wrong boot.img. To use OST I think you have to be unlocked critical, but maybe someone smarter will correct me.

You're right, to use Ost tool u have to unlock critical!

2WildFirE said:
You're right, to use Ost tool u have to unlock critical!
Click to expand...
Click to collapse
FAILED (remote: 'Flashing Unlock is not allowed')
Any ideas?

szilard0933 said:
FAILED (remote: 'Flashing Unlock is not allowed')
Any ideas?
Click to expand...
Click to collapse
Have you tried to switch slot to A?

czupyt said:
Have you tried to switch slot to A?
Click to expand...
Click to collapse
Now I switched to slot A, critical unlocked. With OST I flashed NB1-4390-0-00WW-B01.nb0 successfully but now its stuck on Nokia logo..
I tried to install newer frimware:
NB1-484A-0-00WW-B03.nb0
NB1-488B-0-00WW-B04.nb0
But its stopped on "Checking device status..."
I tried a factory reset in recovery and now its wooooorking
I just try to root it...

szilard0933 said:
Now I switched to slot A, critical unlocked. With OST I flashed NB1-4390-0-00WW-B01.nb0 successfully but now its stuck on Nokia logo..
I tried to install newer frimware:
NB1-484A-0-00WW-B03.nb0
NB1-488B-0-00WW-B04.nb0
But its stopped on "Checking device status..."
I tried a factory reset in recovery and now its wooooorking
I just try to root it...
Click to expand...
Click to collapse
For the future, for OST LA 6.0.4 and Oreo SW (which is NB1-488B-0-00WW-B04.nb0) use the following workaround:
https://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791

czupyt said:
For the future, for OST LA 6.0.4 and Oreo SW (which is NB1-488B-0-00WW-B04.nb0) use the following workaround:
https://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791
Click to expand...
Click to collapse
Thanks GUYS!
Now its working pretty well
And a last question, how can I update the security patches because now I got update failed for 2018-07.
I found this
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
But after downloading update I got install problem..

What failed for you

czupyt said:
What failed for you
Click to expand...
Click to collapse
I tried to install but install failed and after that I didnt had wireless.
I reflashed with OST after that :
fastboot flash boot_a stock_boot_nb01_488_sp04_sep.img
same thing..

szilard0933 said:
I tried to install but install failed and after that I didnt had wireless.
I reflashed with OST after that :
fastboot flash boot_a stock_boot_nb01_488_sp04_sep.img
same thing..
Click to expand...
Click to collapse
There is a little bit chaos in your words. You wrote once that all is fine now, after that you said update had not worked for you, and you showed steps to OTA update with Magisk with A/B partition scheme. After that you said you reflashed with OST, but you entered fastboot flash command. You also mentioned that your critical unlock bootloader status is true.
Could you run phone in download mode and use fastboot getvar all command and paste here the results?

Bricked P20 PRO, please help.

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!

V40 has unlocked bootloader and can fastboot, but is otherwise bricked. Any hope for TWRP?

Having trouble installing TWRP.
I can fastboot and attempt:
`fastboot boot TWRP.img`
But it either fails or "succeeds" and then just hangs on the LG Logo.
`fastboot flash recovery TWRP.img`
-returns an error that recovery_a doesn't exist.
`fastboot flash abl_a TWRP.img`
-returns "Volume is Full"
Any ideas what I may be doing wrong?
Device is an ATT LG V40 with the V35 Engineering Bootloader if that helps.

You don't say if it's at&t pie or Q. Let's assume it's Q 30b?
Follow this link for the bootable partition with twrp already injected. You can either use qfil to flash it, or more easily since u have fastboot, just do fastboot flash boot_a the_name_of_the_file.img.
The only thing about using fastboot is you want to save the original boot_a image first. At&t doesn't make their kdz available and if u want /need to go back to stock u need to save it first.
After flashing it (either way), you need to immediately go to recovery, don't boot the device, u have to format data and reboot to recovery and then flash magisk and no verity zip. Otherwise a backup of your data won't work as it will be encrypted.
just one point, don't every flash something to a partition when yer not sure what yer doing. The abl partition is only about 1 meg in size, it's the 'android boot loader'. You could, if unlucky, flash something wrong for that partition and end up overwriting the partitions that are next to it, and essentially (just about) brick the device.
cheers

AsItLies said:
You don't say if it's at&t pie or Q. Let's assume it's Q 30b?
Click to expand...
Click to collapse
Sorry! It's Pie.
AsItLies said:
Follow this link for the bootable partition with twrp already injected. You can either use qfil to flash it, or more easily since u have fastboot, just do fastboot flash boot_a the_name_of_the_file.img.
Click to expand...
Click to collapse
This gives me the following:
Writing 'abl_a' FAILED (remote: 'Errorflashing partition :Volume Full')
I receive a similar message for `abl_b`, `recovery`, and `boot_a`
If I attempt flashboot boot the_image.img then I can get a success message on the fastboot-side and the phone reboots, but once again just to stick at the LG V40 screen.

sharpienation said:
Sorry! It's Pie.
This gives me the following:
Writing 'abl_a' FAILED (remote: 'Errorflashing partition :Volume Full')
I receive a similar message for `abl_b`, `recovery`, and `boot_a`
If I attempt flashboot boot the_image.img then I can get a success message on the fastboot-side and the phone reboots, but once again just to stick at the LG V40 screen.
Click to expand...
Click to collapse
Wow, so I don't think you understood some things. First, stop trying to flash an image to the wrong partition then what it's for. It is NOT for abl_a, and it is NOT for recovery (there is no recovery partition on a treble phone). STOP DOING THAT.
and second, because that boot_a (ONLY!!!) partition is for Q, as I said, you need one for Pie, and shouldn't even be trying to use it anyway.
and third, you can't fastboot boot these boot/twrp images, they have to be flashed to the partition and then you have to boot to recovery immediately after (don't try to boot the phone).
So if you can't flash the image with fastboot then the only option would be to use qfil, again, be sure to back up the original image first.
I'll look around and see if I can find one for Pie. We may have to create one if it's not around.
cheers

Just checking, but u do know how to use qfil yes? And, how did u get fastboot on the device? Using qfil I'm guessing? and you deleted laf_a? or the engineering abl?
This info is important because 1) the fastboot you get when simply erasing the laf_a is not as powerful and full featured as the engineering abl. The actual capabilities of the (laf_a erased) fastboot varies by OS variant, but some of them are basically worthless.
2) you'll have to be able to use qfil to get this accomplished.
let me know and we'll go from there.