• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM] Dirty Unicorns 14.7 {Bonito} (09/13/20)

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,687
113
New York

About Us:
Dirty Unicorns is an AOSP based project built to enhance the stock Android experience.

Our focus has been and is always to contribute back to the community. That is ultimately why we do what we do.

We DO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. This includes, but is not limited to; Devices, Gerrit, our websites and services, etc.. The only thing that we ask in return is that you have patience, search the thread for answers prior to posting, read diligently, and try to enjoy the process with us!



Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_google_bluecross


Flashing Instructions:
If you have a device that uses TWRP
  • Verify that you're using the latest version of TWRP
  • Perform a FULL WIPE: (A full wipe is when you wipe system/data/cache/dalvik)
  • Flash the latest version of this ROM
  • Reboot and ENJOY!

If you have a device that does not use TWRP
  • Download boot.img and ROM zip from DU server
  • Reboot into bootloader and flash the boot.img

    Code:
    fastboot flash --slot all boot boot.img
  • Reboot to recovery
  • Go to recovery select factory reset
  • Select Apply update from ADB to flash the zip

    Code:
    adb sideload nameofbuild.zip
  • Reboot and ENJOY!

If you're just updating DU on a device without TWRP
  • Download ROM zip from DU server
  • Reboot into recovery and select Apply update from ADB to flash the zip
  • Reboot system now and ENJOY!


**All bugs and feature requests must be reported to JIRA**

**If you use Xposed, please don't bother reporting any bugs**

**If you use another kernel, please don't bother reporting any bugs**

**If you fail to follow these instructions, please don't bother reporting any bugs**



Download Links:

Build(s) - Bonito


Other Links:

ROM Source - https://github.com/DirtyUnicorns

Gerrit - http://gerrit.dirtyunicorns.com

Crowdin (translations) - https://crowdin.net/project/dirtyunicorns

JIRA (Bug Reporting / Feature Requests) - http://jira.dirtyunicorns.com/

Telegram - https://t.me/dirtyunicorns / https://t.me/DirtyUnicornsSupport


XDA:DevDB Information
Dirty Unicorns, ROM for the Google Pixel 3a XL

Contributors
NYCHitman1, jbats
Source Code: https://github.com/DirtyUnicorns

ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP

Version Information
Status: Stable
Current Stable Version: 14.7
Stable Release Date: 2020-09-13

Created 2020-08-08
Last Updated 2020-09-13
 

ahagersr

Senior Member
May 1, 2013
207
68
0
Thank you so much!

I've used nothing but DU since March and I'd like to thank you for your continued work on our device. Hopefully now more people will find and appreciate your efforts!
 
  • Like
Reactions: jbats

41rw4lk

Senior Member
Dec 11, 2010
843
322
63
Springfield, MO
@jbats good to see you round these parts. Just installed DU for the 1st time on bonito; runs good, looks good, and I like the new boot logo and recovery. Any plans to build an in rom updater like lineage or aosip? I've become a fan of seamless updates. Anyways, nice work as usual and thanks for the rom.
 

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,687
113
New York
@jbats good to see you round these parts. Just installed DU for the 1st time on bonito; runs good, looks good, and I like the new boot logo and recovery. Any plans to build an in rom updater like lineage or aosip? I've become a fan of seamless updates. Anyways, nice work as usual and thanks for the rom.
Currently, no. However, we are planning to do this in the future.
 

godpowerrr

Senior Member
Jun 9, 2016
371
280
0
I've installed Bliss and Dirty Unicorns,
Dirty Unicorns is better IMO because of the minimal apps and quickness of multi-tasking.
Only complaint I would have is the lack of customization when it comes to status bar and colors.
Love the ROM and still using it, ty DU team. Please make variations of your boot animation
 
Last edited:

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,687
113
New York
I've installed Bliss and Dirty Unicorns,
Dirty Unicorns is better IMO because of the minimal apps and quickness of multi-tasking.
Only complaint I would have is the lack of customization when it comes to status bar and colors.
Love the ROM and still using it, ty DU team. Please make variations of your boot animation
We're not making anymore variations of the boot animation. We have a light version and a dark version. That's good enough for us.

As for the lack of customization, we include what we find useful. We're never going to be one of these cookie cutter kitchen sink ROM's you see littered across XDA. If you would like to make a particular feature request, check the OP for instructions on how to do so.
 

ssurell

Senior Member
Nov 28, 2013
270
74
0
49
Bowling Green
FYI

Tried flashing boot .img and rom.zip from perminent TWRP (stock Pie), and does not work. I'll update to Q and follow the directions now.:p

Ok? I have no adb device detected from DU recovery. I guess I'll truy TWRP. Nevermind, temporary TWRP doesn't work with June release of Q.
Back to initial Pie factory image, and now will not boot into DU recovery. Temporary TWRP will not flash du_bonito-v14.6-20200808-1220-OFFICIAL and gives an error.
Flashed bootloader-bonito-b4s4-0.2-6355063.img, radio-bonito-g670-00042-200421-b-6414611.img, and 20200808-OFFICIAL-boot.img from fastboot and DU recovery has adb and sideload is working, but get an error at 47%
Code:
C:\Users\Russell\Downloads\Android\ADB and Fastboot>adb sideload du_bonito-v14.6-20200808-1220-OFFICIAL.zip
serving: 'du_bonito-v14.6-20200808-1220-OFFICIAL.zip'  (~47%)    adb: failed to read command: No error
In recovery
Code:
Step 1/3
Error applying update:  7 (ErrorCode::kInstallDeviceOpenError)
E:Error in /sideload/package.zip (status 1)
Maybe a bad download, but I'll probably try v14.5 if I'm going to go through the trouble downloading again.
Honestly, I already pulled the trigger on an LG V20, and just playing with this a bit more before it goes on Swappa. No SD slot, no decent recovery partition, and USB 2.0? No thanks.
 
