Database Develop

[Q] Troubleshooting, Hard Bricked?

I did a full wipe on TWRP (EVERYTHING), and now I have no OS. My phone will only reboot into the HTC logo and I can't even get into the bootloader now, or turn the screen off. It just stays on the HTC logo. When I hold volume down and power, the buttons blink, but nothing else happens.

arattan said:
I did a full wipe on TWRP (EVERYTHING), and now I have no OS. My phone will only reboot into the HTC logo and I can't even get into the bootloader now, or turn the screen off. It just stays on the HTC logo. When I hold volume down and power, the buttons blink, but nothing else happens.
Click to expand...
Click to collapse
Try keeping the power button pressed for about 10-15 seconds till the phone completely shuts off. Then try going to bootloader?
Or does your phone reboot even if the power button is pressed for a while??

arattan said:
I did a full wipe on TWRP (EVERYTHING), and now I have no OS. My phone will only reboot into the HTC logo and I can't even get into the bootloader now, or turn the screen off. It just stays on the HTC logo. When I hold volume down and power, the buttons blink, but nothing else happens.
Click to expand...
Click to collapse
answered so many times, i'll just copy/paste
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
^^ choose whatever ROM you like
.

Honor 9 Lite "my test with other devices developer-ROMs"

@VigneshS007
test system-arm64-ab.img
boot to custom-recovery
wipe cache (formatting cache .. down)
wipe data/factory reset / confirm yes / confirm yes - format 0..100%
vol-up and power and usb-wire in phone and pc : boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 1.547s
usb-wire out phone / return in phone
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 14.497s]
writing 'system'...
OKAY [ 3.356s]
sending sparse 'system' (421628 KB)...
OKAY [ 13.025s]
writing 'system'...
OKAY [ 2.928s]
sending sparse 'system' (388444 KB)...
OKAY [ 11.666s]
writing 'system'...
OKAY [ 2.704s]
finished. total time: 48.177s
now is in phone custom-recovery, data fresh formated, system-arm64-ab.img
usb-wire is in phone
fastboot reboot
phone boot... / black screen / <- 3x / Huawei eRecovery "Factory data reset(recommended)" yes(do it)
low-level format 0..5% / reset failed! / reboot system now
phone boot 2x and go to Huawei eRecovery (this flash dont work / shutdown)
vol-down press and hold, usb-wire put in phone, phone boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 14.281s]
writing 'system'...
OKAY [ 3.511s]
sending sparse 'system' (421628 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 21.386s
usb-wire out phone
usb-wire in phone
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 14.359s]
writing 'system'...
OKAY [ 3.235s]
sending sparse 'system' (421628 KB)...
OKAY [ 12.947s]
writing 'system'...
OKAY [ 2.931s]
sending sparse 'system' (388444 KB)...
OKAY [ 11.664s]
writing 'system'...
OKAY [ 2.710s]
finished. total time: 47.846s
fastboot reboot and fast usb-wire out phone
You device is booting now... /black screen <- 2x /Huawei eRecovery /THIS way not work!!!
vol-down press and hold, usb-wire put in phone, phone boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (458906 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 14.487s
usb-wire out phone
vol-up press and hold and power /boot to eRecovery/ factory reset
phone off
vol-down press and hold, usb-wire put in phone, phone boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system.img
phone off
power
phone boot to factoryOS !!! this is the best: my phone work, no bootloop or other error
i think, the problem is "i am" or the instructions or "what else"
i think, if i do factory-reset the phone low-level format "data" and set inside instructions "test by next boot what system.img is installed" or other test
this test i now 5x do and the way is by all the same.
anyone info i missing to get out of this loop
i hope very powerful: anyone developer write twrp and system(LOS or RR) for this phone !
at the moment i could nail it to the wall / i am very frustrated / a little bit
excuse me for long writing text, i hope the mistake is easier to find

Flash this https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688 ARM 64 A only device @JamesBott

now, lets go, next test :good:
download run... finish
test system-arm64-aonly.img
fastboot devices (phone is online!)
fastboot flash system system-arm64-aonly.img
fastboot reboot
the rest is "the same procedure as test bevor"
this phone (my H9L) not boot in other system.img
by now in nothing else
the problem must inside my phone
or other question : have anyone other system.img in H9L and this work ? H9L with LLD-L31 ? not from india or ..., from EU (European Union)
what is different in my phone than other users ? i don't know it
now is custemOS inside again. different to last rom-install: SU is now outside! only different what i see

For everyone who is interested: I have build my first treble build based on pure AOSP 8.0... As my 6X didn't received EMUI 8.0 already I would be glad if some Honor 9 Lite or P Smart user could try to install and run my build on his device as it is based on P Smart blobs: Install it like a normal treble build. Extract the zip (it isnt flashable zip !), unlock BL, flash system.img via fastboot - boot to stock recovery and perform a factory reset - reboot... if booted up report back and provide some screenshots! Here is DL: https://www.androidfilehost.com/?fid=962187416754471220

JamesBott said:
now, lets go, next test :good:
download run... finish
test system-arm64-aonly.img
fastboot devices (phone is online!)
fastboot flash system system-arm64-aonly.img
fastboot reboot
the rest is "the same procedure as test bevor"
this phone (my H9L) not boot in other system.img
by now in nothing else
the problem must inside my phone
or other question : have anyone other system.img in H9L and this work ? H9L with LLD-L31 ? not from india or ..., from EU (European Union)
what is different in my phone than other users ? i don't know it
now is custemOS inside again. different to last rom-install: SU is now outside! only different what i see
Click to expand...
Click to collapse
Firstly... Honor 9 lite dont have a/b partition so you have to take the a-Partition images...
Secondly... V9 of the treble image would work (its on android 8.0)...

Hi @felix-development,
that what i reed - sounds very interesting. my next test is your download.
question : have you "twrp full function" ?
i mean twrp backup/restore "system, data..." ?
my twrp do backup/restore system "yes" data "no" (de- en-cryption ?)

JamesBott said:
Hi @felix-development,
that what i reed - sounds very interesting. my next test is your download.
question : have you "twrp full function" ?
i mean twrp backup/restore "system, data..." ?
my twrp do backup/restore system "yes" data "no" (de- en-cryption ?)
Click to expand...
Click to collapse
you should be on normal emui 8 with just bl unlocked... flash system.img via fastboot - and after that do a factory reset in erecovery (if didn't do by unlocking bl already)
Gesendet von meinem BLN-L21 mit Tapatalk
---------- Post added at 09:35 AM ---------- Previous post was at 09:33 AM ----------
JamesBott said:
Hi @felix-development,
that what i reed - sounds very interesting. my next test is your download.
question : have you "twrp full function" ?
i mean twrp backup/restore "system, data..." ?
my twrp do backup/restore system "yes" data "no" (de- en-cryption ?)
Click to expand...
Click to collapse
by the way you are free to pm me as i saw we speak the same lanuage
Gesendet von meinem BLN-L21 mit Tapatalk

Hi @felix-development,
ALL Test's ending in eRecovery, "Download latest version and recovery / Reboot / Shutdown"
That's no problem, i flash stock and all good! Phone work with stock It's only work.
Procedure:
flash other system; reboot; (phone boot / black screen) 3x / eRecovery "reset data" .... low-level-format 0..100% / reboot / (phone boot / black screen) 3x / eRecovery, "Download latest...
i think, the problem sit on the frontside from phone
any idea, what i doing false ?
or is in this moment fact: no other rom work on H9L ?
last step: flash system system.img (stock) phone boot "normal" and work !
My daily driver is my old elephon p8 mini.
Honor 9 Lite sleep and wait for next test

JamesBott said:
Hi @felix-development,
ALL Test's ending in eRecovery, "Download latest version and recovery / Reboot / Shutdown"
That's no problem, i flash stock and all good! Phone work with stock It's only work.
Procedure:
flash other system; reboot; (phone boot / black screen) 3x / eRecovery "reset data" .... low-level-format 0..100% / reboot / (phone boot / black screen) 3x / eRecovery, "Download latest...
i think, the problem sit on the frontside from phone
any idea, what i doing false ?
or is in this moment fact: no other rom work on H9L ?
last step: flash system system.img (stock) phone boot "normal" and work !
My daily driver is my old elephon p8 mini.
Honor 9 Lite sleep and wait for next test
Click to expand...
Click to collapse
A logcat could help to fix or to see wheres the problem...

@Darkest-Dark
logcat is a good word: how & who i find on end test (stand in eRecovery) the logcat ?
or if i reflash stock: if logcat from last test available ( how & who) ?
i can all do what hav to do with system and recovery. that's no risk. reflash system and/or recovery and stock work!

@Darkest-Dark
logcat is a good word: how & who i find on end test (stand in eRecovery) the logcat ?
or if i reflash stock: if logcat from last test available ( how & who) ?
i can all do what hav to do with system and recovery. that's no risk. reflash system and/or recovery and stock work!

JamesBott said:
@Darkest-Dark
logcat is a good word: how & who i find on end test (stand in eRecovery) the logcat ?
or if i reflash stock: if logcat from last test available ( how & who) ?
i can all do what hav to do with system and recovery. that's no risk. reflash system and/or recovery and stock work!
Click to expand...
Click to collapse
Look here...
https://forum.xda-developers.com/showthread.php?t=2303834

i found
Now type this in the terminal
Code:
adb logcat -v long > logcat.txt
or
Code:
adb logcat > logcat.txt
you shall have a log file called name of logcat.txt inside your ADB folder.
i test next day !
if this work we have backup from stock without twrp, simple & good
i write my experiences after test !

Hi, TWRP now available. Look https://forum.xda-developers.com/9-lite/development/honor-9-lite-twrp-3-2-1-0-available-t3771358
From now Backup/Restore NO problem

principle question & understand question
all test's NOT work.
last test made with twrp : twrp/install system.img, twrp flash this image with no errors.
now reboot to system : twrp write "no OS is installed .."
i mean, the problem is the differences from Android 7 and 8
i mean : in Android 8 is boot-sequence other as in Android 7
why : i have updated one+ 3T and Sony Z 2, inside LOS 14.1, updated to LOS 15.1, this 2 phones work no with OREO.
i mean, this updates for Android 7 core and i need now LOS 15.1 for installing on Android 8 core.
my knowledge : i am wait on LOS 15.1, written for OREO-Core.
the first version H9L came with factory-Android 7, all LOS 14.1 (RR ...) work on this
my phone is from February 2018 and have factory-OREO on board
with OREO begin a new era
essence : i am to fast with this phone and OREO wait on developer's
but - the factory-OREO work good enough for me (with root) - only : i am LOS-fan since many year :angel:

i am test https://forum.xda-developers.com/9-lite/development/kangvip-rom-emui-8-0-t3775904
for first oreo-developer-rom work good. it is stock-rom with modified menu ( menu / advanced settings).

How to flash ALE-L21 ( P8 lite) from fastboot mode

I can not enter a normal download mode ( to reflash) the P8 lite. So the only way now( I think ) is to use a fastboot mode ( That is the only that works. now) But fastboot &rescue mode screen says PHONE LOCKED.
I already use a minimal ADB and fastboot application but do not know what to do next
Can anyone give me a clue how to continue?
Thanks

Written using Google Translate.
Is it not possible to install the original version of the Huawei software from the microSD memory card using the dload folder and a combination of three buttons?
All information contained in the phone will be lost!
Wysłane z Mi A1

I do not know how to flash files there. The combination of three buttons does not work only fastboot mode but when I try to flash an image I will get the following error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (22672 KB)...
OKAY [ 0.742s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.772s
Does it mean the Phone is locked? Or a developer mode not enabled?

Jane11 said:
I do not know how to flash files there. The combination of three buttons does not work only fastboot mode but when I try to flash an image I will get the following error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (22672 KB)...
OKAY [ 0.742s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.772s
Does it mean the Phone is locked? Or a developer mode not enabled?
Click to expand...
Click to collapse
Enter fastboot mode and try to use Hi suite, hope it helps.
The 3 button combo, try to press all of them, when phone boots release power button but continue pressing volume one's.
Also don't forget to have the firmware update.app in dload folder on the root of sdcard.

Icone24 said:
Enter fastboot mode and try to use Hi suite, hope it helps.
The 3 button combo, try to press all of them, when phone boots release power button but continue pressing volume one's.
Also don't forget to have the firmware update.app in dload folder on the root of sdcard.
Click to expand...
Click to collapse
HiSuite says that Device is not connected even though the mobile is in fastboot mode and command fastboot devices lists the mobile as connected.
What now? Thanks

Jane11 said:
HiSuite says that Device is not connected even though the mobile is in fastboot mode and command fastboot devices lists the mobile as connected.
What now? Thanks
Click to expand...
Click to collapse
Try the combo way like i wrote. If it doesn't work i don't know how to help you.

Unable to Flash Recovery (Tried TWRP and Orangefox)

It would seem that for me Flashing the TWRP Recovery (or any other, tried Orangefox too) doesn't work. I would really appreciate some input on this.
Here's some info:
- Redmi 4
- MIUI 10.2 | Stable // 10.2.2.0(MBECNXM)
- Android version 6.0.1
- Android Security Patch level 2018-04-01
- Unlocked the Phone (Successfully)
- Booted into fastboot
- used "fastboot flash recovery <filename>.img" to flash the twrp image (also tried older versions of the twrp image; also tried the orange fox recovery image)
It gives me the following output:
Code:
C:\Minimal ADB and Fastboot> fastboot flash recovery twrp.img
Sending 'recovery' (36040 KB) OKAY [ 1.002s]
Writing 'recovery' OKAY [ 0.977s]
Finished. Total time: 2.046s
- I proceed to use "fastboot boot twrp.img"
It gives me the following output:
Code:
C:\Minimal ADB and Fastboot> fastboot boot twrp.img
Sending 'boot.img' (36040 KB) OKAY [ 1.001s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
Now unto the errors / things I've tried:
- If I try to just use "fastboot reboot" -> it proceeds to eternally get stuck on the "mi.com" loading screen
- If I try to use the "standard" power off > Power + Vol Up -> The phone boots into the Chinese interface which is not TWRP (yellow big buttons, bottom button is blue) -> I change the language to english, hit "Recovery" and it yet again either stays stuck or boots into Mi 3.0 Recovery
I have tried all TWRP Santoni versions currently officially available on the official TWRP site.
All give me the same error if I try to boot the recovery direclty through fastboot as seen above: "(remote: dtb not found)"
can anyone please help me with this?

Flash latest stock ROM with fastboot first without re locking bootloader, boot into it, and then flash twrp 3.2.3-1 official from fastboot again, and then disconnect the phone and reboot into recovery with vol up + down + power button and ensure that you have downloaded lazyflasher into your phone storage, and after booting twrp, flash lazyflasher, clear cache and reboot system. Done!

[HELP FİNDİNG TWRP]P SMART FİG-LX1 C432

I am trying to install lineageos for 2 days now twrp keeps giving error would anyone could send me hak86's twrp image I couldnt find on telegram sourceforge and github thanks and it is now stuck on formatting data

there is (now) a functioning link in the "main" topic forum:
see https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985
@haky 86 : thnx for that

Bokkahontas said:
there is (now) a functioning link in the "main" topic forum:
see https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985
@haky 86 : thnx for that
Click to expand...
Click to collapse
I can remake it, but I need some testers as I don't have the device right now.

@haky 86 : that would be nice, since installing the twrp failed:
$ fastboot flash recovery twrp-3.4.0.0-v1-figo-haky86.img
> Sending 'recovery' (10734 KB) OKAY [ 0.382s]
> Writing 'recovery' FAILED (remote: 'partition length get error')
> fastboot: error: Command failed
device is properly connected, I also doublechecked that bootloader is still unlocked after upgrade from emui 8 to 9.1 (Build is 9.1.0.216(C432E22R1P5))
Can we merge this topic with the following, so there is no parallel discussion in two different topics within the forum?! ;-)
=> https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985

switch recovery with recovery_ramdisk

twrp installation succeded with _ramdisk, thanks for the fast reply!
I followed then instructions from official lineage 16 wiki (https://wiki.lineageos.org/devices/figo/install) to install lineageOS 16. Sideload of the actual zip (lineage-16.0-20210115-nightly-figo-signed) in twrp also worked perfectly and I eagerly tipped on "reboot" in twrp hoping to see my new OS booting for the the first time... BUT:
Unfortunately I got stuck at a probably similar point as Capybar (see https://forum.xda-developers.com/t/...k-recovery-and-cant-boot-into-system.4126357/):
Phone stopped being able to enter any recovery at all. The system itself does not boot. The HUawei start screen "Your device has been unlocked and cannot be trustet (...) only tells me (...) "Your device is booting now...", the recovery option never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now").
Then it shows me the Teamwin Logo and at that point freezes.
I cannot acces the phone with adb oder fastboot from host machine..
=> Does anybody knows if there is a possibility to gain acces to recovery?

if stuck on Huawei splash screen, just run factory reset with stock recovery.
to boot into recovery on this crap;
* Keep pressing on vol up + vol down + power.
* Leave vol down button only and keep pressing other 2 buttons once huawei splash screen appears .
* you should able to boot into recovery.

thnx again haky !!!
Nevertheless feeling stupid now (or rather like my mum when I first modified our home-PC autoexec.bat on a 386DX machine in MS DOS to make the PC wish her a good morning on the VGA display) .Back to topic:
I managed to get the the phone start in recovery boot mode asking me
(1) Press Power key to continue
(2) Press Volume Uo key (...) to enter erecovery to restore aour device
(3) Vour device will continue to booot (...)
=> all options result in the same(?) everlasting bootloop
so I succesfully tried fastboot boot mode (error 64 message on screen) and flashed your stock recovery:
$ fastboot devices -l
> XEDDU*********** fastboot usb:2-2
$ fastboot flash recovery_ramdisk 9.1_stock_rec.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.156s]
writing 'recovery_ramdisk'...
OKAY [ 0.269s]
finished. total time: 1.425s
Rebooting phone again leads to bootloop
Edit: Not the very same bootloop since twrp-logo does not appear anymore but phone message is "Your device is booting now ... " and that's it
Got some ideas?
Edit#2 [SOLVED]: put fastboot option -w into command for flashing stock recovery => phone resurrected to stock software (at least)

Thanks for the update!
Im was stuck in the same situation. If you succeed in flashing LineageOS I would love to hear how.
Good luck!

without a phone I can't do a sh*t, try this recovery (3.5.0) and tell me if boots or not.

haky 86 said:
without a phone I can't do a sh*t, try this recovery (3.5.0) and tell me if boots or not.
Click to expand...
Click to collapse
While flashing it I get the following log:
.\fastboot flash recovery_ramdisk .\recovery.img -w
target reported max download size of 471859200 bytes
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
sending 'recovery_ramdisk' (13452 KB)...
OKAY [ 0.376s]
writing 'recovery_ramdisk'...
OKAY [ 0.102s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.068s]
finished. total time: 0.546s
I can boot into the recovery. My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
After flashing it again with the -w option, it works again.
An other issue I have is, when I try to wipe eg. cache, it works, but while trying to update the partition details, it "failed to mount '/data' (Invalid argument)". The same happens, when I install something.

Zet24 said:
While flashing it I get the following log:
.\fastboot flash recovery_ramdisk .\recovery.img -w
target reported max download size of 471859200 bytes
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
sending 'recovery_ramdisk' (13452 KB)...
OKAY [ 0.376s]
writing 'recovery_ramdisk'...
OKAY [ 0.102s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.068s]
finished. total time: 0.546s
I can boot into the recovery. My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
After flashing it again with the -w option, it works again.
An other issue I have is, when I try to wipe eg. cache, it works, but while trying to update the partition details, it "failed to mount '/data' (Invalid argument)". The same happens, when I install something.
[/QUOT]
can you pm me a screenshot?
Click to expand...
Click to collapse

1) @haky 86 : I can also boot into the (3.5.0) recovery
EDIT (fyi): could boot into that recovery, but after installation of stock rom (and likewise in official linage rom) my SIM Card was not detected.
Using "old" stock recovery [9.1_stock_rec.img] and SIM Card works fine. Still that Wifi-Password-Problem...
Zet24 said:
(...)
My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
(...)
Click to expand...
Click to collapse
2) @Zet24 : this looks rather to a twrp 3.4.0.0 error (?) because previously I got the same which finally ended in stucked teamwin screen and bootloop (see above)
3) @Zet24 : I managed to flash and boot into official figo lineage 16 ROM (lineage-16.0-20210122-nightly-figo-signed) by copying the zip file on sd card and install it directly in twrp (install >> from zip file) -- actually I don't know why sideload method doesn't work..
Unfortunately I couldn't not connect to wifi (see discussion in main topic Forum: https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3975303/post-83896865) even after wiping data and cache with stock recovery, but that is for another time/topic

I posted a tutorial on how to flash Lineage OS on this phone on the other Thread... the Lineage OS thread.

Bokkahontas said:
twrp installation succeded with _ramdisk, thanks for the fast reply!
I followed then instructions from official lineage 16 wiki (https://wiki.lineageos.org/devices/figo/install) to install lineageOS 16. Sideload of the actual zip (lineage-16.0-20210115-nightly-figo-signed) in twrp also worked perfectly and I eagerly tipped on "reboot" in twrp hoping to see my new OS booting for the the first time... BUT:
Unfortunately I got stuck at a probably similar point as Capybar (see https://forum.xda-developers.com/t/...k-recovery-and-cant-boot-into-system.4126357/):
Phone stopped being able to enter any recovery at all. The system itself does not boot. The HUawei start screen "Your device has been unlocked and cannot be trustet (...) only tells me (...) "Your device is booting now...", the recovery option never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now").
Then it shows me the Teamwin Logo and at that point freezes.
I cannot acces the phone with adb oder fastboot from host machine..
=> Does anybody knows if there is a possibility to gain acces to recovery?
Click to expand...
Click to collapse
Hi, How did you manage to unlock bootloader?