[ROM][DISCONTINUED][UNOFFICIAL] LineageOS 16.0 [MATE 9] 2018-11-11

osk4rin

Senior Member
Sep 7, 2015
643
118
43
San Diego
That is a bad news man, bummer!!
Anyway, thanks for such a nice work for our beloved Mate 9. In that case I'll get a new device. There is nothing else to do around here. Just to say thanks :)
 

godkingofcanada

Senior Member
Nov 13, 2013
1,031
453
103
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.
 

thelongdiv

Member
Aug 3, 2014
48
9
0
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.
Thanks for the offer. Can't wait to see it!
 
  • Like
Reactions: godkingofcanada

godkingofcanada

Senior Member
Nov 13, 2013
1,031
453
103
I forgot to mention I keep unbranded vanilla aosp gsi system images over in the project treble forum under a/an, since I do both. So when a big change occurs the gsi there gets updates right away within a day or 2. Then the device rollouts begin afterwards. Its easier to make a universal gsi anyone can install first before doing custom variants, this way everyone can get on it with little wait to test.
 
  • Like
Reactions: edjocute

antho86

Member
Feb 6, 2009
12
0
0
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
 

thelongdiv

Member
Aug 3, 2014
48
9
0
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
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.
 

antho86

Member
Feb 6, 2009
12
0
0
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.
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
 

ante0

Senior Member
Dec 28, 2009
3,206
1,576
243
Stockholm
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
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.
 
Last edited:

antho86

Member
Feb 6, 2009
12
0
0
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.
ok, i will try,
do you have a link or a tutorial ?please.
is it a problem if i do an update from android 9 to android 8?
thx

edit: i flash with recovery_ramdisk and it,s work . many thank :D
 
Last edited:

antho86

Member
Feb 6, 2009
12
0
0
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 .

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)?
 
Last edited:

ante0

Senior Member
Dec 28, 2009
3,206
1,576
243
Stockholm
after 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
 

antho86

Member
Feb 6, 2009
12
0
0
Uh. Flash images for the android version you are on. It sounds like you flashed Nougat recovery to recovery_ramdisk

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...

Do you have a link please for a good firmware?
I need only UPDATE.ZIP ? (1.9go)
 
Last edited:

ante0

Senior Member
Dec 28, 2009
3,206
1,576
243
Stockholm
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...
The 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/
 

antho86

Member
Feb 6, 2009
12
0
0
The 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/
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
 
Last edited:

ante0

Senior Member
Dec 28, 2009
3,206
1,576
243
Stockholm
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?
 

antho86

Member
Feb 6, 2009
12
0
0
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?

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
 

ante0

Senior Member
Dec 28, 2009
3,206
1,576
243
Stockholm
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
 

antho86

Member
Feb 6, 2009
12
0
0
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

fastboot getvar rescue_enter_recovery :

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar rescue_enter_rec
overy
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.030s