[Galaxy Ace II Android Development] ace2nutzer:
Yeah, that's usually the "default".

In the past i was also providing updates without to force format /system and wipe dalvik-cache, but this was causing a lot of problems.

Wait, what u Guys mean with providing ROM updates that contains only the updated files instead a FULL ROM is ONLY possible if u'll ALWAYS flash EVERY update !

The difference for our FULL ROM packages are just simply: u can skip updates, and just flash latest one and everything is fine ... while with the other method u'll have to download all missing updates and then flashing them all in the right order. - OF course i mean with our self-made packages ... but the original OTA updates probably doesn't have such problems.

But again, don't expect too much from us private developers ... we are not SAMSUNG, also we don't work for them.

Later i'll upload the FINAL CM11 FULL package .. and that's it ! - So no need to mess it up at all with the ROM installer :good:

Anyway, Kernel + App updates will still continue :cool:

Wow! that's probably the biggest post in this Thread ! :D

Not a (soft)brick! but bootloop in a worst case. u had probably to try again to boot to recovery ... for me when installing the A2N Kernel for the first time, so coming from stock recovery .. then i also need to try 2 times .. then it shows up ... and honestly i can't understand why ... the strange thing is that'll never happen again ... !

Maybe it's better to update the how-to.

Why? - u can also more easily flash the A2N ODIN kernel. :)

yeah, on that point it's now mess it up. (because of wrong procedure)

Wrong ! - u've to flash first A2N kernel ... then reboot to recovery .....and then u can repartition or do other things.

Yup ! because of missing kernel u didn't flash before.

yeah again useless step ;)

,

Yes, also normal ... u wiped all partitions .. and then later u didn't format them .. so how it should work ?

apart from that, even if u did that, then the stock recovery from samsung wouldn't mount /system .. .because of some difference in the filesystem ... once it was formatted with A2N Kernel.

So just forget to do anything with it.

yeah that's was a good idea. :good:

Yeah, looks like something went wrong ! - But once one step didn't work like expected, so like it's on the How-to, then it's a really bad idea to just skip the step and simply continue the how-to without to know what u're doing!

Anyway, i don't say that the steps i've described on the how-to are the only one working steps for the success !

So Probably there are different ways on how to achieve the same result ... but u'll need some how-know.

So if u aren't a power-user, then don't try to smart out an how-to written by a developer.

Wrong odin version! - For this Phone, the Version 3.07 works best. - Other versions maybe work as well, but they aren't tested and confirmed to work as well!

Yes also normal :)

Not clear what to mean here ...

u've to flash a firmware "as it's", so if it's a normal one ... then do not flash it with an PIT file from any other package !!!

And viceversa never ever flash a 3-parted ROM by just flashing only one file and even without to use his pit- file !!

This is completely wrong and VERY DANGEROUS ! - U can Soft-Brick your Phone ! (later u need a Riff-Box to get it to work!)

yes, that's what i said before ... it can't mount /system ... and it's normal ..

Nope, hard-brick = hardware is broken and u can't boot your system. (this isn't the case)

Soft-Brick = Bootloader is missing or the wrong bootloader is installed !

Therefore u'll need a Riff-Box in order to write proper Bootloader back into the phone ... so that Download-mode works again ! (that was also not the case !)

In Summary: u can't brick your phone by flashing ALL my provided packages ... even NOT if u flash them in the random order all at once! - U'll probably achieve an Bootloop in the worst case ... and that's it !

If want a Soft-Brick, then u need to flash a wrong Stock ROM or to mess it up with the ODIN Settingss .. or to flash pit-files with the inappropriate bootloader !

,

WRONG ! - By default there's almost nothing overclocked ... except the LCD ... ;)

This Kernel is even underclocked ! (but still faster than Stock :D )

(CPU/GPU min. freq is lower than stock)

their max. freq's are like stock.

Yes ... check the how-to .. .there is also a repartition methof for the use with both sdcards ... so like u've it now .... in order to don't waste space. - But of course, the sdcard_only Variant is better.

100% u didn't followed the how-to.

Because if u do exactly what it says, then u never run in troubles.

God damn ! Again ? :D

The Stock & A2N Kernel have the recovery inside the kernel.img (boot.img)

i.e. while in Chrono kernel it's splitted.

So once u flash A2N kernel, it's almost impossible that u don't have a working recovery ....

In the worst case, u'll have a black screen because of low-quality chip from the LCD ...

Anyway, with some how-know u still can manage everything with ADB :)

We are here on a developer forum .... not a standard forum :o

I do suggest to carefully read post #1 + 3.

And then do exactly what i wrote in the steps.

As i said, maybe u'll need to try 2 times to boot to recovery after flashing A2N Kernel.

Yes, u're now tired to flash so many times, without to know if it's actually a right way to do so.

So again, read and read again, till u understand what those steps does.

For the better understanding u can even unpack those packages and check which files are inside, also check the updater-script ... and try to understand. If u have a question, jest ask here in the forum.

We are all here to help.

Of course it works! - But wait for others reports.

Anyway, if now only users reports that it failed too, then it's not useful ... .because the users where is worked, they will probably not post !

It doesn't matter ... but latest is optimal.

Yes, and yes, it works with both kernel variants.

Anyway some apps can't be installed with the default kernel ...

so that's why sdcard_only is recommended.

Thanks! ;)

What's overcloked ?! - or u mean that you did it overclocked ... because i didn't for sure .... there's only ability to do so :)

OMG !! :D So u've for real some bad luck for such things ! :eek: