[ROM][OFFICIAL][NIGHTLY][GRIFFIN] AICP 13.x | Oreo 8.x

[YOLOKazim]

so i cleanly flashed the unofficial version of the rom,
everything was running fine until i rebooted the device to install the drivers for viper4android
now my device is completely dead
i even plugged it into my pc to see if maybe i could get it into recovery mode by using the adb command line but no.
im not really sad about bricking my phone but just surprised at the way it did.
many thanks for making this amazing rom which helped me get more experienced!

 

[ExtraBasher]

so i cleanly flashed the unofficial version of the rom,
everything was running fine until i rebooted the device to install the drivers for viper4android
now my device is completely dead
i even plugged it into my pc to see if maybe i could get it into recovery mode by using the adb command line but no.

Holding Power + Vol- to force reboot the device does nothing? Even if you cannot boot into TWRP but still have access to fastboot via bootloader then you can boot to a TWRP image to reflash the ROM, or if it's bad enough then flash the stock firmware to get back on your feet.

 

[David1one]

Wich may build exactly?

15.05 but I have to say that it does randomely reboot sometimes. Not as much as on the latest official builds though, which was constantly annoying. Its stable enough for me.

 

[alkxx]

15.05 but I have to say that it does randomely reboot sometimes. Not as much as on the latest official builds though, which was constantly annoying. Its stable enough for me.

But battery life is definitely better on the 15.5. build?

 

[akkinju]

is VOLTE works??

 

[David1one]

But battery life is definitely better on the 15.5. build?

No, I don't think so. The later builds have better battery standby imo.

 

[David1one]

The build of 20th June is very stable. Only had random reboots after installing viper4android.
I removed audiofx and am now testing wether or not that was the problem.

 

[alkxx]

The build of 20th June is very stable. Only had random reboots after installing viper4android.
I removed audiofx and am now testing wether or not that was the problem.

Please report back if it's suitable as a daily driver especially in terms of battery life.

 

[David1one]

Please report back if it's suitable as a daily driver especially in terms of battery life.

With magisk it is not stable for some reason. I wouldn't recommend the official builds for a while. Use Erfan's builds or any other time based on them.

 

[David1one]

2nd of July official build is stable. Didn't have any random reboots yet.

 

[Edmontonchef]

2nd of July official build is stable. Didn't have any random reboots yet.

Are you using magisk as well?

 

[ExtraBasher]

Are there any unlisted revisions following the Bluetooth operating voltage change back in May, perhaps that are in the unofficial builds? Nothing recent via Gerrit and Github since then.

 

[David1one]

Are you using magisk as well?

Yes. Works.

 

[Edmontonchef]

was working great until I tried updating the build. Should probably clean flash only.

 

[TobiPeter]

was working great until I tried updating the build. Should probably clean flash only.

Clean flash doesn't solve the problems, I also tried it once.

Some builds are just more stabel than others I guess.

 

[[email protected]]

Question about OTA

All is working ok, checking for updates I saw a newer version, do I downloaded and installed, the phone boot on recovery mode, install the update, boot in normal mode, pass the new boot logo, then arrived to the unlock screen and reboot.

Reading the forum, I saw that I must install the root again, every time that I do an update, so the loop can be caused because I installed the update but not Magik.


Thanks

 

[ExtraBasher]

was working great until I tried updating the build. Should probably clean flash only.

Clean flash doesn't solve the problems, I also tried it once.

Some builds are just more stabel than others I guess.

All is working ok, checking for updates I saw a newer version, do I downloaded and installed, the phone boot on recovery mode, install the update, boot in normal mode, pass the new boot logo, then arrived to the unlock screen and reboot.

Reading the forum, I saw that I must install the root again, every time that I do an update, so the loop can be caused because I installed the update but not Magik.

I assume you folks were flashing the official July 4th or 5th builds, ja? Details, DETAILS!
Only if the build platform that AICP uses gave build statuses for each new build like Jenkins does.

From what I understand, without any new commits to the griffin source since May 4th it would be safer to stay with aicp_griffin_o-13.1-UNOFFICIAL-20180412 or the last working official build from or after May 4th as there is nothing new anyway.

 

[[email protected]]

Thanks for the info, I am on 2018-06-27, so you recommend go back to aicp_griffin_o-13.1-UNOFFICIAL-20180412 ??

 

[ExtraBasher]

Thanks for the info, I am on 2018-06-27, so you recommend go back to aicp_griffin_o-13.1-UNOFFICIAL-20180412 ??

If you are using a later build and it works fine then stick with it because it already includes all commits previous to it; however, without any new changes, updating with potentially unstable builds would be more trouble than helpful right now.

I definitely do recommend looking at the changelogs for new builds before deciding to updating to weight any possible risks of updating

 

[TobiPeter]

If you are using a later build and it works fine then stick with it because it already includes all commits previous to it; however, without any new changes, updating with potentially unstable builds would be more trouble than helpful right now.

I definitely do recommend looking at the changelogs for new builds before deciding to updating to weight any possible risks of updating

Wait man, I never had just a single problem with any unofficial version of AICP.