Database Info

Bricked?

Hello community
I think i bricked my P8 MAX.
What i did, rooted the phone with Kingroot, altered the Dualwindow file.
Three days ago i tried to install B209 and now it won´t boot up.
I always stay at the animated Huawei Logo.
erecovery is not able to load a Firmware and when i try to do something in Fastbbot, i always get remote command not allowed. In Fastboot it says PHONE Unlocked....
Any suggestions?

audiaudi said:
Hello community
I think i bricked my P8 MAX.
What i did, rooted the phone with Kingroot, altered the Dualwindow file.
Three days ago i tried to install B209 and now it won´t boot up.
I always stay at the animated Huawei Logo.
erecovery is not able to load a Firmware and when i try to do something in Fastbbot, i always get remote command not allowed. In Fastboot it says PHONE Unlocked....
Any suggestions?
Click to expand...
Click to collapse
Which Rom where installed before you updated to B209?

Hirs_E_Fruit said:
Which Rom where installed before you updated to B209?
Click to expand...
Click to collapse
B029

audiaudi said:
B029
Click to expand...
Click to collapse
Stock B029 with Stock Recovery?
OTA Update from B029 to B209?

Stock b029 with stock recovery
Rooted
B209 update through dload folder
I downloaded the b209 form kangvip thread, but the regular one.

audiaudi said:
Stock b029 with stock recovery
Rooted
B209 update through dload folder
I downloaded the b209 form kangvip thread, but the regular one.
Click to expand...
Click to collapse
You never got your Phon to start full into OS after update?

Nope

Does anybody know, why i always get remote command not allowed when using fastboot?

audiaudi said:
Does anybody know, why i always get remote command not allowed when using fastboot?
Click to expand...
Click to collapse
hey you only need flash these files from update.app
boot
cust
recovery
cache
system
reboot and when Android is finish booting copy the update.app to /dload in internal storage and reset factory... then... upgrade from internal storage... BACKUP you NVRAM contents but no lost IMEI how is my case

I can't....
fastboot flash boot boot.img
I get: remote command not allowed

do you have the BOOTLOADER UNLOCK ?..
fastboot oem unlock CODE
??
audiaudi said:
I can't....
fastboot flash boot boot.img
I get: remote command not allowed
Click to expand...
Click to collapse

On the screen it shows phone unlocked but i don't know if it's true cause I didn't unlock so it must have been unlocked before.
And i can't get an umlock code through the Huawei site cause i haven't the huawei id on the phone long enough and know, obviously i can't....

audiaudi said:
On the screen it shows phone unlocked but i don't know if it's true cause I didn't unlock so it must have been unlocked before.
And i can't get an umlock code through the Huawei site cause i haven't the huawei id on the phone long enough and know, obviously i can't....
Click to expand...
Click to collapse
I unlock bootloader with a paid tool..( dont say the name this tool... ), cost to 5 dlls USA

audiaudi said:
Hello community
I think i bricked my P8 MAX.
What i did, rooted the phone with Kingroot, altered the Dualwindow file.
Three days ago i tried to install B209 and now it won´t boot up.
I always stay at the animated Huawei Logo.
erecovery is not able to load a Firmware and when i try to do something in Fastbbot, i always get remote command not allowed. In Fastboot it says PHONE Unlocked....
Any suggestions?
Click to expand...
Click to collapse
Try this version of fastboot...
https://drive.google.com/folderview?id=0B5I_q70mNuR4bWp5Wl9LOGdFQnc

