Have not tried to be honest. He probably forked the vendor from DU.
[OFFICIAL]-[10.0_r35]-Havoc-OS - [05.10.20]
- Thread starter slothdabski
- Start date
No issues here but I did end up using the stock kernel from the November updated from Google. Might be worth a shot if you're interested.
I am very happy to find out that this rom has absolutely every additional feature that i have ever asked for. The only thing that bugs me is that i am not seeing how to root after the sideload. Does this process alter the boot. Img somehow or that is the file itself i have to patch with magisk?
Last edited:
you can patch yourself the boot.img with magisk and then fastboot flash it
Is this rom dual SIM support as same in q beta 2 ?
Sent from my Pixel 3 using Tapatalk
Sent from my Pixel 3 using Tapatalk
@slothdabski I found out what was causing the adb errors all the time when trying to flash havoc. Apparently I had an old HTC sync program installed which was conflicting with the latest adb files. They was from my old sensation
eSIM activation bug
Found out today that if "SIM Manager" is updated from Play Store (https://play.google.com/store/apps/details?id=com.google.android.euicc),
user will not be able to activate new eSIM on this ROM.
Reverting app to stock version allows to activate eSIM.
The error itself is quite cryptic (obfuscated):
Found out today that if "SIM Manager" is updated from Play Store (https://play.google.com/store/apps/details?id=com.google.android.euicc),
user will not be able to activate new eSIM on this ROM.
Reverting app to stock version allows to activate eSIM.
The error itself is quite cryptic (obfuscated):
Code:
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: derived ClearcutLogger.MessageProducer
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: java.lang.RuntimeException: Field zzabul for c.b.a.c.j.Wc not found. Known fields are [public int c.b.a.c.j.Wc.h, public long c.b.a.c.j.Wc.i, public int c.b.a.c.j.Wc.j, public c.b.a.c.j.Ea c.b.a.c.j.Wc.k, public c.b.a.c.j.Ea c.b.a.c.j.Wc.l, public byte c.b.a.c.j.Wc.m, public static final c.b.a.c.j.Wc c.b.a.c.j.Wc.f, public static volatile c.b.a.c.j.wa c.b.a.c.j.Wc.g]
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.j.Qb.a(SourceFile:88)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.j.Qb.a(SourceFile:55)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.j.Cb.a(SourceFile:21)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.j.Zb.a(SourceFile:3)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.j.Zb.a(SourceFile:7)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.j.gb.f(SourceFile:2)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.j.gb$c.d(SourceFile:6)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.j.gb$a.e(SourceFile:1)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.b.a$b.a(SourceFile:5)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.b.a.d.a(SourceFile:20)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.c.a.a.c.b(SourceFile:2)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.c.a.a.Da.a(SourceFile:3)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.c.a.a.e$a.c(SourceFile:18)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.c.a.a.e$a.b(SourceFile:15)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.c.a.a.e$a.a(SourceFile:42)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.c.a.a.e.handleMessage(SourceFile:121)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at android.os.Handler.dispatchMessage(Handler.java:103)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at c.b.a.c.j.l.dispatchMessage(SourceFile:1)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at android.os.Looper.loop(Looper.java:214)
11-17 01:41:17.041 19621 19662 E ClearcutLoggerApiImpl: at android.os.HandlerThread.run(HandlerThread.java:67)=============================
Havoc-OS v3.0 Official Update
Android 10
=============================
Date: 11-17-2019
Device: Pixel 3 (blueline)
Device changelog:
Switch to ElementalX kernel
Download Links:
• ROM: https://bit.ly/2OjgHpu
• Boot image for flashing zip: https://bit.ly/33R6GWZ
Switching kernel sources appears to have addressed black screen issue. I haven't had an occurrence on in 48 hours.
Source updates:
Now Playing track info appears on ambient display
Battery style options
Additional status bar icons can be hidden
Dismiss notifications with fingerprint gesture
Sent from my Pixel 3 XL using Tapatalk
Havoc-OS v3.0 Official Update
Android 10
=============================
Date: 11-17-2019
Device: Pixel 3 (blueline)
Device changelog:
Switch to ElementalX kernel
Download Links:
• ROM: https://bit.ly/2OjgHpu
• Boot image for flashing zip: https://bit.ly/33R6GWZ
Switching kernel sources appears to have addressed black screen issue. I haven't had an occurrence on in 48 hours.
Source updates:
Now Playing track info appears on ambient display
Battery style options
Additional status bar icons can be hidden
Dismiss notifications with fingerprint gesture
Sent from my Pixel 3 XL using Tapatalk
Thanks for you guys' hard working, but unfortunately, I just got my pixel 3 today, I found it was really trouble to flash to ROM for me, even though I follow the guide, I keep failing for8 hours, the boot.img could only flash into either slot_a or slot_b, and then I use the volume key to enter the recovery mode, it's always the dead android logo and no command, is there any way that I could enjoy the ROM?
You have to use
fastboot reboot fastboot
When at the bootloader screen first. Then when you are in fastbootd you can arrow down to enter recovery
Sent from my Pixel 3 XL using Tapatalk
alright, lemme try again
---------- Post added at 11:34 PM ---------- Previous post was at 11:25 PM ----------
I seem have no idea what fastbootd mode is, lemme google it, do some homework again, thanks for your patient
It is a userspace fastboot/recovery, mainly needed now that our device uses dynamic partitionsalright, lemme try again
---------- Post added at 11:34 PM ---------- Previous post was at 11:25 PM ----------
I seem have no idea what fastbootd mode is, lemme google it, do some homework again, thanks for your patient
Sent from my Pixel 3 XL using Tapatalk
I can understand the words separately, but definitely have no idea what's going on when it groups into a sentence, basically how could I enable the userspace fastboot/recovery(that's the fastbootd mode right?)? please cosidered my pixel 3 is complete new, everything is the default setting(at the same time my brain as well Orz)
Is there still Pixel stand support? The setup process doesn't pop up like on a stock ROM when you first set it on the stand. I did update the app using the latest on apk mirror. Also thanks for the update
Pixel stand and squeeze arent available for Android ten yet.
Sent from my Pixel 3 XL using Tapatalk
just unlock the bl and then follow instructions to the letter.. that's all.. no need to understand userspace things to get the rom flashed
It is easy once you get the hang of it, just copy and paste each adb command posted in op(just edit the Havoc Build name as it is different for each new build)
okay, unlocked bootloader, but once I've tired to type fastboot reboot fastboot, it said fastboot: usage: unknown reboot target fastboot, is that anything goes wrong?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone