[OFFICIAL]-[10.0_r35]-Havoc-OS - [05.10.20]

[fuzzgruble]

@slothdabski
Posted in the telegram but wasn't sure where to report exactly.
Having an issue with setting up RCS in Google Messages by default. I have to use the known workaround changing the RCS Flags to get it to set up and work. Took a log while it was is the process of "setting up" RCS.

 

[fuzzgruble]

@slothdabski
Posted in the telegram but wasn't sure where to report exactly.
Having an issue with setting up RCS in Google Messages by default. I have to use the known workaround changing the RCS Flags to get it to set up and work. Took a log while it was is the process of "setting up" RCS.

To be clear, I am using blueline with Google Fi and RCS has no issue setting up on stock.

 

[sangiman]

Hi All.

I have Pixel 3(blueline)
To begin with, I flashed the factory image on slot_a and slot_b.
Also tried with, flashed attached boot img on single slot and flashed attached boot img to both slots.
Then, I followed these steps like 10,000 times, but whatever I do I get either 1 of 2 errors.

Error 1: When I flash the attached boot.img(attached screenshot has the files i'm using) it reboots to a dead android screen with "No command" written on it. I try holding VolUp+power buttons to boot into recovery lands on to the same screen. When i enter fastboot mode and try to boot recovery from selecting options, it throws an error reason: " error booting boot.img"

Error 2: When I try to flash older ROM(attached screenshot has the files i'm using here) it shows a timestamp and cannot be downgraded error. I flashed an older version of factory image+old version of ROM+old version of boot img.
Nothing worked. I also changed the metadata to avoid the timestamp error but then fastboot could not verify the integrity of the file.

Also the below command does not work :

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot

Please help, I'm tired of flashing over and over again with no luck with any of the versions.

Thanks in advance !!

To get to the recovery when you're on the dead Android screen it's: hold the power button and one click on the volume up button.

 

[[email protected]]

Hi. I'm interested in installing this rom. I've been using the bootleggers rom for the past year and a half or so.

Everyone seems to be pretty happy with this rum. But I had a question about the instructions. 8n the OP, it mentions next to flash boot image- "this allows stock recovery to flash unsigned rom zip since we dont have TWRP".
What does it mean we don't have TWRP? I do....how would we be flashing without TWRP? Thanks for any help

 

[fuzzgruble]

Hi. I'm interested in installing this rom. I've been using the bootleggers rom for the past year and a half or so.

Everyone seems to be pretty happy with this rum. But I had a question about the instructions. 8n the OP, it mentions next to flash boot image- "this allows stock recovery to flash unsigned rom zip since we dont have TWRP".
What does it mean we don't have TWRP? I do....how would we be flashing without TWRP? Thanks for any help

TWRP doesn't exist for Android 10 on our device. Stock recovery is located in the boot.img. So this is a modified boot.img that allows the recovery to update ROM over ADB

 

[[email protected]]

TWRP doesn't exist for Android 10 on our device. Stock recovery is located in the boot.img. So this is a modified boot.img that allows the recovery to update ROM over ADB

Wow. I knew nothing about this. So how are we flashing zips?

 

[fuzzgruble]

Wow. I knew nothing about this. So how are we flashing zips?

Depends on what zip you're talking about. But assuming things like kernel zips, they need to have anykernel scripts built in to them, which if it is being offered as a zip then it should. Those you can flash in EXKM or FKM when you already have root access. Gaining root access with Magisk is a matter of putting a boot image (right now the options are stock or Despair's kernel) on your internal storage, installing the Magisk manager, patching said boot image, then transferring the patched image to your PC, then flashing said boot image via Fastboot.

We might be getting a bit OT here though.

 

[slothdabski]

=============================

Havoc-OS v3.0 Official Update

Android 10

=============================

Date: 11-23-2019

Device: Pixel 3 (blueline)

Device changelog:

Merge Linux 4.9.202

Screen attention

Live caption

Smart charging

Download Links:

• ROM: https://bit.ly/2s4RSWD

• Boot image for flashing zip: https://bit.ly/37zuEZa

Installation Notes: https://bit.ly/2Na6PyW

Havoc-OS v3.0 Changelog 11-23-19:

• Added Gaming mode

• Added Custom Logo in statusbar

• Added Custom Carrier Label

• Added Statusbar Clock customizations

• Added Quick Settings Pulldown options

• Added Suppress notifications sound/vibration if screen is On

• Added Unlink ring and notification volumes

• Added Tap volume buttons to answer call

• Fixed "Clear All" recent app screen loop bug

• Fixed Double tap to wake on ambient display

• Fixed Power menu layout on low DPI

• Other fixes and improvements



Sent from my Pixel 3 XL using Tapatalk

 

[danteissaias]

Some overlays which are in Havoc such as `FontRubikRubikOverlay` use fonts that aren't included in the system. https://android.googlesource.com/platform/external/google-fonts/ - these are the fonts that are missing.

 

[Xdevillived666]

Damn. I still get FC using android auto and black screen then freeze then reboot. I tried pulling logs but wasn't able to . Thought it may have been a cable issue so I switched cables which allowed me to get to navigate screen but when tapping bottom left menu button to open apps, it froze again. I wont bother about it anymore but can someone else try to use auto in their car and let me know if you succeed?

 

[danteissaias]

Latest build appears to be a QD... build. This means there is capability for the new Google assistant to be ported, it also appears that Live Caption is enabled for the latest build.

 

[slothdabski]

If anyone experiences the black screen issue again, it seems to be back after merging the latest Linux stable into kernel source. I will be reverting it back to previous state.

Until a new build is released you can just flash the boot image from prior to the merge (or patch with magisk and then flash)

https://sourceforge.net/projects/havoc-os/files/blueline/boot_20191117.img/download

Sent from my Pixel 3 XL using Tapatalk

 

[Xdevillived666]

If anyone experiences the black screen issue again, it seems to be back after merging the latest Linux stable into kernel source. I will be reverting it back to previous state.

Until a new build is released you can just flash the boot image from prior to the merge (or patch with magisk and then flash)

https://sourceforge.net/projects/havoc-os/files/blueline/boot_20191117.img/download

Thanks for the info ,sir. Which build date's boot image would that be? The 9th or the 12th?


Edit:I'm an idiot. Didn't see you out the link to said date,haha. Sheesh.

 

[slothdabski]

Thanks for the info ,sir. Which build date's boot image would that be? The 9th or the 12th?


Edit:I'm an idiot. Didn't see you out the link to said date,haha. Sheesh.

17th

Sent from my Pixel 3 XL using Tapatalk

 

[glehel]

Interestingly, I never had a black screen. i have tried almost all kernels, i am currently using despair v9 kernel and it is very stable.
I have had this problem with PIE HAVOC-OS and kirisakura kernel in the past. something he did not like dtbo.img because it was modified, it only worked fine with factory dtbo.img. Check the one with black screen error that the factory dtbo.img is on this partition !! If another kernel flashed before, it can overwrite the dtbo partition.

 

[spddl]

it is possible to use the bubbles/chat-heads?

 

[Xdevillived666]

17th

Hi sir. Used boot.img from 17th but still issues with Android auto freezing whole phone and forcing a reboot. I will try an earlier boot.img to see if that resolves things.


Just to verify, if I flash an earlier boot.img I only need to flash it and am not required to wipe user data, correct?

Also: cannot log while running Android auto for the above reason. Namely, whole phone becomes unresponsive.

 

[slothdabski]

Hi sir. Used boot.img from 17th but still issues with Android auto freezing whole phone and forcing a reboot. I will try an earlier boot.img to see if that resolves things.


Just to verify, if I flash an earlier boot.img I only need to flash it and am not required to wipe user data, correct?

Also: cannot log while running Android auto for the above reason. Namely, whole phone becomes unresponsive.

No one said it would fix your Android auto issue. I already said I don't have Android auto and can't test or pull logs. You haven't submitted logs either.

The black screen issue is a separate problem where you go to use the phone and it doesn't wake up. Afaik no one using the boot image from the 17th has been experiencing it

Sent from my Pixel 3 XL using Tapatalk

 

[Xdevillived666]

No one said it would fix your Android auto issue. I already said I don't have Android auto and can't test or pull logs. You haven't submitted logs either.

The black screen issue is a separate problem where you go to use the phone and it doesn't wake up. Afaik no one using the boot image from the 17th has been experiencing it

Sent from my Pixel 3 XL using Tapatalk

Yeah, I understand and I worded it incorrectly. When I open android auto while plugged, I get the black screen and unresponsive phone. I try to pull logs but the phone is unresponsive and reboots. Sorry about the confusing message. I didn't mean to imply that I thought reverting to a different boot.img would fix it. Apologies

 

[Slomies]

11/23 build running great! Thanks @slothdabski I did update the kernel to ElementalX 2.08 though and no black screen.

Sent from my Pixel 3 using Tapatalk