Thanks for the offer. Can't wait to see it!I'm not going to "pick up" full support, because I develop for other devices and I really don't have time to add another full blown device. Ive seen many people say this works ok for daily use. So. What I will offer in this thread is that if you want a new GSI rom down the road once some security updates or 9.1 update get released, I will create it and post it for people. I dont own the device, but I do own treble enabled devices, and can build GSI and roms from source. And I do have friends who own this phone.
Hi. This isn't the case for me.Hi,
after install lineageOS16 , TWRP are blocked and i can't access to custom recovery. i can boot the phon on lineageOS et fastboot is ok. How can i install again TWRP? because i want to install the rom stock, thx
Do you have a link for the recovery.img ? compatible with lineageOS because i try it TWRP (3.1.1/3.2.2/3.2.3) and i have an error every time : failed (remote: partition length get error)Hi. This isn't the case for me.
You're saying that you can't access TWRP now? Start the phone in bootloader and reinstall TWRP from there.
If you really just want to restart to stock you should use the built in recovery functionality of the phone.
Are you flashing to recovery_ramdisk?Do you have a link for the recovery.img ? compatible with lineageOS because i try it TWRP (3.1.1/3.2.2/3.2.3) and i have an error every time : failed (remote: partition length get error)
And i can't use isuite, the recovery functionality dosen't work; erecovery same. i boot at twrp and the phone block....
i don't know what to do?
thx
ok, i will try,Are you flashing to recovery_ramdisk?
Regardless, it probably will not boot anyway due to updated system.
To reflash stock, flash system.img and recovery_ramdisk.img from stock update.app in fastboot and reboot to recovery and factory reset.
after this i would like to go to rom stock but now i have a poblem , my phone doesn't boot .Are you flashing to recovery_ramdisk?
Regardless, it probably will not boot anyway due to updated system.
To reflash stock, flash system.img and recovery_ramdisk.img from stock update.app in fastboot and reboot to recovery and factory reset.
Uh. Flash images for the android version you are on. It sounds like you flashed Nougat recovery to recovery_ramdiskafter this i would like to go to rom stock but now i have a poblem , my phone doesn't boot .
i have
ERROR MODE
Pease update system again
Error !
Func no: 11 (recovery image)
Error NO :2 (load failed!)
I need help please
i extract update.app and i flash system/recovery/erecovery/kernel......
no work...
do i need flash in same time or i can flash separate ( reboot)?
Uh. Flash images for the android version you are on. It sounds like you flashed Nougat recovery to recovery_ramdisk
The correct way (unless I'm misunderstanding you) :i flash
system.img --> fastboot flash system system.img
erecovery--> fastboot flash recovery_ramdisk erecovery-ramdisk/erecovery_VBMETA/Erecovery_Vendor
Kernel --> fastboot flash kernek kernel.img/ramdisk
recovery--> fastboot flash recovery_ramdisk recovery_ramdisk.img/recovery_Vbmeta/recovery_vendor
and it's not working...
i try this with firmware 371 for MHA L29 EuropeThe correct way (unless I'm misunderstanding you) :
fastboot flash system system.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
And for eRecovery, you can't flash it from fastboot unless you use the backdoor or edited nvme.
But
fastboot flash erecovery_ramdisk erecovery_ramdisk.img
fastboot flash erecovery_kernel erecovery_kernel.img
fastboot flash erecovery_vendor erecovery_vendor.img
fastboot flash erecovery_vbmeta erecovery_vbmeta.img
So each image is flashed to the partition of the same name as the image.
Firmware is found on http://pro-teammt.ru/firmware-database/
One of your previous posts said:i try this with firmware 371 for MHA L29 Europe
fastboot flash system system.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
Same error
FUNC NO:11 (recovery image)
Error NO/2 (load failed)
and for erecovery:
target reported max download size of 471859200 bytes
sending 'erecovery_ramdisk' (32768 KB)...
OKAY [ 0.720s]
writing 'erecovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.730s
One of your previous posts said:
"is it a problem if i do an update from android 9 to android 8?"
Does this mean you are on Pie now? I mean did you update to Pie before flashing Lineage?
No, then it's all good.not before lineage, the is no stock pie for mate 9?
i have android 8 and i flash lineageOS 16, lineageOS16 working but when i wanted go back to rom stock i flash android 8...
do i need flash android 9 before?
thanks for you time
No, then it's all good.
But that error usually comes up when you flash a Nougat image to Oreo, or image is corrupt.
Pie only exists as beta for Mate 9 so far.
If it was the wrong build phone would boot.
So I'm not sure what's wrong...
Flashing all recovery_ partitions, kernel and ramdisk usually solves this error.
You could try this in fastboot:
fastboot getvar rescue_enter_recovery