[ROM & Kernel] [AOSP Based] [Minimal] 01/15/18 Invictrix ROM 8.1

[placebo_domingo]

here is a roomservice i quickly whipped up.

Many, many thanks! I'm all synced up but can't figure how to start the build.

*** Can not locate config makefile for product "mata".

 

[techfreak243]

Many, many thanks! I'm all synced up but can't figure how to start the build.

*** Can not locate config makefile for product "mata".

try deleting the vendor, kernel, and device folders. sync and try again

 

[weiyangbo]

I synced lastest source and compiled at home.
Flashed into both ab slots after wiped system,cache,data partitions.
But It cannot boot to system, just reboot to recovery

 

[ElfinJNoty]

I synced lastest source and compiled at home.
Flashed into both ab slots after wiped system,cache,data partitions.
But It cannot boot to system, just reboot to recovery

You flashed a boot.img to your active slot first, after flashing rom, right?

 

[mookiexl]

You're new here... So I'll explain...

When you take something that you do as a hobby... You do it for fun... For yourself... You move along at a pace comfortable for you...

Now... When you originally start sharing it with others... Everyone is all cool about it... They're appreciative of your work... And most importantly... Have patience... Knowing you either don't have time, motivation, or means to crank out the fixes or whatever...

Then... Others hear about it... And they want a try... But they don't know the original guy... So they start running their mouths... Demanding things... And making dude feel bad about his hobby...

Now... Many be they wanted to help... With logs... Or whatever... But actually... All they've done is piss dude off to the point that he stops sharing...

Seen it happen many times... Lost a lot of cool things over the years here... Due to idiots...

And when I see 2 posts in a row... Putting someone on blast... I return the volley...

There are no expectations... This is not Essential's help desk...

This is some dude... In his basement... Either pissing off his parents... Or his wife (or her husband... Or whatever) because he's coding for fun...

Sent from my PH-1 using XDA Labs

This is one of the greatest post I've ever read here. This should be stickied somewhere.

 

[weiyangbo]

[/COLOR]

You flashed a boot.img to your active slot first, after flashing rom, right?

Oh, I didn't...
I think boot will be flashed when I flash whole .zip as well as vendor and system partion.
Am I wrong?
By the way, I use twrp flashed rom in both ab slots.

 

[ElfinJNoty]

[/COLOR]

Oh, I didn't...
I think boot will be flashed when I flash whole .zip as well as vendor and system partion.
Am I wrong?
By the way, I use twrp flashed rom in both ab slots.

When you are flashing your boot partition with TWRP, yes... You must replace TWRP with a boot.img before being able to boot back into a room.

And there really isn't a need to be messing with both a/b slots simultaneously

I'd recommend a back-to-basics followed by flashing a custom rom if your choice as instructed by that OP

 

[weiyangbo]

When you are flashing your boot partition with TWRP, yes... You must replace TWRP with a boot.img before being able to boot back into a room.

And there really isn't a need to be messing with both a/b slots simultaneously

I'd recommend a back-to-basics followed by flashing a custom rom if your choice as instructed by that OP

I just noticed that the kernel source has not been updated for two months while the vendor source has been updated to july version. Is there any possibility that boot failure caused by mismatched source codes?
I has tried RR, AOSIP and AICP. They are all work fine. Are you in Invictrix ROM now？ Just tell me which build are you using now and I will have another try?

 

[ElfinJNoty]

I just noticed that the kernel source has not been updated for two months while the vendor source has been updated to july version. Is there any possibility that boot failure caused by mismatched source codes?
I has tried RR, AOSIP and AICP. They are all work fine. Are you in Invictrix ROM now？ Just tell me which build are you using now and I will have another try?

I don't mean to be rude....
But you notice the kernel source hasn't been updated for two months(that's because there was no need to update the kernel) and you see vendor source is updated to July......

What has that got to do with the fact you need to flash a working kernel(boot.img) back to the boot partition after using TWRP, and prior to booting into the rom?

---------- Post added at 11:05 PM ---------- Previous post was at 11:03 PM ----------