Last edited:

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,687
113
New York
Tried flashing boot .img and rom.zip from perminent TWRP (stock Pie), and does not work. I'll update to Q and follow the directions now.:p

Ok? I have no adb device detected from DU recovery. I guess I'll truy TWRP. Nevermind, temporary TWRP doesn't work with June release of Q.
Back to initial Pie factory image, and now will not boot into DU recovery. Temporary TWRP will not flash du_bonito-v14.6-20200808-1220-OFFICIAL and gives an error.
Flashed bootloader-bonito-b4s4-0.2-6355063.img, radio-bonito-g670-00042-200421-b-6414611.img, and 20200808-OFFICIAL-boot.img from fastboot and DU recovery has adb and sideload is working, but get an error at 47%
In recovery
Maybe a bad download, but I'll probably try v14.5 if I'm going to go through the trouble downloading again.
Honestly, I already pulled the trigger on an LG V20, and just playing with this a bit more before it goes on Swappa. No SD slot, no decent recovery partition, and USB 2.0? No thanks.
If you're coming from Pie, you need to flash stock to both slots to get your firmware up to date.

TWRP does not work on Q for Pixel 3 and 4.

Please do some research before messing with the device further.
 

ssurell

Senior Member
Nov 28, 2013
270
74
0
49
Bowling Green
If you're coming from Pie, you need to flash stock to both slots to get your firmware up to date.

TWRP does not work on Q for Pixel 3 and 4.

Please do some research before messing with the device further.
I like to try every possible combination of flashing, maybe resize or dd some partitions at sleep deprived 4am, whatever. But I've been using the factory flash-all images, so I assume both slots, else what good are they. Some of the problem may have been with the myriad of adb versions I have littering my system. A photographic memory would be more effective than research redundancy (I forgot thinking temp. TWRP still worked).
Come to think of it, I think I flashed the June OTA going to Q. So that's likely why I didn't have ADB with DU Recovery
 
Last edited:

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,687
113
New York

I like to try every possible combination of flashing, maybe resize or dd some partitions at sleep deprived 4am, whatever. But I've been using the factory flash-all images, so I assume both slots, else what good are they. Some of the problem may have been with the myriad of adb versions I have littering my system. A photographic memory would be more effective than research redundancy (I forgot thinking temp. TWRP still worked).
Come to think of it, I think I flashed the June OTA going to Q. So that's likely why I didn't have ADB with DU Recovery
Unfortunately, it doesn't. The flash-all script only flashes to the active slot on the device, so you would have to manually change slots and run said flash-all script again to be completely up to date. As for the platform-tools versions, I believe 30.0.4 is the latest revision available at this time. Might be a good idea to download that and delete everything else you have.

Outside of this, our flashing instructions are very clearly labeled and should get you through the process of flashing DU as long as you follow the instructions that are applicable to you.
 
  • Like
Reactions: ssurell

champ784

Senior Member
May 31, 2013
419
151
0
Richmond
Great ROM, only issue I have is that whenever I try to change the volume while using my Pixel Buds, the system UI crashes and restarts every time. I've also found that this isn't device specific and happened on other phones I've had with Bliss. Aside from that, great work!
 

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,687
113
New York
Great ROM, only issue I have is that whenever I try to change the volume while using my Pixel Buds, the system UI crashes and restarts every time. I've also found that this isn't device specific and happened on other phones I've had with Bliss. Aside from that, great work!
Could be a larger platform issue. You could provide logs to Google, but seeing as R is literally right around the corner -- they'll likely ignore it until the revision is out to the masses.
 
Last edited:

socksi

Senior Member
Jun 3, 2010
53
27
18
Download from DU site fails

I can't download any file greater than 1GB in size from https://download.dirtyunicorns.com/
It always stops at exactly 1 GB.
Unfortunately the latest DU release for bonito is 1.07 GB in size.
Can you confirm that? Maybe it's my Internet connection. I've tried different browsers and even wget.
Are there any mirrors?
 

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,687
113
New York
I can't download any file greater than 1GB in size from https://download.dirtyunicorns.com/
It always stops at exactly 1 GB.
Unfortunately the latest DU release for bonito is 1.07 GB in size.
Can you confirm that? Maybe it's my Internet connection. I've tried different browsers and even wget.
Are there any mirrors?
Hi @socksi. I have downloaded the file in 12 secs from our server without issue. Unfortunately, we do not use mirrors.

I will reach out to our webmaster and have him look into it. Stay tuned.
 

socksi

Senior Member
Jun 3, 2010
53
27
18
Hi @socksi. I have downloaded the file in 12 secs from our server without issue. Unfortunately, we do not use mirrors.

I will reach out to our webmaster and have him look into it. Stay tuned.
It fails even when using a VPN tunnel. Most probably it's not my Internet connection.
Maybe some kind of GEO blocking? I'm from Germany.