• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Needed! S2 stuck at any kernal (Dorimanx & Siyah) logos on boot up

A

amoxitine

Newbie
Hi there,

Got a bit of a problem! Been using the Dorimanx kernals with stock Orange 4.0.4 and haven't had any issues until now. I was on Dorimanx 7.43 and things have been fine but tried 4.76 today, which booted and was working fine for a few hours but notice that the Wifi wasn't coming on so rebooted the phone then it got stuck on the kernal logo.

Therefore I booted into recovery, ran GS2KernalWipe, installed Siyah via Odin (which has worked before), fixed permissions, cleared all the caches, but no matter what I do I just can't get the phone to reboot past the logo now.

Does this mean I will need to reflash stock 4.0.4? If so does anyone have a link for the UK Orange version for the i9100P as I can only find 4.0.3 ( which is taking ages to download!)

If anyone could help or offer advice I would be grateful as I'm knackered without my phone lol.

Cheers,

Dave
 
Hi snatylor,

Yeah I've reflashed 7.43 and Siyah as well, but both kernals stick at the logo, so I'm buggered at the mo :(

I guess I'll need to get my mits on stock 4.0.4 or should I try something like Neat? (I have a Titanium backup of everything)
 
naith_kk said:
have you tried flashing other kernels like stock kernels temporarily? it may work...
Click to expand...

Haven't tried any stock kernals yet, just Dorimanx 7.43 and Siyah which have both worked fine before so makes me wonder if something has corrupted with the stock 4.0.4 ROM to prevent it from booting up properly
 
Right so I've gone and installed Neat Lite and I have a working phone and have restored my apps, only one odd thing is that I appeared to have lost about the last 2 weeks worth of SMS messages...does anyone know why that might be as they are stored on the SD card as far as I know?
 
Regarding my missing SMS messages, I've managed to answer that one! It looks like my Titanium backup of the database file MMSSMS.db which holds all of the text messages was last backed up on 23rd Jan and so when I've run a full backup it's plonked that one in and probably overwritten the existing one that was up to date.

Oh well sometimes you gotta learn these things the hard way!
 
You must log in or register to reply here.
Back
Top Bottom