ajsmsg78 said:
Try this version of fastboot...
https://drive.google.com/folderview?id=0B5I_q70mNuR4bWp5Wl9LOGdFQnc
Click to expand...
Click to collapse
The same...
C:\test>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23406 KB)...
OKAY [ 0.511s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.529s

you extract the img files with a profile ??? I use the unknow... other... and mmmm you probe the names of file and partition are diferent ?
fastboot flash boot BOOT.IMG ...(name of file exactly )

same problem in here...
someone can help us?
FAILED (remote: Command not allowed)

same problem here.. please help us

Huawei P8 Max DAV703 Android 6.0 EMUI 4.0 64 GB chinese variant trying to convert to EU
Well I hope that it isn't completely FUBAR.. I know there has to be a way, but i forget how.
No fastboot, no adb support.. no recovery, no bootloader.. fastboot was only available through software.
I have hard reset which has reset it to bootloop, and I have system upgrade that whatever I do, crashes at 5%
Basically, I bricked my Huawei.
I partially rooted it with kingoroot without doing anything..
but other apps saw it as unrooted so i was going to do the proper way, unlock bootloader, etc..
Then I discovered the Huawei SRK tool for bootloader/kernel/recovery etc.
Checked if my bootloader was unlocked, it was..
restarted the phone, it was fine
Then I was going to flash the recovery, and that's when it went into a bootloop
Like always.. just the logo shows, and if i try to turn it off, it restarts.
Huawei P8 Max DAV703 Android 6.0 EMUI 4.0
hard reset works - pressiing vol up down and power pushes it into hard reset but it stays in bootloop.
usb in, vol down power - puts into update mode which stops at 5% with error.
My next idea would be to try and extract the necessary files and try to use the Huawei update extractor tool
but after trying many update files, I can't find the one that would work, unless it will just keep crashing at 5% always.
Would anyone know what I could do in this situation?

Another Honor 8 Bricked

Hello,
After the purchase of my phone i unlocked the bootloader, installed a custom rom of android M, everything went fine, twrp, root, etc.
Few days ago I wanted to give a shot at Nougat. I went through a couple roms but lacking certain functions i needed. I then tried one last stock nougat beta rom (from this link : https://forum.xda-developers.com/honor-8/development/beta-android-7-0-emui-5-l04c567b320-frd-t3529465
This was the worst rom i've encountered. Please don't use it.
Three reasons : No bluetooth, TWRP gone, and no keyboard pre-installed.
Yes. You can only first boot this rom with google voice typing. I'm not joking.
More than that i cannot finish the initial boot of the rom, i get stuck at the "enter your google account" (try to enter yours with google voice...)
I can't even ignore it, it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device".
Anyway, now that I lost TWRP i wanted to flash it back. My bootloader being still unlocked (phone shows "your device has been unlocked and cannot be trusted" at each boot), i went to adb to flash twrp.
I got this message after trying to flash it :
...
FAILED (remote: Command not allowed)
...
I get this message after i try to flash TWRP, update, boot or anything.
I've read that i need to enable oem unlock in the developer settings. Thing is I'm stuck before i can access any parameters.
I even tried Huawei Multi-Tool, with boot, recovery, unbrick, but again, can't flash anything.
tl;dr :
- Nougat 7.0 EMUI 5.0
- Stuck in initial boot
- Only type with google voice
- No TWRP
- FAILED (remote: Command not allowed) error when trying to flash anything
What can I do ?
EDIT : I did manage to enter my google account, but it says that i need to log in with one of the owner's account. I never entered any other account on my phone... Definitely stuck.

This question was already answered a million times before! Just use the search button!
This Honor 8 forum is full of threads created by newly come member that just create a new thread without any use when they could just search for the already answered questions!

Plug in USB to computer, hold down power + volume down until you enter bootloader. Flash recovery system image again, then reboot into recovery and re flash another ROM.

Telperion said:
Plug in USB to computer, hold down power + volume down until you enter bootloader. Flash recovery system image again, then reboot into recovery and re flash another ROM.
Click to expand...
Click to collapse
Even when i'm in fastboot mode I can't flash anything, boot.img, recovery.img, system.img... nothing.
Fastboot mode shows "PHONE Unlocked" "FRP Lock", if that helps.
I tried using the rollback solution shown here https://forum.xda-developers.com/honor-8/help/totally-screwed-honor-8-t3556678/post71033483#post71033483. Intermediate package did apply but the full android 6.0 firmware failed to update.
And yes I've been searching around this forum before posting, but I can't find a post talking about my problem, being unable to access the rom in normal boot, unable to flash anything.
Is there a way to fix the "FAILED (remote: Command not allowed)" error message ? As it is the only think keeping me from doing anything on my phone
Or maybe trick the phone into flashing a rom through recovery (like a rollback but with a random custom rom instead) ?

Hi, did you ever find a fix for this?

Rommco05 said:
Are you missing some stuff from the system?
Click to expand...
Click to collapse
I don't believe so. Why?

Rommco05 said:
You need to install zip data. Which is your model and build number?
Click to expand...
Click to collapse
FRD-L04, and my Build Number is whatever the build number is for the first Nougat Beta from last year haha.
But how would I install zip data if flashing stuff via fastboot isn't working?

Are you referring to the Data Fix.zip? Also, I haven't been able to flash the 6.0 Stock ROM Via ercovery.
---------- Post added at 09:16 AM ---------- Previous post was at 09:14 AM ----------
Rommco05 said:
FRD-L04 US model, right? First beta was maybe B320..?? Via dload
Click to expand...
Click to collapse
Are you referring to the Data Fix.zip? Also, I haven't been able to flash the 6.0 Stock ROM Via ercovery.

Rommco05 said:
FRD-L04 US model, right? First beta was maybe B320..?? Via dload
Click to expand...
Click to collapse
Rommco05 said:
For flash to 6.0 u need rollback packages and full M rom. Is your phone US model? I try send u links if is
Click to expand...
Click to collapse
Yeah I have the US model

Rommco05 said:
First install biggest second small, over dload methodhttp://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v72309/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...09/f1/full/hw/usa/update_data_full_hw_usa.zip
Click to expand...
Click to collapse
Thanks, so what's the install method for this?

Root your One Hyper

Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done

CTSProfile and BasicIntegrity false, any ideas?

Space_Dog said:
CTSProfile and BasicIntegrity false, any ideas?
Click to expand...
Click to collapse
It's probably the version. I have same situation

mingkee said:
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
Click to expand...
Click to collapse
What is this FastbootD? Something new on Android 10, cause the Pixel 4 has it too...

AndroidManager2020 said:
What is this FastbootD? Something new on Android 10, cause the Pixel 4 has it too...
Click to expand...
Click to collapse
It's Android 10 way to flash boot, recovery, dtbo, vbmeta, and super
The interface is more like stock recovery with fastbootd on the top

mingkee said:
It's Android 10 way to flash boot, recovery, dtbo, vbmeta, and super
The interface is more like stock recovery with fastbootd on the top
Click to expand...
Click to collapse
I totally understand the concept but what different between regular fastboot, mfastboot, and fastbootD?

mingkee said:
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
Click to expand...
Click to collapse
For the retail channel on my device, should be LARET which had (2) Builds, the latest being (XT2027-1_DEF_RETLA_10_QPFS30.103-12-5-2_subsidy-DEFAULT_regulatory-XT2027-1-SUTEL-DS_CFC.xml.zip) i'll change to RETAIL after i receie the device. I am worried about getting OTAs later then Brazil/LA Channels.. There are NO RETAIL Firmware Packages for the Retail Channel Device. I guess ill have to see what model it is, Purchased from Amazon, which is where I got my G8+ for a CHEAP $205.83 and as soon as i went to reorder a replacement, price jumped $75, like amazon knew i was going to reorder the same device. Then i came across the one hyper and for a few $$$$ more, specs and chipset are better, same exact specs as the Zoom and the Hyper ran me $314 and the Zoon is like $394.00 I Just need something new to keep me busy until the Edge+ is released....and currently also a Pixel 4 XL (Trying to trade for a LG V60 thinq with the Dual Screen. ) Pixel is 1 month old, 1.5 months at the most, OEM Box, OEM accessories ONLY EVER USED, a couple cases.
Been a Android user since 2010, never had an LG Android. Wait, i had the V40/V50 for under 12 hrs and hated it. it felt cheap and clunky.... But i feel in love with this V60. And i also have (2) Moto G7 aka River. My Moto Def should be here tuesday hopefully. See how quick i can brick this one Moto G8+ was bricked on day one but i pulled out of it using a brand new Levovo Upgrade Tool!

Magisk install
I cannot find on XDA if we can or cannot install Magisk on the XT2027-1 ( One Hyper )
I found a few other sites on the internet that say it can be installed
BUT I tend to err on the side of caution.
I do not want to nuke this phone.
Is this a possibility to install Magisk or not?
I use Viper4 Android and a few other apps like blockada and such
Finally, IF Magsik is installed, I cannot get OTA updates, correct?
Can I uninstall Magisk, update OTA, then reinstall Magisk?
Thank you all

jharkness316 said:
I cannot find on XDA if we can or cannot install Magisk on the XT2027-1 ( One Hyper )
I found a few other sites on the internet that say it can be installed
BUT I tend to err on the side of caution.
I do not want to nuke this phone.
Is this a possibility to install Magisk or not?
I use Viper4 Android and a few other apps like blockada and such
Finally, IF Magsik is installed, I cannot get OTA updates, correct?
Can I uninstall Magisk, update OTA, then reinstall Magisk?
Thank you all
Click to expand...
Click to collapse
Have run into issues......... Damn Windows update restarted computer in middle of night before I was to finish rooting.
I can get into bootloader and when I try to flash I am stuck in bootloop
I get the following errors:
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Sending 'vbmeta_a' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 5
OKAY [ 0.000s]
Finished. Total time: 0.016s
Ideas on how to fix? This was flashing back the ORIGINAL stock rom
---------- Post added at 07:57 AM ---------- Previous post was at 07:11 AM ----------
FIXED Rescue and Smart Assistant from Lenovo fixed it

Got it fixed thanks to Rescue and Search program from Motorola
Would like to know since TWRP is not working with the One Hyper, is there a way that I can make a master rom backup via ADB or FASTBOOTD?
If so, can someone make a batch file or list all the things to backup this rom?
I would greatly appreciate it. Thank you

I have my Magisk installed on my Hyper and all is working well. I just got Moto trying to download and update a patch (assuming Google security update). It could not update obviously.
My question is how can I UNinstall magisk , all the modules, and then update my Hyper?
Now if I uninstall magisk I will lose root, correct?
This is the rom I am currently using........DEF_RETAIL_QPFS30.103-47-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC

jharkness316 said:
I have my Magisk installed on my Hyper and all is working well. I just got Moto trying to download and update a patch (assuming Google security update). It could not update obviously.
My question is how can I UNinstall magisk , all the modules, and then update my Hyper?
Now if I uninstall magisk I will lose root, correct?
This is the rom I am currently using........DEF_RETAIL_QPFS30.103-47-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
in order to take updates you would need to restore the stock boot image with fastboot or magisk, and then update your device, then take the new boot image from the downloaded update and patch with magisk and then flash it to regain magisk root, you do not need to uninstall magisk or the modules but you will need to restore stock boot partitions to allow the device to not error out during the install process. This is how it has been in the past for magisk official guides can be found on magisk website here: https://topjohnwu.github.io/Magisk/ota.html

[deleted]

LOSQ/LiR - LineageOS 17.1/18.1-UNOFFICIAL-GSI

For those who want to try LineageOS 17.1/18.1-UNOFFICIAL-GSI . IMO stable enough to be used as your daily driver.
LOSQ/LiR is not developed nor maintained by me!
Credits: @eremitein
Requirements: basically full stock EMUI 9.1, with stock recovery_ramdisk.
Note: I prefer to install in fastboot mode, it's quick, easy and most importantly, safe.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Install arm64-b.. only!
1. LOSQ - LineageOS 17.1-[10]-unofficial-GSI
with the GAPPS
GAPPS
without GAPPS
Vanilla
-----------------------
LiR- LineageOS 18.1-unofficial-[11]-GSI
Download
2. Extract the ROM .img file from the compressed file.
3. Flash extracted losq/lir... .img from fastboot , use command
fastboot flash system (file_name).img
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot .
NFC patch:
https://forum.xda-developers.com/t/losq-lineageos-17-1-unofficial-gsi.4219291/post-84394147
Magisk root (23.0):
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ),
- download and install Magisk manager-23.apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
- Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1):
- copy TWRP file to the SD card, and also copy to the SD card patched Recovery_ramdisk:
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
- flash TWRP - run command
fastboot flash recovery_ramdisk (TWRP's_name).img
- boot into TWRP, select storage - SD Card, select "Install image", find TWRP-9.1.img file and mark eRecovery, swipe. Go back, find magisk_patched-23.img file, mark Recovery, swipe. Go back to the TWRP's main menu, select Reboot > Recovery. Done.
Note: you then need to boot your phone every time via Recovery. It'll boot into android as normal but with root.
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
To remove Magisk reinstall stock recovery_ramdisk via TWRP or fastboot , download Here
How to boot into TWRP:
- Turn off your phone, connect to the PC (or charger), then press and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset).
Tips:
https://forum.xda-developers.com/t/treble-gsi-favorite-gallery-camera-and-file-manager.4246019/

