Dirty Unicorn Roms Oreo 8.1

[zelendel]

But their site says I should be able to dirty flash if coming from a previous version.

That doesnt mean it will always work. Mainly with the new setup they started using a month or so back.

Also dirty flashing is never advised nor are bug reports accepted if you do dirty flash. So I would get into the habit of clean flashing every single time.

 

[C-3OP]

Maybe there are problems with the gapps, I have no problems with the gapps from the DU download page. Also no problems with dirty flashs.

 

[zelendel]

Maybe there are problems with the gapps, I have no problems with the gapps from the DU download page. Also no problems with dirty flashs.

He is running an update from January. Before they made the change for user builds. They even told everyone that it would need a clean flash. But then again people want to be lazy so the devs just sit back and laugh when they have issues with a dirty flash.

 

[C-3OP]

OK, i have made clean flashs with the latest BeansGapps at the beginning of march and on 30.3. after the RC build, to the weeklys always dirty flashs, that has always worked ...

 

[rsafford]

He is running an update from January. Before they made the change for user builds. They even told everyone that it would need a clean flash. But then again people want to be lazy so the devs just sit back and laugh when they have issues with a dirty flash.

I was running the March 23 version.

I just tried a clean flash and got the same result.

If your site tells people to dirty flash and you laugh at them, there is something wrong with you.

---------- Post added at 05:42 PM ---------- Previous post was at 05:33 PM ----------

Maybe there are problems with the gapps, I have no problems with the gapps from the DU download page. Also no problems with dirty flashs.

I just tried with no gapps. still can't get past the boot screen.

 

[zelendel]

I was running the March 23 version.

I just tried a clean flash and got the same result.

If your site tells people to dirty flash and you laugh at them, there is something wrong with you.

---------- Post added at 05:42 PM ---------- Previous post was at 05:33 PM ----------



I just tried with no gapps. still can't get past the boot screen.

You are giving it enough time to boot right? Normally about 3 or 4 minutes. Sometimes longer. Maybe a bad download.

From your first post it looked like you said You were on the January build.

 

[rsafford]

You are giving it enough time to boot right? Normally about 3 or 4 minutes. Sometimes longer. Maybe a bad download.

From your first post it looked like you said You were on the January build.

I know how to flash a ROM and boot my phone. The problem is with DU. I have been using the rc and weeklies since January, but the march 30 and April 6 releases just don't go past the spinning boot screen. I don't think its a bad download. They just made a change that my phone doesn't agree with.

 

[zelendel]

I know how to flash a ROM and boot my phone. The problem is with DU. I have been using the rc and weeklies since January, but the march 30 and April 6 releases just don't go past the spinning boot screen. I don't think its a bad download. They just made a change that my phone doesn't agree with.

Well then I will, have to say it's something with your setup. As others have it working as do I and I even build my own every day to test each commit. Maybe the gaps you use. A logcat will tell you just what is going on.

 

[rsafford]

Well then I will, have to say it's something with your setup. As others have it working as do I and I even build my own every day to test each commit. Maybe the gaps you use. A logcat will tell you just what is going on.

I've tried opengapps, eziogapps, and no gapps. I'm not saying that du doesn't work. Just saying that there is a subset that it doesn't work for and I'm one of them

 

[zelendel]

I've tried opengapps, eziogapps, and no gapps. I'm not saying that du doesn't work. Just saying that there is a subset that it doesn't work for and I'm one of them

Which really makes zero sense. No offense intended. There has to be something. Maybe the full, wipe (formatting system and data) is not working properly. Post it to the jira with a logcat. (the log is important as it will be ignored with out it) maybe the devs will be more help. Posting here really doesn't do much as DU has walked away from xda.

 

[laupuy]

All is good here: OP3 (ext4, encrypted, OpenBeta31)
dirty flash from latest weekly (wipe cache, dalvik, system), flash DU 12.1, Ezio gapps, kantjer's magisk 180406 with blu_spark twrp 8.61

Thanks DU :good:

 

[C-3OP]

dirty flash from latest weekly (wipe cache, dalvik, system)

Just to clarify it for me, that (wipe system) is not a dirty flash, right?
Or is it a dirty flash if data is preserved and system is deleted?
I just install the new weekly (and magisk) without wipe and do the wipe dalvik/cache after the installation and restart.

 

[zelendel]

Just to clarify it for me, that (wipe system) is not a dirty flash, right?
Or is it a dirty flash if data is preserved and system is deleted?

The system partition is always deleted when you flash a rom. (at least the real roms and not winzip roms) Not wiping data is what is a dirty flash but devs never advise doing that due to data corruption and other issues.

 

[C-3OP]

The system partition is always deleted when you flash a rom.

okay, thank you, 'something like that' I always thought.

 

[zelendel]

okay, thank you, 'something like that' I always thought.

Yeah if you look at the script as it is running, it formats the system partition. There are talks about making it do data as well by a few teams. To remove that majority of issues users have flashing. This way every rom update is as if the device is out of the box clean.

 

[C-3OP]

On the internet, there are many definitions of dirty and clean flash and some write of "remnants of the old installation", which can make problems. Therefore, I thought that a dirty flash overwrites only the old system, but if it is formatted anyway, with these remainders probably meant the data partition.
But with all theory, dirty flashing works for me anyway. (Never clean, always dirty! )

 

[rsafford]

I ended up decrypting and wiping out everything to start from zero. It boots now, but a couple of apps won't work after Google restored my backup. Namely Textra and Twitter. Any idea what's going on now?

 

[zelendel]

I ended up decrypting and wiping out everything to start from zero. It boots now, but a couple of apps won't work after Google restored my backup. Namely Textra and Twitter. Any idea what's going on now?

You may have to wipe the app data. I have never had any luck with google restoring stuff. It always seems to be corrupted. So I stopped doing it.

 

[rsafford]

You may have to wipe the app data. I have never had any luck with google restoring stuff. It always seems to be corrupted. So I stopped doing it.

Wiped, uninstalled, restarted, reinstalled, still won't work. I started using pulse, but don't love it.

 

[zelendel]

Wiped, uninstalled, restarted, reinstalled, still won't work. I started using pulse, but don't love it.

Grab matlog from the play store and grab a log. This will tell you what is going on.