Problem with latest CM10 nightly.

[Nagrom]

Hi guys.

Just a quick note to warn you all that Chainfire seems to conflict quite baldy with Siyah 5i. Just updated to S5i with no problems. Then I installed Chainfire which I've used in the past with no problems.

Then my phone bricked. I couldn't even boot past the Samsung splash screen.

LuckilyI could boot to recovery, andI still had the CM10 nightly thatI flashed earlier. Flashed that, and disaster averted.

Andy.

 

[ironass]

Hi guys.

Just a quick note to warn you all that Chainfire seems to conflict quite baldy with Siyah 5i. Just updated to S5i with no problems. Then I installed Chainfire which I've used in the past with no problems.

Then my phone bricked. I couldn't even boot past the Samsung splash screen.

LuckilyI could boot to recovery, andI still had the CM10 nightly thatI flashed earlier. Flashed that, and disaster averted.

Andy.

Before anybody panics at the thread title...

This has nothing to do with either the ChainFire kernel or the Siyah 5.0i kernel as such.

It is a problem experienced only by those who have flashed the latest CyanogenMod ROM, CM10, Nightly build, 20121110.

These Nightly builds are experimental and notoriously unreliable and unstable and are flashed at the users own risk.

The problem with this Nightly build was detected yesterday and is well documented in the CM10 thread on xda developers where people were being advised not to flash this latest build or revert back to a previous Nightly build.

Just to clarify, the term, "Bricked", is used for a handset that is completely dead and will not even turn on.

Perhaps the thread title should read... "CM10, Nightly build, 20121110 problem", rather than alarming ChainFire and Siyah users.

I hope that makes things clearer

 

[Nagrom]

Yeah what Ironass said LOL.

My bad.

Has there been a stable CM10 release yet, or is it possible to back date to CM9 without doing a full wipe, like a normal update?

Andy

 

[ironass]

Yeah what Ironass said LOL.

My bad.

Has there been a stable CM10 release yet, or is it possible to back date to CM9 without doing a full wipe, like a normal update?

Andy

I would strongly advise that, if you are flashing CM10 Nightly's, you thoroughly read the CM10 thread on xda developers, that I linked to in my previous post, first as this could save you making the same mistake again. This thread will also alert you to the latest releases.

Can I respectfully suggest that you edit your post by going into Edit and the Advanced and change the title of your thread so as not to alarm all the ChainFire and Siyah kernel users.

 

[ironass]

Just came across this, now, prophetic post by me to Nagrom, yesterday...

Nightly CM releases are experimental... sometimes more mental than experi. They are really for the die hard flashers and sometimes are minor and sometimes major improvements. Other times they can crash your phone... so be warned! Once they have enough mod's up together they do a release or stable version. The choice is yours. :ahhhhh:

 

[Nagrom]

I updated to that nightly release, and everything seemed fine. Still running it now infact, still with no real problems. The problem I encountered only seemed to appear once I flashed, S5i, and Chainfire. So thats whyI posted my original post, and title. You said I Try it at my own risk, so I did.

I appreciate your knowledge Ironass, but there's no need for sarcasm when someone takes your advice, and it goes tits up. If I could delete this thread I would do.

I'm now going to flash back to neat, add much as I love the tweaks of CM, more myther than its worth.........

 

[ironass]

I appreciate your knowledge Ironass, but there's no need for sarcasm when someone takes your advice, and it goes tits up. If I could delete this thread I would do.

I'm sorry to see that you feel that way.

My advice yesterday was that it was risky and experimental and that, "they can crash your phone... so be warned!" and that the "choice was yours". I therefore think that I had warned you what could, and did, happen.

Since the problem with this CM10 Nightly was known prior to your flashing that Nightly, I guess that you had not fully read the developers thread regarding the ROM Nightly or you would have known this and not been surprised by the outcome. I cannot force people to read all about the ROM's that they flash, particularly experimental ones, on their phones... that is their responsibility.

My issue with your original post and thread title was that it indicated that both Siyah and ChainFire kernels were a problem which could, "Brick", peoples phones, a very costly outcome, and would needlessly panic a lot of users of these kernels on other ROM's. The problem, as you now know, is not with the kernels, per se, but rather with their initial utilisation in the CM10 Rom's Nightly build 20121110 which hopefully be rectified on the next release.

 

[Nagrom]

Okay thanks Iron, and no harm done. A misunderstanding, and over reaction on my part.

I apologise if I came across defensive. I assumed the problem was a conflict with CF, and Siyah, as CM10 is running fine.

Thanks again, and I hope we can put the matter to bed now.

Andy