I have tried this rom - but without the magisk as I don't really care for root.. However.. This rom still has one big missing feature.. Fingerprint unlock. I can go to register fingerprint. Add the finger multible times to complete the circle.. however.. every time it misses just the last part - it will fail. If anyone has a fix for this I would be happy to use this as my daily driver as it works just fine.

whitetigerdk said:
This rom still has one big missing feature.. Fingerprint unlock
Click to expand...
Click to collapse
I'm afraid you're wrong... It works perfectly for me.

Can confirm that so far everything works flawless. Fingerprint sensor is working on the phone too.
Thank you Alf.
Just two additional questions:
How will updates be perform in future?
How to switch from LOS 16 to this rom - the other P20 lite we have is still on v.16?
Cheers
Horqai

horqai said:
How will updates be perform in future?
Click to expand...
Click to collapse
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
horqai said:
How to switch from LOS 16 to this rom
Click to expand...
Click to collapse
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!

-Alf- said:
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
Click to expand...
Click to collapse
Ugh, is there a way to install emui 9 without it locking my bootloader? I unlocked my bootloader via the @huaweihax method.

[/QUOTE]
XRealX said:
Ugh, is there a way to install emui 9 without it locking my bootloader?
Click to expand...
Click to collapse
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
XRealX said:
I unlock my bootloader via the @huaweihax method.
Click to expand...
Click to collapse
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method

OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
Click to expand...
Click to collapse
There's no way I'm paying for unlocking!
The huaweihax method works this way: you give some information about your device and you flash a slock file to the ramdisk. It unlocks your phone.
To prevent EMUI 9 from re-locking your device, you can flash a zip file to have a custom bootloader unlock code.
Btw, I have hyperlinked the thread that describes this in the "thingy" word.
I guess that custom code should work even if my device is re-locked.

I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone

I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone

How can I repair the factory erecovery I am using the phenix program but it gives me recovery error

itrisev said:
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
Click to expand...
Click to collapse
Sorry, this is not the DC-Phoenix support chat, let's please remember to keep conversations and comments in this thread about LOSQ - LineageOS 17.1, thanks...

Thanks @-Alf-
I followed all your advice in the LOS 16 thread to get 16 installed, but couldn't get gapps to work. So I thought lemme give LOS 17 a shot since it includes gapps, and it works great! However I get the same issue with fingerprint as @whitetigerdk. During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work. Try again or use a different finger". I can provide a screenshot but it's literally just that text.
Apart from that everything seems to work fine. Haven't installed magisk yet, will do that next.

An3skmbi said:
During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work.
Click to expand...
Click to collapse
-Alf- said:
Tested on 9.1.0.132.
Click to expand...
Click to collapse
-Alf- said:
Clean OS
Click to expand...
Click to collapse
-Alf- said:
Install Service ROM using dload method (9.1.0.132 recomm.)
Click to expand...
Click to collapse
Most of custom ROMs require lower build number, on latest build number may or may not work correctly.
If you have followed this guide to the letter and it didn't work, i'm afraid I cant help you .
I've not had any major issue with this LineageOS.
P.S.:
If all this has worked on my device, it does not mean that it goes with everyone else, and vice versa (we are talking about Huawei devices ).

