[ROM] Dirty Unicorns 6.0.1 {Flounder} (09/09/16)

Status
Not open for further replies.

uzi2

Senior Member
Jun 6, 2008
2,528
638
113
See my previous post #1236.
Yes, I've read you're post and the edit.
I'm more than happy to test any kernel you produce.
I was only suggesting that a review of commits to the kernel since 0603 is more likely to strike gold than a rebuild from scratch.
And, of course, the superSU script, which alters the kernel.
 
Last edited:

ZeroSkylineX

Senior Member
Sep 8, 2013
139
29
0
Toronto, ON
If you folks don't mind -- http://goo.gl/forms/v73Arer2GrX9uax83

I've discovered that this is an issue of encryption vs decryption.
Thank you, I'm happy that you listened to your fans and did the right thing. If I can make a suggestion for next time, please take your criticisms a bit more lightly. Just because there's something wrong with the boot process, does not always mean it's a user issue. For a while, you neglected to acknowledge it was an issue with the ROM and that it was a user issue because we didn't "read".

I'd understand if it works for you but a vast majority here indicated that it was stuck on a bootloop. Us posting here serves two purposes. It's to inform you, the developer and other users from falling into the same fate. Judging from the posts alone, more users had issues than a successful boot. Also considering it's a categorized as a stable rom, we have higher expectations of less bugs and issues.

Myself personally, I ONLY download and install Stables so I did not expect a Stable rom to boot loop. I'm glad that you finally investigated the matter further after hearing the concerns from various members but I felt that you should've looked into it much earlier instead of neglecting it. It was not looked into until it was already late June/early July, which was on schedule for the 10.4 release. I was originally just going to skip 10.3 as a whole, but I will try it out anyway now that you provided a fix. Other than that man, keep up the good work and I appreciate all that you do. I have DU installed on all my devices and couldn't be happier.
 

uzi2

Senior Member
Jun 6, 2008
2,528
638
113
The issue has been resolved and merged into source upstream.
My experience suggests that there is still an issue with the kernel or superSU script introduced after 0603.
I have attempted to update from 0624(0603 kernel) to 0702 and am unable to boot.
Restoring the boot.img (0603) from my backup solves the problem.

I will try a clean install later...
Clean install will not boot.
Problem not yet solved unless the reversions somehow didn't make it into the 0702 build
 
Last edited:

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,694
263
New York
My experience suggests that there is still an issue with the kernel or superSU script introduced after 0603.
I have attempted to update from 0624(0603 kernel) to 0702 and am unable to boot.
Restoring the boot.img (0603) from my backup solves the problem.

I will try a clean install later...
Clean install will not boot.
Problem not yet solved unless the reversions somehow didn't make it into the 0702 build
The fix didn't make it into the weekly yesterday.
 

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,694
263
New York
Thank you, I'm happy that you listened to your fans and did the right thing. If I can make a suggestion for next time, please take your criticisms a bit more lightly. Just because there's something wrong with the boot process, does not always mean it's a user issue. For a while, you neglected to acknowledge it was an issue with the ROM and that it was a user issue because we didn't "read".

I'd understand if it works for you but a vast majority here indicated that it was stuck on a bootloop. Us posting here serves two purposes. It's to inform you, the developer and other users from falling into the same fate. Judging from the posts alone, more users had issues than a successful boot. Also considering it's a categorized as a stable rom, we have higher expectations of less bugs and issues.

Myself personally, I ONLY download and install Stables so I did not expect a Stable rom to boot loop. I'm glad that you finally investigated the matter further after hearing the concerns from various members but I felt that you should've looked into it much earlier instead of neglecting it. It was not looked into until it was already late June/early July, which was on schedule for the 10.4 release. I was originally just going to skip 10.3 as a whole, but I will try it out anyway now that you provided a fix. Other than that man, keep up the good work and I appreciate all that you do. I have DU installed on all my devices and couldn't be happier.
I do listen, trust me. However, how much can you expect me to do when I'm unable to duplicate your issues? Logs didn't capture anything. It wasn't until I looked at what changed in mr2 source that I realized the issue was only for those who have encrypted devices, which aren't many. A handful, at most.
 

uzi2