[/COLOR]

Oh, I didn't...
I think boot will be flashed when I flash whole .zip as well as vendor and system partion.
Am I wrong?
By the way, I use twrp flashed rom in both ab slots.

Yes you are wrong.

Need to flash a working boot.img and replace the TWRP you put in the boot partition.

On these a/b devices, kernel recovery and ramdisk all share the boot partition. If you flash TWRP via fastboot, you are essentially telling the phone to boot recovery instead of booting the kernel>rom

---------- Post added at 11:10 PM ---------- Previous post was at 11:05 PM ----------

I just noticed that the kernel source has not been updated for two months while the vendor source has been updated to july version. Is there any possibility that boot failure caused by mismatched source codes?
I has tried RR, AOSIP and AICP. They are all work fine. Are you in Invictrix ROM now？ Just tell me which build are you using now and I will have another try?

No I am not "in" Invictrix.

I am a board member of Team Bliss. We collaborate and work with the man behind Invictrix. The OP. He is a good guy. He has also stopped building this rom and sharing it with XDA.

I hope you learn what you are doing with your device, and don't end up breaking things. There is plenty of material on XDA/the interwebs to help you become more familiar with the Essential Phone, and common practices with a/b treble supported devices.

Take care, and good luck

 

[weiyangbo]

I don't mean to be rude....
But you notice the kernel source hasn't been updated for two months(that's because there was no need to update the kernel) and you see vendor source is updated to July......

What has that got to do with the fact you need to flash a working kernel(boot.img) back to the boot partition after using TWRP, and prior to booting into the rom?

---------- Post added at 11:05 PM ---------- Previous post was at 11:03 PM ----------



Yes you are wrong.

Need to flash a working boot.img and replace the TWRP you put in the boot partition.

On these a/b devices, kernel recovery and ramdisk all share the boot partition. If you flash TWRP via fastboot, you are essentially telling the phone to boot recovery instead of booting the kernel>rom

---------- Post added at 11:10 PM ---------- Previous post was at 11:05 PM ----------



No I am not "in" Invictrix.

I am a board member of Team Bliss. We collaborate and work with the man behind Invictrix. The OP. He is a good guy. He has also stopped building this rom and sharing it with XDA.

I hope you learn what you are doing with your device, and don't end up breaking things. There is plenty of material on XDA/the interwebs to help you become more familiar with the Essential Phone, and common practices with a/b treble supported devices.

Take care, and good luck

Thank you for your reply
I will have another try and make sure the kernel is flashed to boot partition.
By the way, I was very impressed by BlissRom, I still remeber BlissRom bring me to Android Lolipop. Very appreciate for your work!

 

[dirtyreturn]

@ElfinJNoty , you mentioned the OP stopped building this ROM - entirely??? Or only updating their website? Hope you can help.

Sent from my PH-1 using Tapatalk

 

[jmkarnai01]

@ElfinJNoty , you mentioned the OP stopped building this ROM - entirely??? Or only updating their website? Hope you can help.

https://invictrixrom.com/ did you check there first before posting or was it just for conversation?

 

[dirtyreturn]

https://invictrixrom.com/ did you check there first before posting or was it just for conversation?

No, I checked first. According to @ElfinJNoty, the OP has stopped building the ROM/sharing on XDA. So, I checked their website and saw the last build was 07/28 and I'm still wondering if this ROM is maintained anywhere...

P.S. --- also for conversation. Maybe, there may be a final answer or something.
P.S.S. --- @USA-RedDragon , is your decision to stop maintaining for this device altogether???

 

[BakedTator]

No, I checked first. According to @ElfinJNoty, the OP has stopped building the ROM/sharing on XDA. So, I checked their website and saw the last build was 07/28 and I'm still wondering if this ROM is maintained anywhere...

P.S. --- also for conversation. Maybe, there may be a final answer or something.
P.S.S. --- @USA-RedDragon , is your decision to stop maintaining for this device altogether???

Seems like it stopped being built to make room for the Android p bring up...I have nothing to prove this, it's just an assumption