@-Alf- Thanks, that might be it. I'm on firmware 9.1.0.200(C185E4R1P8T8) as that was the recommended one for LOS 16. Let me give it a shot with 132, will update with results.
Edit: With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.

An3skmbi said:
With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
Click to expand...
Click to collapse
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
IMO you can get it via paid service only, for 17euros , hm...look here
.132
The difference between .132 and .200 is google patch - may 2019 vs. july 2019.

-Alf- said:
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
Click to expand...
Click to collapse
What about this one? http://huawei-firmware.com/rom/huawei-p20-lite/ane-lx1/42056
It doesn't have a dload folder, it's just the update.zip basically, so I'm not sure how to flash it only unlocked my phone yesterday, not used to huawei roms yet.
Edit: they explain how here, you create the dload folder manually.

An3skmbi said:
they explain how here, you create the dload folder manually.
Click to expand...
Click to collapse
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .

-Alf- said:
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
Click to expand...
Click to collapse
What do you mean really reliable when the guide is for Android 6? Is there a way to flash the 132 ROM from huawei-firmware?
Also, magisk installation worked perfectly by following your instructions. I can pass safety net with the universal safetynet fix module and got google play certification with the props module.
Is there a way to now boot into TWRP (erecovery)? Currently when booting it doesn't show the option to hold volume up to enter erecovery, it immediately says your phone is booting now. The only way to get into TWRP is to fastboot flash recovery twrp, do stuff there, then flash magisk_patched-ane-v21 over recovery and reboot.
Edit: I captured a logcat while getting the fingerprint enrollment error, there are some exceptions about the enrollment, not sure if that could mean something to the devs to help fix it?