Senior Member
Jun 6, 2008
2,528
638
113
I do listen, trust me. However, how much can you expect me to do when I'm unable to duplicate your issues? Logs didn't capture anything. It wasn't until I looked at what changed in mr2 source that I realized the issue was only for those who have encrypted devices, which aren't many. A handful, at most.
My device is encrypted, but I have not actively set it this way. I would expect there are more than a handful who have encrypted devices as it is set by default. Maybe there are only a handful with encrypted devices left using this ROM.
After a full wipe, the ROM will boot as normal.
 
Last edited:

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,694
263
New York
My device is encrypted, but I have not actively set it this way. I would expect there are more than a handful who have encrypted devices as it is set by default. Maybe there are only a handful with encrypted devices left using this ROM.
After a full wipe, the ROM will boot as normal.
Clearly, I was only referring to those using DU. I don't care about those that use other ROM's.
 

PieceKeepr

Senior Member
Jun 13, 2010
1,303
273
0
Florida
So is there an advantage to not being encrypted performance or reliability wise or does it make things easier to work with in general? This is my first Nexus device and since it was encrypted by default I didn't mess with it.

Sent from my Nexus 9 using Tapatalk
 

maelfilk

Senior Member
Nov 17, 2010
830
119
0
Novosibirsk
So is there an advantage to not being encrypted performance or reliability wise or does it make things easier to work with in general? This is my first Nexus device and since it was encrypted by default I didn't mess with it.

Sent from my Nexus 9 using Tapatalk
AFAIK decrypted N9 works slightly faster and as i recall i even get a bit more free space without encryption. Besides, encryption does not 100% make your device safe, i.e. this article: https://thehackernews.com/2016/07/hacking-android-encryption.html
 
  • Like
Reactions: PieceKeepr

PieceKeepr

Senior Member
Jun 13, 2010
1,303
273
0
Florida
So I've been searching and reading about doing away with encryption and I'm seeing various methods from flashing zips to flashing boot images to some saying that TWRP handles it.

What is the current preferred method and is it something that will stick from here on or does it need to be redone say on a clean flash?

Sent from my Nexus 9 using Tapatalk
 

uzi2

Senior Member
Jun 6, 2008
2,528
638
113
So I've been searching and reading about doing away with encryption and I'm seeing various methods from flashing zips to flashing boot images to some saying that TWRP handles it.

What is the current preferred method and is it something that will stick from here on or does it need to be redone say on a clean flash?

Sent from my Nexus 9 using Tapatalk
Back up to USB using TWRP and also back up anything useful you have in internal storage.
Use TWRP to format userdata, then restore data from your backup. Job done.
It is the stock kernel that is responsible for the default encryption, so as long as you don't go back to stock your device will remain unencrypted.
 
Last edited:
  • Like
Reactions: PieceKeepr

Cancertoast

Member
Jan 15, 2013
11
0
0
Does anyone have any idea why TWRP suddenly disappeared? I was having a vendor mismatch after updating to 10.3 (I think that is the latest OFFICIAL release off the top of my head,) so I downloaded the latest Nexus image, removed the vendor.img and flashed. When I rebooted, Android kept crashing and force closing over and over again; so much so I had to just hard power down.. So I went to return to recovery, only to discover that TWRP was no longer installed; it reverted to the factory recovery screen, with the standard reboot options.

Gonna try and full flash, along with cache, system, dalvik, etc. And reapply the latest vendor.img tonight, before I give up and just return to stock.
 
Last edited:

NYCHitman1

Recognized Developer
Apr 9, 2010
5,551
6,694
263
New York
Does anyone have any idea why TWRP suddenly disappeared? I was having a vendor mismatch after updating to 10.3 (I think that is the latest OFFICIAL release off the top of my head,) so I downloaded the latest Nexus image, removed the vendor.img and flashed. When I rebooted, Android kept crashing and force closing over and over again; so much so I had to just hard power down.. So I went to return to recovery, only to discover that TWRP was no longer installed; it reverted to the factory recovery screen, with the standard reboot options.

Gonna try and full flash, along with cache, system, dalvik, etc. And reapply the latest vendor.img tonight, before I give up and just return to stock.
Oh, that's just messed up. However, to answer your question -- I've never seen that happen to anybody before.
 
Status
Not open for further replies.
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