An3skmbi said:
Is there a way to flash the 132 ROM from huawei-firmware?
Click to expand...
Click to collapse
Nope.
An3skmbi said:
Is there a way to now boot into TWRP (erecovery)?
Click to expand...
Click to collapse
Oops I thought I mentioned it in my post, mea culpa.
You have two options:
1. Turn off phone, connect to PC (or charger), then pres and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
2. Restart phone, when appears the yellow warning on screen, press Volume up, hold for ~ 2 sec,
release the button and immediately press and hold again for 2 sec, repeat it 6-7 times, the device will reboot into Stock Recovery , then you can do normal restart - Reboot system now.

General Official Android 13 firmware is now available

It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/...300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.

MarekPietrzak said:
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-33.0210.0210.200-1.1.300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
Click to expand...
Click to collapse
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo

Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse

MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
hey, Thanks for replay, i am facing now another messeges.
1- the phone does not charging at all
2- when i plug in into chrage its reboot again and again.
3- the bootloader is open, but when i try to flash any files through bootloader i get:
FAILED (Status read failed (Too many links))
or
FAILED (remote: 'Warning: battery's capacity is very low
to recovery mode i am unable to go there
i tried boot or flash the twrp.img also only boot.img also flash_raw_and_wipe_data.cmd
nothing helps me!!!

Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.

MarekPietrzak said:
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
Click to expand...
Click to collapse
I've tried leaving it on overnight and it never charges, there's even no charging lights.
Yesterday I tried flashing via Bugjeager and it didn't work either (betwenn to android devices)
Although the bootloader is unlocked, it gives me a Not Allowed In Lock State message!
the current version of the installed firmware is that old that i flashed WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw, it is non extractable so i cant get the boot.img of it!

I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system

MarekPietrzak said:
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
Click to expand...
Click to collapse
wow you are alive haha i thought you not gonna answer me again. ok just 1 second

rami88436 said:
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
Click to expand...
Click to collapse
Sometimes I can be a bit slow to respond as I am on the university during day. Hopefully your issue seems to be possible to be solved just by flashing raw firmware and wiping data partition.

so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?

rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root

chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
try root your phone through kirnal su

chairman011 said:
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
Click to expand...
Click to collapse
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.

I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse

MarekPietrzak said:
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
Click to expand...
Click to collapse
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
rami88436 said:
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
Click to expand...
Click to collapse
Oh ok ok makes sense. Usually when I face a brick problem I just flash raw firmware fastboot

Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
chairman011 said:
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
Click to expand...
Click to collapse

MarekPietrzak said:
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
Click to expand...
Click to collapse
Oh wow thank you man I'll give it a shot.

I found a gui-based app on github to systemlessly debloat, it is easier to use than this script I posted link to. Here is the link: https://github.com/sunilpaulmathew/De-Bloater

Does anyone have the full RAW firmware, flashed via fastboot? Thank you all

ThienAn2023 said:
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
Click to expand...
Click to collapse
Mod. edit: private link removed. alecxs